The moment your software creates, receives, maintains, or transmits protected health information on behalf of a covered entity, you are a business associate, and most of HIPAA's Security Rule applies to you directly, with direct enforcement exposure to match. Since the HITECH Act, OCR does not need to go through your customer to reach you. Health-tech companies frequently misjudge this boundary in both directions: some assume a signed BAA is the compliance program, while others burn effort on HIPAA when their data flows never actually trigger it. Getting the applicability analysis right is step one, because everything else is scoped by it.
For a software company, the practical work of HIPAA readiness looks different from a hospital's. Your risk analysis centers on the product architecture: where PHI flows, which services and stores touch it, how tenants are isolated, what your subprocessors see. Your safeguards live in infrastructure-as-code, IAM policy, and encryption defaults rather than facility badges. And your BAA obligations run in two directions: upstream commitments to customers that your sales team wants signed quickly, and downstream agreements with every cloud and SaaS vendor in the PHI path. Readiness means making all three layers consistent.
RiskSensai content is informational only. It is not an audit opinion, assurance, or legal or accounting advice.