GeneticReport SpecimenType extension is bound to two value sets

XMLWordPrintableJSON

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

      Confirmed this problem, traced to a bug in publication tooling. Will fix in the final publication.

      Suggested Resolution: Persuasive.

      Show
      Confirmed this problem, traced to a bug in publication tooling. Will fix in the final publication. Suggested Resolution: Persuasive.
    • Richard Esmond/Kurt Allen: 10-0-1
    • Enhancement
    • Non-substantive

      In both the differential and the snapshot for GeneticReport, two value set bindings are shown:

      (1) v2 Specimen Type (example) and (2) GeneticSpecimenTypeVS (extensible)

      When navigating to the SpecimenType extension, only one binding is presented (v2 Specimen Type). The CIMPL code indicates GeneticSpecimenTypeVS was intended. It would seem something is up with the mapping…

      REF: MCODE-105

            Assignee:
            May Terry
            Reporter:
            Mark Kramer
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: