Patient Discharge Summary

Standard Operating Procedure: Patient Discharge Summary

1. Document Control & Revision History

---

2. Executive Summary & Scope

This SOP establishes the mandatory operational framework for the creation, validation, and transmission of Patient Discharge Summaries (PDS). Adherence is required to ensure compliance with CMS Conditions of Participation (CoP) 42 CFR § 482.43 and Joint Commission standards regarding the continuity of care. The scope encompasses all clinical personnel (Physicians, Nurse Practitioners, PAs) authorized to execute discharge orders within the Electronic Health Record (EHR) ecosystem.

---

3. Prerequisites & Tool Requirements

• Software Access: Validated EHR credentials with 'Attending/Provider' privilege level.
• Interoperability: Active connection to the Health Information Exchange (HIE) or Direct Messaging gateway.
• Documentation Standards: Access to the institutional clinical documentation improvement (CDI) style guide.
• Training: Completion of 'Transitions of Care' regulatory compliance module (Renewed biennially).
• PPE: N/A (Administrative/Clinical documentation workflow).

---

4. Roles & Responsibilities (RACI Matrix)

R = Responsible, A = Accountable, C = Consulted, I = Informed

---

5. Step-by-Step Operational Procedure

Phase I: Clinical Data Aggregation

• Verify patient physiological stability and discharge readiness criteria.
• Import current 'Problem List' and 'Medication Administration Record' (MAR).
• Review pending diagnostic results (Labs/Imaging) for actionable follow-up.

Phase II: Documentation & Reconciliation

• Populate 'Hospital Course' narrative with concise clinical rationale for admission and interventions.
• Perform 'Medication Reconciliation': Explicitly denote additions, deletions, or changes to home medication regimen.
• Draft 'Follow-up Plan': Specify provider name, contact, date, and time for post-discharge appointments.

Phase III: Verification & Transmission

• Conduct 'Teach-Back' verification with patient/caregiver regarding discharge instructions.
• Execute digital signature on PDS within EHR.
• Trigger automated transmission to the primary care physician (PCP) via secure Direct Message.
• Provide printed/electronic summary copy to patient prior to egress.

---

6. Quality Assurance & Verification Criteria

Audits will be conducted on a monthly random sample of 10% of discharges. Failure to meet the following benchmarks triggers a departmental review.

• Timeliness: PDS transmitted/finalized within 24 hours of clinical discharge.
• Completeness: 100% of PDS must include: (1) Final diagnosis, (2) Medications at discharge, (3) Pending labs, (4) Specific follow-up parameters.
• Accuracy: Zero discrepancies between the discharge MAR and the finalized medication list.
• Tolerance: 0% threshold for "Missing Follow-up Provider" designation.

---

7. Practical Troubleshooting Scenarios

Scenario A: EHR Latency or Downtime

• Symptoms: System timeout prevents save/transmission of summary.
• Protocol: Utilize the approved 'Downtime Downtime PDS Template' (Paper). Secure in the medical records vault; input data into EHR manually within 4 hours of system restoration. Notify IT Helpdesk via priority ticket.

Scenario B: Critical Lab Result Post-Discharge

• Symptoms: Pathological results populate for an already discharged patient.
• Protocol: Attending Physician must be notified via paging system within 30 minutes of result entry. Attending to contact patient/PCP directly. Generate an 'Addendum to PDS' and re-transmit to PCP via secure gateway.

Scenario C: Patient/Family Refusal of Discharge

• Symptoms: Patient refuses to leave; discharge summary drafted but incomplete due to lack of transition destination.
• Protocol: Hold transmission of PDS. Immediate consult with Case Management and Risk Management. Document 'Discharge Against Medical Advice' (AMA) or 'Discharge Delay' status in the clinical notes.