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

US Core heart-rate example is not conformant to http://hl7.org/fhir/StructureDefinition/heartrate

    XMLWordPrintableJSON

    Details

    • Type: Technical Correction
    • Status: Published (View Workflow)
    • Priority: Medium
    • Resolution: Persuasive
    • Specification:
      US Core (FHIR)
    • Raised in Version:
      3.1.0
    • Work Group:
      Cross-Group Projects
    • Related Page(s):
      (NA)
    • Grouping:
    • Resolution Description:
      Hide

      remove '

      {beats}' from the valueQuantity code value
      change '{beats}

      /min' to 'beats/min' in the valueQuantity unit's unit value

      Show
      remove ' {beats}' from the valueQuantity code value change '{beats} /min' to 'beats/min' in the valueQuantity unit's unit value
    • Change Category:
      Correction

      Description

      https://www.hl7.org/fhir/us/core/Observation-heart-rate.xml.html includes a heart rate like:

        <valueQuantity>
          <value value="44.0"/>
          <unit value="{beats}/min"/>
          <system value="http://unitsofmeasure.org"/>
          <code value="{beats}/min"/>
        </valueQuantity>
      

      This conflicts with https://www.hl7.org/fhir/heartrate.html which indicates that the code value must have the fixed value /min.

      I've read https://chat.fhir.org/#narrow/stream/179166-implementers/topic/UCUM.20bpm.20-.20heart.20rate.20at.20wrist and I understand that these are really the same concept in UCUM, but our systems do not.

      I also read https://jira.hl7.org/browse/FHIR-13573 and I believe that FHIR-I made the wrong decision on that one... we would prefer a fixed string of "{beats}/min" vs "/min", even if the "{beats}" is just for humans.

      However, assuming that ship has sailed, I think US Core should live with that decision and update this sample to have a code value of "/min".

        Attachments

          Activity

            People

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

              Dates

              Created:
              Updated:
              Resolved: