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

How mCODE Inherits from US Core

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • US Minimal Common Oncology Data Elements (mCODE) (FHIR)
    • Clinical Interoperability Council
    • Profile Conformance
    • Hide

      US rules and regulations now require US Core. As US Core evolves, mCODE has had to re-evaluate the parent classes of certain profiles. For example, in US Core 5.0 there are now two profile on Condition instead of one, and involve different categories (Condition.category), and a new profile for clinical examination results. To maintain alignment, the parent profiles of KarnofskyPerformanceStatus and ECOGPerformanceStatus were switched from Observation to the newly-introduced US Core Observation Clinical Test Result Profile

      Another issue is that there is no US Core generic observation profile in 5.0. Observations that can in different circumstances derive from clinical examination, imaging, or laboratory results do not cleanly fall into any US Core profile's catchment. This is the case with CancerDiseaseStatus. In addition, certain profiles will not inherit from US Core, for example, those that come from the Genomics Reporting IG or do not fit a US Core profile. These will have to be explicitly waived by FMG. 

      Show
      US rules and regulations now require US Core. As US Core evolves, mCODE has had to re-evaluate the parent classes of certain profiles. For example, in US Core 5.0 there are now two profile on Condition instead of one, and involve different categories (Condition.category), and a new profile for clinical examination results. To maintain alignment, the parent profiles of KarnofskyPerformanceStatus  and  ECOGPerformanceStatus  were switched from Observation to the newly-introduced  US Core Observation Clinical Test Result Profile .  Another issue is that there is no US Core generic observation profile in 5.0. Observations that can in different circumstances derive from clinical examination, imaging, or laboratory results do not cleanly fall into any US Core profile's catchment. This is the case with CancerDiseaseStatus. In addition, certain profiles will not inherit from US Core, for example, those that come from the Genomics Reporting IG or do not fit a US Core profile. These will have to be explicitly waived by FMG. 
    • Jim McClay/Saul Kravitz :8-0-0
    • Correction
    • Non-compatible
    • current

    Description

      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?

      Attachments

        Activity

          People

            may_terry May Terry
            Mark_Kramer Mark Kramer
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: