This page is part of the Personal Health Device FHIR IG (v0.2.0: STU 1 Ballot 2) based on FHIR R4. The current version which supercedes this version is 1.0.0. For a full list of available versions, see the Directory of published versions

PHD Patient Profile

In Continua uploads the patient information is the only content that is not provided by the PHD. The PHG must obtain this information out of band. In Remote Patient Monitoring there is also a concern about protecting Patient Health Information. Thus one Continua upload option is that a Patient Resource is never generated and no patient information is present on the PHG. Instead, the health care provider gives the PHG the ‘logical id’ of a Patient Resource that may or may not exist on the destination server. The PHG uses this logical id in the Observation.subject element with the assumption that the server will understand the reference when the Observation is received.

Otherwise, if the PHG is to create the Patient Resource, this profile requires that only the Patient.identifier.system, Patient.identifier.value, Patient.identifier.type.coding.code and Patient.identifier.type.coding.system be populated. The Patient.name element is optional. This approach still affords Patient Health Information protection since the values in the required fields cannot be associated to a person without some kind of dictionary.

The profile in the meta element shall be http://hl7.org/fhir/uv/phd/StructureDefinition/PhdPatient

The structure definition for the Phd Patient Profile is given here

Mapping

When a Patient resource for a known patient is to be created by the PHG the following mapping is used:

When a Patient is unknown the following mapping is used:

Examples:

An example of a PHD patient mapping is given here. The example contains an optional name element.