Keystra n., prescription directions

Prescription directions for a pharmacist to review.

Keystra shows the original prescription directions beside fields for a pharmacist to fill in and approve. Unclear text stays marked for review.

The problem

what arrives at the pharmacy

Prescription instructions can arrive in shorthand. A pharmacist needs to confirm what each line means before it goes onto a label or into a record.

what needs a pharmacist’s review

A pharmacist checks every line. Keystra leaves uncertain text for review and refuses uploaded files with patient identifiers before storing them.

what the pharmacist can do

Review the original instruction
The screen keeps the prescription line beside the fields the pharmacist fills in and approves.
See Plate I and Plate III.
Leave unclear text for review
When Keystra cannot read part of a line, it leaves the field for the pharmacist instead of guessing.
See Plate I and Plate III.
Refuse files with patient details
An upload that may identify a patient is refused before the app stores it.
See Plate II.
Keep approved work consistent
The finished set uses the lines a pharmacist approved, so later changes do not silently replace them.

Plate III. A diagram of a sample prescription line beside its fields. The data is made up.