Patient Flags - NHS England - Implementation Guide STU1
0.4.0 - ci-build

Patient Flags - NHS England - Implementation Guide STU1 - Local Development build (v0.4.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

Add Patient Flag Record

Overview

For high level requirements, see Key purposes of the Patient Flag

Usecase

Patient Flag Practitioner«abstract»Record«abstract»Add Patient Flag record Patient«abstract»Consult include

System Interactions

The practioner decides to record patient flag information.

This could be done with individual calls to the required endpoints, or can be done in a single transaction Bundle. A transaction Bundle can help with data integrity requirements and also help to reduce required http calls.

PatientPatientPractitionerPractitionerFHIR APIFHIR APIPatient FlagPatient FlagAdditional DetailAdditional DetailConsult patientRecord adjustment record (transaction Bundle)Create/update resourceValidatereturnalt[Validation failed]rollbackloop[for each Additional Detail resource]Create/update resource (any)Validatereturnalt[Validation failed]rollbackOperationOutcome

Examples

The following set of examples constitute the individual associated resources with the intial addition of a flag for Reasonable Adjustment. This include a patient Flag resource, the adjustment Flag resource and the associated Condition resource. All resources have contained provenances.

A transaction Bundle is also given that allows these resources (plus the patient) to be entered in an atomic traction. It uses PUTs, where in the case of an intial update, it may be done as a conditional update

The following set of examples are for the same patient, and constitute an addition flag and condition. The transaction Bundle here illustates an idempotent update by simply adding the new resources to the first transaction Bundle.