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.

Thursday, April 9, 2015

IHE Clinical Mapping Profile

We completed the standards selection process for the IHE Clinical Mapping profile today. The purpose of this profile is to support mapping of terminologies from one system to another.  We have two use cases for this profile which we are working together with PCD on this year:

  1. PCD's use case involves mapping from IEEE Medical Device Codes to LOINC, for the purpose of translating from IEEE vocabularies into LOINC vocabularies for Vital Signs.  This supports, for example, the need of organizations which must report vital signs values in LOINC, as is proposed in the 2015 Certification critiera.
  2. PCC's use case involves translation of SNOMED CT codes for clinical use to ICD-10 codes for billing.
We plan on having two (or possibly three) transactions in this profile.

The first transaction relies on the FHIR $translate operation on the ConceptMap resource.  In this transaction, you would specify the input code, and some optional context (in an extension to the $translate operation).  The output would be the concept in the target vocabulary.  

We haven't decided whether or not to also incorporate the $batch operation from this resource, this would be the "possibly third" transaction.

We will have an optional transaction from the Clinical Mapper to support download of the ConceptMap resource, so that the translation could be performed locally.  The reason that this is optional is because some translations can be readily supported and implemented algorithmically from the ConceptMap data, while other translations (e.g., SNOMED-CT to ICD-10) might not be as simply represented or implemented.  This option would apply to both actors in this profile.

So now we have two profiles in PCC which are planning on using FHIR DSTU-2 content.