Uploaded image for project: 'Project Scope Statements/Proposals'
  1. Project Scope Statements/Proposals
  2. PSS-2085

Create Profiles on Bundle and Composition to match the rules of CDA

    XMLWordPrintableJSON

Details

    • Icon: Project Proposal Project Proposal
    • Resolution: Done
    • Icon: Medium Medium
    • None
    • Structured Documents
    • Unknown
    • Create Profiles on Bundle and Composition to match the rules of CDA to be incorporated into base FHIR.

    Description

      Organization: CDA Management Group

      Resourcing: TBD - Needs to be discussed with HL7.

      Timeline: TBD - Based on resourcing.

      Priority: The priority of this project is HIGH because it is crucial for the planned roadmap for CDA, which is following the direction set by HL7 for all product families to align with FHIR.

      CMG has identified the need to create profiles on Bundle and Composition to facilitate alignment between CDA & FHIR.

      This is necessary because these resources are generalized in FHIR for many use cases and don't include specific guidance needed to explain how they should be used in a way consistent with CDA.

      Example: The CDA standard identifies specific participations and act relationships that should be expressed in the header of CDA documents.  The FHIR composition resource needs to be profiled to match these requirements.  e.g. Legal Authenticator, authenticator, informationRecipient, data enterer, etc. are all roles in CDA document header, and we need guidance to how they get represented in FHIR composition resources.

      In FHIR, the Bundle resource, when of type document, is used to represent documents.  This concept doesn't exist in CDA, so guidance is required to explain to implementers how to populate a Bundle resource.   

      Deliverable: This project will create profiles on the Bundle and Composition resources which can be included as default profiles within FHIR.  Similar to the Vital Sign profile on observation, which comes with the base standard.

      Attachments

        Activity

          People

            Unassigned Unassigned
            jiraadmin Jira Admin
            Watchers:
            21 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: