Relax cardinality on GenomicsReport category

XMLWordPrintableJSON

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

      DiagnosticReport.category was constrained on purpose to 1..1 for backwards compatibility to US Core DSTU2, which some mCODE implementers want to support, and for consistency so that one mCODE logical model can map to both FHIR US Core STU3 and US Core DSTU2.

      We will further explore relaxing cardinality if there is a compelling use case and if there are systems which send multiple categories in a DiagnosticReport instance.

      Proposed Resolution: Persuasive

      Show
      DiagnosticReport.category was constrained on purpose to 1..1 for backwards compatibility to US Core DSTU2, which some mCODE implementers want to support, and for consistency so that one mCODE logical model can map to both FHIR US Core STU3 and US Core DSTU2. We will further explore relaxing cardinality if there is a compelling use case and if there are systems which send multiple categories in a DiagnosticReport instance. Proposed Resolution: Persuasive
    • Richard Esmond/Kurt Allen: 10-0-1
    • Enhancement
    • Non-substantive

      DiagnosticReport.category allows for multiple categories in R4. Why are you resticting it to one? You can require that one of them to be GE, but also allow for other categories like LAB.

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

              Created:
              Updated:
              Resolved: