HIPAA Compliance for Direct Primary Care Membership Practices
Does HIPAA apply to a cash-pay or membership-based DPC practice?
A cash-pay or membership model does not, by itself, exempt a direct primary care (DPC) practice from HIPAA. For a health care provider, HIPAA generally applies when the provider transmits health information electronically in connection with a transaction for which HHS has adopted a standard. A provider may transmit the transaction itself or use a billing service or another agent to do it on its behalf. HHS’s Summary of the HIPAA Privacy Rule explains that using electronic technology alone—such as email—does not make a provider a covered entity.
Consider what the practice actually does, not just how it describes its business. If it collects membership fees directly from patients and does not conduct HIPAA-standard electronic transactions, it may not qualify as a HIPAA covered entity as a health care provider. But submitting electronic claims, checking insurance eligibility, or requesting referrals or prior authorization using adopted transaction standards can change the analysis. A third-party billing service conducting a standard transaction for the practice counts too. HHS’s overview of adopted transaction standards lists examples such as claims, eligibility inquiries, and referral authorization.
Do not confuse routine electronic communications or credit-card membership payments with HIPAA-standard electronic transactions. The key question is whether the practice transmits information in connection with a transaction for which HHS has adopted a standard. If the practice is a covered entity, HIPAA obligations apply even when it contracts out billing or other operations.
Which state privacy and medical-record laws may apply?
HIPAA is a federal privacy baseline, not a replacement for state law. Depending on where you practice and the services you provide, state requirements may address medical-record access and retention, confidentiality, breach reporting, telehealth, or particular patient groups or types of information. HIPAA generally does not set medical-record retention periods; HHS notes that state law usually governs how long records must be retained. HHS’s medical-record retention guidance explains this distinction.
When a state privacy law is more protective or gives patients greater rights than HIPAA, it may apply alongside HIPAA or, in certain circumstances, take precedence over a conflicting HIPAA requirement. HHS guidance on more stringent state laws explains the general rule. Identify the states where you provide care, employ staff, or hold records, then confirm which laws apply to your practice and update your workflows and notices accordingly.
Keep record-retention duties separate from HIPAA’s documentation rule. HIPAA requires covered entities to retain specified compliance documentation for six years, but that is not a universal six-year medical-record retention period. Check the applicable state rules and seek jurisdiction-specific legal advice where needed.
How to assess and manage risks to electronic protected health information
If HIPAA applies, the Security Rule requires an accurate and thorough HIPAA Security Rule risk assessment of potential risks and vulnerabilities to the confidentiality, integrity, and availability of electronic protected health information (ePHI). Use the assessment to identify where ePHI resides, who can access it, how it moves through the practice, and what could expose it, alter it, destroy it, or make it unavailable. HHS’s risk analysis guidance describes the required scope and the role of risk management.
Document identified risks, their likelihood and potential impact, existing safeguards, and the steps you will take to address gaps. Prioritize the work: assign an owner and timeline for each corrective action, then record what you changed and whether the change reduced the risk. The Security Rule allows safeguards to be scaled to the organization, but a small practice still needs to protect all ePHI it creates, receives, maintains, or transmits. HHS’s Security Rule summary explains the rule’s flexible, technology-neutral approach.
HIPAA does not prescribe one universal schedule for repeating a full risk analysis. HHS says the process should be ongoing, with the frequency shaped by the practice’s circumstances. Reassess when meaningful changes—such as a new EHR, vendor, location, workflow, or security incident—may affect risk, and periodically review the overall security program. HHS’s guidance on risk analysis clarifies that the Security Rule does not set a specific risk-analysis frequency.
What written policies, workforce training, and incident procedures are required?
A covered practice must adopt and document reasonable and appropriate policies and procedures to comply with the Security Rule. Assign responsibility to a security official, define workforce access to ePHI, and establish safeguards for workstations, devices, facilities, and electronic systems. Review and update the documentation when relevant environmental or organizational changes occur; HIPAA-required compliance documentation generally must be retained for six years.
Provide workforce training on the security policies and procedures relevant to their work, document that training, and provide additional training within a reasonable period when a material policy change affects their duties. HIPAA does not make an annual certificate renewal a universal federal requirement. A certificate may show that someone completed a course; it does not establish that the organization is HIPAA-compliant. Staff must also receive any practice-specific training needed to follow your own procedures. HHS’s audit protocol describes workforce training and documentation expectations.
Written security incident response procedures should tell staff how to recognize and report suspected incidents, who investigates them, how the practice will limit harm, and how it will document the incident and outcome. Include practical steps for events such as a lost device, misdirected message, compromised password, ransomware, or unauthorized record access. Assess any impermissible use or disclosure separately under the Breach Notification Rule; not every security incident is automatically a reportable breach. HHS’s security incident guidance explains the response, mitigation, and documentation requirements.
Ready to simplify HIPAA compliance?
Join thousands of organizations that trust Accountable to manage their compliance needs.
Get Started Free TodayWhen must a DPC practice provide a Notice of Privacy Practices?
A DPC practice that is a covered health care provider with a direct treatment relationship must provide its Notice of Privacy Practices acknowledgment process no later than the first service delivery, except that an emergency permits providing the notice as soon as reasonably practicable afterward. The practice must make a good-faith effort to obtain the patient’s written acknowledgment of receipt. If the patient does not provide one, document the effort and the reason it was not obtained. HHS’s Notice of Privacy Practices guidance describes these provider requirements.
The acknowledgment records receipt; it is not the patient’s consent to uses or disclosures otherwise permitted by HIPAA. A provider generally does not need a new acknowledgment every year or whenever it changes its notice. It must make a revised notice available as required, and if it has a physical service location, keep the notice available there and post it prominently. HHS’s acknowledgment FAQ confirms that a new acknowledgment is not required merely because the notice changes.
Which vendors require business associate agreements?
A vendor generally needs a written business associate agreement (BAA) if it performs a function or service for the covered practice that involves creating, receiving, maintaining, or transmitting PHI on the practice’s behalf. Common examples may include an EHR or cloud-hosting provider, billing or claims service, medical transcription service, or outside IT provider with access to PHI. A cloud provider that stores ePHI may be a business associate even if it cannot view encrypted data. HHS’s cloud-computing guidance explains the BAA requirement for cloud services handling ePHI.
Evaluate each vendor’s actual role and access rather than relying on a generic “HIPAA compliant” label. The agreement should define permitted uses and disclosures, require appropriate safeguards, and address reporting and return or destruction of PHI when the relationship ends. A vendor’s claim of certification does not replace the practice’s own obligations or the required agreement.
Some limited exceptions apply. For example, a courier acting only as a conduit for PHI generally does not require a BAA, and a financial institution performing ordinary payment-processing services may fall outside the business-associate definition. Confirm that the vendor’s role truly fits an exception before relying on it. HHS’s Business Associates FAQs discusses these distinctions.
How to identify and safeguard ePHI across systems and devices
Start with an inventory and data-flow map. Look beyond the EHR: ePHI may appear in scheduling and patient portals, email and messaging, telehealth platforms, e-prescribing tools, lab interfaces, billing systems, cloud storage, backups, phones, tablets, laptops, removable media, printers, and paper-to-digital workflows. Track where information is created, received, maintained, and transmitted; who can access it; and which vendors handle it.
Use the risk assessment to select reasonable safeguards for those systems and devices. Depending on the risks and the practice’s circumstances, measures may include role-based access, unique user accounts, multifactor authentication, secure configurations, encryption, audit-log review, automatic screen locking, controlled device use, protected backups, and secure disposal. The Security Rule requires reasonable and appropriate administrative, physical, and technical safeguards; it does not mandate one identical technical setup for every practice. HHS’s Security Rule summary describes these safeguard categories and the need to scale protections to risk.
For a DPC practice, the practical starting point is to determine whether it conducts HIPAA-standard electronic transactions, map every place ePHI is handled, and use the resulting risk assessment to guide policies, training, vendor agreements, and safeguards. Revisit that work when the practice, its technology, or its risks change.
FAQs
Does a membership model exempt a DPC practice from HIPAA?
No. Membership billing alone does not determine HIPAA status. A provider may be a HIPAA covered entity if it or someone acting on its behalf transmits health information electronically in connection with a transaction for which HHS has adopted a standard. A practice that does not conduct such transactions may not qualify as a covered entity through its provider activities, but other laws may still apply.
What electronic transactions can make a DPC practice a HIPAA covered entity?
Examples include electronic claims, health-plan eligibility inquiries, and referral or prior-authorization requests conducted using adopted standards. A billing service or other agent conducting a standard transaction for the practice can count. Ordinary email by itself does not make a provider a covered entity.
How often must a covered DPC practice conduct a security risk assessment?
HIPAA does not specify a fixed annual interval for the risk analysis. The process should be ongoing, and the practice should reassess as needed when changes or incidents could affect ePHI risk. Document the assessment and revisit it periodically based on the practice’s environment and circumstances.
Which DPC vendors need a business associate agreement?
Generally, a vendor needs a BAA when it performs a service for the covered practice that involves creating, receiving, maintaining, or transmitting PHI on the practice’s behalf. Examples can include EHR or cloud services, billing, transcription, and IT support with PHI access. Apply any exception—such as the conduit exception—only when the vendor’s actual role qualifies.
Table of Contents
- Does HIPAA apply to a cash-pay or membership-based DPC practice?
- Which state privacy and medical-record laws may apply?
- How to assess and manage risks to electronic protected health information
- What written policies, workforce training, and incident procedures are required?
- When must a DPC practice provide a Notice of Privacy Practices?
- Which vendors require business associate agreements?
- How to identify and safeguard ePHI across systems and devices
- FAQs
Ready to simplify HIPAA compliance?
Join thousands of organizations that trust Accountable to manage their compliance needs.
Get Started Free Today