Direct Secure Messaging

The Direct Secure Messaging replaces fax-based workflows with secure, standards-driven communication using DirectTrust messaging and the IHE profiles. It enables structured exchange of referrals, attachments, and status updates, providing full visibility into referral progress across organizations without requiring point-to-point custom integrations.

By packaging referrals in CCD/C-CDA format and sending them through DirectTrust endpoints, the originating provider can automatically receive acknowledgments and completion notices. This creates a closed-loop handoff where every referral has a traceable lifecycle, from initiation to completion, with standardized ACK, HOLD, and COMPLETE status codes defined in the IHE 360X framework

Benefits

• Eliminates fax dependencies: Moves referral workflows to DirectTrust-compliant secure messaging with structured content and attachments.
• Improves referral visibility: Tracks referral progress with standardized status updates (ACK, HOLD, COMPLETE).
• Reduces care leakage: Ensures follow-ups are completed by closing the communication loop between sender and receiver.
• Minimizes custom integration: Leverages national standards (DirectTrust, IHE 360X) for interoperability without proprietary APIs.
• Enhances compliance and auditability: Maintains secure, timestamped message trails aligned with HIPAA and 45 CFR §164.312(b).

Capabilities

• DirectTrust address book sync: Manages validated endpoints for secure exchange between organizations.
• CCD/C-CDA packaging: Embeds structured patient data, orders, and clinical context in interoperable formats.
• Status messaging: Supports IHE 360X-compliant ACK, HOLD, and COMPLETE event notifications for closed-loop tracking.
• Audit and provenance tracking: Logs referral initiation, message exchange, and acknowledgment timestamps for compliance.
• Referral dashboards: Displays active and completed referrals with filtering by organization, specialty, or timeframe.

Implementation Notes

• Requires DirectTrust-compatible endpoints and a 360X-capable EHR or intermediary.
• Status codes are standardized under IHE 360X but may vary by vendor implementation detail.
• Attachments should follow C-CDA and LOINC/SNOMED coding conventions for maximum interoperability.
• Integration can be achieved using FHIR Task or ServiceRequest resources where 360X is not natively supported.

Great for

• Referral Coordinators: Track referral status and outcomes with automated acknowledgment and completion messages instead of manual follow-ups.
• Compliance and HIM Teams: Replace fax-based referrals with auditable, standards-based messaging that ensures delivery and accountability.
• Interoperability Architects: Implement 360X-compliant closed-loop referral logic using DirectTrust messaging and C-CDA attachments.
• Clinical Operations Leaders: Improve referral turnaround and continuity of care with automated, traceable exchanges between organizations.