Removal of dataAbsentReason element from mCode BP profile breaks conformance with base BP profile. - MCODE #107

XMLWordPrintableJSON

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

      The words "vice versa" are incorrect. The correct statement is that any instance that conforms to the current profile also will conform to the FHIR profile.

      We disagree with the specific example provided by the voter, however. Child profiles can only add constraints to their parent profiles. Changing cardinality from 0..1 to 0..0 is permitted, but not the reverse. An mCODE-compliant resource that omits an element because the mCODE profile restricts it to 0..0 does indeed comply with its parent profile if the parent profile allows 0..1 occurrences of the element.

      Regardless, based on the approved ballot proposal in GF#24526, we will be eliminating the mCODE vital sign profiles, and instead, refer to the vital sign profiles provided in the base FHIR standard ( http://hl7.org/fhir/bp.html ).

      Proposed resolution: Persuasive with mod (delete profile)

      Show
      The words "vice versa" are incorrect. The correct statement is that any instance that conforms to the current profile also will conform to the FHIR profile. We disagree with the specific example provided by the voter, however. Child profiles can only add constraints to their parent profiles. Changing cardinality from 0..1 to 0..0 is permitted, but not the reverse. An mCODE-compliant resource that omits an element because the mCODE profile restricts it to 0..0 does indeed comply with its parent profile if the parent profile allows 0..1 occurrences of the element. Regardless, based on the approved ballot proposal in GF#24526, we will be eliminating the mCODE vital sign profiles, and instead, refer to the vital sign profiles provided in the base FHIR standard  (   http://hl7.org/fhir/bp.html   ). Proposed resolution: Persuasive with mod (delete profile)
    • Richard Esmond/Kurt Allen: 10-0-1
    • Correction
    • Compatible, substantive

      Existing Wording: dataAbsentReason 0..0

      Comment:

      Conformance note "any BloodPressure that conforms to the current profile also will conform to the FHIR profile, and vice versa." is incorrect. The "base" BP profile http://hl7.org/fhir/bp.html the Observation.dataAbsentReason is a MustSupport field of 0..1, so an implementer is allowed to send Observation.dataAbsentReason; an implementer of mCode would reject a message if it contained Observation.dataAbsentReason element, breaking the conformance note.

      We have found two such examples, but there may be many more that need to be reviewed.

      Summary:

      Removal of dataAbsentReason element from mCode BP profile breaks conformance with base BP profile.

            Assignee:
            May Terry
            Reporter:
            Ken Sinn
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: