In the table the displayed name of the QICore-DeviceRequest Profile is wrong. - QUALITY #44

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • US QI Core (FHIR)
    • STU3
    • Clinical Quality Information
    • (NA)
    • 1.8.0
    • Hide

      Mapping table on QI-Core home page (http://hl7.org/fhir/us/qicore/2019Sep/index.html) will be corrected to reference the appropriate mappings - with new US Core update:Mapping table on QI-Core home page (http://hl7.org/fhir/us/qicore/2019Sep/index.html) will be corrected to reference the appropriate mappings - with new US Core update:
               Implantable Device to US Core Implantable Device to FHIR base Device
               Device directly to FHIR base Device
               DeviceRequest directly to FHIR base DeviceRequest
               See also 24063 23800

      Show
      Mapping table on QI-Core home page ( http://hl7.org/fhir/us/qicore/2019Sep/index.html ) will be corrected to reference the appropriate mappings - with new US Core update:Mapping table on QI-Core home page ( http://hl7.org/fhir/us/qicore/2019Sep/index.html ) will be corrected to reference the appropriate mappings - with new US Core update:          Implantable Device to US Core Implantable Device to FHIR base Device          Device directly to FHIR base Device          DeviceRequest directly to FHIR base DeviceRequest          See also 24063 23800
    • Viet Nguyen/Peter Muir: 25-0-0
    • Correction
    • Compatible, substantive

      Existing Wording: QICore-Device

      Proposed Wording: QICore-DeviceRequest

      Comment:

      In the table the displayed name of the QICore-DeviceRequest Profile is wrong. It should be QICore-DeviceRequest, instead if QICore-Device (which is in the previous row)

      Summary:

      In the table the displayed name of the QICore-DeviceRequest Profile is wrong.

            Assignee:
            matthew_tiller
            Reporter:
            Javier Espina
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: