Explore development tutorials, how-tos and case studies


Key Words

Ideas for using the EPS Prescription Tracker API – Patient Facing Apps

Back to the related article about the EPS Prescription Tracker API.

Don’t get too excited. This API does not meet the primary needs that patient facing applications need with regard to prescribed and dispensed medication data. The reason is that the API does not expose actual medication names, quantities or dosages. 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 4 medication items and only 1 prescription appears via the API then 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. See the article Electronic Prescription Service (EPS) For Dummies Part II: A deeper look for more on the status values used by the EPS.