Skip to end of metadata
Go to start of metadata


Publication Request

Publication Request

1. Published Name of the Standard for which request is being made

HL7 FHIR® Implementation Guide: C-CDA on FHIR, Release 2

2. Standards Material/Document

Unballoted STU Update

3. Date of Request

Sep 21, 2020

4. Use Period

5. Reason for extension, timeline, and actions

6. Original Publication Date

7. End date of the current STU period

Feb 12, 2022

8. Length of the requested extension

9. Review Process

Peer review

10. HL7 Work Group making this request and date

SDWG/2019-07-25

10a. Requesting WG Date

Jul 25, 2019

11. URL of approval minutes

https://confluence.hl7.org/display/SD/2019-07-25+Agenda+and+Minutes

12. HL7 Product Management Group

FMG

12a. Management Group Date of Approval

Aug 26, 2020

13. URL of approval minutes

https://confluence.hl7.org/pages/viewpage.action?pageId=91984601

14. Is the artifact ready for final publication?

Yes

15. If not ready, please describe remaining steps.

16. Tool name used to produce the machine processable artifacts in the IG

Trifolia on FHIR

17. The name of the “IG artifact” within the context of the above mentioned tool.

ccda

18. Balloted Name of the standard for which request is being made

19. Requested name for published standard

20. If CMET, list IDs balloted

21. Project Insight Number

1122

22. Document Realm

US

23. Ballot cycle in which the document was successfully balloted

2017-01

24. Results of that ballot (following reconciliation activities):

24. Results of that ballot (following reconciliation activities):

(not needed for errata, STU extension, or unballoted STU update)

25. Affirmative

26. Negative

27. Abstentions

28. Not Returned

29. Total in ballot pool

30. Date on which final document/standards material was supplied to HQ

Feb 13, 2020

31. URL of publication material/ SVN repository

https://github.com/HL7/ccda-on-fhir-r4

32. Publishing Facilitator

Rick Geimer

33. Special Publication Instructions

34. URL of ballot reconciliation document

N/A

35. Has the Work Group posted its consideration of all comments received in its reconciliation document on the ballot desktop?

36. Substantive Changes Since Last Ballot?

Yes

37. Product Brief Reviewed By

38. Date Product Brief Reviewed

Aug 26, 2020

39. Has the Product Brief changed?

Product Brief

Product Brief

40. Family

41. Section

Implementation Guides

42. Topic

Medical Records Patient Care Patient Referral

43. Please Describe the Topic

44. Product Type

Implementation Guide

45. Parent standard

46. Parent Standard Status

47. Update/replace standard

http://www.hl7.org/fhir/us/ccda/

48. Common name/search keyword

C-CDA on FHIR, CCDA

49. Description

Consolidated CDA (C-CDA) is one of the most widely implemented implementation guides for CDA and covers a significant scope of clinical care. Its target of the ‘common/essential’ elements of healthcare is closely aligned with FHIR’s focus on the ‘80%’. There is significant interest in industry and government in the ability to interoperate between CDA and FHIR and C-CDA is a logical starting point. Implementers and regulators have both expressed an interest in the ability to map between FHIR and C-CDA.

This Implementation Guide (IG) defines a series of FHIR profiles on the Composition resource to represent the various document types in C-CDA. This release does not directly map every C-CDA template to FHIR profiles, rather tries to accomplish the C-CDA use case using Composition resource profiles created under this project (the equivalent of Level 2 CDA documents), and begins by linking to the profiles created under the US Core project for any coded entries that would normally be included in C-CDA sections. To have a simpler, more streamlined standard that reuses existing work and focuses on the 80% that implementers actually need in production systems, the resources of US Core represents a portion of the 80% needed for coded entries for coded entries of CCD, Care Plan & Discharge Summary).

Targets

Targets

These are categories of potential users, implementers, or other interested parties such as those that are indicated on the Project Scope Statement under “Stakeholders/Vendors/Providers”. Select those that are applicable, or suggest others:

50. Stakeholders

Clinical and Public Health Laboratories, Immunization Registries, Regulatory Agency, Standards Development Organizations (SDOs), Payors, Other (specify in text box below)

51. Vendors

EHR, PHR, Health Care IT, Clinical Decision Support Systems, Lab, HIS, Other (please specify)

52. Providers

Healthcare Institutions (hospitals, long term care, home care, mental health) Other (specify in text box below)

53. Benefits

54. Implementations/Case Studies

55. Development Background







This publication request was blocked by FMG, requesting that several things be done to the IG before publication. FMG wanted the following:

Additional pages

  • Background
  • Specification
  • Downloads

Complete Bundle example

CapabilityStatement showing that implementers must produce and consume document Bundle

RESOLVED: FMG approved updates on 2020-08-26

This publication request was voted on as part of the Pharmacist Care Plan publication request, because PCP is dependent on CCDA-on-FHIR.