Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-30208

Allow workflow-instantiatesCanonical on Composition

    XMLWordPrintableJSON

    Details

    • Type: Change Request
    • Status: Resolved - No Change (View Workflow)
    • Priority: Medium
    • Resolution: Not Persuasive
    • Specification:
      FHIR Core (FHIR)
    • Raised in Version:
      R4
    • Work Group:
      FHIR Infrastructure
    • Related Artifact(s):
      Composition
    • Grouping:
    • Resolution Description:
      Hide

      A few issues:

      1. A single Composition can, in theory, be used as the root of many documents, each having a different subset of resources included in the Bundle (i.e. each with a distinct GraphDefinition)
      2. The semantics of "instantiatesCanonical" are about an event adhering to an order set, protocol, etc.  Not a description of what resources should be (or are?) inside a DocumentBundle. 

      If there's a desire to define a Composition that says "this is the set of resources that should be included in the Bundle when a document is generated with me as the root", that should be a different extension.  If there's a need to indicate that a specific DocumentBundle adheres to a specific GraphDefinition, that should be handled via something on Bundle.meta.  (We've talked about the possibility of Bundle.meta.profile being able to be GraphDefinition in addition to StructureDefinition, though so far, no action has been taken on this.)

      In either case, this isn't something we can back-port into R4.  So for now, a custom extension will be needed or you could possibly pre-adopt an R5-defined extension (once one is created).

      Show
      A few issues: A single Composition can, in theory, be used as the root of many documents, each having a different subset of resources included in the Bundle (i.e. each with a distinct GraphDefinition) The semantics of "instantiatesCanonical" are about an event adhering to an order set, protocol, etc.  Not a description of what resources should be (or are?) inside a DocumentBundle.  If there's a desire to define a Composition that says "this is the set of resources that should be included in the Bundle when a document is generated with me as the root", that should be a different extension.  If there's a need to indicate that a specific DocumentBundle adheres to a specific GraphDefinition, that should be handled via something on Bundle.meta.  (We've talked about the possibility of Bundle.meta.profile being able to be GraphDefinition in addition to StructureDefinition, though so far, no action has been taken on this.) In either case, this isn't something we can back-port into R4.  So for now, a custom extension will be needed or you could possibly pre-adopt an R5-defined extension (once one is created).
    • Resolution Vote:
      Jose Costa Teixeira/Ryan Moehrke: 7-0-1

      Description

      The workflow-instantiatesCanonical extension is allowed in many places, but not on Composition (even though it is allowed on DocumentReference). This is needed in the case that a GraphDefinition was used to construct a Composition (see [Composition Examples](http://build.fhir.org/ig/HL7/cqf-recommendations/examples.html#composition-index) in the CPG IG for examples of use).

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            bryn.rhodes Bryn Rhodes
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:
              Vote Date: