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 Condition

Overview

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

Usecase

System Interactions

The practioner decides to record condition information on a reasonable adjustment record as supporting detail e.g. Blind or low vision - both eyes. This typically after a patient consultation and SHALL be 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.

Examples

• Patient example

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

• Patient flag
• Reasonable Adjustment flag 1
• Condition 1
• ​Transaction Bundle 1

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.

• Reasonable Adjustment flag 2
• Condition 2
• ​Transaction Bundle 2