ra data model

input/images-source/ra-data-model.plantuml

@@ -16,12 +16,6 @@ entity "Patient Flag" as pfg {
 
 package "Additional Detail" {
 
-entity "Consent" as con {
-  *patient : Patient
-  *category : CodeableConcept
-  *contained : Provenance (Contained)
-}
-
 entity "Condition" as cod {
   *patient : Patient
   *code : CodeableConcept
@@ -43,11 +37,9 @@ entity "Provenance" as prov {
 }
 }
 
-pat ||..|| con : provides
 pat ||--o{ cod : has
 pat ||--o| pfg : has
 pat ||--o{ prfg : has
-con ||--|| prov : contains
 cod ||--|| prov : contains
 pfg ||--|| prov : contains
 prfg ||--|| prov : contains

input/pagecontent/data-model.md

@@ -8,7 +8,16 @@ A Patient Flag API record is made up of a Flag resource and any other 'detail' r
 
 ### Reasonable Adjustments
 
-The RA record is made up of Consent, Condition, Flag and Provenances resources.  The Consent, Condition and Flag resources are linked via a Patient resource.  Provenance of all resources that make up an RA record must be stored.  This is modelled here as a contained resource, and as such has no lifetime outside of the constituent RA record resources.
+The RA record is made up of Flag, Provenance and Condition resources.  
+
+The presence of and entitlement to reasonable adjustments is represented by a PatientFlag resource. It can be interpreted as meaning 'this patient has reasonable adjustments'.
+
+Individual adjustments are represented as ProgrammeFlag resource instances. They can be interpreted as meaning e.g.'this patient requires Easy read'
+
+Patients may optionally request details of underlying conditions are recorded and shared where this enhances healthcare. These are represented as FlagCondition resources
+
+Provenance of all resources that make up an RA record must be stored.  This is modelled here as a contained resource, and as such has no lifetime outside of the constituent RA record resources.
+
 
 <div style="text-align: left;">
   {%include ra-data-model.svg%}