4.1 Structure Definition Precription Record
A prescription can be structured in a bundle according to the NDHM
4.1.1 Mandatory and Must Support Data Elements
The data-elements that mandatory (i.e data MUST be present) or must be supported if the data is present in the sending system (Must Support definition) can be viewed through the different views below. Profile specific guidance and examples are provided as well. The Formal Profile Definition below provides the formal summary, definitions, and terminology requirements.
4.1.1.1 Each PrescriptionRecord must have:
- a type
- a patient
- author of the prescription
- attester
- section
4.1.1.2 Each PrescriptionRecord must support:
- Composition.type.text
- Section.code.entry.MedicationRequest
4.1.1.3 Profile specific implementation guidance:
Prescription may be represented using PrescriptionRecord Profile with SNOMED CT System for identification of codes.
- Composition.type.coding.system = "http://snomed.info/sct"
- Composition.type.coding.code = "440545006" (Prescription record (record artifact))
If a patient has been prescribed medication then it may be represented using MedicationRequest resource. MedicationRequest resource can be structured as per NDHM MedicationRequest profile
If the prescription has an attachment then it may be represented using a Binary resource. Binary Resource can be structured as per NDHM Binary profile Binary that builds on base FHIR profile Binary
4.1.2 Examples
4.1.3 Formal Views of Profile Content
Description of Profiles, Differentials, and Snapshots.The official URL for this profile is:
https://simplifier.net/ndhm/prescriptionrecord