Hospitals do not operate alone. Around every hospital is a network of employed physician practices, independent groups with admitting privileges, specialty clinics, urgent care centers, and outpatient services. Patients move between these settings constantly, and so do orders, results, referrals, and records.
When the hospital EHR goes offline, those connections break in ways that are easy to overlook in a facility-focused downtime plan. A clinic cannot send a referral. A practice cannot see results that were released during the outage. A patient sent from a clinic to the emergency department arrives with no records. And when a practice has its own outage, the hospital may not hear about it until a patient arrives confused.
Coordinating downtime preparedness with affiliated practices closes those gaps. It requires clear communication, defined handoffs, shared practice, and attention to the compliance rules that govern how hospitals and independent physicians can work together.
Where the Dependencies Are
Start by mapping how practices connect to the hospital:
- Shared EHR environment. Some practices use the hospital’s EHR through an extension or hosting arrangement and go offline when the hospital does
- Orders and results. Practices order labs and imaging at the hospital and depend on results coming back
- Referrals and transitions of care. Patients move from clinics to specialists, the ED, or inpatient admission
- Scheduling. Practices may schedule hospital procedures and diagnostic tests
- Hospital-based clinicians. Physicians who work in both settings rely on records in both
- Admission and discharge notifications that practices use to follow up with patients
Three Types of Practices, Three Types of Needs
Not every practice needs the same coordination.
Employed practices on the same EHR go offline at the same time as the hospital. They should be included in the system downtime plan, with their own workstations, procedures, and orientation.
Independent practices on a hospital-hosted EHR depend on the hospital’s outage response but may not be part of the hospital’s planning. They need explicit inclusion in notification and procedures.
Independent practices on their own EHR have separate outages. The coordination need here is communication and handoff: how each side tells the other when something is wrong and how patients are safely transferred.
The Coordination Elements That Matter Most
A shared notification protocol. Define who at the hospital notifies practices when a downtime event begins, who at each practice receives it, and what channel is used. The channel should not depend on the EHR. Include the reverse path so practices can tell the hospital when they have an outage. Our post on creating a downtime communication plan covers the structure.
A minimum handoff data set. Agree on what information must accompany a patient sent from a clinic to the ED or an admission during an outage, such as current medications, allergies, reason for transfer, and a callback number. A simple transfer eForm or printed form standardizes this.
Rules for orders and results during an outage. Specify how urgent orders are placed, how critical results are communicated by phone, and how those events are documented for later reconciliation.
Scheduling guidance. Decide when practices should continue seeing patients, when to reschedule, and what to tell patients.
Joint practice. Invite practice leaders to planned maintenance window exercises and tabletop discussions. A single shared exercise reveals more about handoff problems than any amount of policy review.
Reconciliation coordination. Results, orders, and referrals that crossed during the outage need to be matched afterward. Assign owners on both sides.
Supporting Smaller Practices
Many affiliated practices have limited IT support and a lean staff. They face the same risks described in our posts on outpatient clinics preparing without a dedicated IT team and ambulatory clinics running smaller EHR platforms. Practical steps include short procedure cards, a small starting deployment of downtime workstations, and a single point of contact. At the published rates, a Tier 1 deployment of 3 to 5 stations is $299 per station per month, so a practice can start small. See the pricing page and the downtime solutions overview.
Compliance Considerations
Coordination with independent physicians has legal boundaries that deserve attention before you design a program.
HIPAA generally permits sharing protected health information for treatment purposes, which supports clinical handoffs during an outage. Where systems or hosting are shared, review whether business associate agreements are needed. The HHS guidance on business associates is a starting point, and the HIPAA Security Rule overview covers contingency planning obligations.
If the hospital plans to provide technology, training, staff time, or subsidies to independent physicians who refer patients, federal fraud and abuse laws such as the Stark Law and the Anti-Kickback Statute may apply. Involve compliance counsel before offering anything of value, even if the intent is purely to improve patient safety.
This is general information, not legal advice, and your counsel should guide the design.
Governance and Ownership
Without a named owner, affiliated practice coordination tends to disappear into the gap between hospital IT and practice management. Assign a practice liaison, review the arrangement annually, and include affiliated practices in your program governance and annual planning cycle. Track simple measures: how quickly practices are notified, whether handoff forms were used, and how many cross-setting orders or results needed manual follow-up after each event.
To discuss how dbtech can support downtime preparedness across a hospital and its affiliated practices, contact our team or request a demo.