Composition.type and Composition.class defintions should be improved according to the improvements made to DocumentReference.

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU1 [deprecated]
    • Structured Documents
    • STU
    • Composition
    • Hide

      Vote: 3/19/2025 SDWG

      Motion by Rick, 2nd by Brett

      Oppose: 0, Abstain: 0, For 22

      Leave the Composition.type definition as is, and update DocumentReference.type definition to match.?

      Leave Composition.class definition as is?and make DocumentReference.class match, but?append to both a note that explicitly states that this is a metadata field from XDS/MHD and point directly to those IHE specs.

      ?


      SDWG feels that the new definition of class in DocumentReference is circular (says?that the class code is the classification) and overlaps with the document type codes that one would put in Composition.type.?

      Many SDWG members feel that Composition.class should be removed from core and added as an extension to MHD, since it is not needed for the general Compositon/Document use case, certainly not by 80% of users.?

      Marking status as approved because we agreed to make a change, but we feel the tracker needs an equivalent status for Not Persuasive with Mod.?

      ?

      Show
      Vote: 3/19/2025 SDWG Motion by Rick, 2nd by Brett Oppose: 0, Abstain: 0, For 22 Leave the Composition.type definition as is, and update DocumentReference.type definition to match.? Leave Composition.class definition as is?and make DocumentReference.class match, but?append to both a note that explicitly states that this is a metadata field from XDS/MHD and point directly to those IHE specs. ? SDWG feels that the new definition of class in DocumentReference is circular (says?that the class code is the classification) and overlaps with the document type codes that one would put in Composition.type.? Many SDWG members feel that Composition.class should be removed from core and added as an extension to MHD, since it is not needed for the general Compositon/Document use case, certainly not by 80% of users.? Marking status as approved because we agreed to make a change, but we feel the tracker needs an equivalent status for Not Persuasive with Mod.? ?
    • Rick Geimer / Brett Marquard : 22-0-0
    • Enhancement
    • Non-compatible
    • DSTU1 [deprecated]

      These are the defintions for these in XDS, under the new IHE ITI TF Volume 3. These definitons are being aligned in DocumentReference and DocumentManifest under 3771

      DocumentReference.class - The class code specifying the high-level use classification of the document type (e.g., Report, Summary, Images, Treatment Plan, Patient Preferences, Workflow).

      DocumentReference.type - The type code specifies the precise type of document from the user perspective. It is recommended that the value Set be drawn from a coding scheme providing a fine level of granularity such as LOINC.

            Assignee:
            Unassigned
            Reporter:
            Brett Marquard
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: