Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-43164

Update DeviceDefinition.deviceName.type

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • FHIR Core (FHIR)
    • R6
    • Orders & Observations
    • DeviceDefinition
    • Hide

      Adjust the DeviceDefinition.deviceNameType binding from Required to Extensible and add a statement that the jurisdiction must clarify which name is to be used as the registered-name plus indicate that as a result a device definition may have multiple names that are the same, but then used for different purposes per the name type and jurisdictional guidance.

      Apply the same change to Device.Name.type.

      Show
      Adjust the DeviceDefinition.deviceNameType binding from Required to Extensible and add a statement that the jurisdiction must clarify which name is to be used as the registered-name plus indicate that as a result a device definition may have multiple names that are the same, but then used for different purposes per the name type and jurisdictional guidance. Apply the same change to Device.Name.type.
    • Dan Rutz / Rob Hausam: 7-0-5
    • Clarification
    • Compatible, substantive

    Description

      There is a need to allow for additional name types and clarify that, while there may be additional name types, e.g., brand name, that the jurisdiction requiring certain use and reporting of a device name would indicate what name for the registered-name.   Thiat may be done through regulation and/or implementation guidance.

      Attachments

        Activity

          People

            costateixeira Jose Costa-Teixeira
            hbuitendijk Hans Buitendijk
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: