Quote Of The Year

Quote Of The Year - Paul Shetler - "Its not Your Health Record it's a Government Record Of Your Health Information"

Thursday, July 25, 2013

A Useful Article And Video On CDA and HL7 V2. A Good Summary Of The Current State Of Play.

This appeared a little while ago.

Will CDA replace HL7 version 2 messaging?

By Herman Oosterwijk, AuntMinnie.com contributing writer

July 18, 2013 -- CDA, or Clinical Document Architecture, is the document standard defined by HL7 as part of its version 3, which is used to exchange information between healthcare providers' electronic health records (EHRs). The new requirements mandate EHR implementation as part of qualifying for federal meaningful use payments.
CDA implementations are still in their infancy, even though at the recent Integrating the Healthcare Enterprise (IHE) Connectathon, there were literally hundreds of those documents exchanged and properly "consumed." Consuming a document means that the information is presented properly and added to the appropriate record in the database. For example, a list of medications in the physician electronic medical record (EMR) is properly updated based on a discharge document from an emergency room visit.
A CDA document exchange is quite different than using an HL7 version 2 message, which, for example, is used for the information exchange between a computerized physician order-entry (CPOE) system and a department scheduler to request an order. Another example would be when a reporting system and an EMR exchange a diagnostic report or exchange a lab result message between an external lab and an EHR. Before going into more details about the differences, let's explain a little bit more about CDA.
There are many CDA "flavors," depending on their use. Each type of CDA is identified by a well-defined and constrained template, which defines what information is required in a particular application. A good example of such a constrained template is the CCD, or continuity of care document, which is required by the U.S. government to exchange information in order to qualify for meaningful use payments. This document contains sections about allergies, medications, problems, and laboratory results, in addition to patient demographic information.
Why do healthcare imaging and information professionals need to know about CDA? Well, CDA is going to be the main "transport" mechanism for clinical information between different systems, especially when these are from different vendors and belong to different healthcare providers or parties. These CDA documents provide a snapshot of a particular event, treatment, or episode of care.
In conclusion, CDA is here to stay; it is quite different from HL7 version 2, with its own field of application; and as healthcare information professionals, it is important to learn about its structure. There is a short video that goes into a little bit more detail about the CDA, its use, and the preferred way to learn about the CDA.
Full article is found here:
(Link to video is in last paragraph)
It is really good to see a clear exposition of where each of CDA and HL7V2 fit and why both are going to co-exist for a very long time to come.
Things are evolving quite quickly in the HL7 space and it is worth keeping an eye on Grahame Grieve’s (an Australian HL7 Expert)  blog which explores all sorts of issues in this space.
See here:

No comments: