Removal of component element from mCode BodyHeight profile breaks conformance with base BodyHeight profile. - MCODE #108

XMLWordPrintableJSON

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

      See 10/12/19 comments from Mark Kramer.

      Proposed resolution: Not Persuasive with Mod.

      Show
      See 10/12/19 comments from Mark Kramer. Proposed resolution: Not Persuasive with Mod.
    • MayTerry/Richard Esmond: 14-0-0
    • Correction
    • Compatible, substantive

      Existing Wording: component 0..0

      Comment:

      Profile description says "this profile builds on observation-bodyheight". If this is intended to say that the mCode BodyHeight profile is conformant to observation-bodyheight, then this is incorrect. The "base" BodyHeight profile http://hl7.org/fhir/R4/bodyheight.html has Observation.component 0..* as MustSupport, so an implementer is allowed to send this value; an implementer of mCode would reject a message if it contained Observation.component, breaking conformance.

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

      Summary:

      Removal of component element from mCode BodyHeight profile breaks conformance with base BodyHeight profile.

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

              Created:
              Updated:
              Resolved: