# What Is DIRECT Secure Messaging?

Direct secure messaging is a standard for sending encrypted health information between healthcare parties, using an address that looks like email and a trust framework that verifies both ends. Each party holds a Direct address issued through a Health Information Service Provider, and messages travel

**Category:** Articles
**Written by:** Zain Qayyum
**Last updated:** Nov 13, 2026
**Source:** https://signals.medsender.com/articles/what-is-direct-secure-messaging

---

Direct secure messaging is a standard for sending encrypted health information between healthcare parties, using an address that looks like email and a trust framework that verifies both ends. Each party holds a Direct address issued through a Health Information Service Provider, and messages travel only between verified participants.

That describes the protocol. It does not explain why, a decade after adoption began, the fax line is still ringing.

## TL;DR

Direct is secure email for healthcare, with identity verification behind it so both ends are known.

It pushes information to a recipient and cannot query another system for a record.

A Direct message frequently carries a document that still has to be read and filed.

It works only where both sender and receiver have adopted it.

Coverage, not capability, is why practices still receive faxes.

The practical question is what happens to the content after it arrives.

## What Direct Actually Is

Two components make it work, and the second is the one that matters for compliance.

### Secure Email With Identity Behind It

An address that looks like an email address, issued through a Health Information Service Provider rather than any mail host. Messages are encrypted in transit, and certificates establish that both ends are verified participants rather than anyone who registered a domain.

### What the Trust Framework Adds

Ordinary encrypted email proves nothing about who is on the other end, which is exactly the problem when sending protected health information. The trust framework is the value: the receiving party has been verified, which is what makes the channel acceptable for clinical content.

## What Direct Does Not Do

Three limits account for most of the gap between what practices expect and what they experience.

### It Pushes, It Does Not Query

Somebody has to decide to send you something. You cannot ask another organisation's system for a record you were never sent. That is a different problem solved by query-based exchange and health information networks, and conflating the two leads to disappointment.

### It Does Not Make the Content Structured

A Direct message frequently carries a document as an attachment, and a document still has to be read, named and filed by somebody. Secure arrival and finished work are not the same thing, which is the point practices discover a few months in.

### It Only Works Where Both Sides Have It

A referring office without a Direct address will send a fax, and that describes most of the long tail of senders a practice cannot control. Coverage rather than capability is the binding constraint, and no individual practice can fix it.

## Why Health Records Systems Still Do Not Talk to Each Other

The honest answer involves several standards doing different jobs, with uneven adoption across all of them.

### Several Standards, Different Purposes

Direct handles push. Query-based exchange handles pull. Newer application programming interface standards handle structured access to specific data elements. Most practices touch all three without anyone naming them, and no single one was ever intended to cover the whole problem.

### Adoption Is Uneven by Design

Participation depends on each organisation's vendor, its network membership and how it has been configured. A practice cannot change the coverage of its own referral sources. It can only change how it handles what arrives, which is where the useful decisions actually sit.

## What This Means for a Practice in Practice

Two conclusions follow, and both are more useful than waiting for the situation to resolve itself.

### Run Both, and Expect To

Direct for partners who have it, fax for everyone else, for the foreseeable future. Any plan assuming fax disappears should come with a date attached, and nobody has been able to supply one for over a decade.

### The Question Is What Happens After Arrival

Whichever channel carried the document, somebody still has to classify and file it unless something does that automatically. Whether the result lands in the chart depends on what your electronic health record (EHR) supports. Ask whether a Direct message is processed the same way as a fax, or whether it lands in a separate inbox that becomes its own backlog.

## How to Decide What to Ask a Vendor

Three questions settle whether a vendor's Direct support is useful to you or merely present. Ask whether they support Direct and through which Health Information Service Provider, since the answer affects which networks you can reach. Ask whether a Direct message is processed identically to a fax or routed somewhere separate, because two inboxes is worse than one. And ask whether the capability is independently accredited, and by whom.

On that last point, one vendor in this category holds Electronic Healthcare Network Accreditation Commission (EHNAC) DirectTrust accreditation for secure messaging, which is an independent assessment rather than a self-declaration. Others list Direct as a supported channel without claiming accreditation, which is a meaningful difference worth asking about. Our guide to[connecting fax and referral software to your EHR](/articles/connecting-fax-referral-software-ehr)covers what happens after arrival,[how fax and referral software integrates with EHRs](/comparisons/fax-referral-software-ehr-integrations)compares what vendors support, and[how automation handles documents, duplicates and downtime](/articles/ai-fax-automation-documents-duplicates-downtime)covers the processing side.

## FAQs

Common questions about Direct secure messaging in healthcare.

### What Is Direct Secure Messaging in Healthcare?

A standard for sending encrypted health information between verified healthcare parties, using an address that resembles email. Each party holds an address issued through a Health Information Service Provider, and a trust framework confirms both ends are genuine participants rather than anyone who registered a domain name.

### Is Direct Secure Messaging the Same as Encrypted Email?

No, and the difference is identity rather than encryption. Ordinary encrypted email protects content in transit but proves nothing about the recipient. Direct adds a trust framework and certificate-based verification, which is what makes it acceptable for protected health information between organisations.

### Does Direct Replace Fax for Medical Practices?

Not in practice, because it only works where both parties have adopted it. Referring offices without a Direct address will keep sending faxes. Most practices run both channels indefinitely, and plans assuming fax disappears rarely come with a credible date attached.

### What Is a Health Information Service Provider?

The organisation that issues and manages Direct addresses and handles message transport on a participant's behalf. Your EHR vendor may act as one, or may partner with a separate provider. Which one you use affects which networks and trust bundles you can reach.

### What Is DirectTrust?

A non-profit that operates the trust framework and accreditation programme underpinning Direct exchange in the United States. Accreditation is performed by the Electronic Healthcare Network Accreditation Commission, so a vendor claiming accredited status has been independently assessed rather than having asserted compliance itself.

### Why Do Health Records Systems Still Not Share Records?

Because several standards cover different parts of the problem and adoption is uneven across all of them. Direct pushes, query-based exchange pulls, and newer interface standards handle structured access. No single standard was designed to cover everything, and participation varies by vendor and configuration.
