Tuesday, November 29, 2011

Green CDA Over The Wire

Over the past decade, I've been closely involved in the evolution of clinical summary/transition of care content standards.    We started with CDA, then merged the CDA and CCR to create the CCD, which we further constrained with the C32 implementation guide.  This year, the Consolidated CDA initiative refined/constrained/optimized the CCD/C32 specifications from IHE, HITSP and HL7 into one easy to use implementation guide.

The only problem with CDA-based standards is that implementation requires expert knowledge of the HL7 Reference Information Model (RIM), a steep learning curve for new developers.    Ideally, HL7 and informatics experts would use the RIM or Detailed Clinical Models to develop templates containing easy to read and parse XML that does not require knowledge of the underlying information model.

Green CDA aims to do that - the simplicity of CCR XML tagging with the expandability and modeling of CDA.    However, there is a controversy.  What do we send on the wire - full CDA or Green CDA?

At the November HIT Standards Committee meeting we endorsed moving forward with GreenCDA as the single over the wire format.

It's likely that existing users of full CDA over the wire will be concerned about the costs and effort required to move to Green CDA on the wire.

Robert Worden, an expert on HL7 mapping tools, wrote a great summary that explains the path forward through the use of transforms:

"There is now tooling which can define a Green CDA and generate 100% reliable transforms to full CDA, all in the same step.  That tooling is being used in the UK for the NHS Interoperability Toolkit; and it has been linked to MDHT, so it could be used to Green consolidated CDA and generate the transforms.

Once you have reliable, maintainable transforms, the question “Green CDA or full CDA on the wire?” becomes much less crucial. Any organization, such as ONC, which wishes to endorse Green CDA over the wire (to make life much easier for implementers), can do so, provided they make the transforms readily available. Then, people can use Green CDA over the wire – but anyone who prefers to receive full CDA can always do so, by applying the transform to the Green CDA he receives. RIM experts and non-experts can both be happy.

It is like using banknotes instead of gold for currency, as has been done for several hundred years. Using gold bars for every transaction would be very clumsy, so people used notes which were backed by gold. The bank “promises to pay the bearer on demand” the equivalent in gold. Similarly the Green=>full transform “promises to pay the bearer on demand” a full CDA, if he wants it.

HL7 has now realized that its CDA gold bars are rather clunky, and should encourage the use of banknotes, backed by its RIM-based gold semantics. CDA is the reserve currency, and Green CDAs are the banknotes that people want to use (but counterfeit notes, not backed by the gold transforms, would be worthless!)."

Green CDA over the wire is the right future state.  Transforms will help us get there without requiring stakeholders to rip and replace what they have already built.

We have a plan!

5 comments:

Grahame Grieve said...

The problem with this is, "which greenCDA"?

Keith W. Boone said...

John, respectfully, that's not a plan, that's an idea. Plans include schedules and resources, with well-understood time frames.

GreenCDA as Graham points out, is not a definitive standard, but rather a process for simplifying CDA. That process has yet to be automated. It has only be executed once, mostly manually on the HITSP C32. The automation step is needed over the CDA Consolidation work, and that is but ONE step of the plan to be figured out before the idea put forth can be executed (there are other dependencies as well).

Grahame Grieve said...

I should've provided a reference that clarifies more: http://www.healthintersections.com.au/?p=480

David said...

John, thanks for explaining your ideas. I'll have more thoughts on Green "over the wire" (vs. as a generator of normative CDA) later, but I'd like to give more credit to Consolidated CDA, which did much more than simplify C32 CCD. It also harmonized and combined many other CDA sections and document types (Discharge Summary, Operative Note, several others) that go far beyond C32 CCD. So whereas C32 contained only 17 sections, Consolidated CDA contains a library of 58 sections covering many concepts that can't be handled by CCD alone. To handle all the use cases, GreenCDA standards (TBD) would need to address all these sections, at least in priority order.

Will Ross said...

the great thing about data standards is that adoption, messy though it may be, trumps all debates about this pattern or that nuance. in other words, designers design the best they can, but in the end the users rule.