The HIPAA consulting market ranges from deeply experienced practitioners to firms selling templates with a certificate attached. Because there is no licensing for HIPAA consultants and no official certification of HIPAA compliance, the burden of evaluation falls on the buyer.
This guide is written for practice managers, compliance officers, CTOs and founders making that decision. It applies to any firm you evaluate — including ours.
Key points
- Define the problem and scope before requesting proposals.
- Look for healthcare-specific experience matched to your environment.
- Be wary of anyone offering to certify you or guarantee compliance.
- Ask for a redacted sample deliverable — it tells you more than a sales deck.
Start with your own scope
Before talking to consultants, write down what you need. Proposals are only comparable when they answer the same question. Useful scoping inputs include:
- Your role — covered entity, business associate or both.
- Size: number of locations, workforce members and in-scope systems.
- Environment: on-premises, cloud, hybrid; EHR and major applications.
- Trigger: first program build, customer requirement, breach, OCR inquiry, acquisition.
- Desired outputs: risk analysis, gap analysis, policies, training, remediation support, ongoing help.
Evaluation criteria
| Criterion | What good looks like |
|---|---|
| Healthcare and HIPAA depth | Can explain the difference between required and addressable specifications, risk analysis versus gap analysis, and BA obligations without notes |
| Relevant environment | Experience with organizations like yours — a hospital, a dental group and a SaaS vendor have very different risks |
| Technical capability | Can assess cloud configuration, identity, logging and applications, not just policies |
| Methodology | Names a recognized approach (for example NIST SP 800-66 Rev. 2 / SP 800-30 concepts) and explains how it is applied |
| Deliverable quality | Risk-rated findings tied to evidence, with practical remediation steps |
| Honesty about limits | Clearly says what is out of scope, and works alongside your legal counsel on legal questions |
| Independence | Discloses prior work that could affect objectivity |
Questions to ask in the first conversation
- 1
How will you scope our risk analysis?
Listen for an inventory-led approach that covers all ePHI — including vendors, mobile devices, backups and shadow IT.
- 2
Can we see a redacted sample deliverable?
A real sample shows whether you will get a risk register you can manage from or a generic narrative.
- 3
Who will actually do the work?
Ask about the individuals assigned, their relevant experience, and whether any work is subcontracted.
- 4
How do you handle technical testing?
Understand what is tested directly, what relies on interviews, and whether vulnerability scanning or penetration testing is included or separate.
- 5
What happens after the report?
Clarify whether remediation support, policy drafting and follow-up review are included, optional or out of scope.
- 6
Will you sign a BAA?
If the consultant will access PHI during the engagement, they are a business associate and should sign one.
Red flags
- Offers to make you "HIPAA certified" or issues a compliance certificate or seal. HHS does not certify organizations, and no private certificate has official standing.
- Guarantees compliance, a passing result, or protection from OCR penalties. No consultant can guarantee compliance.
- Describes its review as "OCR-approved" or implies government affiliation.
- Proposes a fixed package without asking about your environment.
- Treats a questionnaire or the HHS SRA Tool output as a complete risk analysis with no validation.
- Cannot explain the difference between required and addressable specifications.
- Provides legal opinions without involving counsel, when the firm is not a law firm.
- Is unwilling to sign a BAA despite needing PHI access.
Comparing proposals side by side
Once proposals arrive, normalize them before comparing price. Two quotes for a "HIPAA risk assessment" can describe very different amounts of work — our guide to HIPAA consulting cost explains the main drivers. Lay them out against the same questions:
- Which locations, systems, vendors and environments are in scope — and which are explicitly excluded?
- How is evidence gathered: interviews only, document review, configuration review, technical testing?
- Is the output a risk-rated register, a gap list, or a narrative report?
- How many review cycles on drafts are included, and is there a final readout to leadership?
- Are policy drafting, remediation support and follow-up validation included or priced separately?
- What does the firm need from your team, and how much staff time should you plan for?
Checking references
Ask for references from organizations similar to yours in size and type, and ask them specific questions: Was the scope delivered as proposed? Were findings accurate and actionable? Did the deliverable hold up when a customer, auditor or regulator looked at it? How responsive was the team after the report was delivered? Be aware that many healthcare clients cannot be named publicly; a firm declining to disclose client names is not a red flag, but it should be able to arrange confidential reference calls.
Structuring the engagement
A phased approach reduces risk for both sides: begin with a HIPAA gap analysis or HIPAA security risk assessment, then decide on remediation support based on what is found. Make sure the statement of work defines scope, deliverables, timeline, assumptions, your team's responsibilities, PHI handling and data return at the end.
If you are deciding between advisory help and independent testing, read HIPAA compliance consultant vs. auditor first.
After you hire
Assign an internal owner who can get answers and access quickly; engagements stall when the consultant waits weeks for documents. Treat the deliverable as the start of your risk management work, not the end. And keep ownership: the consultant advises, but your organization remains responsible for its HIPAA program.
Frequently asked questions
Do HIPAA consultants need a certification?
There is no government license or official certification for HIPAA consultants. Professional credentials in privacy, security or audit can indicate relevant knowledge, but experience and deliverable quality matter more.
Can a consultant guarantee we are HIPAA compliant?
No. A consultant can assess, advise and help remediate, but compliance depends on how your organization operates every day and is never guaranteed.
Should our HIPAA consultant sign a BAA?
If they will create, receive, maintain or transmit PHI on your behalf during the engagement, yes. Many engagements can be designed to minimize PHI access.
Is the cheapest proposal a bad sign?
Not necessarily, but compare scope carefully. Low-priced offers sometimes exclude technical testing, remediation guidance or validation of the risk analysis.
Is a law firm or a consulting firm better?
They do different things. Law firms provide legal advice and privilege; consulting firms typically handle risk analysis, technical and operational work. Many organizations use both, with the consultant working alongside counsel.
Authoritative sources
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.