HIPAA-Compliant Telework and Home Office Policy Template for Remote Medical Coding Companies
Use this adaptable template to establish clear expectations for remote medical coding work involving protected health information (PHI). Customize it to your organization’s contracts, systems, workforce roles, and documented security risk analysis; a policy template alone does not make an organization HIPAA compliant.
What should a remote medical coding telework policy include?
A telework policy should explain who may work remotely, which tasks they may perform, what systems and devices they may use, and how they must protect PHI. It should apply to employees and, where relevant, contractors and subcontractors who handle PHI on the company’s behalf.
Set out clear rules for approved work locations, access authorization, confidentiality, incident reporting, record handling, and consequences for policy violations. Assign responsibility for approving remote access, reviewing safeguards, and responding to reported incidents. The HIPAA Security Rule requires regulated entities to use administrative, physical, and technical safeguards appropriate to their circumstances; see the eCFR administrative safeguards and eCFR physical safeguards.
Use the following as a starting point, not a substitute for your organization’s own review: “Remote workers may access, use, or disclose PHI only as authorized for their assigned duties, through company-approved equipment and systems, and in accordance with applicable policies, client agreements, and law.”
How should employees secure a home workspace for PHI?
Require employees to work in a location where household members, visitors, and passersby cannot see or overhear PHI. Position screens away from windows and shared areas, use a privacy screen when appropriate, and lock the screen whenever stepping away—even briefly. Headphones can help prevent others from hearing confidential calls.
Employees should not let anyone else use a work device or view PHI on a screen. They should avoid discussing patient details in shared spaces and should not use smart speakers, personal assistants, or other recording devices near confidential work. The company’s rules should also state whether remote work from public places or while traveling is prohibited or requires specific safeguards.
These are practical policy controls, not a prescribed home-office checklist for every organization. HIPAA requires safeguards for workstations that access electronic PHI (ePHI), including safeguards that restrict access to authorized users. The organization should decide which measures are appropriate through its security risk analysis.
What device and system controls protect electronic PHI?
Require access through company-approved devices and accounts. As a company baseline, prohibit shared user credentials, personal email, unapproved file-sharing services, and local downloads or storage of ePHI. Use unique user identification and access rights that match each coder’s assigned work. Role-based access control can help apply the minimum necessary standard by limiting access to information a person needs for their duties, subject to applicable Privacy Rule requirements and exceptions.
Consider requiring multi-factor authentication for remote access, device encryption, supported operating systems, security updates, endpoint protection, and secure network connections. These are safeguards to evaluate and adopt based on risk—not a checklist of identical technologies prescribed for every organization. HIPAA requires protections for ePHI access and transmission, while the choice of appropriate measures depends on the organization’s circumstances.
Configure an automatic session logoff or comparable session protection based on your risk analysis. Automatic logoff is an addressable implementation specification: the organization must assess whether it is reasonable and appropriate, implement it when appropriate, or document its determination and any applicable alternative. HIPAA does not prescribe one universal inactivity interval. Review the current eCFR technical safeguards and HHS guidance on telecommuting and access controls.
Prohibit employees from bypassing security controls or sending PHI through unapproved channels. Establish a fast reporting process for suspected phishing, lost devices, misdirected messages, unusual account activity, or other possible security incidents.
How should paper records and PHI be stored and disposed of?
Allow printing only when the work requires it and the company has approved the process. If printing is permitted, require employees to collect pages immediately, keep them in a locked cabinet or other secure storage when not in use, and prevent household members or visitors from accessing them. The policy should explain how to transport approved records and return them to the organization or client.
Employees should not place PHI in household recycling, regular trash, or an unapproved shredding service. Specify an approved destruction method, such as returning records to the company or using a cross-cut shredder if permitted by the organization’s procedure. Keep a process for documenting and reporting lost, misplaced, or improperly discarded records.
For electronic media and devices, define how PHI is removed before reuse and how devices are returned, sanitized, or destroyed. The Security Rule requires policies and procedures for the final disposition of ePHI and media that store it, as described in the eCFR device and media controls.
Ready to simplify HIPAA compliance?
Join thousands of organizations that trust Accountable to manage their compliance needs.
Get Started Free TodayWhat should a remote medical coder telework agreement document?
Have each remote coder acknowledge the organization’s telework and security rules in writing. The agreement should identify approved work locations and equipment, permitted systems, confidentiality expectations, procedures for handling paper records, and the requirement to report a suspected security incident promptly.
It should also cover device return, access removal when duties change or employment ends, cooperation with authorized security reviews, and the consequences of violating policy. Make clear that PHI may be used only for authorized work and must not be retained, copied, or disclosed for personal purposes.
A worker’s telework agreement is not the same as a business associate agreement (BAA). When a medical coding company acts as a business associate, the covered entity generally must have a written agreement with it that meets HIPAA requirements. A BAA may also be required between business associates and subcontractors that handle PHI on their behalf. Describe the relevant relationship and obligations in the appropriate contract; see HHS sample business associate agreement provisions.
How should companies assess, train, and monitor remote coders?
Include remote access, home workstations, devices, workflows, and relevant third parties in the organization’s security risk analysis. Document identified risks, chosen safeguards, responsible owners, and follow-up actions. Reassess when operational or environmental changes could affect ePHI security, such as a new remote platform, material changes to remote work, or a significant security incident. HHS explains the risk analysis requirement in its Guidance on Risk Analysis.
Train employees on the policies and procedures that apply to their roles, including secure remote access, the minimum necessary standard where applicable, phishing awareness, paper handling, and incident reporting. Provide training to new workers and when material policy changes affect their duties, and keep records of completed training. A training completion certificate documents a training event; it does not by itself establish that the company or its systems comply with HIPAA. HIPAA does not create a universal annual certificate-renewal requirement, though an organization may set a refresher schedule in its own policy.
Review system activity and access rights through a documented process. Monitor relevant audit logs and access reports, investigate anomalies, and remove or adjust access when a worker changes roles or leaves. The Security Rule requires regular review of information system activity and appropriate procedures for workforce access and incident response.
What work hours, communication, and performance standards should the policy set?
Define expected work hours, timekeeping rules, availability, break practices, and procedures for notifying a supervisor about absences or connectivity problems. Clarify how employees should request help when an approved system is unavailable and what they may do while waiting. They should not move PHI to a personal device or use an unapproved application as a workaround.
Set approved communication channels for routine work, sensitive discussions, and urgent security reports. Direct employees to verify recipients before sending messages and to use only company-approved systems for PHI. The policy should provide a contact method for reporting incidents outside ordinary work hours and explain that prompt reporting is required even when the employee is unsure whether PHI was exposed.
Measure performance using role-appropriate quality, timeliness, productivity, and documentation standards. Tell coders how work will be reviewed, how corrections will be handled, and how supervisors will address performance concerns. Keep monitoring focused on legitimate operational and security needs, and explain what activity may be reviewed in systems containing ePHI.
In summary, an effective remote coding policy pairs secure workspaces and devices with role-based access, clear records-handling rules, documented risk assessment, appropriate training, and defined reporting and performance expectations.
FAQs.
Can medical coders access PHI from a home office?
Yes, when the organization authorizes remote access and applies safeguards appropriate to the risks. HHS confirms that Security Rule access controls and safeguards apply to employees who telecommute or work from home and access ePHI. Use approved systems, limit access to authorized duties, and protect the workspace from unauthorized viewing or use.
What security controls should remote medical coding companies require?
Set controls based on a documented security risk analysis. Common policy measures include company-approved devices, unique accounts, role-based access, secure remote connections, appropriate authentication, device protection, session locking or logoff, activity review, and incident reporting. HIPAA requires appropriate safeguards but does not prescribe the same technology configuration for every organization.
Can remote coders print or store patient records at home?
Only if the company permits it and has established safeguards and procedures. Prohibit unapproved printing, local storage, and disposal. If paper copies are authorized, require secure storage, restricted access, and approved return or destruction. If electronic storage is approved, specify the permitted device or system and how the records must be protected and removed when no longer needed.
How often should a company review its telework security practices?
Set a review schedule that fits the organization’s risk and operating environment, and reassess when significant changes or incidents occur. HIPAA requires a documented risk analysis, ongoing risk management, regular review of information system activity, and periodic evaluation; it does not set one universal annual review date for every telework policy.
Table of Contents
- What should a remote medical coding telework policy include?
- How should employees secure a home workspace for PHI?
- What device and system controls protect electronic PHI?
- How should paper records and PHI be stored and disposed of?
- What should a remote medical coder telework agreement document?
- How should companies assess, train, and monitor remote coders?
- What work hours, communication, and performance standards should the policy set?
- FAQs.
Ready to simplify HIPAA compliance?
Join thousands of organizations that trust Accountable to manage their compliance needs.
Get Started Free Today