Home / Services / Security & Compliance / HIPAA Compliance
HIPAA COMPLIANCE CONSULTING
HIPAA compliance for health tech, built into how you work.
Risk analysis, Security Rule safeguards, policies, BAAs and breach readiness for healthcare providers and the software companies that serve them.
Free 30-minute call · Written proposal in 48 hours · NDA before we talk
HIPAA IN SHORT
What is HIPAA compliance?
HIPAA compliance means protecting patients' health information (PHI) the way US federal rules require. Covered entities and their business associates must run a documented risk analysis, apply administrative, physical and technical safeguards, sign business associate agreements and report breaches. There is no official HIPAA certification; you prove compliance with evidence.
WHO MUST COMPLY
Health tech & SaaS
Telehealth platforms
Clinics & hospitals
Health insurers
Billing & claims vendors
Cloud & IT providers to healthcare
Key facts
ENFORCED BY
The US Department of Health and Human Services, Office for Civil Rights (OCR).
KEY RULES
Privacy Rule, Security Rule and Breach Notification Rule.
APPLIES TO
Covered entities and their business associates, including software vendors handling PHI.
BREACH NOTICE
Affected individuals without unreasonable delay, and no later than 60 days after discovery.
CERTIFICATION
None official. Many vendors add SOC 2 or HITRUST to prove it to buyers.
THE SECURITY RULE
The three HIPAA safeguards, in plain English
The Security Rule protects electronic PHI (ePHI). It is flexible on how, but strict on proving you thought it through and wrote it down.
ADMINISTRATIVE
Administrative safeguards
Risk analysis and management, a named security official, workforce training, access management, contingency planning and vendor oversight.
Starts with: a written security risk analysis
PHYSICAL
Physical safeguards
Facility access, workstation use and security, and device and media controls, including how laptops and drives are disposed of.
Applies to: offices, data centers and remote work
TECHNICAL
Technical safeguards
Unique user IDs, access control, audit logs, integrity controls, encryption and secure transmission of ePHI.
Expect: MFA, encryption and audit logs
COVERED ENTITY VS BUSINESS ASSOCIATE
Covered entity or business associate: which are you?
Most health tech companies are business associates. You still carry direct liability under the Security Rule.
Covered entity
Business associate
Who it is
Providers, health plans and clearinghouses
Vendors that create, receive, store or send PHI for a covered entity
Examples
Clinics, hospitals, insurers
EHR and telehealth platforms, billing, cloud and IT providers
Must sign a BAA?
Yes, with every business associate
Yes, with the covered entity and with your own subcontractors
Breach duties
Notify individuals, HHS and sometimes the media
Notify the covered entity, which then notifies others
OUR ADVICE
Selling software to US healthcare? Assume you are a business associate. Get your risk analysis, policies and BAA template ready before the first enterprise hospital deal, not during it.
DELIVERY TIMELINE
How HIPAA compliance works
Most health tech teams reach a defensible HIPAA program in 2 to 4 months, then keep it current with yearly reviews.
01
Scope PHI
Map where PHI is created, stored and sent, and which vendors touch it. Typical: 1–2 weeks.
02
Risk analysis
A written security risk analysis across all ePHI systems. Typical: 2–3 weeks.
03
Safeguards
Administrative, physical and technical safeguards implemented. Typical: 4–8 weeks.
04
Policies & BAAs
Policies, procedures and BAAs with customers and subcontractors. Typical: 2–3 weeks.
05
Train & test
Workforce training and a tabletop breach-response exercise. Typical: 1–2 weeks.
06
Evidence & review
Evidence organized for audits, and a yearly review cycle set up.
DELIVERY TIMELINE
Typical total: 2–4 months to a defensible program
01
Scope PHI
1–2 weeks
02
Risk analysis
2–3 weeks
03
Safeguards
4–8 weeks
04
Policies & BAAs
2–3 weeks
05
Train & test
1–2 weeks
06
Evidence & review
Ongoing
THROUGHOUT THE PROJECT
You always know where you stand
Weekly status updates
Progress, owners and dates
One accountable lead
A single point of contact, start to finish
Customer questionnaires
We help you answer hospital security reviews
WHAT'S INCLUDED
Everything you need to prove HIPAA compliance
Built for health tech companies that sell to hospitals, clinics and payers.
✓
PHI data mapping
Where PHI lives, how it flows and who can access it.
✓
Security risk analysis
The written risk analysis OCR asks for first, with a treatment plan.
✓
Policies & procedures
A complete HIPAA policy set, written for how your team works.
✓
Technical safeguards
MFA, encryption at rest and in transit, audit logging and access reviews.
✓
BAA management
A BAA template, plus review of your vendors' and subcontractors' agreements.
✓
Workforce training
Short, role-based HIPAA training with completion records.
✓
Breach response plan
Clear roles, timelines and a tested notification playbook.
✓
Audit-ready evidence
Everything organized for customer reviews, OCR inquiries or a SOC 2 or HITRUST audit.
You own every policy, risk analysis and piece of evidence. No lock-in, ever.
EXPERT INSIGHTS
What most HIPAA guides won't tell you
Lessons from health tech teams that sell to hospitals.
01
There is no "HIPAA certified".
No government body certifies HIPAA compliance. Claims of HIPAA certification are marketing; buyers want evidence, a risk analysis and often a SOC 2 or HITRUST report.
02
The risk analysis is the first thing OCR asks for.
A missing or outdated security risk analysis is one of the most common findings in enforcement actions. Keep it current.
03
"Addressable" does not mean optional.
Addressable safeguards must be implemented or replaced with a documented, reasonable alternative.
04
Your cloud provider signs a BAA, not your compliance.
AWS, Azure and Google Cloud offer BAAs, but only for eligible services you configure correctly. The rest is on you.
05
Logs are part of your defense.
Audit logs that show who viewed which record are both a safeguard and your evidence when something goes wrong.
06
Combine HIPAA with SOC 2.
Hospitals increasingly ask for SOC 2 too. One control set covers most of both.
TOOLS & FRAMEWORK MAPPING
HIPAA-ready on the platforms you use
We configure HIPAA-eligible services correctly and connect evidence to your compliance platform.
CLOUD (BAA AVAILABLE)
AWS
Microsoft Azure
Google Cloud
COMPLIANCE PLATFORMS
Vanta
Drata
Secureframe
IDENTITY & ACCESS
Okta
Microsoft Entra ID
Google Workspace
LOGGING & MONITORING
AWS CloudTrail
Datadog
Microsoft Sentinel
DATA PROTECTION
AWS KMS
Azure Key Vault
Cloud DLP
ONE CONTROL SET, MAPPED TO
SOC 2
HITRUST CSF
ISO 27001
NIST CSF
GDPR
PROOF
Use cases for Penetration Testing
Real problems, the services we combined, and the results.
All use cases →
HEALTHCARE
AI scribe
HIPAA
AI virtual care for multi-site clinic groups
THE CHALLENGE
Stretched clinicians and patient data spread across systems.
OUR APPROACH
A patient app, ambient AI scribe and predictive operations on FHIR, built HIPAA-ready.
WHAT SUCCESS LOOKS LIKE
Less after-hours documentation, fewer missed appointments and one view of each patient.
3
apps: patients, clinicians, clinic operations
Read the story →
1 / 3
RELATED INDUSTRIES
Built for your industry
HIPAA Compliance adapted to the rules, systems and customers of your industry.
All industries →
BLOG & RESOURCES
Insights on security, compliance and privacy
Practical guides for founders and technology leaders. No jargon.
View all resources →
HEALTH & AI
HIPAA and generative AI: using LLMs with patient data safely
BAAs, minimum necessary data and the guardrails that protect PHI.
Akash Soni, Founder & CEO · 9 min read
HEALTH & AI
AI scribes for clinics: accuracy, consent and EHR integration
How to pilot an ambient scribe and measure time saved.
Akash Soni, Founder & CEO · 8 min read
INTEGRATION
FHIR integration guide: what FHIR APIs can and can't do
SMART on FHIR, US Core and how to plan an EHR integration.
Akash Soni, Founder & CEO · 8 min read
FAQ
HIPAA questions, answered
Straight answers for health tech teams. If yours isn't here, ask us directly.
Still unsure? Talk to a security expert. 30 minutes, no pitch.
Book a free consultation
Is there an official HIPAA certification?
No. The US Department of Health and Human Services does not certify HIPAA compliance, and there is no official HIPAA certificate. Companies show compliance through a documented security risk analysis, safeguards, policies, training and signed business associate agreements, and often add a third-party assessment, SOC 2 or HITRUST.
Does HIPAA apply to my software company?
HIPAA applies if you create, receive, store or transmit protected health information (PHI) for a covered entity, such as a hospital, clinic or health plan. That makes you a business associate. Most healthtech, telehealth, EHR-integrated and medical billing software companies selling to US providers fall under HIPAA.
What is a business associate agreement (BAA)?
A business associate agreement (BAA) is a contract required by HIPAA between a covered entity and a vendor that handles protected health information. It sets out how PHI is protected, used and reported if breached. You need BAAs with customers and with your own vendors, such as cloud and AI providers.
What is a HIPAA security risk analysis?
A HIPAA security risk analysis is a required, documented review of where electronic protected health information lives, the threats to it and how well your safeguards protect it. It is the foundation of HIPAA compliance, and missing or outdated risk analyses are among the most common findings in HHS enforcement.
Is AWS, Azure or Google Cloud HIPAA compliant?
AWS, Microsoft Azure and Google Cloud offer HIPAA-eligible services and will sign a BAA, but the cloud itself does not make you compliant. Under the shared responsibility model you must configure encryption, access control, logging and backups correctly. We set this up and document it for audits.
How long does HIPAA compliance take?
Most software companies reach a solid HIPAA compliance baseline in 6 to 12 weeks. That covers the security risk analysis, administrative, physical and technical safeguards, policies, workforce training and BAAs. Ongoing compliance then needs annual risk reviews, monitoring and regular training.
What are the HIPAA breach notification deadlines?
Affected individuals must be notified without unreasonable delay and no later than 60 days after a breach is discovered. Breaches affecting 500 or more people must also be reported to HHS within 60 days, and to the media in affected states. Smaller breaches are reported to HHS annually.
What is the difference between HIPAA and HITRUST?
HIPAA is a US law that sets requirements for protecting health information. HITRUST is a private, certifiable framework that combines HIPAA, NIST, ISO and other controls into one assessment. Large health systems and payers often ask vendors for HITRUST because it gives independent, certified assurance.
RELATED SERVICES
SOC 2 Compliance & Audit Readiness →
The report hospitals increasingly ask for
Penetration Testing (VAPT) →
Test the apps that handle PHI
Cloud & Application Security →
Configure HIPAA-eligible cloud services correctly
Backup & Disaster Recovery →
Keep patient data available after an incident
Find out where you stand on HIPAA, in one free call.
Book a free 30-minute call. You'll leave with your PHI risk hot spots and clear next steps, whether or not we work together.
Your PHI risk hot spots
Clear next steps
NDA before we talk