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

Identifier requirements in profiles

XMLWordPrintableJSON

    • Icon: Change Request Change Request
    • Resolution: Unresolved
    • Icon: Highest Highest
    • FHIRCast (FHIR)
    • 3.0.0-ballot
    • Infrastructure & Messaging
    • STU
    • FHIRcast Encounter for Open Events
      FHIRcast Patient for Open Events

      Various profiles require additional fields (cardinality 1.. )that are not required by FHIR but are desirable in many Healthcare deployments, but not all.

      We should replace these with  MS 0..* and add SHALL:populate obligation.

      This still indicates that the element has to be present when available but allows for deployments that do not use the element.

       

            Unassigned Unassigned
            bvdh Bas van den Heuvel
            Bas van den Heuvel
            Watchers:
            2 Start watching this issue

              Created:
              Updated: