Use case for requiring RelatedPerson.gender

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive
    • Priority: Medium
    • US Bidirectional Services eReferrals (BSeR) (FHIR)
    • STU3
    • Public Health
    • (profiles) [deprecated]
    • Hide

      Requirements traceability mappings and instance examples will be added to all profile defintions. Any existing gaps in fulfillment of identified requirements we be resolved during the process.

      Show
      Requirements traceability mappings and instance examples will be added to all profile defintions. Any existing gaps in fulfillment of identified requirements we be resolved during the process.
    • AMS/Mead: 14-0-0
    • Clarification
    • Non-substantive

      What is the use case for making RelatedPerson.gender a required element? I'm not sure all systems will collect gender on a related person and while "unknown" is in the value set, having this remain optional (0..1) may be a better option unless there is a clear need for this data element.

            Assignee:
            Unassigned
            Reporter:
            Craig Newman
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: