Direct Secure Messaging in Practice—Recommendations for Improvements” was published in Applied Clinical Informatics August 4, 2022 with contributing authors Simone Arvisais-Anhalt, Kathryn Ayers Wickenhauser, Katherine Lusk, Christoph U. Lehmann,  James L. McCormack, and Kristian Feterik.

Article Abstract

Transitions and coordination of care require communication among clinicians that may occur through a variety of channels. Ideally, information received from a referring clinician is integrated automatically into the patient’s electronic health record (EHR) to allow the seamless use of the information.[1] As clinicians work in a plethora of locations and for different employers, handoffs and collaborations rarely occur in a face-to-face setting and instead through electronic communication, such as messaging through EHR-based inboxes.[2] Most clinicians are familiar with EHR-based electronic communication within a health system and some may be aware of electronic communication across organizations that use the same EHR vendor.[3] However, fewer are aware of Direct Secure Messaging (DSM), which facilitates EHR-based electronic communication by health care organizations using different EHR systems (either different instances from the same vendor or across different vendors), even if they use it daily. This editorial intends to introduce the reader to DSM and its functionalities. Additionally, we highlight current challenges and shortcomings of this point-to-point communication tool that have prevented DSM from achieving a more important role in health care interoperability. Since 2011, DSM has been available as a push mechanism (sender-initiated) for exchanging encrypted health information among clinicians, patients, and organizations via the Internet.[4] EHR vendors are required to support DSM capabilities to meet the Certified Electronic Health Record Technology (CEHRT) requirements of 2014 and 2015.[5] [6] Although CEHRT helped to promote near-universal implementation of DSM capabilities among EHR vendors, EHR vendors implemented this feature under a variety of names resulting in a confusing nomenclature ([Table 1]).

DSM is a flexible technical framework that was designed from the start to support a wide range of use cases for secure patient information transmission. Because DSM is agnostic to the message contents and can support multiple file formats as attachments, common uses include transitions of care (sending patient care summaries and coordinating referrals), notifications and messaging (real-time notification of acute care admissions, discharges, and transfers), and administrative functions (patient-specific pharmacy notifications). [Table 2] lists some of the currently used or proposed use cases for DSM in contrast to other modalities of health information exchange (HIE).

If the data are formatted using existing standards such as the Consolidated Clinical Document Architecture, discrete elements may be incorporated directly into the receiving EHR. For example, a DSM message that contains the patient’s immunization data in a machine-readable format can be used to incorporate past immunizations into the local EHR’s immunization section allowing the EHR’s forecasting tool to access the data and avoid duplicate, unnecessary immunizations. The benefits of incorporating data contrast with traditional modes of communication such as fax, scanned paper records, or email ([Fig. 1]). Even if incorporated into the EHR, scanned or faxed records are usually in the form of attachments that are not searchable or accessible to decision support. Given DSM’s secure and encrypted nature, the authors are unaware of any cases where it has been misused to send spam.

Access the full Journal article from Applied Clinical Informatics here.