Skip to main content

Guidance for developers: prescription tracker API – patient facing apps

This API does not expose actual medication names, quantities or dosages, so it does not meet the primary needs that patient facing applications need with prescribed and dispensed medication data. There is no way to link a repeat prescription request with the resulting Prescription ID’s.

The strategic solution to correlate requested prescriptions with authorised prescriptions and associated EPS prescription ID’s is the GPConnect API. Also please read a white paper on authentication and authorisation for FHIR interfaces onto local and national services/systems.

Using the Prescription Tracker API based on assumptions

If the patient has requested up to four medication items and only one prescription appears via the API, it can be assumed to be related if:

a) the prescription is from the correct GP practice

b) the prescription contains the expected number of medication item references

c) the prescription status is “To Be Dispensed”

d) the prescription date is after the requested date

If an assumed linked applies then the API can then be queried (polled) to track the prescriptions status through the “To Be Dispensed” >> “With Dispenser” >> “Dispensed” >> “Claimed” process. Find out more about the status values.

Related pages

Last edited: 3 July 2019 3:19 pm