Confirmed, Received, Acted On: A Better Way to Deliver Referrals and Diagnostic Results

A positive test result leaves your system. A referral gets sent. A care-gap notification goes out. But did any of them actually reach the provider responsible for taking action?

Healthcare generates clinical information constantly—the challenge is ensuring it reaches a useful destination. This article breaks down why delivery confirmation matters, what causes communication failures, and how to build workflows that verify clinical information reaches the right care team through the right channel.

Why Diagnostic Results, Referrals, and Care-Gap Notifications Fall Through the Cracks

Delivering diagnostic results, referrals, and care-gap notifications with confirmation requires three things working together: accurate provider data, intelligent routing to the recipient's preferred channel, and verification that the message actually reached someone who can act on it. Most healthcare organizations send clinical communications without knowing whether any of that happened.

Here's the thing—sending a message and confirming delivery are completely different. A lab can flag an abnormal result and send it out, but did it reach the ordering provider? What if that provider changed practices two months ago? A referral can leave your system, but did it land in an inbox someone actually checks?

Three types of clinical communication share this vulnerability:

• Diagnostic results: Abnormal findings that require timely follow-up often sit unread in portals or get routed to outdated addresses.

• Referrals: Requests for specialty care stall when the receiving office fails to acknowledge them, leaving the sending provider unaware.

• Care-gap notifications: Alerts about overdue screenings or quality measures go unread because they arrive through channels providers don't monitor.

Each represents clinical information that only creates value when it reaches someone who can take action.

What Delivery With Confirmation Really Means in Healthcare

Traditional healthcare communication operates on a "send and hope" model. You click send, the message leaves your system, and you assume it arrived. Delivery with confirmation replaces that assumption with verifiable proof.

True confirmed delivery goes beyond a transmission receipt. It means clinical information reached the intended recipient through their preferred channel—and ideally, someone acknowledged it. This distinction matters because healthcare communication involves two separate challenges. First, technical delivery: did the message reach a valid endpoint? Second, human receipt: did the right person actually receive it?

A fax transmission confirmation tells you the document went through. It doesn't tell you whether anyone picked it up, whether it reached the correct provider, or whether that provider still works at that location.

The Three States of Confirmed Clinical Communication

Thinking about confirmed delivery as a progression helps clarify what success actually looks like. Each state builds on the one before it.

Confirmed delivery to the right endpoint

The first state is technical confirmation—proof that your message reached a valid digital address. For Direct Secure Messaging (secure email designed for healthcare), confirmation comes through a Message Disposition Notification, or MDN. Think of an MDN like a read receipt that confirms the receiving system accepted the message.

For fax, technical confirmation is a transmission receipt. For EHR-integrated delivery, it's acknowledgment from the receiving system. This baseline confirmation answers one question: did the message arrive somewhere?

Received by the right person or system

Endpoint delivery alone isn't enough. A message can reach a valid address and still miss the person responsible for the patient.

This happens more often than you might expect. Providers change practices, retire, or shift their communication preferences. A referral sent to a physician's old Direct address might technically "deliver" to an inbox no one monitors anymore. Reaching the right person requires accurate, continuously updated provider directory data—not just a list of addresses, but verified information about where providers actually practice and how they prefer to receive clinical communications.

Acted on inside the clinical workflow

The ultimate confirmation is action. Did the specialist schedule the referred patient? Did the PCP order the follow-up test after seeing the abnormal result? Did the provider close the care gap?

This closed-loop confirmation transforms communication from a one-way broadcast into a coordinated workflow. While not every message type supports full action tracking, the goal remains the same: knowing that clinical information led to clinical response.

The Cost of Unconfirmed Delivery for Health Systems, Diagnostic Companies, and Payers

When delivery goes unconfirmed, the consequences show up across clinical, operational, and financial dimensions.

Missed abnormal results and patient safety risk

Abnormal test results that never reach the ordering provider become "lost to follow-up." The patient assumes no news is good news. The provider assumes the test was normal or that someone else is handling it. Meanwhile, a condition that could have been caught early progresses.

Patient safety events like this stem directly from communication failures, not clinical judgment errors. Candello's 2025 Benchmarking Report found that communication breakdowns now account for 40% of malpractice cases.

Referral leakage and lost in-network revenue

Referral leakage occurs when patients receive care outside the intended network. Sometimes patients choose a different provider. But often, the referral never reached the specialist's office, the patient never received scheduling information, or the referring provider had no way to follow up.

For health systems, each leaked referral can represent $821,000–$971,000 in annual lost revenue per physician, as well as fragmented care. For patients, it means navigating a confusing, uncoordinated system.

Weaker performance in value-based care and quality programs

Care-gap notifications exist to help providers close quality-measure gaps—screenings, preventive services, and chronic disease management. When notifications don't reach providers, gaps stay open.

The result shows up in quality scores, star ratings, and value-based contract performance. Organizations that can't reliably communicate care gaps to the right providers struggle to improve population health metrics, regardless of how sophisticated their analytics might be.

What Causes Confirmation Failures in Clinical Communication

Understanding why delivery fails helps identify where to focus improvement efforts.

Outdated provider directories and digital endpoints

Provider information changes constantly. Physicians move practices, join new groups, retire, or change their preferred communication methods. Most provider directories update infrequently—Defacto Health's 2025 report found only 2 of 124 payers reached 70% accuracy—which means the address you're sending to may no longer be accurate. This is one of the most common—and most preventable—causes of failed delivery.

Manual fax and portal workflows

Fax remains widespread in healthcare, yet it offers minimal delivery verification. A transmission confirmation tells you the fax machine received the document. It doesn't tell you whether anyone retrieved it, read it, or acted on it.

Portal-based workflows create a different problem: they require recipients to log in and check for messages. If a provider doesn't regularly monitor a particular portal, messages accumulate unread.

Limited Direct Secure Messaging coverage

Direct Secure Messaging provides genuine delivery confirmation through MDN receipts, making it one of the most reliable channels for clinical communication. However, not all providers participate in Direct networks, and coverage varies significantly by region and specialty. When a recipient lacks a Direct address, senders face a choice between less reliable channels or manual outreach.

Disconnected EHRs and care team systems

Healthcare organizations use different EHR platforms that don't automatically share delivery status or acknowledgments—a persistent healthcare interoperability challenge. A message sent from one system may arrive in another without any confirmation flowing back to the sender. This creates blind spots where senders have no visibility into what happened after they clicked send.

No visibility into delivery status

Perhaps the most frustrating failure mode is simply not knowing. Many organizations send clinical communications without any mechanism to track whether they were delivered, received, or acted upon. Without visibility, problems go undetected until a patient falls through the cracks or an audit reveals systematic communication gaps.

How to Deliver Clinical Information With Confirmation

Moving from "send and hope" to confirmed delivery involves a structured approach.

Step 1. Identify the right recipient with accurate provider data

Start with verified, current provider information. This means more than a name and NPI—it includes the provider's current practice location, specialty, and preferred communication endpoints. Accurate identification prevents the most common delivery failures before they happen.

Step 2. Route through the recipient's preferred channel

Different providers prefer different communication methods. Some monitor their Direct Secure Messaging inbox regularly. Others rely on their EHR's internal messaging. Some still depend on fax.

Intelligent routing selects the best delivery path based on what actually works for each recipient, rather than forcing all communications through a single channel.

Step 3. Capture delivery confirmation at the endpoint

Each channel provides different types of confirmation. Direct Secure Messaging generates MDN receipts. Intelligent eFax provides transmission verification with enhanced tracking. EHR-integrated delivery can capture system-level acknowledgments. The key is to capture whatever confirmation the channel supports and make it visible to the sender.

Step 4. Resolve failed deliveries automatically

Delivery failures happen. Addresses change, systems go down, and endpoints become inactive. A confirmed delivery system detects failures and responds—either by automatically attempting alternate routes or by flagging the issue for manual intervention. This active management dramatically improves overall delivery success rates.

Step 5. Close the loop with acknowledgment and action

The final step moves beyond technical delivery to human confirmation. Did the recipient acknowledge the message? Did they take the expected action? While full closed-loop tracking isn't always possible, even partial acknowledgment—like confirming a referral was received—provides valuable visibility.

What Is a Closed-Loop Referral and Results Workflow

A closed-loop workflow gives senders visibility into the entire communication lifecycle, not just the initial send.