Can you address how An HL7 standard that is short for Fast Healthcare Interoperability Resources and pronounced “Fire”. The standard defines a set of “Resources” that represent granular clinical concepts. The resources provide flexibility for a range of healthca... might impact Continuity of Care Document (CCD) The HL7 CCD is the result of a collaborative effort between the Health Level Seven and American Society for Testing Materials (ASTM) to “harmonize” the data format between ASTM’s Continuity of Care Record (CCR)... exchange? Will CCDs fade away, or will they coexist?
Answer from FHIR stands for Fast Healthcare Interoperable Resource. This emerging standard combines the best features of HL7 V2, HL7 V3, and CDA, while leveraging the latest web service technologies. The design of FHIR is based on RESTful web services. With REST... Governance Board Co-Chair and Corepoint Health CTO Dave Shaver:
Tags: FHIR, FHIRworks
Given that we've been trying to exchange CCDs in the U.S. for Meaningful Use environment and we're already exchanging them with the HIEs, I don't think they will go away. I do believe that we're going to be doing a lot more document exchange in the context of FHIR.
I know the guys at Lantana Group have written some interesting thoughts on that topic. In addition, if you look at the document resources that exist in FHIR, I think we could eventually end up with a version of FHIR that will replace Clinical Document Architecture (CDA) HL7 CDA uses XML for encoding of the documents and breaks down the document in generic, unnamed, and non-templated sections. Documents can include discharge summaries, progress notes, history and physical reports,... proper.
So just to kind of re-cover the question, the process we sit in with FHIR is there's currently a draft standard for trial use. The first DSTU has been published and that's what the The Argonaut Project addresses the recommendations of the JASON Task Force, a joint task force of the ONC‘s HIT Standards and Policy Committees and is a joint project between HL7 International and several vendor and provider organizations. The purp... Project is currently based around. We are in the middle of validating DSTU 2. The hope is that this is going to be complete this summer, that this is again what the Argonaut Project is hopefully going to pick up and they're going to incorporate this in their production software, which means in the next year or so people could start actually using FHIR more confidently.
I think we'll likely to call the next FHIR DSTU version 3 to avoid confusion. And then we're going to end up with FHIR version 1.0 (no longer a DSTU). The DSTU 3 is going to be very likely be released in early 2016 and then version 1.0 of the normative standard will be released mid to late 2016.