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

Composition.type binding different from DocumentReference.type

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • FHIR Core (FHIR)
    • R5
    • Orders & Observations
    • Composition
      DocumentReference
    • Hide

      We will change the example binding to a non-C80 set populated with a reduced set of LOINC codes drawn from its document ontology. 

      Show
      We will change the example binding to a non-C80 set populated with a reduced set of LOINC codes drawn from its document ontology. 
    • Marti Velezis / Riki Merrick : 13 - 0 - 2
    • Clarification
    • Compatible, substantive
    • R5

    Description

      The preferred value set for DocumentReference.type is a superset of the preferred value set for Composition.type. There doesn't appear to be any reason for this difference; presumably both resources can catalog the same types of documents.

      Suggest unifying on a common value set.

      Attachments

        Activity

          People

            Unassigned Unassigned
            esilver Elliot Silver
            John Moehrke
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: