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

Add ‘type’ as a field or extension to Annotation Element

    XMLWordPrintableJSON

Details

    • Change Request
    • Resolution: Not Persuasive
    • Medium
    • FHIR Core (FHIR)
    • R4
    • Modeling & Methodology
    • Datatypes
    • Hide

      We believe that there are three use cases for Annotation types:
      1) where the type of the Annotation is specified by the context of the Resource data element, eg. MedicationRequest.dispenseRequest.dispenserInstruction
      2) where the type of the Annotation is not necessary
      3) where the type of the Annotation is not specified by the context of the Resource data element but is necessary for some use cases, eg MedicationRequest.note

      For #1 and #2 an Annotation.type does not make sense.
      For #3, we believe that it makes more sense for the Resource data element to be a Backbone that includes a context-specific value set of types and the Annotation itself.  This appears to make more sense than having a non-context-specific coded type element in Annotation.  Alternately, an implementation guide could specify an IG-specific extension to convey the type of Annotation.

       

      Show
      We believe that there are three use cases for Annotation types: 1) where the type of the Annotation is specified by the context of the Resource data element, eg. MedicationRequest.dispenseRequest.dispenserInstruction 2) where the type of the Annotation is not necessary 3) where the type of the Annotation is not specified by the context of the Resource data element but is necessary for some use cases, eg MedicationRequest.note For #1 and #2 an Annotation.type does not make sense. For #3, we believe that it makes more sense for the Resource data element to be a Backbone that includes a context-specific value set of types and the Annotation itself.  This appears to make more sense than having a non-context-specific coded type element in Annotation.  Alternately, an implementation guide could specify an IG-specific extension to convey the type of Annotation.  
    • Grahame Grieve / Lloyd McKenzie: 5-0-0

    Description

      Currently there is no way to differentiate the type of note within the Annotation element. For some resources like MedicationRequest, it would be helpful to understand the type of note when multiple notes are present. In the ePrescribing workflow there is need to differentiate between a Physicians order comment versus a Note to the pharmacy. The request is for a field  or extension of ‘type’ that is a CodeableConcept be added to the Annotation element.

      Attachments

        Issue Links

          is duplicated by

          Change Request - A request for a change that is more than a simple Technical Correction to one of HL7's specifications FHIR-22102 Annotation doesn't has a type/code

          • Medium - Has the potential to affect progress.
          • Duplicate
          mentioned in

          Page Loading...

          Activity

            People

              Unassigned Unassigned
              fp4633 Fran Pivonka
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: