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

Why is udiCarrier.deviceIdentifier not mandatory

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Highest Highest
    • FHIR Core (FHIR)
    • R4
    • Orders & Observations
    • Device
    • Hide

      Proposed motion to change deviceIdentifier cardinality to (1..1).  If there is a udiCarrier then the device identifier must be available.  

      Show
      Proposed motion to change deviceIdentifier cardinality to (1..1).  If there is a udiCarrier then the device identifier must be available.  
    • Marti Velezis / Riki Merrick: 9-0-5
    • Enhancement
    • Compatible, substantive
    • R5

    Description

      Short and long description both say this component is mandatory, yet the cardinality is 0..1. Please provide a comment or requirements element explaining why it's optional or make it required

      (Comment 113 - imported by: Ron G. Parker)

      Attachments

        Activity

          People

            costateixeira Jose Costa-Teixeira
            lloyd Lloyd McKenzie
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: