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

RelatedPerson: Add reference to person in addition to a patient reference

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive with Modification
    • Icon: Medium Medium
    • FHIR Core (FHIR)
    • STU3
    • Patient Administration
    • RelatedPerson
    • Hide

      Representing a graph of person relationships beyond those that pertain directly to patient care (either representing an actor involved in care, or family history of illness) is really outside the scope of FHIR.

      There are several security and privacy related considerations (e.g. GDPR) to representing a full network of person relationships in a healthcare system.

      In some cases, it might be appropriate to use Patient, if the related person is a Patient, however not all personal relationships are appropriate to represent in Patient (e.g. a great-grandmother that never received care at the relevant organization).

      You might consider using extensions on Person to document the relationships that person has with other persons.

       

      We do think we should clarify the Person resource narrative to clarify that the "networks" that a person may be involved in are networks for the purpose of healthcare provision, not networks of personal relationships.

      Proposed update to the Person Master Index section on the Person resource:

      These may also operate outside of government in the private sector, such as associations or healthcare networks that a person may be involved with and may work in the same was as they do inside government. The usage of the data into the healthcare environment is not the only use of the register.

       

       

      Show
      Representing a graph of person relationships beyond those that pertain directly to patient care (either representing an actor involved in care, or family history of illness) is really outside the scope of FHIR. There are several security and privacy related considerations (e.g. GDPR) to representing a full network of person relationships in a healthcare system. In some cases, it might be appropriate to use Patient, if the related person is a Patient, however not all personal relationships are appropriate to represent in Patient (e.g. a great-grandmother that never received care at the relevant organization). You might consider using extensions on Person to document the relationships that person has with other persons.   We do think we should clarify the Person resource narrative to clarify that the "networks" that a person may be involved in are networks for the purpose of healthcare provision, not networks of personal relationships. Proposed update to the Person Master Index section on the Person resource: These may also operate outside of government in the private sector, such as associations or healthcare networks that a person may be involved with and may work in the same was as they do inside government. The usage of the data into the healthcare environment is not the only use of the register.    
    • Brian Postlethwaite / Olivia Bellamou-Huet: 4-0-0
    • Clarification
    • Non-substantive
    • R5

    Description

      In Norway we have identified the need to serve information about citizens using a Person Master Index for healthcare, and in that use-case we are going to use HL7 FHIR to define the interfaces to access this Registry. In time some healthcare specific information will be added to this registry to solve use-cases that are not of interest to organizations outside healthcare here in Norway. Most of the person data will however be information from the central registry of norwegian citizens, but in the healthcare specific registry this information will be served through a FHIR interface. We will need profiles and extensions to incorporate some of the data that exist in the common Person Master Index.

      I think the note describing the Person resource used in a PMI describes our thinking quite clearly: "Note: This style of system may use the Person resource without any FHIR references to Patient or Practitioner resources. In these environments the Master Index is likely to have a master identifier that performs this logical linking."

      A central part of the information in the PMI is relations from person to person. To serve this use-case there is a need to express relations person to person, and not necessarily concerning a Patient resource.

      We propose to rename the patient reference in RelatedPerson to Person and allow references to both Patients and Person using this reference.

      Attachments

        Activity

          People

            Unassigned Unassigned
            thomiz Thomas Tveit Rosenlund
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: