prescription-order
This message definition describes the rules for a Prescription Order interactions used in a FHIR Messaging exchange.
The FHIR Message Bundle MUST contain one MessageHeader resource conforming to NHSDigital-MessageHeader.
MessageHeader.eventCoding
| System | Code |
|---|---|
| Message Events | prescription-order |
"eventCoding": { "system": "https://fhir.nhs.uk/CodeSystem/message-event", "code": "prescription-order", "display": "Prescription Order" }
MessageHeader.focus
| Profile | Min | Max | Notes |
|---|---|---|---|
| NHSDigital-MedicationRequest See note below |
1 | 4 | The following elements must be the same for each MedicationRequest in the Bundle: - extension:NHSBSAprescriptionType - status- intent- category - subject - requester - groupIdentifier - courseOfTherapyType, when the value is continuous-repeat-dispensing - dispenseRequest.validityPeriod |
| NHSDigital-CommunicationRequest | 0 | * | This is for legacy support of patient messages (e.g. surgery opening times and repeat medication lists) that would of been printed on the right hand side of paper prescriptions. |
| NHSDigital-Provenance | 0 | 1 | MUST for $process-message endpoint. This holds the Advanced Electronic Signature (AES) for the prescription. |
| Response Required |
|---|
| always |
| Allowed Responses |
|---|
| NHSDigital-OperationOutcome |
</identifier>
</eventCoding>
</focus>
</focus>
</allowedResponse>
</MessageDefinition>
{
{
}
],
},
{
},
{
}
],
]
}
Note
The underlying conformance profile for the NHSDigital-MedicationRequest is https://fhir.nhs.uk/StructureDefinition/NHSDigital-MedicationRequest-Message. This profile mandates the use of a referenced resources for subject and requester.