Austin’s technology sector includes a growing number of companies building software for healthcare — clinical workflow tools, patient engagement platforms, analytics, AI products and infrastructure for digital health. Most of them hit HIPAA the same way: a first healthcare customer asks them to sign a business associate agreement, followed by a long security questionnaire.
This page focuses on that moment. Texas-specific law — including the broader Texas definition of covered entity and its training rules — is covered on our Texas HIPAA consulting page, and applies to Austin companies in the same way.
Key points
- Signing a BAA makes you directly liable for Security Rule compliance and certain Privacy Rule obligations.
- Enterprise customers will ask for evidence — a risk analysis, policies, training records — not just a statement.
- SOC 2 and penetration tests help win deals but are not HIPAA requirements under the current rule.
- Texas law can treat your company as a covered entity in its own right; see the Texas page.
How we work with Austin companies
Engagements are remote by default, which suits distributed engineering teams. On-site working sessions can be arranged when a team prefers it. We work with founders, engineering leads and whoever has been handed "compliance" — often a COO or head of security wearing several hats.
Are you becoming a business associate?
If your product creates, receives, maintains or transmits PHI on behalf of a covered entity (or another business associate), you are a business associate. That status comes from what you do, not from whether a contract has been signed. Once you are one, you are directly liable for complying with the Security Rule, for breach notification to your customer, and for certain Privacy Rule obligations, including only using and disclosing PHI as your BAA permits.
Signing a BAA under §164.504(e) and §164.314 is a commitment to have a real program in place. Before signing, founders should understand what they are agreeing to — including breach notice timing (often shorter than HIPAA’s 60-day outer limit for business associates), subcontractor flow-down and termination rights. Our business associate compliance service covers this in depth.
What enterprise security reviews actually ask for
Hospital and health plan security teams have seen many vendors claim to be "HIPAA compliant". They will usually ask for evidence. Being ready with these documents shortens deal cycles more than any marketing language.
| Request | HIPAA basis | Notes |
|---|---|---|
| Risk analysis | Required, §164.308(a)(1)(ii)(A) | Must cover your actual environment, including cloud and SaaS tools |
| Risk management plan | Required, §164.308(a)(1)(ii)(B) | Shows you are acting on findings |
| Security policies | Required, §164.316 | Must match how you really operate |
| Workforce training records | Required, §164.308(a)(5) | Texas law adds state-specific training — see the Texas page |
| Subcontractor BAAs | Required, §164.308(b), §164.314 | Cloud hosting, support tools, email, analytics |
| SOC 2 report | Not a HIPAA requirement | Common customer ask; separate attestation |
| Penetration test | Not an explicit HIPAA requirement | Good practice; supports technical evaluation |
| MFA, encryption, logging | Encryption is addressable; MFA is good practice under the current rule | Customers often treat these as mandatory |
A practical path for an early-stage company
- 1
Map PHI in your architecture
Trace PHI through your application, databases, logs, backups, support tools and analytics. Logs and error trackers are where PHI most often leaks unexpectedly.
- 2
Lock down vendors
Get BAAs from every subcontractor that touches PHI, and move PHI out of tools that will not sign one. A cloud provider’s BAA does not make your application compliant — responsibility is shared.
- 3
Complete a real risk analysis
Document threats, vulnerabilities, likelihood and impact for your environment. A HIPAA risk assessment designed for SaaS is the backbone of your evidence pack.
- 4
Write policies you actually follow
Keep them short, specific and aligned with engineering practice. Retain them for six years under §164.316.
- 5
Build a reusable security review package
Prepare answers to the common questionnaires, a security overview and a summary of your risk management status.
Common Austin health-tech pitfalls
Most of the problems we see in young health-tech companies are not exotic attacks. They come from moving fast with production data and from sales promises that run ahead of the program behind them.
- Using production PHI in staging or developer laptops without equivalent safeguards.
- Shipping AI or analytics features that send PHI to third-party APIs without a BAA in place.
- Assuming de-identification without meeting the Safe Harbor or Expert Determination standards in §164.514.
- Claiming HIPAA certification or full compliance in sales materials — no official HIPAA certification exists, and such claims can create legal exposure.
- Forgetting that Texas law may treat the company as a covered entity with its own training and disclosure duties.
Frequently asked questions
We use a HIPAA-eligible cloud service. Are we compliant?
No, not by that alone. The provider’s BAA covers its infrastructure responsibilities. You remain responsible for your application, access controls, configuration, logging, policies and workforce.
Do we need SOC 2 to sell to hospitals?
HIPAA does not require SOC 2, but many enterprise customers ask for it. A HIPAA risk analysis and SOC 2 overlap considerably, so planning them together saves effort.
Does Texas law add anything for an Austin SaaS company?
Potentially. Texas Chapter 181 defines covered entity broadly and adds training and disclosure duties. Our Texas page summarizes these; confirm applicability with counsel.
How long does it take to get ready for a security review?
It depends on your current state, architecture and the number of vendors involved. A short scoping conversation is usually enough to estimate effort — see our consulting cost resource for the factors that drive it.
Authoritative sources
- HHS — Business associates
- HHS — Guidance on HIPAA and cloud computing
- HHS — Sample business associate agreement provisions
- HHS — Preemption of state law (HIPAA FAQs)
This page is general information, not legal advice. Regulations and guidance change; confirm current requirements with the official sources above and, where needed, qualified legal counsel.