Establishing the Authenticity, Reliability, and Trustworthiness of Content Between Trading Partners

Printer Friendly, PDF & Email
Type Standard / Implementation Specification Standards Process Maturity Implementation Maturity Adoption Level Federally required Cost Test Tool Availability
Implementation Specification
Balloted Draft
Pilot
Rating 1
No
Free
No
Emerging Implementation Specification
Balloted Draft
Pilot
Feedback Requested
No
Free
No
Limitations, Dependencies, and Preconditions for Consideration Applicable Value Set(s) and Starter Set(s)
  • The first implementation specification listed is focused on data provenance representation for CDA R2 implementations and the use of CDA templates.
  • Note that the maturity level of FHIR resources may vary. The FHIR Maturity Model and each of the levels is described on the HL7 wiki.
  • The FHIR implementation specification listed leverages the W3C Provenance specification to represent HL7® support of provenance throughout its standards. It is explicitly modeled as functional capabilities in ISO/HL7 10781 EHR System Functional Model Release 2 and ISO 21089 Trusted End-to-End Information Flows. Mappings are available within the resource. 

  • See CDA & FHIR projects in the Interoperability Proving Ground.
  • Feedback requested

Comment

CDA IG needs work

Document last updated with ballot comments Release1 - Sep 30, 2015. This document has seen little use and needs further definition. As kwboone stated the FHIR definition is better suited.  For the sake of implementation there needs to be a better operational definition of provenance and at what level is this expected. Document, section, data?  From the ONC 2nd Annual Forum it was clear that the industry has not engaged with the concept of data level provenance in a way that can be shared.