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

Level of Precision/Rounding and Unit of Measure

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • FHIR Core (FHIR)
    • R6
    • Clinical Quality Information
    • Measure
    • Hide

      The Measure resource already has a scoringUnit element that supports specifying the expected UCUM unit for the score:

      https://hl7.org/fhir/R5/measure-definitions.html#Measure.scoringUnit

      There is also an R4 extension defined in the QM IG that can be used for this purpose.

      Scoring precision, however, is not currently supported.

      Propose adding:

      scoringPrecision positiveInt 0..1 How many decimals (The number of decimal places to include in the score when the score is a decimal-valued result)

      Also recommend adding a tracker to QM IG and possibly SANER to support specifying precision using an extension (or pre-adopting the new R6 element?)

      Show
      The Measure resource already has a scoringUnit element that supports specifying the expected UCUM unit for the score: https://hl7.org/fhir/R5/measure-definitions.html#Measure.scoringUnit There is also an R4 extension defined in the QM IG that can be used for this purpose. Scoring precision, however, is not currently supported. Propose adding: scoringPrecision positiveInt 0..1 How many decimals (The number of decimal places to include in the score when the score is a decimal-valued result) Also recommend adding a tracker to QM IG and possibly SANER to support specifying precision using an extension (or pre-adopting the new R6 element?)
    • Juliet Rubini/Bryn Rhodes: 25-0-0
    • Enhancement
    • Compatible, substantive

    Description

      There is no clarity what level of precision/rounding the MeasureReport.group.measureScore should be expressed, or when to express it as a percentage or fraction.  While that could be in the Measure.definition or Measure.guidance, that is not computable.

      Propose to add .scoringPrecision that indicates the number of decimals to include, and .scoringUnitOfMeasure or simply .scoringPercentage as a boolean enabling automatic population of the desired value.

      Attachments

        Activity

          People

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

            Dates

              Created:
              Updated:
              Resolved: