Overview
This section provides a list of the PRSB headings used for text sections in the ITK3 FHIR Digital Medicines Medication Review Headings notification based on the “Standards for the clinical structure and content of patient records” documentation.
This section lists the following
- The headings used
- An overview of the type of information carried within the text section
- An example of a text section instance
- A list of the coded resources which may be used to give the text carried in the section in a coded format.
Medications Sections and Coded profiles
This diagram illustrates the sections used in Digital Medicines Medication Review Headings document and which sections allow coded representation of the section text.
The text sections are carried in the FHIR Composition Resource.
This is profiled as the CareConnect-ITK-DM-EmergencySupply-Composition
Typical Text Section Content
This diagram shows the elements of a typical text section which is found in the FHIR Composition Resource. Note: the examples of section HTML in this specification show only example HTML format such as tables. This is an exemplar format. There is no mandated format for the section HTML.
Must Support Property
Some elements in the Composition Resource used within ITK3 Digital Medicines documents have the “mustSupport” property set to “true”.
These are :
- Composition.encounter
- Composition.custodian
- Composition.section(slice) sections: Attendance details, Consent, History, Information and advice given, Plan and requested actions and Referrer details
The “mustSupport” property has been added to all the elements that must be supported regardless of cardinality. Whether the conformance of the element is mandatory or optional has no relevance for the “mustSupport” property. This means that for sending or receiving systems to claim conformance to any ITK3 Digital Medicines Composition Profile the following MUST be true:
- The sending system MUST support the creation and sending of all the elements in the list above.
- The sending system MUST support the creation and sending of all Composition.section slices with the specified sub-elements and narrative.* See Note 1.
- The receiving system MUST support the processing of all the elements in the list above.
- The receiving system MUST support the display of all Composition.section slices with the specified sub-elements and narrative.
Note 1 - There are rules around when sections are sent or not sent in a document. These are specified in the document headings sections.
Headings Used By Medication Review Headings Document
Section Name | SNOMED Concept | Cardinality | Conformance | Associated Coded Profiles |
---|---|---|---|---|
Allergies and adverse reactions | 886921000000105 | 0..1 | Optional | 1 |
Attendance details | 1077881000000105 | 0..1 | Required | 1 |
Consent | 61861000000100 | 0..1 | Required | 0 |
Distribution list | 887261000000109 | 0..1 | Required | 7 |
Eligibility criteria | 61871000000107 | 0..1 | Optional | 1 |
GP practice | 886711000000101 | 1..1 | Mandatory | 1 |
History | 717121000000105 | 0..1 | Required | 0 |
Information and advice given | 1052951000000105 | 0..1 | Required | 0 |
Medications and medical devices | 933361000000108 | 1..1 | Mandatory | 2 |
Patient demographics | 886731000000109 | 1..1 | Mandatory | 1 |
Plan and requested actions | 887201000000105 | 0..1 | Required | 0 |
Referral details | 886721000000107 | 0..1 | Required | 0 |