How to request a new prescription
There are two variations of entry points for ordering a new issue of a prescription
These are either from starting at viewing a patients Medications (MedicationStatement
) or viewing a patients Prescriptions (MedicationRequest
).
Starting with Medication
If a Patient wishes to start at viewing their Medications, a standard user journey would look like this:
Search by NHS Number to obtain
MedicationStatement
resources related to the patient, using the endpoint: GET /FHIR/R4/Patient/{NHSNumber}
/MedicationStatementThis returns a
Bundle
containingMedicationStatement's
which includes information surrounding the Medication to be displayed to the patient.Each MedicationStatement references a
MedicationRequest
withintent
ofplan
. TheMedicationRequest
is a representation of the prescription, these contain further details about the prescription itself, i.e. whether it's acute or repeat and if it has expired.The next stage in the user journey would be to resolve the referenced
MedicationRequest
to obtain thecourseOfTherapyType
of the Prescription (as part of MVP we're only building for reordering of repeat prescriptions, although the API can cater for this), and also to validate that it is a valid authorization that hasn't expired. Use the Endpoint: GET /MedicationRequest/{id}
for this stage.Once the prescription has been validated as authorized and repeat, we can then use the same id to request a reorder of that prescription.
Create a new request of a prescription reorder using
Task
and having afocus
that has a reference of the sameMedicationRequest
that hasintent
, theTask
resource is then used as the requestbody for the endpoint: POST /FHIR/R4/Task/At this stage the patient can then track the status of the order, or send a cancellation up (until the point the request is actioned).
INTERACTION DIAGRAMS TO BE COMPLETED
Starting with prescriptions
If a Patient wishes to start at viewing their Prescriptions, a standard user journey would look like this:
Search by NHS Number to obtain
MedicationRequest
resources related to the patient, using the endpoint: GET /FHIR/R4/Patient/{NHSNumber}
/MedicationRequestThis returns a
Bundle
containingMedictionRequest's
which includes information surrounding the Prescription's to be displayed to the patient.At this stage it is possible to verify which are repeat prescriptions, by the
courseOfTherapyType
and which are still authorized to be reordered.Now the id of the validated
MedicationRequest
can be used to create a new request of a prescription reorder.
This will be done the same way, using Task
and having a focus
that references the same MedicationRequest
that has intent
, the Task
resource is then used as the requestbody for the endpoint: POST /FHIR/R4/Task/
- At this stage the patient can then track the status of the order, or send a cancellation (up until the point the request is actioned).
INTERACTION DIAGRAMS TO BE COMPLETED
Requesting to a one off pharmacy nomination
Should the patient choose to order to a one off nomination this can simply be done by including the ODS code of the one off nominated pharmacy in the input
element of the Task
resource.
Example:
"input": [ { "type": { "coding": [ { "system": "https://fhir.hl7.org.uk/GPConnect-PrescriptionOrderingParameters", "code": "preferred-performer", "display": "Preferred performer" } ] }, "valueIdentifier": { "system": "https://fhir.nhs.uk/Id/ods-organization-code", "value": "FLM49" } } ]