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

Clarify MustSupport for Observaiton.component.value[x] vs dataAbsentReason

    XMLWordPrintableJSON

Details

    • Change Request
    • Status: Published (View Workflow)
    • Medium
    • Resolution: Persuasive with Modification
    • US Core (FHIR)
    • 4.0.0
    • Cross-Group Projects
    • Blood Pressure Example
      US Core Pulse Oximetry Profile
    • Profiles and Extensions
    • Mandatory and Must Support Data Elements
    • Hide

      Background:

      1) In the general case where the components are must support (min = 0): for example Pulse Ox Profile 

      Because the components are must support (min = 0)

      A server that always values Pulse-Ox + FlowRate + Concentration does not need to support DAR.

      A server that values Pulse-Ox without FlowRate may OMIT FlowRate and/or Concentration, or provide a DAR. The cardinality of the component is 0..*.

       

      2) In the exceptional case where the component are mandatory ( min => 1)for  US Core Blood Pressure:

      Even a server that always values diastolic and systolic  needs to support DAR  because the component are mandatory ( min => 1) the invariant vs-3 "Observation.component If there is not a value a data absent reason must be present" 

      Proposal:

      Will clarify in guidance.

       

      Show
      Background: 1) In the general case where the components are must support (min = 0) : for example Pulse Ox Profile  Because the components are must support (min = 0) A server that always values Pulse-Ox + FlowRate + Concentration does not need to support DAR. A server that values Pulse-Ox without FlowRate may OMIT FlowRate and/or Concentration, or provide a DAR. The cardinality of the component is 0..*.   2) In the exceptional case where the component are mandatory ( min => 1)for  US Core Blood Pressure: Even a server that always values diastolic and systolic  needs to support DAR  because the component are mandatory ( min => 1) the invariant vs-3 "Observation.component If there is not a value a data absent reason must be present"  Proposal: Will clarify in guidance.  
    • Eric Haas/Brett Marquard: 22-0-1
    • Enhancement
    • Non-substantive

    Description

      US Core 4.0 added guidance that "Systems that never provide an observation without a value are not required to support Observation.dataAbsentReason"

      It is not clear if the same guidance applies to profiles with MS `Observation.component`, specifically in pulse-ox and bp profiles

      For example, if a server never provide pulse-ox without FlowRate component, does server still required to support Observation.dataAbsentReason and/or Observation.component(for FlowRate).dataAbsentReason?

       

      Attachments

        Activity

          People

            ehaas Eric Haas
            yunwwang Yunwei Wang
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: