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 Reasonable Adjustment Record

Overview

For high level requirements, see Key purposes of the Reasonable Adjustment Flag

Usecase

After obtaining consent from a patient, a Reasonable Adjustment Record may be created. This consists of a Flag resource containing an adjustment and a Condition resource may also optionally be created to record the details of an impairment.

If a Reasonable Adjustment Record exists, a Flag resource designated as the patient flag must be created to indicate that there are reasonable adjustments recorded for the patient. There is a single instance of this type of resource per patient.

Patient Flag Patient or Proxy PractitionerRecordAdd Reasonable Adjustment record Patient Patient AdvocateConsult include

System Interactions

The practioner decides to record a condition with the patients consent. 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.

PractitionerPractitionerPatientPatientFHIR APIFHIR APIPatient FlagPatient FlagAdjustment FlagAdjustment FlagConditionConditionExamine patientSuggest adjustmentsRecord adjustment record (transaction Bundle)alt[Validation failed]rollbackCreate/update resourceValidatereturnalt[Validation failed]rollbackCreate/update resourceValidatereturnalt[Validation failed]rollbackCreate/update resourceValidatereturnalt[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 includes 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.