HIPAA · Questions answered
HIPAA Questions Answered
Straight answers to the questions healthcare organizations and their technology vendors ask about protecting health information and meeting HIPAA, from InfoGuard’s senior cybersecurity practitioners.
Where we work. InfoGuard serves healthcare providers, health plans, and health technology companies across California from offices in Silicon Valley and Irvine, including San Jose and Silicon Valley, San Francisco and the Bay Area, Los Angeles, Orange County and Irvine, and San Diego. We also support clients throughout the United States.
Section A
HIPAA basics
1. What is HIPAA, and how do we know whether our organization needs to comply?
The Health Insurance Portability and Accountability Act (HIPAA) sets national rules for protecting health information. It applies to covered entities, such as healthcare providers, health plans, and clearinghouses, and to business associates that create, receive, store, or transmit protected health information (PHI) on their behalf, including many SaaS, cloud, and IT vendors. If you handle PHI for any of them, HIPAA applies to you.
2. What counts as protected health information (PHI)?
PHI is individually identifiable health information, such as diagnoses, treatment, test results, or payment details, linked to identifiers like a name, date of birth, address, email, or medical record number. Electronic PHI (ePHI) is PHI stored or sent electronically, and it is what the Security Rule protects. Properly de-identified data is not PHI, so knowing exactly where PHI lives is the first step in controlling scope.
3. Is there an official HIPAA certification?
No. HHS does not certify organizations or endorse any HIPAA certification. Compliance is enforced by the HHS Office for Civil Rights (OCR). What matters is a documented program: a current risk analysis, implemented safeguards, policies, training, and business associate agreements. Many healthcare customers also ask for independent proof, such as a SOC 2 report or HITRUST certification.
4. What are the Privacy Rule, Security Rule, and Breach Notification Rule?
The Privacy Rule governs how PHI is used and shared and gives patients rights to their information. The Security Rule requires administrative, physical, and technical safeguards for ePHI, starting with a risk analysis. The Breach Notification Rule requires notifying individuals, HHS, and sometimes the media when unsecured PHI is breached. Business associates are directly liable under the Security Rule and parts of the others.
5. What is the proposed HIPAA Security Rule update, and should we wait for it?
In January 2025, HHS proposed the first major Security Rule overhaul in two decades. It would make most safeguards required, including encryption, multi-factor authentication, an asset inventory and network map, regular vulnerability scans and penetration tests, and restoring critical systems within 72 hours. As of October 2026 it is not final. Don’t wait: the current rule is enforced now, and these practices already reduce breach risk.
6. Do we need both HIPAA compliance and SOC 2?
Often, yes. HIPAA is the legal requirement, while many hospitals and health plans also ask vendors for a SOC 2 report or HITRUST certification as independent proof before signing a business associate agreement. We map the frameworks together so one set of controls and evidence serves both, which speeds healthcare sales.
Section B
Working with InfoGuard
7. Where does InfoGuard provide HIPAA services in California?
InfoGuard provides HIPAA risk analysis, remediation, and ongoing compliance support across California from offices in Silicon Valley and Irvine. We work with healthcare organizations and health technology companies in San Jose and Silicon Valley, San Francisco and the Bay Area, Los Angeles, Orange County, and San Diego. Most work is done remotely, with on-site sessions for clinics and facilities when needed, and we support clients throughout the United States.
8. Do you work with small practices and midsize healthcare organizations?
Yes. Small and midsize practices face the same rules as large health systems with far fewer resources, and that is where we help most. We scope the work to your locations, systems, and vendors, so you protect patient data and meet HIPAA without building a program you can’t sustain.
9. Which healthcare organizations do you work with?
In more than 15 years of compliance work, InfoGuard has served clients across industries. For HIPAA, we work with medical practices and multi-site clinics, healthcare providers, health technology and SaaS companies, and IT and service vendors acting as business associates. Because we approach HIPAA as cybersecurity practitioners, safeguards protect PHI without slowing down care or product delivery.
10. Do we need a designated security official, and can you fill that role?
Yes, HIPAA requires you to designate a security official responsible for your security program, and a privacy official for covered entities. Many smaller organizations don’t have a qualified person in-house. InfoGuard can serve as your virtual security officer, leading the program, keeping the risk analysis current, and supporting your team, while your organization keeps final accountability.
11. What makes InfoGuard's approach different, and will we work directly with senior practitioners?
InfoGuard has protected healthcare organizations for years, including a multi-location healthcare provider we have supported for more than 15 years, with secure networks and practical HIPAA programs. We produce a risk analysis that follows HHS guidance and turn it into a prioritized plan. Senior practitioners do the hands-on work, and the safeguards they build protect patients, not just paperwork.
12. What qualifications and experience should we look for in a HIPAA provider?
Start with the firm itself: choose a cybersecurity company, where cybersecurity is the core function, not a compliance-only shop. A HIPAA program built on real security expertise holds up under scrutiny and protects patient data from ransomware and breaches. Then look for practitioners with recognized credentials such as CISSP, CISA, and CISM, healthcare experience, and hands-on depth in network, cloud, and endpoint security. Ask who will do the work and how they perform the risk analysis. InfoGuard is a cybersecurity firm first, and its engagements are led by senior practitioners holding these credentials.
13. Can you help if we don't have a security team, or work alongside our IT provider or MSP?
Yes to both. If you have no security team, we act as your security function, performing the risk analysis, writing policies, and guiding implementation. If you have an IT provider, MSP, or internal team, we work alongside them, assigning clear roles, responsibilities, and accountability. Your MSP is likely a business associate too, so we also confirm its agreement and safeguards.
Section C
Cost, timeline and proposal
14. How much does HIPAA compliance cost, what affects the price, and what is included in your fee?
There is no flat fee. Cost depends on the number of locations, systems, devices, and vendors that handle PHI, and how much remediation is needed. After an initial assessment, we provide a firm quote that lists exactly what is included: PHI mapping, the security risk analysis, remediation support, policies and procedures, business associate review, workforce training, and a readiness review, so there are no surprise charges.
15. How long does it take to become HIPAA compliant?
A security risk analysis typically takes a few weeks, depending on your size and locations. Remediation then follows a prioritized plan over the following months, fixing the highest risks first. HIPAA compliance is ongoing rather than a finish line, so we focus on reaching a defensible program quickly and keeping it current.
16. How much staff time should we budget?
Plan for one internal owner, usually a practice manager, compliance lead, or IT lead, spending a few hours a week, with heavier weeks during the risk analysis and remediation. Clinical and administrative staff contribute in short interviews and training. Because InfoGuard does much of the hands-on work, your team stays focused on patients and customers.
17. What should we prepare before requesting a proposal, and what should we look for when reviewing one?
Before requesting a proposal, gather your locations and headcount, the systems that hold PHI, such as EHR, billing, email, and cloud services, your IT provider and key vendors, any existing risk analysis or policies, and any customer or audit deadline. When reviewing proposals, check who does the work, whether the risk analysis follows HHS guidance, and whether remediation and business associate review are included.
18. How are responsibilities split between our team and your consultants?
Your organization owns compliance, operates the safeguards, and designates the security and privacy officials. InfoGuard maps PHI, performs the risk analysis, writes policies, guides remediation, reviews business associates, and trains staff. We define these roles, responsibilities, and accountability in writing at kickoff, so every task has an owner and OCR would see clear accountability.
19. Who owns the risk analysis, policies, and documents created during the engagement?
You do. Your risk analysis, policies, procedures, and evidence belong to your organization, so you can keep using and updating them after the engagement ends. HIPAA requires you to keep this documentation for six years, so ownership matters if your team, vendors, or IT provider change.
Section D
Readiness and preparation
20. How do we know whether we're compliant, and can you assess our gaps first?
You’re on solid ground when you have a current risk analysis, safeguards that address the risks it found, written policies that staff follow, completed training, signed business associate agreements, and evidence for each. The surest way to know is a gap assessment and readiness review that mirrors what OCR asks for in an investigation, so gaps are found and fixed before an incident or complaint exposes them.
21. What deliverables should we expect?
Expect a map of where PHI lives and flows, a documented security risk analysis with risk ratings, a prioritized risk management plan, tailored policies and procedures, a business associate inventory and agreement review, workforce training materials and records, and a readiness review result. Together they form the documentation OCR expects and a program your team can keep running.
22. What is a HIPAA security risk analysis, and how often do we need one?
A security risk analysis is an accurate and thorough assessment of threats and vulnerabilities to the confidentiality, integrity, and availability of your ePHI, with each risk rated by likelihood and impact. It is the foundation of the Security Rule, and a missing or outdated one is among OCR’s most common findings. Review it at least annually and whenever systems, locations, or vendors change significantly.
23. Do you help implement safeguards and write policies tailored to our organization?
Yes. We don’t stop at documentation. InfoGuard helps implement the administrative, physical, and technical safeguards your risks call for, including multi-factor authentication, encryption, access controls, audit logging, backups, endpoint protection, and incident response. We write policies that describe how your organization actually operates, because policies nobody follows offer no protection in an investigation.
24. What documentation and evidence do we need?
Keep your risk analysis and risk management plan, policies and procedures, security official designations, training records, business associate agreements, access reviews, audit log reviews, incident and breach records, and contingency plan tests. HIPAA requires you to retain documentation for six years. We give you an evidence plan that says what to keep, where, and by whom.
25. What is a business associate agreement, and who needs one?
A business associate agreement (BAA) is a contract requiring a vendor that handles PHI to safeguard it, report breaches, and pass the same obligations to its subcontractors. Covered entities need BAAs with business associates, and business associates need them with their subcontractors, such as cloud hosts, IT providers, and SaaS tools that touch PHI. We inventory your vendors, review agreements, and assess the riskiest ones.
26. Do you work with compliance platforms such as Vanta and Drata?
Yes. InfoGuard is an official Vanta and Drata partner. These platforms track HIPAA safeguards and automate some evidence, but the risk analysis, PHI mapping, policy writing, business associate review, and remediation still need an experienced practitioner. We work alongside your platform so you get the most from it.
27. How should we handle AI tools that process PHI?
Treat AI tools like any vendor that handles PHI: include them in your risk analysis, sign a BAA before sending PHI, confirm how data is stored, used, and whether it trains models, and control which staff can use them. Many general-purpose AI tools are not covered by a BAA, so staff need clear rules. We assess AI use in your environment and set practical guardrails.
28. Can HIPAA be coordinated with SOC 2, ISO 27001, or HITRUST to reduce duplicate work?
Yes. HIPAA safeguards overlap heavily with SOC 2, ISO 27001, and HITRUST. We map your controls once across the frameworks you need and reuse the same policies, risk analysis, and evidence, so healthcare customers’ security reviews draw on one program instead of several.
29. How do you assess cloud services such as AWS, Azure, Google Cloud, and Microsoft 365?
We confirm each cloud provider will sign a BAA and that you use only its HIPAA-eligible services for PHI. Then we assess the controls you configure, such as access, multi-factor authentication, encryption, logging, and backups, because the provider secures its infrastructure while you remain responsible for how you use it.
30. How do you assess vendors and business associates?
We inventory every vendor that creates, receives, stores, or transmits PHI, confirm a BAA is in place, classify vendors by risk, and review the security of the riskiest ones through questionnaires, reports, and certifications. Vendor breaches are a leading cause of healthcare data exposure, so oversight matters beyond paperwork.
Section E
Investigations and breaches
31. What triggers an OCR investigation, and what will they ask for?
OCR investigations usually follow a reported breach or a complaint, and OCR also runs compliance audits. Investigators typically ask first for your risk analysis, risk management plan, policies, training records, business associate agreements, and evidence of the safeguards you claim. A readiness review that mirrors these requests is the best preparation, and we can support you through an investigation.
32. What are HIPAA's breach notification requirements?
For breaches of unsecured PHI, notify affected individuals without unreasonable delay and no later than 60 days after discovery. Notify HHS as well: within 60 days for breaches affecting 500 or more people, and annually for smaller ones. Breaches affecting more than 500 residents of a state or jurisdiction also require notifying prominent media. Business associates must notify the covered entity. State laws may add stricter rules.
33. How do we decide whether a security incident is a reportable breach?
An impermissible use or disclosure of PHI is presumed to be a breach unless a documented risk assessment shows a low probability that the PHI was compromised, considering the type of data, who received it, whether it was actually viewed, and how well the risk was mitigated. Encrypted data meeting HHS guidance is generally not “unsecured.” We help you assess incidents quickly and document the decision.
34. Is a ransomware attack a HIPAA breach?
Usually, yes. HHS guidance treats encryption of ePHI by ransomware as a breach unless you can document a low probability that the PHI was compromised. Healthcare is a top ransomware target, so tested backups, multi-factor authentication, patching, and monitoring matter as much as policy. If an attack happens, follow your incident plan and assess notification obligations immediately.
35. What are the penalties for HIPAA violations?
OCR can impose civil penalties in tiers based on culpability, from violations the organization didn’t know about to willful neglect left uncorrected, with annual caps per type of violation that exceed $2 million after inflation adjustments. Many cases end in settlements with corrective action plans and years of OCR monitoring. State attorneys general can also enforce HIPAA, and criminal penalties apply to knowing misuse.
36. What commonly delays HIPAA compliance, and how do we avoid it?
The most common delays are not knowing where PHI lives, a risk analysis that never gets finished or updated, missing business associate agreements, and remediation that stalls without an owner. Avoid them by naming a security official, mapping PHI early, and working the highest risks first instead of trying to fix everything at once.
37. How do you track progress and keep leadership informed?
We work from a shared plan with owners and target dates for every task, and send regular status updates covering progress, open risks, remediation status, and decisions needed. Leadership sees where the program stands and what is needed from them, without having to manage the details.
38. How do we protect PHI when sharing evidence with consultants?
Share only what each requirement needs, and avoid sending PHI at all where possible. Use screen sharing or de-identified samples, and encrypted, access-controlled channels instead of email attachments. When we need access to PHI, we sign a BAA first. InfoGuard is a cybersecurity firm and handles client evidence under strict confidentiality and need-to-know access.
39. How do California privacy laws relate to HIPAA?
California adds its own rules on top of HIPAA, including the Confidentiality of Medical Information Act (CMIA), state breach notification requirements, and privacy laws covering health data that HIPAA doesn’t reach. Organizations operating in California often need to meet both. We help you identify where state requirements are stricter and build them into one program; for legal interpretation, involve your counsel.
Section F
Ongoing compliance
40. How do we maintain HIPAA compliance, and what ongoing support do you offer?
Keep your risk analysis current, run safeguards consistently, review access and audit logs, train staff, test backups and your contingency plan, and manage business associates. InfoGuard offers ongoing support, including risk analysis updates, monitoring, policy updates, vendor reviews, training, and incident support, and can serve as your virtual security officer, so your program doesn’t drift.
41. How do we show healthcare customers and partners that we're compliant?
Since there is no HIPAA certificate, show your program: a summary of your risk analysis and safeguards, your policies, your willingness to sign a BAA, and independent proof such as a SOC 2 report, HITRUST certification, or a third-party assessment. We help you answer hospital and health plan security questionnaires accurately, so BAAs get signed faster.
42. How do new locations, systems, or vendors affect our compliance?
New clinics, EHR or cloud systems, mergers, or vendors that handle PHI change your risks and must be reflected in your risk analysis, safeguards, and business associate agreements. Bring them to us before you go live, and we’ll assess the impact and update your program, so changes don’t open gaps an attacker or investigator would find.
43. Can HIPAA compliance also strengthen our cybersecurity and reduce risk?
It should. Healthcare is a top ransomware target, and a real HIPAA program tightens access, encryption, monitoring, backups, and incident response against the attacks that take systems down and expose patients. InfoGuard approaches HIPAA as cybersecurity practitioners: compliance should validate good security, not substitute for it, so your investment protects patients, operations, and revenue.
44. How do we describe our HIPAA compliance accurately?
Avoid saying you are “HIPAA certified,” because no official certification exists. Say instead that you maintain a HIPAA compliance program, will sign a BAA, and, if true, hold independent attestations such as SOC 2 or HITRUST. Overstated claims damage trust with sophisticated healthcare buyers. We help you word website, sales, and contract statements that are accurate and hold up to scrutiny.
Also see: HIPAA Control Requirements · HIPAA Compliance services
Next step
Tell us where you stand
Tell us what you’re trying to accomplish. We’ll reply with clear next steps.
