Does mCODE inherit too much from US Core?

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Considered for Future Use
    • Priority: Medium
    • US Minimal Common Oncology Data Elements (mCODE) (FHIR)
    • STU3
    • Clinical Interoperability Council
    • Profiles
    • Hide

      The current mCODE IG does require that mCODE implementers conform to US Core v3. The reviewer raises the point that implementation of US Core actually stands in the way of mCODE. Although we don't want to delay mCODE, allowing misalignments between US Core and mCODE would be moving in the wrong direction. At the same time, we suspect that some mCODE adopters will not necessarily support the full set of MustSupport flags in US Core. If this becomes a significant problem, we might add clarification about the difference between mCODE must supports and US Core must supports.

      Proposed resolution: Considered for future use.

      Show
      The current mCODE IG does require that mCODE implementers conform to US Core v3. The reviewer raises the point that implementation of US Core actually stands in the way of mCODE. Although we don't want to delay mCODE, allowing misalignments between US Core and mCODE would be moving in the wrong direction. At the same time, we suspect that some mCODE adopters will not necessarily support the full set of MustSupport flags in US Core. If this becomes a significant problem, we might add clarification about the difference between mCODE must supports and US Core must supports. Proposed resolution: Considered for future use.
    • Richard Esmond/May Terry: 12-0-1

      mCODE bases its profiles on US Core. As a result, all the US Core MustSupport flags are inherited, whether or not they must be supported from the viewpoint of mCODE. This suggests that only systems that are conformant with US Core can be mCODE conformant, which raises the bar for mCODE conformance. Does mCODE have to wait until underlying systems fully implement US Core?

      A related issue are the all the resource references in mCODE that require US Core Practitioner, US Core Organization, etc. Again, to be mCODE conformant, is it really necessary for the referenced resources to conform to US Core?

            Assignee:
            May Terry
            Reporter:
            Mark Kramer
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: