What does the Build NHS EPS Prescription Message (HL7/FHIR) skill do?

Assemble a prescriber's medication order into an Electronic Prescription Service (EPS) message for submission to the NHS Spine — dm+d medicine coding, prescriber/patient/dispenser routing, HL7 V3 / FHIR R4 resources under SCCI0052, with a worked example.

How do I run the Build NHS EPS Prescription Message (HL7/FHIR) skill?

Copy the skill and paste it into your own Claude or ChatGPT, then provide your source data. FinchContext skills run inside your own AI assistant, so your financial data never leaves your control.

Which region does the Build NHS EPS Prescription Message (HL7/FHIR) skill cover?

United Kingdom. It targets the local tax authority / e-invoicing format described on this page.

Build NHS EPS Prescription Message (HL7/FHIR)

Skill: Assemble a prescription into an EPS message for the NHS Spine

Region: United Kingdom Category: Health care Does: Takes a prescriber's medication order and assembles the Electronic Prescription Service (EPS) prescription message for submission to the NHS Spine, coding medicines against the dm+d dictionary and carrying prescriber, patient and dispenser routing. Spec: NHS England EPS — HL7 V3 / FHIR R4 prescription messages, dm+d coding, SCCI0052 (Information Standard for EPS)

Sends a prescription electronically from a prescribing system to a nominated dispenser via the Spine. EPS is moving from HL7 V3 to the FHIR-based Electronic Prescription Service API. Element names follow the EPS message / FHIR resources, not a verbatim schema.

When this applies

A GP, prescriber or hospital system issues an acute or repeatable/repeat-dispensing prescription to be routed electronically.
The patient has a nominated pharmacy (or a one-off token via barcode for non-nominated dispensing).
Items are prescribable and coded in dm+d (Dictionary of Medicines and Devices).

Structure (prescription → EPS message)

MessageHeader: messageId, sender (prescribing system, ODS code), Spine endpoint
Patient: NHS Number (10-digit), name, DOB
PractitionerRole: prescriber (GMC/professional code), organisation (ODS), prescribing site
MedicationRequest (per line item):
  - medication coded to dm+d (VMP/AMP SNOMED code)
  - dosageInstruction, quantity + unit, course/duration
  - prescriptionType (acute / repeat / eRD), repeats authorised/issued
  - nominated dispenser (ODS code) or token
Provenance / digital signature (Smartcard / advanced electronic signature)

Data rules

dm+d coding — every item carries a valid dm+d (SNOMED CT) code for the VMP/AMP; free-text-only items are rejected.
NHS Number — 10 digits passing the Modulus 11 check digit; PDS-traced where required.
ODS codes — prescribing organisation and nominated dispenser identified by ODS codes; prescriber by professional registration.
Signature — prescriptions are signed (Smartcard / advanced electronic signature); controlled drugs follow Schedule-specific rules.
eRD — electronic Repeat Dispensing carries authorised issue count and review date.

Worked example (outline)

Acute prescription, prescriber GMC 1234567 at GP practice ODS A12345
  Patient NHS 943 476 5919, Amoxicillin 500mg capsules (dm+d AMP code), qty 21
  Dosage: 1 capsule three times a day for 7 days
  Nominated dispenser ODS FA123 (community pharmacy)
  Signed via Smartcard -> sent to Spine EPS endpoint

Submitted to the NHS Spine via the EPS (FHIR) API; the dispenser downloads it at the nominated pharmacy.

Validation checklist

Each item coded to a valid dm+d (VMP/AMP) code
NHS Number valid (10 digits, Modulus 11)
Prescriber professional code and ODS organisation present
Nominated dispenser ODS code (or token) set
Dosage, quantity, course and prescription type complete
Digital signature applied; controlled-drug rules met
Message conforms to SCCI0052 / current EPS FHIR profile

Last updated: 2026-06-04 — confirm the current schema/version, identifiers, coding and standards against current authority (nhs.uk / NHS Digital EPS API) guidance before use.