The Direct Project and Corepoint Integration Engine

Direct Project’s simplicity makes data exchange possible for all providers

Corepoint Health customers can exchange health data with external organizations using The Direct Project protocol, which is a simplified data transport method many compare to a secure electronic fax or email. Direct Project truly offers a simplified method for externally sharing health data in a variety of formats including Consolidated CDA (CCD), HL7 v2 and DICOM.

In the traditional email sense, Direct is nothing more than a fax machine replacement. Instead of faxing patient health information (PHI) to other providers, the PHI will be attached to an email and sent using SMTP as the protocol. The email will be secure and a designated Health Information Service Provider (HISP) will be utilized.

Users of Direct communication will be both individuals who will send secure emails with attached PHI and machines that send and receive automated messages. The main limitation of Direct Project data communication is its inability to accommodate query-based workflows—it is purely a push-based method of communication.

“Having Corepoint Integration Engine in place gives me peace of mind about the performance of every interface and I know the product will keep us ahead of the curve with future health data exchange initiatives.”
Edward Martinez

Senior Vice President and CIO

Miami Children’s Hospital

Direct Project is a government-sponsored initiative to promote the secure communication of patient health information. Direct uses the simple mail transfer protocol (SMTP) as its communication backbone.

Basic Direct Project workflow diagram

Basic Direct Project Workflow Diagram

Direct Project workflow using Corepoint Integration Engine

Direct Project Workflow using Corepoint Integration Engine

Direct Project use cases

Health system

As Corepoint Health customers know, health data exchange is not a one-way relationship—it takes two organizations to make a transaction. Through Direct messaging, Corepoint Integration Engine users can receive and incorporate health data from “less interoperable” facilities, allowing the completion of data exchange.

From the hospital side, action lists automatically distribute summary of care files upon discharge to HIEs, ACOs, referring physicians or downstream caregivers. Additionally, lab order result messages can be distributed to the ordering physician—all without the need for programming or paperwork activities from clinical staff.

In short, all certified EHR systems must be Direct compatible. By using Corepoint Integration Engine as the catalyst of your health data environment, this can be accomplished seamlessly, in real time, and with confidence that the message will be securely received.

Clinics and providers

In an era of mergers and an increasing number of hospitalists, physician-owned clinics continually have to find new ways to differentiate their services from their competitors. With the availability of Direct messaging in Corepoint Integration Engine, providers (radiology, clinics and labs) are able to work around the EHR interfacing obstacle and directly send and receive Direct Project SMTP messages, all without the need for scripting or coding.

Patient referrals you receive from large health systems will utilize Direct protocol, making it easier for your clinic to electronically connect to or interface with regional referral sources. Direct has the potential to also greatly reduce the IT manpower divide between regional health systems and smaller medical clinics, to the benefit of both parties and their patients.

Direct Project allows clinics to easily receive referrals and authorizations and transmit order result messages to any organization with a Direct address.

Patient access

As healthcare modernizes and becomes more connected, patients are increasingly interested in accessing their PHI. Direct Project protocol allows patients to become an extension of the care team by giving them access to their health data, which improves accuracy and helps them prepare for doctor visits and unexpected emergencies.

Through their personal Microsoft HealthVault account, a patient can receive a Direct Project message from their caregiver containing their PHI. From HealthVault, they can view the PHI for accuracy and also forward their data to future caregivers using secure, Direct Project protocol.

When patients are more involved in their care, studies show that results improve dramatically.

“The bottom line is that Corepoint Integration Engine allows me to focus more on what I need to accomplish instead of how I’m going to get there.”
Chris Ryan

CIO, Auburn Community Hospital

How secure is Direct communication?

Meaningful Use stage 2 requirements

Direct Project

The ONC requires all Stage 2-certified complete EHRs to support Direct Project transport protocol, making it the “minimum threshold” communication method for exchanging health data. Organizations can use other methods in Corepoint Integration Engine, such as SOAP-based Web Services, but certified EHRs are not required to support these methods according to final Stage 2 rules.

Consolidated CDA

Consolidated CDA is the standard required for transfer of care by Meaningful Use Stage 2. It represents harmonization of Health Story guides, HITSP C32, part of the IHE Patient Care Coordination, and the original CCD by HL7. The Consolidated CDA implementation guide defines templates used to structure documents. With one implementation guide and defined templates, the standard is much easier to analyze and implement.

“Corepoint is a great company. They stand as the greatest example of how a vendor should treat customers. I cannot say enough great things about Corepoint. I tell everyone I know about them.”
Chief Information Officer

Download PDF

 Print Friendly