more trims

NHSDigital · Jun 30, 2024 · eff2382 · eff2382
1 parent f77e321
commit eff2382
Show file tree

Hide file tree

Showing 15 changed files with 24 additions and 133 deletions.
diff --git a/input/images-source/add-ra-record-usecase.plantuml b/input/images-source/add-ra-record-usecase.plantuml
@@ -10,7 +10,7 @@ usecase "Add Reasonable Adjustment record" as add
 }
 
 
-package Consenter {
+package "Patient or Proxy" {
   actor Patient as pat
   actor "Patient Advocate" as pad
 }

diff --git a/input/images-source/data-model.plantuml b/input/images-source/data-model.plantuml
diff --git a/input/images-source/remove-ra-record-usecase.plantuml b/input/images-source/remove-ra-record-usecase.plantuml
@@ -10,7 +10,7 @@ usecase "Remove Reasonable Adjustment record" as add
 }
 
 
-package Consenter {
+package "Patient or Proxy" {
   actor Patient as pat
   actor "Patient Advocate" as pad
 }

diff --git a/input/images-source/retrieve-ra-record-usecase.plantuml b/input/images-source/retrieve-ra-record-usecase.plantuml
@@ -10,7 +10,7 @@ usecase "Retrieve Reasonable Adjustment record" as add
 }
 
 
-package Consenter {
+package "Patient or Proxy" {
   actor Patient as pat
   actor "Patient Advocate" as pad
 }

diff --git a/input/pagecontent/add-patient-flag-record.md b/input/pagecontent/add-patient-flag-record.md
@@ -12,7 +12,9 @@ For high level requirements, see [Key purposes of the Patient Flag](index.html#p
 
 ### 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.
+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.
 
 <div style="text-align: left;">
   {%include add-pf-record-sequence.svg%}
@@ -26,7 +28,6 @@ The following set of examples constitute the individual associated resources wit
 
 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](https://www.hl7.org/fhir/http.html#cond-update)
 
-* [Consent](Consent-RAConsentExample1.html)
 * [Patient flag](Flag-RAPatientFlagExample1.html)
 * [Reasonable Adjustment flag 1](Flag-RAFlagExample1.html)
 * [Condition 1](Condition-RAConditionExample1.html)

diff --git a/input/pagecontent/add-reasonable-adjustment-condition.md b/input/pagecontent/add-reasonable-adjustment-condition.md
@@ -1,6 +1,6 @@
 ### Overview
 
-For high level requirements, see [Key purposes of the Patient Flag](index.html#pf-key-purposes)
+For high level requirements, see  [Key purposes of the Reasonable Adjustment Flag](index.html#ra-key-purposes) 
 
 ### Usecase
 
@@ -12,7 +12,9 @@ For high level requirements, see [Key purposes of the Patient Flag](index.html#p
 
 ### 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.
+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.
 
 <div style="text-align: left;">
   {%include add-pf-record-sequence.svg%}
@@ -26,7 +28,6 @@ The following set of examples constitute the individual associated resources wit
 
 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](https://www.hl7.org/fhir/http.html#cond-update)
 
-* [Consent](Consent-RAConsentExample1.html)
 * [Patient flag](Flag-RAPatientFlagExample1.html)
 * [Reasonable Adjustment flag 1](Flag-RAFlagExample1.html)
 * [Condition 1](Condition-RAConditionExample1.html)

diff --git a/input/pagecontent/add-reasonable-adjustment-record.md b/input/pagecontent/add-reasonable-adjustment-record.md
@@ -1,7 +1,5 @@
 ### Overview
 
-Patient consent must be obtained before recording any adjustment or impairment.  See [Consent to Share Information](consent-to-share-information.html) for details of requirements around consent.
-
 For high level requirements, see [Key purposes of the Reasonable Adjustment Flag](index.html#ra-key-purposes) 
 
 ### Usecase

diff --git a/input/pagecontent/add-reasonable-adjustment.md b/input/pagecontent/add-reasonable-adjustment.md
@@ -1,6 +1,6 @@
 ### Overview
 
-For high level requirements, see [Key purposes of the Patient Flag](index.html#pf-key-purposes)
+For high level requirements, see [Key purposes of the Reasonable Adjustment Flag](index.html#ra-key-purposes)
 
 ### Usecase
 
@@ -12,7 +12,9 @@ For high level requirements, see [Key purposes of the Patient Flag](index.html#p
 
 ### 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.
+The practioner decides to record reasonable adjustment record information for a single reasonable adjustment e.g. provision of large print. This 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.
 
 <div style="text-align: left;">
   {%include add-pf-record-sequence.svg%}
@@ -26,7 +28,6 @@ The following set of examples constitute the individual associated resources wit
 
 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](https://www.hl7.org/fhir/http.html#cond-update)
 
-* [Consent](Consent-RAConsentExample1.html)
 * [Patient flag](Flag-RAPatientFlagExample1.html)
 * [Reasonable Adjustment flag 1](Flag-RAFlagExample1.html)
 * [Condition 1](Condition-RAConditionExample1.html)

diff --git a/input/pagecontent/additional-examples.md b/input/pagecontent/additional-examples.md
diff --git a/input/pagecontent/basic-query-examples.md b/input/pagecontent/basic-query-examples.md
diff --git a/input/pagecontent/remove-patient-flag-record.md b/input/pagecontent/remove-patient-flag-record.md
@@ -13,19 +13,18 @@ For high level requirements, see [Key purposes of the Patient Flag](index.html#p
 
 ### System Interactions
 
-In the following sequence diagram, a patient revokes consent.  The Consent resource is updated to reflect the patient dissent, and all adjustment records are deleted.
+In the following sequence diagram, a patient and/or practitioner decide to remove the patient flag.
 
 <div style="text-align: left;">
 
   {%include remove-pf-record-sequence.svg%}
 
 </div>
 
-The following resource types will be deleted from the record if consent is not granted i.e.
+The following resource types will be deleted from the record: 
 
 * [Patient Flag](StructureDefinition-PatientFlag.html)  
-* [Programme Flag](StructureDefinition-ProgrammeFlag.html)  
-* [Condition Flag](StructureDefinition-FlagCondition.html) 
+* any resources detailing supporting information
 
 #### Example
 

diff --git a/input/pagecontent/remove-reasonable-adjustment-condition.md b/input/pagecontent/remove-reasonable-adjustment-condition.md
@@ -1,6 +1,6 @@
 ### Overview
 
-For high level requirements, see [Key purposes of the Patient Flag](index.html#pf-key-purposes)
+For high level requirements, see [Key purposes of the Reasonable Adjustment Flag](index.html#ra-key-purposes)
 
 
 #### UseCase
@@ -13,7 +13,8 @@ For high level requirements, see [Key purposes of the Patient Flag](index.html#p
 
 ### System Interactions
 
-In the following sequence diagram, a patient revokes consent.  The Consent resource is updated to reflect the patient dissent, and all adjustment records are deleted.
+In the following sequence diagram, a patient and/or practitioner decide to remove the condition information as supporting detail on th reasonable adjustment record.
+
 
 <div style="text-align: left;">
 

diff --git a/input/pagecontent/remove-reasonable-adjustment-record.md b/input/pagecontent/remove-reasonable-adjustment-record.md
@@ -1,14 +1,12 @@
 ### Overview
 
-A patient may deny or revoke their consent to share adjustment or impairment information at any point. See [Consent to Share Information](consent-to-share-information.html) for details of requirements around consent.
+A patient and/or practitioner decide to remove the reasonable adjustment record.
 
 For high level requirements, see [Key purposes of the Reasonable Adjustment Flag](index.html#ra-key-purposes)   
 
 
 #### UseCase
 
-If a patient denys consent, then this must be recorded and all adjustment records must be removed.
-
 <div style="text-align: left;">
 
   {%include remove-ra-record-usecase.svg%}
@@ -17,7 +15,7 @@ If a patient denys consent, then this must be recorded and all adjustment record
 
 ### System Interactions
 
-In the following sequence diagram, a patient revokes consent.  The Consent resource is updated to reflect the patient dissent, and all adjustment records are deleted.
+In the following sequence diagram, a patient and/or practitioner decide to remove the reasonable adjustment record. All adjustment records are deleted.
 
 <div style="text-align: left;">
 

diff --git a/input/pagecontent/remove-reasonable-adjustment.md b/input/pagecontent/remove-reasonable-adjustment.md
@@ -13,19 +13,17 @@ For high level requirements, see [Key purposes of the Patient Flag](index.html#p
 
 ### System Interactions
 
-In the following sequence diagram, a patient revokes consent.  The Consent resource is updated to reflect the patient dissent, and all adjustment records are deleted.
+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.
 
 <div style="text-align: left;">
 
   {%include remove-ra-sequence.svg%}
 
 </div>
 
-The following resource types will be deleted from the record if consent is not granted i.e.
+The following resource types will be deleted from the record:
 
-* [Patient Flag](StructureDefinition-PatientFlag.html)  
 * [Programme Flag](StructureDefinition-ProgrammeFlag.html)  
-* [Condition Flag](StructureDefinition-FlagCondition.html) 
 
 #### Example
 

diff --git a/sushi-config.yaml b/sushi-config.yaml
@@ -92,9 +92,6 @@ menu:
     Remove Reasonable Adjustment: remove-reasonable-adjustment.html
     Add Reasonable Adjustment Condition: add-reasonable-adjustment-condition.html
     Remove Reasonable Adjustment Condition: remove-reasonable-adjustment-condition.html
-  Additional Examples: 
-    CPIS/FGM demo: additional-examples.html
-    Basic Query Examples: basic-query-examples.html
   Artifacts: artifacts.html
   About: 
     Downloads: todo.html