Direct Project Series, 3 of 3 (See Part 1: The Basics and Part 2: The Benefits)

The Direct Project has the capability to handle a variety of data formats, including all the standard healthcare formats. Computer to computer sharing of patient health information is simplified by XDM packaging. All of the metadata for the content, such as CCDContinuity of Care Document (CCD) The HL7 CCD is the result of a collaborative effort between the He... More/CDA, CCRContinuity of Care Record (CCR) is an XML-based standard for the movement of “documents” between... More, HL7HL7 is a Standards Developing Organization accredited by the American National Standards Institute (... More V2, DICOMDigital Imaging and Communications in Medicine (DICOM) is a common format for image storage. It allo... More, etc., is defined in a metadata file. This allows the receiving system to decide rather simply how to process the content.

In addition, content can be displayed without the need to parse apart the document. Take for instance the very simple prospect of displaying a CCDContinuity of Care Document (CCD) The HL7 CCD is the result of a collaborative effort between the He... More document. Without metadata, even when the document is in an XML format (such as CCDContinuity of Care Document (CCD) The HL7 CCD is the result of a collaborative effort between the He... More/CDA or CCRContinuity of Care Record (CCR) is an XML-based standard for the movement of “documents” between... More), the receiving application would still need to "look inside" the content before it can decide how to render the contents. But with XDMCross-enterprise Document Media Interchange (XDM) – What itss used for: According to IHE, XDM tran... More metadata available, the application can do that, and a lot more decision making about how to process the content, without ever looking inside it. This allows for a much simpler processing path.

Roles of an Interface Engine with Direct Project

The Direct protocol will simply be another connection method into and out-of integration engines. However, the integration engine can determine how involved it will be in the formation of the Direct message.

A base level of Direct support would involve creating an unsecure MIME message and handing this off to a HISPHISP, or Health Information Service Provider, is an email service provider that follows Direct Proje... More. The HISPHISP, or Health Information Service Provider, is an email service provider that follows Direct Proje... More would then be responsible for encrypting the data with a public key, signing the payloadPayload refers to the content of the message being sent (i.e., the message body). with hash and a private key, and routing the message via SMTP to the receiving HISPHISP, or Health Information Service Provider, is an email service provider that follows Direct Proje... More.

a full participation in direct would involve the integration engine performing all the functions of a hispHISP, or Health Information Service Provider, is an email service provider that follows Direct Proje... More, including encrypting and signing on the sending side and decrypting and authenticating on the receiving side along with managing all the certificates.

if the integration engine acts as a full hispHISP, or Health Information Service Provider, is an email service provider that follows Direct Proje... More, then the engine could choose to only act as a hispHISP, or Health Information Service Provider, is an email service provider that follows Direct Proje... More for messages that flow thru the integration engine, or it could also act as a hispHISP, or Health Information Service Provider, is an email service provider that follows Direct Proje... More for any other application that wants to send secure e-mails.

Tags: ,
 Print Friendly