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

Make Patient.contact.name 0..* to support preferred names

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Medium Medium
    • FHIR Core (FHIR)
    • R5
    • Patient Administration
    • Patient
    • Hide

      Agree to update cardinality of Patient.contact.name to be 0..* and

      Update

      Definition to say "Name associated with the contact person"

      Short Name to say "Name associated with the contact person"

      Requirements  to say "Contact persons need to be identified by name, and it may be necessary to represent multiple names for that contact person, such as legal name and usual (Name to Use) name"

      Show
      Agree to update cardinality of Patient.contact.name to be 0..* and Update Definition to say "Name associated with the contact person" Short Name to say "Name associated with the contact person" Requirements  to say "Contact persons need to be identified by name, and it may be necessary to represent multiple names for that contact person, such as legal name and usual (Name to Use) name"
    • Line Saele / Charles Ye : 10-0-0
    • Enhancement
    • Non-compatible

    Description

      Patient.contact.name is currently 0..1.  This is a problem if we want to communicate names with different use types for a single individual.  For example, both a legal name (use=official) and preferred name (use=usual).

       

      I suggest we make the cardinality of Patient.contact.name be 0..*.

      Attachments

        Activity

          People

            cooper.thompson Cooper Thompson
            cooper.thompson Cooper Thompson
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: