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

References specific extension for measurement protocol

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • US Core (FHIR)
    • 7.0.0-ballot
    • Cross-Group Projects
    • US Core Average Blood Pressure Profile
    • Hide

      Background

      While we agree with the commenter that it would be ideal to reference a specific standard FHIR extension, there is no single choice or consensus on which one is preferred.  The extension the commenter references uses codes to define protocols and references an extensible binding with a single concept.  We think more appropriate choices for protocols include these FHIR standard extensions:

      1. http://hl7.org/fhir/StructureDefinition/workflow-adheresTo
      2. *http://hl7.org/fhir/StructureDefinition/workflow-instantiatesUri*
      3. http://hl7.org/fhir/StructureDefinition/workflow-instantiatesCanonical

      ... and for number of measurements: 

      1. CardX  “Number of Measurements” Extension: http://hl7.org/fhir/uv/cardx-htn/StructureDefinition/NumberOfMeasurementsExt

       

      Tentative Decision ( Needs Discussion):

      1. For protocols, update the Profile Specific Implementation Guidance bullet to:

      • from FHIR extensions pack

       

       

      • the other FHIR standard listed are deprecated in future versions of FHIR?

      2. for number of measurements, use a component to represent the count. 

        • Issues: no standard LOINC or SNOMED CT code for the concept "number of measurements". ( Need to check HL7 vocabularies)
          • average = sum of measures/number of measurements
        • value is integer
        • the benefit of being an inline element, not an extension.
        • no MS or Additional USCDI Extension
        • update examples
      Show
      Background While we agree with the commenter that it would be ideal to reference a specific standard FHIR extension, there is no single choice or consensus on which one is preferred.  The extension the commenter references uses codes to define protocols and references an extensible binding with a single concept.  We think more appropriate choices for protocols include these FHIR standard extensions: http://hl7.org/fhir/StructureDefinition/workflow-adheresTo * http://hl7.org/fhir/StructureDefinition/workflow-instantiatesUri* http://hl7.org/fhir/StructureDefinition/workflow-instantiatesCanonical ... and for number of measurements:  CardX  “Number of Measurements” Extension: http://hl7.org/fhir/uv/cardx-htn/StructureDefinition/NumberOfMeasurementsExt   Tentative Decision ( Needs Discussion): 1. For protocols, update the Profile Specific Implementation Guidance bullet to: Information about the protocol  SHOULD  be supplied in either: Observation.note.text  (for example, “24-hour ambulatory measurement.”) the standard FHIR extension http://hl7.org/fhir/StructureDefinition/workflow-adheresTo   from FHIR extensions pack     the other FHIR standard listed are deprecated in future versions of FHIR? 2. for number of measurements, use a component to represent the count.  Issues: no standard LOINC or SNOMED CT code for the concept "number of measurements". ( Need to check HL7 vocabularies) average = sum of measures/number of measurements value is integer the benefit of being an inline element, not an extension. no MS or Additional USCDI Extension update examples
    • Eric Haas/Hans Buitendijk: 38-0-4
    • Enhancement
    • Compatible, substantive

    Description

      The Profile Specific Implementation Guidance states:

      • Information about the protocol or number of measurements used to determine the averages SHOULD be supplied in either:
        • Observation.note.text (for example, “24-hour ambulatory measurement.”)
        • a component observation in Observation.component
        • an extension

      Rather than referencing any extension, considering the availability of the measurement protocol extension, we suggest to replace "an extension" with "the measurement protocol - http://hl7.org/fhir/us/vitals/StructureDefinition/MeasurementProtocolExt"

       

      That still leaves with the "SHOULD" the opportunity to use another extension, but starts to align with already available extensions that support this capability.

      Attachments

        Activity

          People

            Unassigned Unassigned
            hbuitendijk Hans Buitendijk
            Hans Buitendijk
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: