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

Add conformance statements saying when mCODE profiles must be used

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • US Minimal Common Oncology Data Elements (mCODE) (FHIR)
    • 1.0.0 [deprecated]
    • Clinical Interoperability Council
    • (many)
    • Hide

      We developed a set of requirements that specify when a resource should (or must) conform to a specific mCODE profile. These requirements are partially machine-testable and tests will be developed using INFERNO.

      We also are recommend that applications populated meta.profile as a signal that a resource is expected to conform, following requirements in both US Core and FHIR itself.

       Note this is related to FHIR-28249, which establishes an overall picture of what full system compliance with mCODE means.

      Show
      We developed a set of requirements that specify when a resource should (or must) conform to a specific mCODE profile. These requirements are partially machine-testable and tests will be developed using INFERNO. We also are recommend that applications populated meta.profile as a signal that a resource is expected to conform, following requirements in both US Core and FHIR itself.  Note this is related to FHIR-28249 , which establishes an overall picture of what full system compliance with mCODE means.
    • Russ Leftwich / May Terry: 5-0-1
    • Enhancement
    • Non-compatible

    Description

      The most important type of conformance-related statements are missing from the IG, namely, ones that require the use mCODE profiles. 

      This type of requirement has the form: If resource type = R and R.code = X, the instance SHALL conform to Y, where Y is a FHIR profile. An example is where:

      • R = Observation
      • X = LOINC code 88040-1
      • Y = the mCODE CancerDiseaseStatus profile

      The mCODE IG should explicitly list every such requirement.

      As it stands, practically any system could be judged mCODE compliant, even if that system fails to adopt mCODE profiles, because the mCODE IG never explicitly spells out situations where mCODE profiles must be used.

      Attachments

        Activity

          People

            Unassigned Unassigned
            Mark_Kramer Mark Kramer
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: