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

RelatedPerson lists Guardian and Power of Attorney as use cases, but neither are in the value set

    XMLWordPrintableJSON

Details

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

      We added these codes as part of the change in https://jira.hl7.org/browse/FHIR-31670

       

      Show
      We added these codes as part of the change in https://jira.hl7.org/browse/FHIR-31670  
    • Sonja Ziegler / Iryna Roy : 3-0-0
    • Enhancement
    • Compatible, substantive
    • R5

    Description

      Guardian and Power of Attorney are use cases for Related Person, but are not in the provided value set

      This is related to FHIR-15841 for a similar issue for Patient.contact. The proposed disposition recommends separating role and relationship as 0..* elements.

      We would support this approach, as the MCC project needs to track the relationship to the patient of the person who is performing the role of Power of Attorney

      The v3 ValueSet *http://hl7.org/fhir/v3/vs/RoleCode* has the code  POWATT for Power of Attorney and child codes for specific types of Power of Attorney roles (durable POA, healthcare POA, and special POA)

      Attachments

        Activity

          People

            brian.postlethwaite Brian Postlethwaite
            lconstab Lorraine Constable
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: