HIPAA Compliance Requirements for Lymphedema Therapy and Compression Garment Clinics
Lymphedema therapy and compression garment clinics may create or receive sensitive information such as diagnoses, treatment notes, measurements, photographs, insurance details, and fitting records. Whether HIPAA applies depends on the clinic’s role and how it handles covered electronic transactions—not simply on the fact that it provides health-related services.
If your clinic is a HIPAA covered entity or business associate, you need appropriate administrative, physical, and technical safeguards for protected health information (PHI). The requirements are flexible enough to account for a clinic’s size and operations, but they still call for documented decisions and effective protections.
When Is a Lymphedema Clinic a HIPAA Covered Entity?
A clinic that furnishes health care is generally a covered entity if it electronically transmits health information in connection with a transaction for which HHS has adopted a standard. Examples include electronic claims, eligibility inquiries, and referral authorization requests. The rule applies whether the clinic sends the transaction itself or uses a billing service to do so on its behalf. See HHS guidance on covered entities.
Cash-only payment does not, by itself, determine HIPAA status. A clinic that receives cash but also submits standard transactions electronically—for example, through a billing intermediary—may still be a covered entity. Conversely, a health care provider that does not conduct any standard transaction electronically may not meet the covered-entity definition on that basis alone. Ordinary email or other electronic communication does not automatically make a provider a covered entity; the communication must relate to a covered transaction. HHS explains this distinction in its Summary of the HIPAA Privacy Rule.
A business that only sells compression garments is not automatically a covered entity just because its products relate to health care. Consider whether the business also furnishes health care and whether it conducts standard transactions electronically. A clinic may also have HIPAA obligations if it acts as a business associate for another covered entity.
How Should Clinics Conduct and Document an ePHI Risk Analysis?
The HIPAA Security Rule requires covered entities and business associates to conduct an accurate and thorough assessment of potential risks and vulnerabilities to the confidentiality, integrity, and availability of the electronic protected health information (ePHI) they hold. A HIPAA Security Rule risk analysis is the starting point for choosing safeguards; HIPAA does not prescribe one required assessment method.
Identify where your clinic creates, receives, maintains, or transmits ePHI. This inventory may include the electronic health record, scheduling and billing systems, email, patient portals, cloud storage, staff phones or tablets, backups, and photographs or measurements linked to a patient. Include vendor systems and remote access, not just equipment physically located in the clinic.
Document reasonably anticipated threats and vulnerabilities, the safeguards already in place, and the likelihood and potential impact of risks. For example, consider unauthorized access to an unlocked workstation, lost mobile devices, misdirected emails, ransomware, or a system outage that prevents staff from retrieving care records. HHS’s risk analysis guidance describes these assessment steps.
Use the findings to select and prioritize risk-management measures, assign responsibility, and record what you will do and when. Reassess when your systems, vendors, services, or workflows change, and document the updated assessment and actions. Required Security Rule documentation must generally be retained for six years from its creation or the date it was last in effect, whichever is later, as described in HHS guidance on policies, procedures, and documentation.
What Administrative Safeguards Should Clinics Implement?
Administrative safeguards are the policies, assigned responsibilities, and workforce practices that help protect ePHI. The Security Rule includes a security management process, assigned security responsibility, workforce security, security awareness and training, security incident procedures, contingency planning, and periodic evaluation. HHS summarizes these requirements in its HIPAA Security Rule overview.
Assign a person to coordinate security activities, even if the clinic is small and one person has multiple responsibilities. Set rules for granting, changing, and ending workforce access; limit access according to each person’s role; and establish appropriate sanctions for violations. Train workforce members on clinic policies, patient privacy, secure handling of ePHI, and how to report a suspected incident.
HIPAA requires a security awareness and training program, but it does not make an annual training certificate a universal federal compliance requirement. Training should reflect the clinic’s actual policies and risks, including its systems and processes for patient intake, treatment documentation, garment fitting, photographs, and disclosures. A completion certificate may document participation in a course; it does not by itself establish that the organization complies with HIPAA or that a worker has completed the clinic’s employer-specific training.
Maintain written policies and procedures, incident-response steps, contingency plans for emergencies, and records of required assessments and actions. The Security Rule’s addressable implementation specifications are not optional: if a specification is not reasonable and appropriate for your clinic, document why and implement an equivalent measure when reasonable and appropriate. See HHS guidance on risk analysis and implementation specifications.
How Can Clinics Protect Patient Records, Devices, and Workstations?
The Security Rule requires administrative, physical, and technical safeguards to protect ePHI. Paper records are not ePHI, but the Privacy Rule’s protections still apply to PHI in paper and other formats. Secure paper charts, referral documents, printed fitting notes, and other patient information from unauthorized access.
Use practical physical measures such as restricting access to areas where records or systems are kept, positioning screens away from public view, and locking workstations when unattended. Set policies for the proper use of workstations and for handling, moving, reusing, and disposing of devices and media that contain ePHI. HHS describes facility access, workstation use and security, and device and media controls in its physical safeguards guidance.
Use individual user accounts and role-based access rather than shared logins. Configure safeguards such as authentication, access controls, audit logging, and protection against improper alteration or destruction of ePHI. Protect information transmitted over electronic networks from unauthorized access. The Security Rule’s technical safeguards are flexible, so select and configure measures based on your documented risk analysis and environment.
Encryption is an addressable Security Rule implementation specification, not a blanket instruction to use one specific technology in every situation. Evaluate whether encryption is reasonable and appropriate for your clinic; if you decide it is not, document that decision and adopt an equivalent measure where reasonable and appropriate. Because encryption consistent with HHS guidance can affect whether PHI is considered unsecured for breach-notification purposes, document how devices and systems are protected. See the Security Rule overview and HHS Breach Notification Rule.
For mobile devices and clinical images, use clinic-approved systems, protect devices against unauthorized access, and establish procedures for storing, transmitting, and deleting files. Do not assume that a photo is anonymous simply because it focuses on a limb: information that identifies a patient or can reasonably be linked to the patient may be PHI. Apply your privacy and security policies to images used for care, documentation, or communication.
Ready to simplify HIPAA compliance?
Join thousands of organizations that trust Accountable to manage their compliance needs.
Get Started Free TodayHow Should Staff Handle Patient Information and Disclosure Requests?
Set clear procedures for receiving and responding to requests for records, corrections, restrictions, and disclosures. Verify the requester’s identity and authority as appropriate, route requests to the person responsible for privacy matters, and document the response. A patient’s access request should be handled within HIPAA’s deadline even if the records are maintained by a vendor or business associate.
For an individual’s request to access PHI in a designated record set, a covered entity generally must act within 30 calendar days. If it cannot meet that deadline, it may take one additional 30-day period by providing the individual, within the initial period, a written explanation of the delay and the date it will complete its action. See HHS guidance on access-request timelines.
The Privacy Rule generally permits covered entities to use or disclose PHI for treatment, payment, and health care operations without obtaining an individual’s authorization. Other disclosures may require the patient’s authorization or must meet a specific permitted or required purpose. Do not assume that a relative, caregiver, or referring party can receive patient details simply because of their relationship with the patient; follow the applicable permission, authority, or disclosure exception. See HHS guidance on treatment, payment, and health care operations disclosures.
Apply the minimum necessary standard to uses, disclosures, and requests where it applies, such as many payment and operational disclosures. It does not apply to disclosures to or requests by a health care provider for treatment, disclosures to the individual, or certain other exceptions. Build the standard into role-based access and routine disclosure procedures rather than applying it indiscriminately to every exchange. See HHS minimum necessary guidance.
When Do Business Associate Agreements Apply to Clinics?
A business associate is generally a person or organization outside the covered entity’s workforce that performs certain functions or services for the entity involving PHI. Examples can include a billing service, a cloud service provider that maintains ePHI, or a contractor that handles patient records on the clinic’s behalf. Whether an agreement is needed depends on the relationship and the services performed, not only on the vendor’s title. HHS provides examples in its Business Associates FAQ.
When a covered clinic uses a business associate, it generally must have a written business associate agreement (BAA) that describes permitted uses and disclosures and requires appropriate safeguards. The agreement should address reporting impermissible uses or disclosures, breaches, and security incidents, and require applicable protections for subcontractors. HHS provides sample business associate agreement provisions.
A vendor does not necessarily become a business associate merely because it provides a service to the clinic. For example, HHS distinguishes services involving PHI from services where any access to PHI is only incidental and appropriate safeguards are in place. Assess each relationship and document the conclusion. A clinic can also be a business associate when it performs covered functions or services involving PHI on behalf of another covered entity.
What Breach Notification Steps Are Required?
An impermissible use or disclosure of PHI is generally presumed to be a breach unless an exception applies or the covered entity or business associate documents, through a risk assessment, a low probability that the PHI was compromised. The assessment considers the type and extent of information, who received or used it, whether it was actually acquired or viewed, and how the risk was mitigated. HHS explains the definition and assessment factors in its Breach Notification Rule guidance.
When an incident may involve unsecured PHI, promptly contain it, preserve relevant records, investigate what happened, and determine whether notification is required. Document the incident, the decision, mitigation steps, and any notifications. Do not treat every security incident as automatically requiring notification; assess it under the rule and document the basis for your decision.
After a breach of unsecured PHI, a covered entity must notify affected individuals without unreasonable delay and no later than 60 calendar days after discovery. It must also notify the HHS Secretary: breaches affecting 500 or more individuals must be reported without unreasonable delay and within 60 days, while breaches affecting fewer than 500 individuals may be reported annually, no later than 60 days after the end of the calendar year in which they were discovered. A breach affecting 500 or more residents of a state or jurisdiction also requires notice to prominent media serving that area. See the HHS breach notification requirements and HHS breach reporting instructions.
If a business associate discovers a breach of unsecured PHI, it must notify the covered entity without unreasonable delay and no later than 60 calendar days after discovery. The BAA may set a shorter reporting timeframe and define how the parties will coordinate the investigation and notifications. See HHS sample BAA provisions.
In practice, a clinic’s HIPAA program should connect its covered-entity status, documented ePHI risk analysis, workforce policies, device and record safeguards, disclosure procedures, vendor agreements, and breach-response plan. Review these elements when the clinic’s services, systems, staff, or vendor relationships change.
FAQs
Does a cash-only lymphedema clinic have to comply with HIPAA?
Not necessarily. A health care provider is generally a HIPAA covered entity when it electronically conducts a transaction for which HHS has adopted a standard; accepting cash does not itself decide the issue. A cash-only clinic may still be covered if it conducts a standard transaction electronically, including through a billing service. If it does not conduct such transactions, it may not meet the covered-entity definition as a provider, although other laws or contractual obligations may still apply.
What safeguards should a clinic use to protect electronic patient records?
Use safeguards suited to the clinic’s documented risks, such as unique user accounts, role-based access, secure authentication, workstation locking, audit-log review, protected transmission, and secure device handling. Train staff on clinic policies, limit access to people who need it for their work, and maintain response and backup procedures. The Security Rule requires reasonable and appropriate administrative, physical, and technical safeguards rather than one identical technology setup for every clinic.
When does a compression garment clinic need a business associate agreement?
A covered clinic generally needs a BAA when an outside person or organization performs a function or service for it that involves creating, receiving, maintaining, or transmitting PHI. Potential examples include a billing service or a cloud provider that stores ePHI. Assess what the vendor actually does and whether PHI is involved; the vendor label alone does not determine whether a BAA is required.
Who must be notified after a breach of unsecured patient information?
For a reportable breach of unsecured PHI, the covered entity must notify affected individuals and the HHS Secretary; it must also notify prominent media when the breach affects 500 or more residents of a state or jurisdiction. Breaches affecting fewer than 500 individuals may be reported to HHS annually, within 60 days after the end of the calendar year of discovery. A business associate must notify the covered entity after discovering a breach, and the covered entity remains responsible for required notifications unless the parties have arranged for the business associate to perform them.
Table of Contents
- When Is a Lymphedema Clinic a HIPAA Covered Entity?
- How Should Clinics Conduct and Document an ePHI Risk Analysis?
- What Administrative Safeguards Should Clinics Implement?
- How Can Clinics Protect Patient Records, Devices, and Workstations?
- How Should Staff Handle Patient Information and Disclosure Requests?
- When Do Business Associate Agreements Apply to Clinics?
- What Breach Notification Steps Are Required?
- FAQs
Ready to simplify HIPAA compliance?
Join thousands of organizations that trust Accountable to manage their compliance needs.
Get Started Free Today