top of page

Closed-Loop Healthcare: How to Track Test Results, Referrals, and Follow-Up

  • Jul 24
  • 5 min read

A referral is ordered. A test is completed. A report is filed. Everyone assumes someone else closed the loop. 


Weeks later, the patient has not been scheduled. The report has no documented acknowledgement. The follow-up recommendation is still buried in text. The EHR contains the pieces, but the organization has no reliable proof that the intended action occurred. 


This is the open-loop problem in healthcare. 


A healthcare loop is closed only when the required action is completed, reviewed, communicated, documented, and assigned a final disposition. 


 What Closed-Loop Healthcare Means 

Clinical coordinator reviewing AI patient workflow dashboard in hospital

AHRQ describes closing the loop as ensuring that test results are sent, received, acknowledged, and acted upon, including communication with the patient. The same principle applies to referrals, orders, follow-up recommendations, care transitions, and operational tasks. 


A closed loop answers five questions: 

1. Was the action initiated? A test, referral, consultation, outreach task, or follow-up was ordered or recommended. 

2. Was it completed? The appointment occurred, the test was performed, or the task was executed. 

3. Was the result received and reviewed? The responsible professional acknowledged the information. 

4. Was the next action taken? The patient was informed, the care plan was updated, or another step was assigned. 

5. Was final disposition documented? The organization can prove that the loop is complete or explain why it was intentionally closed without further action. 

If any step is missing, the loop remains open. 


Why EHRs Do Not Automatically Close the Loop 

EHRs record events. They do not always reconcile responsibility across systems and teams. 


The referral order may be in the EHR, while scheduling occurs in a separate application. The specialist report may arrive as a document. The recommended next test may appear in unstructured text. Outreach may be recorded in a call-center tool. The original clinician may assume another department owns follow-up. 


AHRQ’s Closed-Loop Diagnostics learning laboratory reported that baseline loop-closure rates across studied workflows were often below 60%. The program used EHR data, referral records, reports, and system-engineering methods to identify breakdowns and test interventions. One symptom-tracking registry reduced the median time to documented symptom resolution from 103 days to 20 days. 


The lesson is operational: reliable follow-up requires a system of accountability, not merely a system of record. 


The Most Common Open Loops 


Test and report follow-up 

  • Laboratory, imaging, or pathology result received without documented acknowledgement. 

  • Follow-up recommendation in a report not converted into an order or task. 

  • Result reviewed, but patient communication is missing. 

  • Repeat testing or monitoring due date passes without completion. 

Referral management 

  • Referral ordered but not scheduled. 

  • Appointment scheduled but not completed. 

  • Specialist visit completed, but the consultation report is missing. 

  • Report received, but the recommended plan is not incorporated into the patient workflow. 

Care transitions 

  • Discharge instructions are documented, but follow-up is not scheduled. 

  • Medication reconciliation remains incomplete. 

  • Receiving team does not acknowledge the handoff. 

  • Required records or summaries do not reach the next setting. 

Patient engagement 

  • Repeated missed appointments do not trigger the defined outreach pathway. 

  • High-priority patient message remains unassigned. 

  • Required assessment or monitoring activity becomes overdue. 

  • Outreach attempts occur, but no final disposition is recorded. 

Operational and revenue follow-through 

  • Prior authorization is requested but not resolved before service. 

  • Documentation deficiency remains open as the claim approaches submission. 

  • A service is delivered but not captured for charge submission. 

  • A denial root cause recurs because the upstream workflow was never corrected. 


The Architecture of a Closed-Loop System 

Healthcare professionals reviewing AI-powered patient journey dashboard

Longitudinal context 

The system needs a timeline across encounters, orders, results, referrals, scheduling, communications, tasks, authorizations, and claims. 

Institution-specific expectations 

The meaning of "overdue" depends on the organization’s pathway, urgency, specialty, payer, and policy. Customer-approved rules should define the expected next step and timeframe. 

Evidence-backed exception detection 

The system should identify the missing or inconsistent step and show the source evidence. It should not simply assign a risk score. 

Clear ownership 

Every exception needs a role, team, or named owner. Shared responsibility often becomes no responsibility. 

Escalation and disposition 

The workflow should define when to remind, escalate, reassign, contact the patient, hold a claim, or close the issue with a documented reason. 

Auditability 

The organization should be able to see when the issue was identified, who reviewed it, what action was taken, and how the loop was closed. 


Why More Alerts Are Not the Answer 

Healthcare teams already face alert fatigue. A closed-loop system should reduce uncertainty, not add noise. 


The design should: 

  • Prioritize high-consequence or overdue exceptions. 

  • Suppress duplicates. 

  • Route findings only to the role that can act. 

  • Include the relevant source evidence. 

  • Let the organization configure thresholds and escalation. 

  • Track resolution so the same issue does not continue to fire. 


A useful exception says: "This referral was ordered 21 days ago under a pathway requiring scheduling within 14 days. No appointment or documented disposition is present. Here are the order, pathway, and scheduling records." 

That is materially different from an alert that says: "Referral may be overdue." 


How Kana Supports Closed-Loop Healthcare 

Kana is designed to connect longitudinal patient information with the workflows surrounding care. For approved use cases, it can evaluate whether required actions appear to have been completed under the organization’s own pathways, timelines, and governance rules. 


Potential closed-loop workflows include: 

  • Results without documented acknowledgement or follow-up. 

  • Referrals that remain unscheduled, incomplete, or without a returned report. 

  • Actions described in notes without evidence of assignment or completion. 

  • Missed appointments requiring the institution’s defined outreach process. 

  • Incomplete care-transition tasks. 

  • Documentation, authorization, or claim issues awaiting resolution. 


Kana surfaces the supporting evidence and routes the finding to authorized personnel. It does not diagnose patients or make autonomous treatment decisions. 


How to Start Without Creating a Massive Integration Project 

Choose one loop with high volume, clear ownership, and measurable consequences. 

Good candidates include: 

  • High-priority imaging follow-up. 

  • Specialty referrals from primary care. 

  • Post-discharge appointments. 

  • Prior authorization before a scheduled procedure. 

  • Missing documentation before claim submission. 


Map every step, system, owner, expected timeframe, exception, and closure condition. Test the workflow retrospectively. Then route only high-confidence prospective exceptions to a controlled work queue. 


Measure: 

  • Completion rate. 

  • Median days to closure. 

  • Number of overdue cases. 

  • Staff effort per case. 

  • Escalation rate. 

  • Patient contact and completion. 

  • Prevented cancellations, rework, or denials. 


The Bottom Line 

Healthcare organizations do not need more proof that open loops exist. They need a reliable way to find them, assign them, and close them. 

The intelligence layer should tell the organization what remains unresolved, why it matters under its own standards, and who needs to act next. 


Frequently Asked Questions 

Question: What does closing the loop mean in healthcare? 

Answer: It means confirming that a test, referral, follow-up, or other required action was completed, reviewed, communicated, acted upon, and given a documented final disposition. 

Question: Why do referrals remain open even when an EHR is used? 

Answer: The order, scheduling, specialist visit, report, patient communication, and next action may occur in different systems and teams. The EHR may record pieces without continuously reconciling ownership and completion. 

Question: How can AI improve referral and result follow-up? 

Answer: AI can connect the relevant records, compare the timeline with customer-approved pathways, identify missing steps, present source evidence, and route the exception to the correct human owner. 

Question: Does closed-loop AI make clinical decisions? 

Answer: Kana’s proposed approach identifies unresolved actions and workflow exceptions for authorized review. Clinical decisions remain with qualified healthcare professionals. 


Choose one loop your organization cannot reliably see today. Kana can help map the evidence, ownership, escalation, and closure workflow, then validate it against historical data before prospective deployment. 

 
 
 

Comments


bottom of page