Use component rather than extensions - MCODE #102

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • US Minimal Common Oncology Data Elements (mCODE) (FHIR)
    • STU3
    • Clinical Interoperability Council
    • (NA)
    • Extensions
    • Hide

      The reviewer recommends using components to represent the circumstances associated with Observations. This is interesting recommendation considering that:

      1) The FHIR specification (see http://hl7.org/fhir/R4/observation.html#gr-comp) indicates components are for "supporting results" (note results, not preconditions or circumstances). The specification does not suggest Observation.component should be used for circumstances or preconditions.

      2) The practice of representing circumstances and reconditions by extensions is reinforced by the presence of standard extensions designed specifically for capturing circumstances and/or preconditions of measurement:

      (a) A standard extension for bodyPosition of an observation: http://www.hl7.org/fhir/extension-observation-bodyposition.html

      (b) A standard extension for general preconditions: http://hl7.org/fhir/StructureDefinition/observation-precondition

      3) It is suggested that blood pressure cuff should be captured in Observation.component, but the cuff is the Observation.device, and the size of the cuff is clearly a part of the description of that device. (The same is true if DeviceMetric is used instead of Device).

      4) We believe this recommendation displays a stigma against extensions. To quote the specification, "Unlike many other specifications, there can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core simplicity for everyone."

      Although we find the suggestion to use components for circumstances and preconditions non-persuasive, we will nonetheless reconsider each observation extension to determine: (1) if can be considered a result, and hence suitable for an observation component, (2) whether we have maximized the use of standard extensions.

      Proposed resolution: Persuasive with mod

      Show
      The reviewer recommends using components to represent the circumstances associated with Observations. This is interesting recommendation considering that: 1) The FHIR specification (see http://hl7.org/fhir/R4/observation.html#gr-comp ) indicates components are for "supporting results" (note results , not preconditions or circumstances). The specification does not suggest Observation.component should be used for circumstances or preconditions. 2) The practice of representing circumstances and reconditions by extensions is reinforced by the presence of standard extensions designed specifically for capturing circumstances and/or preconditions of measurement: (a) A standard extension for bodyPosition of an observation: http://www.hl7.org/fhir/extension-observation-bodyposition.html (b) A standard extension for general preconditions: http://hl7.org/fhir/StructureDefinition/observation-precondition 3) It is suggested that blood pressure cuff should be captured in Observation.component, but the cuff is the Observation.device, and the size of the cuff is clearly a part of the description of that device. (The same is true if DeviceMetric is used instead of Device). 4) We believe this recommendation displays a stigma against extensions. To quote the specification, "Unlike many other specifications, there can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core simplicity for everyone." Although we find the suggestion to use components for circumstances and preconditions non-persuasive, we will nonetheless reconsider each observation extension to determine: (1) if can be considered a result, and hence suitable for an observation component, (2) whether we have maximized the use of standard extensions. Proposed resolution: Persuasive with mod
    • MayTerry/Richard Esmond: 14-0-0
    • Correction
    • Compatible, substantive

      Comment:

      [BloodPressureCuffSize, BodyPosition, EvidenceType, PreconditionCode, etc.] If you are conveying information about an observation that qualifies what was observed or how it was observed, you should use Observation.component, not an extension. Components are the more typical mechanism for capturing this information and are also more interoperable. Extensions are more for additional metadata about the observation that doesn't qualify the Observation.code/value.

      Specifically: BloodPressureCuffSize, BodyPosition, EvidenceType, PreconditionCode (Note that there's a standard place to capture this on Specimen), RegionStudied

      Summary:

      Use component rather than extensions

            Assignee:
            May Terry
            Reporter:
            Lloyd McKenzie
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: