Instead of onco-core-RegionStudied-extensionuse another slice on result with a reference to CG IG Regionstudied profile - MCODE #33

XMLWordPrintableJSON

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

      obs-region-studied as an extension was a left-over from the initial design based on the DSTU2-based version of the CG Genomics Reporting IG.

      Per discussion at the Sept 2019 WGM CG Tuesday Q3 session, we agreed to move onco-core-RegionStudied to another slice in Observation.result, aligned with the CG IG genomics-report profile.

      Although, in alignment with GF#[23999|], we will work with the CGWG towards a mutually acceptable design which allows mCODE generated FHIR instances to at least validate against the CG profiles with minimal changes rather than be a direct derivation of the CG Reporting IG profiles.

      Proposed Resolution: Persuasive with Mod

      Show
      obs-region-studied as an extension was a left-over from the initial design based on the DSTU2-based version of the CG Genomics Reporting IG. Per discussion at the Sept 2019 WGM CG Tuesday Q3 session, we agreed to move onco-core-RegionStudied to another slice in Observation.result, aligned with the CG IG genomics-report profile. Although, in alignment with GF# [23999|] , we will work with the CGWG towards a mutually acceptable design which allows mCODE generated FHIR instances to at least validate against the CG profiles with minimal changes rather than be a direct derivation of the CG Reporting IG profiles. Proposed Resolution: Persuasive with Mod
    • Richard Esmond/Kurt Allen: 10-0-1
    • Enhancement
    • Compatible, substantive

      Comment:

      http://hl7.org/fhir/us/mcode/2019SEP/StructureDefinition-onco-core-GenomicsReport.html uses a regionstudied extension onco-core-RegionStudied-extension

      URL: http://hl7.org/fhir/us/mcode/StructureDefinition/onco-core-RegionStudied-extension instead use another slice on result with a reference to an instance of the CG IG Regionstudied profile http://build.fhir.org/ig/HL7/genomics-reporting/obs-region-studied.html

      Also, why not profile from the CG IG diagnostic Report (http://build.fhir.org/ig/HL7/genomics-reporting/diagnosticreport.html)? Are the US-CORE elements the reason? Similar to comments elsewhere, see if there is a reasonable way to add the US-core extensions to a profile of CG IG artifacts which allows referencing both profiles. The extensions have names and urls that allow you to know that the element is the same as in US -core, components will have the same component.code value.

      Summary:

      Instead of onco-core-RegionStudied-extensionuse another slice on result with a reference to CG IG Regionstudied profile

            Assignee:
            May Terry
            Reporter:
            bheale
            bheale, Bob Milius, clemmcdonald
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: