Observation.hasMember Vital Signs Panel Profile Reference Choice

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Highest
    • US Core (FHIR)
    • 3.1.1
    • Cross-Group Projects
    • Vitals-panel [deprecated]
    • Hide

      1) We will develop a base US Core Vital Signs profile

      2) derived individual vital measurement profile as in the base ( Height, Weight, etc ) Excluding the vitals Panel,

      3) as dispositioned in FHIR-23890 limit the value[x] choices for the base US Core Vital Signs profile

      4) as dispositioned in FHIR-23890 limit the effective[x] choices for all US Core Vital  profiles

      5) limit the subject Must Support to US Core Patient while allowing other references

      6) remove the hasMember and deriveFrom element as optional

      Show
      1) We will develop a base US Core Vital Signs profile 2) derived individual vital measurement profile as in the base ( Height, Weight, etc ) Excluding the vitals Panel, 3) as dispositioned in FHIR-23890 limit the value [x] choices for the base US Core Vital Signs profile 4) as dispositioned in FHIR-23890 limit the effective [x] choices for all US Core Vital  profiles 5) limit the subject Must Support to US Core Patient while allowing other references 6) remove the hasMember and deriveFrom element as optional
    • Brett Marquard/Eric Haas: 5-0-4
    • Correction
    • Compatible, substantive

      In context of https://jira.hl7.org/browse/FHIR-28375 we propose that the Data Type list be limited to Observation while also indicating that MolecularSequence and QuestionnaireReponse are not supported.

      MolecularSequence is not an appropriate choice for vital signs as vital signs are not biological sequences, and would not be members of a vital sign or vital sign panel. 

      QuestionnaireResponse is not appropriate either for capturing individual vital signs as that is done by way of observations.  The Observation resource is used primarily for capturing data elements that are "true" observations - lab measurements, vital signs and allows for easy inclusion of reference ranges and interpretations.

      The Vital Signs is in STU status without clear Must Support guidance, thus too immature to include fully as a Must Support in its current state.

      As the FHIR US Core profile is used for accessing and exchanging data based on what the source system has, this should not require the data source system to add functionality to capture a patient as part of the provenance.  Additionally, C-CDA does not impose this requirement either.

      While this JIRA is posted to US Core/Cross-Project Workgroup, we strongly urge the project to work with the Orders & Observations workgroup and FMG to resolve how to ease the restrictions put in the base profile to accommodate US Core requirements.

      Links to pages:

      http://hl7.org/fhir/us/core/STU3.1/index.html

      https://build.fhir.org/ig/HL7/US-Core-R4/index.html

      http://hl7.org/fhir/R4/observation-vitalsigns.html

            Assignee:
            Unassigned
            Reporter:
            Hans Buitendijk
            Andrew Torres, Hans Buitendijk
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: