Incoming Hospital Document Filed Without Action (Missed Consent Requirement)

Category: Clinical Workflow / Document Management / Administrative Risk
Risk Level: 🔴 High Risk (Continuity of Care & Medico-Legal)

---

What Happened

While processing incoming emails and faxes, front desk staff received a document from a hospital in response to a prior request from the practice for a patient’s medical records.

The document was scanned and uploaded directly into the patient’s electronic profile. However, the document was not the requested hospital records. Instead, it was a hospital consent form requiring the patient’s signature before the hospital could release the requested medical information.

After being uploaded into the patient file, no further action was taken. The consent form was not reviewed, forwarded to the doctor, or provided to the patient for completion. As a result, the requested hospital records were not released, and the request process stalled.

---

Risk Identified

Continuity of Care Risk

• Important hospital records were delayed or not obtained.
• Clinical decision-making may occur without complete patient information.

Patient Safety Risk

• Missing historical information may affect diagnosis, treatment planning, or follow-up care.

Medico-Legal Risk

• Failure to action incoming clinical correspondence.
• Practice may be considered responsible for unmanaged or overlooked documents.

Operational Risk

• Breakdown in document workflow.
• False assumption that uploading a document equals task completion.

---

Correct Practice

All incoming external correspondence must undergo document triage before filing completion.

When receiving hospital or specialist documents:

1. Staff must review the document type before finalising filing.
2. If the document requests action (e.g., consent form, clarification, additional information):
   • Flag the document for doctor or nurse review; and/or
   • Contact the patient if action is required.
3. Uploading a document does not complete the workflow unless required actions are confirmed.
4. Action-required documents must generate a task, reminder, or follow-up entry.

---

Standard Rule

• Incoming clinical correspondence must be reviewed for required actions before filing completion.
• Documents requesting signatures, consent, or additional steps must not be passively stored in patient records.
• “Scan and file” is not considered complete processing if action is required.
• Responsibility for follow-up must be clearly assigned.

---

Approved Workflow Practice

When receiving hospital responses:

✅ Ask:

• Is this clinical information or a request for action?
• Does the patient or doctor need to do something next?

If action is required:

• Create a task for the responsible clinician or admin staff;
• Notify the patient when appropriate;
• Document follow-up actions in the system.