2015May core #224 - UDI doesn't identify type

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Retracted
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU1 [deprecated]
    • Orders & Observations
    • Device
    • 5.10.6
    • Hide

      UDI can either be a type or an instance identifer

      Withdrawm by submitter

      Show
      UDI can either be a type or an instance identifer Withdrawm by submitter
    • Clarification

      Existing Wording: Device.udi

      Comment:

      Good to see the UDI in the device resource. But the UDI does not define a "type" of device. It identifies the specified device and model number from the manufacturer. It is more like an NDC code than an RXNorm. code.

      Further devices made up of parts may have many UDIs, one for the pacemaker and one for each of the leads. Am not sure how this all works but would need to have a hierarchical structure to carry all of the parts when they are not pre-packaged as one product

      There is another resource called a device component. Which probably achieves this- but some explanation of how and through what attribute the device connects to its components.

      Believe the data about devies will be look up able at NLM

            Assignee:
            Unassigned
            Reporter:
            clemmcdonald
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: