FHIR R4 Person API

Overview

This asset is a component of MuleSoft Accelerator for Healthcare.

MuleSoft Accelerator for Healthcare enables healthcare providers to unlock critical patient data to build a patient 360 within Salesforce Health Cloud, faster and easier than ever before. The solution includes pre-built APIs, connectors, integration templates, and prescriptive end-to-end reference architecture to bring patient demographics information and COVID-19 test results from any EHR into Health Cloud using HL7 V2 or FHIR standards.

The solution also provides a library of United States Core Data for Interoperability (USCDI) and FHIR R4 resources to help healthcare developers adhere to interoperability needs and jumpstart the development of healthcare digital transformation initiatives.

Use case covered

The Person resource serves as a linkage resource that may provide a reference set of common demographics for an individual (human or animal) across multiple roles.

This linkage can be direct to role-specific FHIR resources (Patient, Practitioner and RelatedPerson) residing on the same or possibly distinct FHIR systems/applications, or indirectly through the use of business identifiers.

The Person resource may be used in many situations/contexts, including:

• A set of demographics that can be used to co-ordinate the maintenance of thisde-normalized information across practitioners, patients and/or related persons
  e.g. link known resources of the different types together within a system
• A state/network based Primary Person Index
  e.g. A National Identifier Index or a Network membership/subscriber list
• A central register that links patient resources from multiple servers, indicating theyall correspond to the same individual
  e.g. Within a large organization with many systems to be able to link the various records,without having to modify the source information with external links
• A support for access monitoring software that is able to assert what practitioner,patient and related person records correspond to the same human being to assist indetecting improper querying.
  e.g. asserting that a Patient A is the same individual as a RelatedPerson B who isrelated to Patient C, who is also Practitioner D. As such, monitoring for PractitionerD’s accesses to Patient A’s records should be carefully scrutinized.
• Local record(s) on a mobile device listing links to remote server patient resources
  e.g. A mobile phone application storing references to the hospitals they have access to

Note: The Person resource is an advanced feature. Many systems don’t have a way to relate information across resource types, or systems, especially from Patient to Practitioner, and therefore might not implement this functionality. Some do have ways of relating the Patient and RelatedPerson resource types. FHIR is also able to do this without the Person resource, utilizing the Patient.link property

This API uses FHIR R4 Person Library.

More information about FHIR R4 Person specification can be found here.