Shared Clinical Office Space Security Risk Assessment Checklist
Shared clinical offices bring together providers, staff, visitors, building operators, and sometimes outside vendors. That creates practical security questions: who can enter each area, what information they might see, and who responds when something goes wrong?
Use this checklist to identify and prioritize risks in the space and the systems connected to it. It is a planning aid—not a substitute for each organization’s HIPAA obligations, legal advice, or a documented, organization-specific risk analysis.
What security risks should a shared clinical office space operator assess?
Start by mapping the people, spaces, equipment, information, and services involved. Consider both routine operations and disruptions such as a lost key, network outage, water leak, or unauthorized entry.
- People and responsibilities: Identify tenant practices, their workforce members, the property operator’s staff, cleaning and maintenance contractors, IT vendors, and visitors. Clarify who manages keys, badges, shared reception, network equipment, and incident reporting.
- Information and equipment: Identify where paper records, prescription forms, printed schedules, devices, and electronic protected health information (ePHI) may be created, received, maintained, displayed, or transmitted.
- Shared and restricted areas: Review entrances, reception areas, hallways, exam rooms, records storage, staff-only rooms, medication storage, telecom closets, and any space where ePHI systems are located.
- Likely threats: Consider unauthorized viewing or entry, theft, shared or improperly retained credentials, misdirected deliveries, unattended workstations, lost devices, phishing, malware, power loss, and environmental damage.
- Existing protections and gaps: Record how access is granted and removed, how visitors are handled, how devices are secured, and how suspected incidents are reported and addressed.
For covered entities and business associates, HIPAA requires an accurate and thorough assessment of potential risks and vulnerabilities to the confidentiality, integrity, and availability of ePHI they hold. The assessment should include relevant systems and the environment in which they operate; HHS explains the HIPAA Security Rule risk analysis requirements. A property operator that is not itself a regulated entity can still use the same method to assess facility risks, while each tenant remains responsible for evaluating its own HIPAA obligations.
How can operators evaluate physical access controls and visitor management?
Walk through the space as a patient, tenant employee, visitor, and service worker would. Check whether people can reach rooms, equipment, or documents beyond what their role requires, including during early, late, and after-hours access.
- List every entrance, key, badge, keypad, lockbox, and other means of entry; identify who is authorized to use each one.
- Check that access is approved for a defined purpose, updated when roles change, and promptly removed when it is no longer needed.
- Set a visitor process that identifies the visitor, records or otherwise tracks entry where appropriate, limits access to approved areas, and specifies when an escort is needed.
- Inspect doors, partitions, reception sightlines, records storage, and rooms containing network or clinical equipment for opportunities to enter, tamper, or view information without authorization.
- Confirm that shared keys and badges are controlled, missing credentials can be reported, and any entry records or camera systems are reviewed according to documented procedures.
- Check how deliveries, maintenance visits, cleaning, and emergency access are handled, including whether vendors may be left alone near clinical areas or devices.
HIPAA’s facility access controls standard calls for policies and procedures to limit physical access to electronic information systems and facilities housing them while allowing properly authorized access. Its implementation specifications address contingency operations, facility security plans, access authorization, and maintenance records. Review the current 45 C.F.R. § 164.310 facility access and physical safeguards requirements and HHS’s physical safeguards guidance when deciding which controls are appropriate to the risks.
Which safeguards protect electronic health information and clinical systems?
Assess the technology used by each tenant and any shared infrastructure, such as Wi-Fi, printers, network closets, check-in kiosks, or building-managed devices. Make clear which party administers each system and who is responsible for access, updates, backups, and incident escalation.
- Individual access: Confirm that each authorized user has an appropriate account and that access is granted, reviewed, changed, and removed as needed. Avoid shared logins that make it difficult to identify who accessed information.
- Workstation security safeguards: Check workstation placement, screen visibility from public areas, automatic locking, secure login, device storage, and procedures for locking or logging off when a workstation is unattended.
- Network separation: Determine whether tenant systems and guest or building networks are separated appropriately. Establish who can administer network equipment and how changes are approved.
- Records and devices: Review how printed material, portable devices, removable media, and equipment containing ePHI are stored, transported, reused, or disposed of.
- Monitoring and recovery: Confirm that appropriate system activity can be reviewed, suspected incidents can be reported, and the responsible organization can restore access to needed information after an outage or other emergency.
- Vendor relationships: Determine whether a technology or facilities vendor creates, receives, maintains, or transmits ePHI on behalf of a regulated organization, and whether the required contract and safeguards are in place.
The Security Rule sets standards for access controls, audit controls, authentication, and transmission security, but it does not prescribe one technology or identical setup for every organization. See the 45 C.F.R. § 164.312 technical safeguards and HHS’s summary of the HIPAA Security Rule. Each covered entity or business associate must assess its own environment and determine which reasonable and appropriate safeguards address its risks.
Document incident reporting contacts and response steps. HIPAA requires regulated entities to have security incident procedures, including identifying and responding to suspected or known incidents, mitigating harmful effects to the extent practicable, and documenting incidents and outcomes. A practical incident response plan should explain how tenants and the operator notify one another without delaying the affected organization’s response; see HHS guidance on security incident procedures.
Ready to assess your HIPAA security risks?
Join thousands of organizations that use Accountable to identify and fix their security gaps.
Take the Free Risk AssessmentHow should shared-space risks be documented and prioritized?
Keep a record that shows what was assessed, what was found, who owns each follow-up, and whether the corrective action worked. A checklist can support this process, but it should not replace an organization’s broader risk analysis.
- Record the scope: Note the location, date, systems and areas reviewed, participating organizations, and any areas or records that were not available for inspection.
- Describe each risk clearly: Record the threat, the vulnerability it could exploit, the information or operation at risk, and the current safeguards.
- Set a consistent priority: Consider both the likelihood of the event and its potential effect on the confidentiality, integrity, and availability of ePHI or on clinical operations. Identify urgent exposures separately.
- Assign an owner and deadline: Specify whether the tenant, property operator, or vendor must act, who will verify completion, and when the status will be reviewed.
- Track decisions: Document planned safeguards, temporary mitigations, accepted residual risks, and the rationale for decisions.
- Revisit the assessment: Review it when the space, tenants, systems, vendors, access arrangements, or threat environment changes, and periodically as part of ongoing risk management.
For regulated organizations, HIPAA requires documentation of required security policies, procedures, actions, and assessments, and specifies a retention period for required documentation. HHS notes that the Security Rule does not prescribe a single risk-analysis method or universal assessment schedule; the process should reflect the organization’s circumstances and be updated as needed. See HHS risk analysis guidance and 45 C.F.R. § 164.316 documentation requirements.
What practical examples help identify security gaps?
Use realistic scenarios to test whether written procedures work in the actual shared environment. The following examples can help reveal gaps that a room-by-room inspection might miss.
- Reception visibility: A patient can read names or appointment details on a monitor while standing at the check-in counter. Consider monitor placement, screen privacy, and staff practices for displaying information.
- Unescorted service worker: A maintenance worker uses a shared badge to enter a tenant’s staff-only area. Check authorization, credential control, escort rules, and how after-hours visits are recorded.
- Shared printer: A printed referral or lab result sits unattended in a common area. Check print-release practices, printer placement, and who retrieves or disposes of abandoned pages.
- Departing tenant employee: A former employee still has a key or system account after leaving a practice. Check whether physical and electronic access removal are coordinated and verified.
- Guest Wi-Fi exposure: A visitor network can reach a clinical device or shared printer. Confirm who manages the network and whether its configuration has been reviewed for tenant separation.
- Lost device: A laptop or tablet disappears from an unlocked room. Check device inventory, secure storage, reporting contacts, and the organization’s process for evaluating possible ePHI exposure.
- Building outage: A power or network interruption prevents staff from accessing clinical systems. Check emergency contacts, downtime procedures, and how authorized access is restored safely.
For each scenario, record what could happen, which control should prevent or limit it, who is responsible, and how you would know the control is working. HHS’s risk analysis guidance recommends considering threats, vulnerabilities, potential impacts, and risk levels rather than treating a checklist item as a pass-or-fail compliance test.
What limitations should operators consider when applying a checklist?
A checklist is a starting point, not a guarantee of HIPAA compliance or security. It can miss risks unique to a tenant’s workflows, systems, contracts, or patient population, and it may become outdated when the space or its occupants change.
- HIPAA responsibilities depend on the organization: The Security Rule applies to covered entities and business associates, not automatically to every landlord, office operator, or coworking provider. Tenants should complete their own assessments; an operator should not represent a general facility checklist as a tenant’s HIPAA risk analysis.
- Controls must fit the risk: HIPAA’s requirements are flexible and scalable. A control that is suitable for one layout or practice may not adequately protect another. The assessment should account for the organization’s size, capabilities, systems, costs, and risks.
- Contracts do not replace safeguards: Written agreements can clarify responsibilities, but they do not by themselves prevent unauthorized access or establish that controls work in practice.
- Business associate agreements depend on the relationship: Sharing a building or leasing office space does not, by itself, make an operator a business associate. The analysis depends on whether the operator performs a covered function or service involving PHI on behalf of a covered entity or business associate. When the relationship meets the definition, the required agreement and safeguards may apply.
- Current rules matter: Check the requirements in force and applicable agency guidance when conducting an assessment. Do not treat a proposed rule as a current legal requirement.
HHS describes business associates by their functions and services involving PHI, not simply by whether they occupy the same premises. Review the HHS Business Associates guidance and consult qualified counsel or a compliance professional when the relationship is unclear.
In short, map shared-space risks, define who owns each safeguard, document and prioritize findings, and reassess when conditions change. Use the checklist to guide a practical review—not as a substitute for each regulated organization’s risk analysis and responsibilities.
FAQs
Who is responsible for security in a shared clinical office space?
Responsibility depends on the relationship, the systems and areas each party controls, and any applicable contract. Each covered entity or business associate remains responsible for its own HIPAA obligations. The operator and tenants should clearly allocate tasks such as facility access, visitor handling, network administration, device security, and incident notification.
How often should an operator conduct a security risk assessment?
HIPAA does not set one universal frequency for conducting a risk analysis. Regulated organizations should conduct and update their analysis as needed, including when environmental or operational changes affect ePHI security. A shared-space operator can set a review schedule suited to its risks and also reassess after significant changes, incidents, or new tenant arrangements. See HHS guidance on risk analysis and updates.
What should operators do after identifying a security gap?
Record the gap, assess its potential impact, and determine whether immediate steps are needed to reduce exposure. Assign a responsible owner and deadline, implement and verify corrective measures, and notify affected tenants when appropriate. If the gap may involve a security incident or PHI, follow the applicable response, reporting, and contract procedures without assuming that the operator alone determines notification obligations.
Does sharing office space make the operator a business associate?
No, not by itself. Business associate status depends on whether the operator performs a covered function or service for a covered entity or business associate that involves PHI, subject to the applicable rules and exceptions. A premises-only relationship does not automatically establish that status, but services involving PHI may require closer review and a business associate agreement. See HHS’s Business Associates FAQs.
Table of Contents
- What security risks should a shared clinical office space operator assess?
- How can operators evaluate physical access controls and visitor management?
- Which safeguards protect electronic health information and clinical systems?
- How should shared-space risks be documented and prioritized?
- What practical examples help identify security gaps?
- What limitations should operators consider when applying a checklist?
- FAQs
Ready to assess your HIPAA security risks?
Join thousands of organizations that use Accountable to identify and fix their security gaps.
Take the Free Risk Assessment