If your app creates, receives, stores or transmits protected health information (PHI) on behalf of a covered entity, HIPAA applies. Building the right safeguards in from the start is far cheaper than retrofitting them.
Are you covered?
Healthcare providers, health plans and clearinghouses are covered entities; companies handling PHI on their behalf are business associates. Consumer wellness apps that don't work with covered entities may fall outside HIPAA but still face FTC and state privacy rules.
Technical safeguards
- Encryption in transit and at rest.
- Unique user identification and strong authentication.
- Role-based access with minimum necessary access.
- Audit logs of access to PHI.
- Automatic session timeouts and secure backups.
Business associate agreements
Use cloud, email, analytics and communication services that will sign a BAA, and sign BAAs with development partners who access PHI.
Common mistakes
PHI in push notifications, logs or analytics events; using consumer tools that don't sign BAAs; and giving developers access to real patient data in test environments.
Technical safeguards are only part of compliance; policies, risk assessments and training are also required.
Frequently asked questions
Is there a HIPAA certification?
No official certification exists; compliance is demonstrated through safeguards, policies, risk assessments and agreements.
Can offshore developers work on HIPAA apps?
Yes, under BAAs and strict controls, ideally without access to real PHI in development.
Which clouds sign BAAs?
Major providers including AWS, Azure and Google Cloud offer BAAs for eligible services.
Ready to put this into practice for your business?
Book a Free Consultation