Feature/generalise profiles (#19)

* generalised flag profiles * generalised flag profiles * generalised flag profiles * generalised flag profiles * generalise condition, fix refs and names * profiles generalised, apply profiles to examples * examples validating against profiles * cpis and fgm examples, all validating * addtional example pages added * fix cpis consent category example * fix flag code for cpis and fgm * added careconnect deps, tidy diagrams, include contact via yml * licence section removed, redundant if using ip-statements * slight mod to intro --------- Co-authored-by: Declan Kieran <[email protected]>
NHSDigital · Mar 22, 2024 · 518c608 · 518c608
1 parent 72a067b
commit 518c608
Show file tree

Hide file tree

Showing 2 changed files with 1 addition and 2 deletions.
diff --git a/input/fsh/examples/0026-FGMPatientFlagExample1.fsh b/input/fsh/examples/0026-FGMPatientFlagExample1.fsh
@@ -1,5 +1,5 @@
 Instance: FGMPatientFlagExample1
-InstanceOf: Flag
+InstanceOf: PatientFlag
 Title: "FGM example of a patient Flag resource"
 Usage: #example
 * meta.profile = "https://fhir.nhs.uk/England/StructureDefinition/PatientFlag"

diff --git a/input/pagecontent/add-reasonable-adjustment-record.md b/input/pagecontent/add-reasonable-adjustment-record.md
@@ -5,7 +5,6 @@ Patient consent must be obtained before recording any adjustment or impairment.
 For high level requirements, see [Key purposes of the Reasonable Adjustment Flag](index.html#key-purposes) 
 
 ### 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.