GenomicsReport should be derived from the HL7 Genomics Reporting IG

XMLWordPrintableJSON

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

      Noted. The mCODE IG authors were initially trying to align with the Genomics Reporting IG but could not directly reference those IGs because it contained many must-support constraints on elements which the primary target audience of mCODE (EHRs) did not need.

      We will however work more actively with the CGWG to find better alignment with the Genomics Reporting IG for the next release.

      The result might not be a direct derivation of the CG profiles. Rather, we will work towards a design which allows mCODE generated FHIR instances to validate against the CG profiles with minimal changes.

      -------

      Proposed resolution: Persuasive with Mod

      Show
      Noted. The mCODE IG authors were initially trying to align with the Genomics Reporting IG but could not directly reference those IGs because it contained many must-support constraints on elements which the primary target audience of mCODE (EHRs) did not need. We will however work more actively with the CGWG to find better alignment with the Genomics Reporting IG for the next release. The result might not be a direct derivation of the CG profiles. Rather, we will work towards a design which allows mCODE generated FHIR instances to validate against the CG profiles with minimal changes. ------- Proposed resolution: Persuasive with Mod
    • May Terry/Richard Esmond: 11-0-0
    • Correction
    • Compatible, substantive

      GenomicsReport should be derived from the HL7 Genomics Reporting IG, (http://hl7.org/fhir/uv/genomics-reporting/StructureDefinition/diagnosticreport). Differential views should be based on that. Please don't create competing genomics standards in HL7 FHIR. Work with the CG workgroup so that the specification they are developing can satisfy your use case. (I know you've already started talking with them).

            Assignee:
            May Terry
            Reporter:
            Bob Milius
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: