Compliance · 2026-05-01 · 8 min read
Your EHR Partner Is HIPAA Compliant. Your Product Probably Isn't Ready.
Many health-tech teams assume their EHR integration partner and their cloud provider's BAA handle HIPAA. They don't. Those cover one of three layers, and the layers they miss are exactly what hospital security reviews and OCR look at.
You Integrate With a HIPAA-Compliant EHR. You're Covered, Right?
Here's a conversation that plays out at a lot of health-tech startups:
"Are we HIPAA compliant?" "We integrate with [EHR] and we run on a cloud provider that signed a BAA with us." "Great. We're good then."
It's an understandable assumption. The EHR vendor talks about HIPAA constantly. Your cloud provider has a HIPAA page and a BAA you clicked through. But here's what nobody told you: the EHR's HIPAA program covers their platform, and your cloud provider's BAA covers their services under a shared-responsibility model. Neither covers your product, your team, or your paperwork.
If you create, receive, maintain, or transmit PHI for a hospital, clinic, or health plan, you are a business associate. Since the 2013 Omnibus Rule, business associates have been directly liable for Security Rule compliance. There are three layers to that, and your partners handle exactly one of them.
The Three Layers of HIPAA for a Business Associate
Layer 1: Platform compliance. This is what your EHR partner and your cloud provider handle. Their infrastructure is encrypted, their services follow access-control rules, and they have been audited. This is real compliance work, but it is their compliance. Your cloud provider's BAA typically covers a list of eligible services, and configuring them correctly is still your job.
Layer 2: Documentation compliance. This is the layer most early-stage teams are missing. It means a formal, documented Security Rule risk analysis that covers your product. Written policies and procedures. A designated Security Official on paper. Training records for everyone with access to PHI. A BAA with every subcontractor that handles PHI. An incident response and breach notification procedure that meets the deadlines in your customers' BAAs.
Your EHR partner generates none of this. Your cloud provider doesn't know whether you've done any of it.
Layer 3: Human judgment. This layer requires someone on your team to apply the rules to your product. Your cloud provider doesn't know that your application logs capture full request bodies. It doesn't know that support engineers paste screenshots of patient records into the help desk. It doesn't know that a new AI feature sends transcripts to a model provider with no BAA. These are your problems to find and fix.
When a hospital's security team reviews you, or OCR opens an investigation, they are not auditing your EHR partner or your cloud host. They are looking at layers 2 and 3. The platform layer is assumed.
What Your BAAs Actually Say
You probably have two kinds of BAA in play.
The BAAs your customers ask you to sign. In these you are the business associate. They typically require you to safeguard their PHI, report security incidents and breaches to them, flow the same obligations down to your subcontractors, and return or destroy PHI when the contract ends. Each one is a promise about your own program.
The BAA your cloud provider signs with you. Here the cloud provider is your subcontractor. Read which services it covers and what it says about your responsibilities. It protects the data on their side of the line. Everything on your side of the line is still yours.
Neither one is a compliance certificate. The misconception that a signed BAA transfers responsibility is common, and it is exactly what a security reviewer probes.
The Enforcement Reality: Fines With No Breach in Sight
You don't need a data breach to get fined. Many enforcement actions are triggered by documentation failures, the layer your partners have nothing to do with.
Comprehensive Neurology, a five-person practice in New York, paid $25,000 under a resolution agreement signed in February 2025, the eighth action in OCR's Risk Analysis Initiative. OCR's investigation started from a 2020 ransomware breach, but the violation it cited was the practice's failure to conduct an accurate and thorough risk analysis — a documentation gap, not the breach itself.
OCR's Risk Analysis Initiative, launched in October 2024, has produced a run of enforcement actions like that one. And OCR's 2020 report on its 2016–2017 audit program found that most audited covered entities failed to implement the risk analysis and risk management requirements effectively.
Most of those cases involved providers. If you sell software to providers, those are your customers, and it is why hospitals and clinics ask their vendors for the same evidence in security reviews and BAAs. A business associate can also be investigated directly.
The Gaps Hiding in Your Company Right Now
You don't need an audit to know where the likely problems are. Here's the short version of what reviewers find at early-stage health-tech companies:
No documented risk analysis. HIPAA requires a formal, written analysis of where ePHI lives in your systems and what the risks are. It has to cover production, backups, logs, analytics, and support tools, not just the database on the architecture diagram.
Missing subcontractor BAAs. Every vendor that touches PHI on your behalf needs a signed BAA: your cloud host, error tracking, logging, email, SMS, the help desk, and any AI model provider. Each missing one is silent liability.
No training records. A kickoff talk is not documentation. You need records of who was trained, on what, and when.
Shared or unreviewed production access. If engineers share credentials or access production without an audit trail, you cannot show who accessed which records, or when.
PHI where it shouldn't be. Request bodies in application logs, patient screenshots in support tickets, exports in personal cloud folders. Each sits outside the safeguards you describe to customers.
No designated Security Official. HIPAA requires a documented designation, not an informal understanding that the CTO "handles compliance."
No breach notification procedure. A business associate must notify the covered entity of a breach of unsecured PHI without unreasonable delay and no later than 60 days after discovery, and many customer BAAs set shorter deadlines. If you don't know which deadlines you've agreed to, you can't meet them.
Every item on this list is a documentation gap. None of them require a breach to become a finding.
Where Shieldra Fits In
We're not going to oversell this. Some HIPAA decisions genuinely require judgment specific to your company, such as how to negotiate a customer's BAA or how to respond to a particular incident. For those, you may still need counsel.
What we handle is the documentation layer, the one that stalls most security reviews.
Shieldra gives you HIPAA policy templates, basic compliance training, an evidence vault, a HIPAA roadmap and a trust center on every plan. The Premium plan adds the Security Rule risk analysis with Security Officer sign-off, vendor BAA tracking with expiry dates, security awareness training with completion records, and a questionnaire workspace with a reusable answer library. When a hospital asks "show us your risk analysis," you have one. When they ask "who completed HIPAA training and when," you have a log. And it runs your HIPAA program without PHI entering the platform.
The Short Version
Your EHR partner is HIPAA compliant, and your cloud provider signed a BAA. That covers their platforms.
You still need:
- A written, dated risk analysis that covers your product
- Documented policies and procedures
- Training records showing who was trained, on what, and when
- A BAA with every subcontractor that handles PHI
- A formally designated Security Official
- A breach notification procedure that meets your customers' BAA deadlines
- A record of where PHI flows in your product, including logs and support tools
If you can't point to an actual document for each of those, you have gaps. They might stay hidden until the next hospital security review, and then they can stall the deal.
It's a fixable problem.
Take Shieldra's free HIPAA readiness check and see where your documentation gaps are before a security reviewer finds them for you.