Device resource limitations regarding AIDC UDI Carrier are overstated

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Duplicate
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU2
    • Orders & Observations
    • Device
    • 8972
    • Clarification

      Based on the Connectathon 13 work, there is no "lmitations on character sets in XML and the need to round-trip JSON data through XML,* AIDC identifiers cannot be conveyed in FHIR*" despite the warning included in: http://hl7.org/fhir/2016Sep/device-mappings.htm

      HAPI FHIR 2.0 escapes delimiters as needed. It's not clear what "character set" limitation is described here. If AIDC UDI cannot be exchanged using FHIR, presumably it would not be possible to exchange then using C-CDA or any other encoding.

      At the FHIR Connectathon we could create and read back device records using an ICCBBA id:

      http://www.fda.gov/downloads/MedicalDevices/DeviceRegulationandGuidance/UniqueDeviceIdentification/GlobalUDIDatabaseGUDID/UCM396595.doc

            Assignee:
            Unassigned
            Reporter:
            Ioana Singureanu
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: