DI should have its own type element - 2016-09 core #261

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Duplicate
    • Priority: Medium

      Existing Wording: For UDI, this element corresponds to the UDI device identifier (DI) part. See UDI mappings for a complete mapping of UDI parts to Device.

      Comment:

      Type is used for both DI and Device Type (e.g., coded concept to categorize the device) and both may be sent when UDI information is sent. Cardinality is 1..1 and they are not exact "translations" of each other.

      The DI should have its own element - it is not a type code versus a string value to identify the device

      Summary:

      DI should have its own type element

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

              Created:
              Updated:
              Resolved: