Convert your FHIR JSON -> XML and back here. The CDA Book is sometimes listed for Kindle here and it is also SHIPPING from Amazon! See here for Errata.

Tuesday, March 25, 2014

Concerns in HL7

Quite a bit of time has been spent recently on many HL7 lists discussing the Concern act found in CCDA and prior specifications including the CCD, the IHE PCC Technical Framework and the HITSP C32.

This structure is based on the Patient Care Concern act, which went through "Harmonization" (The RIM modification process) in 2005/2006, but probably finished being implemented properly in the RIM sometime in 2010 or thereabouts (due to administrative rather than technical issues, and mostly dropped balls on the administrative side).

The Concern Act that the Patient Care Workgroup developed has a great deal of capability.  Current "concerns" among CCDA implementers and HL7 developers is that it is overkill for many uses, e.g., handling allergy lists.

Back in the day (2006) when it was first added to a CDA Implementation Guide (the IHE PCC Technical Framework was first to adopt it), the rationale for including it was to address two issues:

  1. Tracking who added the item to the current (allergies or problems) list.
  2. Tracking when it was added or removed.
Several have noted that this information also appears in audit logs, which is certainly a true statement. However, audit logs are not information items that are typically made available to normal users.

These two pieces of data have clinical significance.  The who tells you who added (or removed) the item from the list, so you can track down what happened.  This may be distinct from who made the observation (e.g., a DX of a disease may have come from another provider).

The question arose from Grahame's work on supporting CCDA capabilities in FHIR.  In looking through FHIR, there are two Resources of interest for Concern.  One is Condition, and the other is AllergyIntollerance.

In examining these two resources, they both support capture of "who recorded" the information and when, in the Condition case, called the Asserter, and in the Allergy case, the Recorder.  Condition also includes onset and abatement dates.  So it already has the necessary components needed to support the capabilities of Concern that are used in the wild to MY knowledge.  The allergy case is missing the onset/abatement dates, likely because of the [mistaken in my opinion] assumption that this is either not important, or that allergies never go away (Never and always are two dangerous words to use in Healthcare or in any other endeavor).  I can live without this capability in allergies because it can be added back through the extension mechanism.

So, to handle what is needed for CCDA in FHIR, applying the 80/20 rule, I'd just use Condition and AllergyIntollerance, and push all the concern pieces NOT present into extension.

    Keith

NOTE: In CDA and elsewhere in HL7 Version 3, Allergy is treated simply as a specialization of problem. While this makes sense to engineers, it makes little sense to many physicians.  This is in part why Concern is used in both places, but also because it supports the capture of information not found in Observation.



2 comments:

  1. Keith, Thanks for this important clarification. I think many (if not all) of the elements we record are assertions (by a human or a machine) and a simpler declarative logic is important. The elements you describe help. But were I representing these assertions in something like PROLOG, I'd make "asserter" and "recorder" different elements for every item (with perhaps defaults). This is probably impractical and not that useful in practice, I grant you. Wearing my physician hat, I also agree that representing an allergy as a specialization of a problem makes no sense.

    On a related note, It is very difficult for most of us to dig through HL7 documents and get to the heart of the matter. Your contributions help a great deal.

    ReplyDelete
  2. Keith,

    Good stuff as usual.

    I've reflected the spirit of what you presented above in a more "nitty gritty details" article on how to use/interpret the two concern act templates in C-CDA R1.1: http://www.cdapro.com/know/26807

    Not sure I have it right yet, but after well over 100 emails on the SDWG listserv on this in the last couple days, I think this piece of it is getting close to converging...

    ReplyDelete