Gravitate Health FHIR Implementation Guide, published by Gravitate Health Project. This guide is not an authorized publication; it is the continuous build for version 0.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/hl7-eu/gravitate-health/ and changes regularly. See the Directory of published versions

• Narrative Content
• XML
• JSON
• TTL

OperationDefinition: focus

This operation calculates a focused version of an ePI as well as the separate extracts. The IPS can either be submitted as an IPS bundle or as an Identifer of the patient (using the ips-identifier parameter). If neither IPS Bundle or IPS identifier are passed as parameters it is expected that the Identifier of the patient is present as part of the security token. If the Identifier of the patient is submitted as an Identifier or as part of a security token it is up to the discression of the service implementing the focus-operation to fetch the IPS of the patient.

If the IPS is delivered as a bundle it must be encoded using Base64 as it is FHIR R4 compliant whereas the focus-operation is FHIR R5 compliant. The focus-operation will internally convert and extract the needed information from the R4 bundle.

The ePI can be delivered either as a Bundle or by using an Identifier of the bundle. Whether the support of both Identifier and Bundle continues to be supported currently remains unknown.

The persona dimension can be delivered either as a Bundle or by using an Identifier of the bundle. Whether the support of both Identifier and Bundle continues to be supported currently remains unknown.

Note: If the IPS is delivered as encoded Base64 content, there is a better opportunity for the submitting client to de-identify the Patient resource as the client can remove the Patient.identifier and mask out names and so on. While this may seem counter intuitive from an IPS point of view, the Patient identifiable components are not needed for the focusing mechanism to operate properly.