Add Reasonable Adjustment

Overview

For high level requirements, see Home.

Use Case

System Interactions

The practitioner decides to record reasonable adjustment record information for a single reasonable adjustment e.g. provision of large print. This is typically after a patient consultation and 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

The following set of examples constitute the individual associated resources with the initial 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 initial 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 illustrates an idempotent update by simply adding the new resources to the first transaction Bundle.

Remove Reasonable Adjustment

Overview

For high level requirements, see Home.

Use Case

System Interactions

In the following sequence diagram, a patient and/or practitioner decide to remove an individual reasonable adjustment. The relevant England-Flag-PatientFlag-Adjustment resource is removed.

The following resource types will be deleted from the record:

Example

Multiple resources can be deleted using a transaction bundle. This RemoveRARecord-Bundle-Example demonstrates deleting the following resources