HIPAA-compliant software development: how we handle patient data

Healthcare software has to pass a security review before it ships. These are the steps Onix Health takes on every project that touches protected health information, and the certifications we do not hold.

What every project gets

1

A BAA before any patient data

We sign a Business Associate Agreement before anyone on the team sees PHI.

2

Per-clinician access

Each clinician sees only their own patients, from the first release.

3

A penetration test before launch

Software that holds patient data is tested before it launches.

4

AI that cites its sources

Assistants answer with links to the record they read, on Claude via AWS Bedrock or Anthropic directly.

What makes an app HIPAA compliant?

An app is HIPAA compliant when the way it is built and run meets the HIPAA Privacy Rule, on who may use and share patient data, and the HIPAA Security Rule, on how electronic patient data is protected. On our projects that means a signed BAA before anyone on the team sees PHI, access set per clinician so each one sees only their own patients, and a penetration test before launch.

What does a BAA cover in a software build?

A Business Associate Agreement is the contract HIPAA requires before a provider or health plan lets a vendor, such as a development team, handle its protected health information. It limits what the vendor may do with the data, requires safeguards and breach reporting, and says what happens to the data when the contract ends. We sign one before anyone on the team sees PHI. The cloud host signs its own BAA, covered in our guide to HIPAA-compliant hosting on AWS.

How is security tested before launch?

Software we build that holds patient data passes a penetration test before it launches. The findings give your HIPAA risk analysis real vulnerability data to work with. The Security Rule requires that analysis of every covered entity and business associate, and our guide to your first HIPAA risk analysis walks through it. For a product that already exists, our free five-day technical audit ends with a written report of what works and what to fix.

Medical device software

We build software as a medical device under an IEC 62304 process: requirements, risk analysis and verification records are written as the software is built, so the documentation an FDA submission needs is ready when you submit. The submission and the clearance stay with you.

Questions security and compliance teams ask

1

Will Onix Health sign a BAA?

Yes. Every healthcare engagement is covered by a Business Associate Agreement before anyone on the team sees protected health information.

2

Which rules do you build to?

The HIPAA Privacy and Security Rules for patient data, and an IEC 62304 process for medical device software, with the software documentation an FDA submission needs.

3

Do you test security before launch?

Yes. Software that holds patient data passes a penetration test before it launches.

4

How do you keep clinicians out of records they should not see?

Access is set per clinician, so each one sees only their own patients; it is built into the first release.

5

Where does patient data go when you use AI?

Our assistants run on Claude via AWS Bedrock or Anthropic directly, under a BAA, and every answer links the record it came from; the provider can be switched.

6

Do you hold SOC 2 or ISO 27001 certification?

No. We work under your BAA and your security review, and we answer your security questionnaire with what we do in practice.