2015May core #373 - UDI doesn't identify repository/jurisdiction

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU1 [deprecated]
    • Orders & Observations
    • Device
    • 5.10.3
    • Hide

      Motion to change .udi datatype from string to identifier Eric Haas/Laurie Burkhardt For-Against-Abstain 7-1-12 Motion on name of element... Keep 'udi' add alias names 'udiCarrier' 'barcodeString' Eric Haas/Margaret Dittloff suggested dataCarrier, udiHRF, barcodeString, udiCarrier, udiString , barCodeData, dataString For - Against - Abstain 1-10-9 Motion on name of element Change name to 'barcodeString' and add aliases 'udiCarrier' 'rfidString' Dan Rutz, Hugh Grover For - Against - Abstain 12-2-6 note to review the definition. on OO 1/21/2016 conf call vote to reopen Lorraine Constable/Dan Rutzt: 13-1-0 UDIBarcodeString violates FHIR element name policy. propose 'udiCarrier' with alias 'udi', 'barcodeString', 'rfidString' Note to review description

      Show
      Motion to change .udi datatype from string to identifier Eric Haas/Laurie Burkhardt For-Against-Abstain 7-1-12 Motion on name of element... Keep 'udi' add alias names 'udiCarrier' 'barcodeString' Eric Haas/Margaret Dittloff suggested dataCarrier, udiHRF, barcodeString, udiCarrier, udiString , barCodeData, dataString For - Against - Abstain 1-10-9 Motion on name of element Change name to 'barcodeString' and add aliases 'udiCarrier' 'rfidString' Dan Rutz, Hugh Grover For - Against - Abstain 12-2-6 note to review the definition. on OO 1/21/2016 conf call vote to reopen Lorraine Constable/Dan Rutzt: 13-1-0 UDIBarcodeString violates FHIR element name policy. propose 'udiCarrier' with alias 'udi', 'barcodeString', 'rfidString' Note to review description
    • Rob Hausam/Mark Jones: 10-1-3
    • Enhancement
    • Non-compatible
    • DSTU1 [deprecated]

      Existing Wording: udi:string

      Comment:

      The UDI does not itself identify the repository or jurisdiction. When using a datatype which has a 'system' the jurisdiction can be held in the system. This will be key for users to be able to know which repository to check for further information as the FDA will not be the only jurisdiction on the planet and with medical tourism people will bring non-FDA UDIs into the FDA jurisdiction.

      The alternate of creating a separate field for each UDI issuing jurisdiction is I think bad design and an unnecceasry burden on implementers.

        1. 7254.png
          7254.png
          152 kB
        2. CurrentView.png
          CurrentView.png
          279 kB
        3. Device_r1.docx
          13 kB

            Assignee:
            Unassigned
            Reporter:
            Paul Knapp
            Paul Knapp
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: