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

RiskAssessment-probability search param maps Range to number

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • FHIR Core (FHIR)
    • R4
    • Clinical Decision Support
    • RiskAssessment
    • Hide

      Change probability to be a choice of Quantity | Range, rather than a decimal. Update the invariant to require that the Quantity be a percentage, just like the percentages in the Range.

      In addition, update the type of the probability search parameter to be a quantity, not a number.

      Show
      Change probability to be a choice of Quantity | Range, rather than a decimal. Update the invariant to require that the Quantity be a percentage, just like the percentages in the Range. In addition, update the type of the probability search parameter to be a quantity, not a number.
    • Juliet Rubini/Stan Rankins: 12-0-1
    • Correction
    • Non-compatible

    Description

      Note:  This is a copy of FHIR-25174 which was closed as not persuasive (incorrectly in my opinion).  We discussed the issue on a CDS conference call and resolved to open a new issue instead of reopening that one.

      -------

      According to http://build.fhir.org/search.html#table the data type 'Range' should map to search parameters of type 'quantity'.

      However, the RiskAssessment-prediction search parameter has an expression like "RiskAssessment.prediction.probability" while this element can be either a decimal or a Range.

      Possible resolutions to this issue include:

      A. Updating the search summary table at 3.1.1.9 to mention that a Range can be mapped to a search parameter of type number; or

      B. Updating the search parameter expression to only select this element when its of type decimal (e.g.

      RiskAssessment.prediction.probability as decimal)

      Attachments

        Activity

          People

            Unassigned Unassigned
            lmsurprenant Lee Surprenant
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: