Extract the Rx number, prescriber, patient, pharmacy, and each medication with its NDC code, strength, quantity, and refills from a prescription PDF.
The full guide: Drug, strength, refills, and sig on a prescription order
Need to scale? Create an API key, then run this from your own code or an agent.
Create an API keyFree account required
Upload a file or pick a sample, and see the fields come back.
No signup · nothing stored
The medications table returns one row per drug with the drug name, NDC code, strength, route of administration, quantity to dispense, and number of refills authorized, alongside the free-text dosing instructions (the sig).
The prescriber name, license or DEA number, and contact, and the patient name, date of birth, gender, identifier, address, and contact details, so the parties on the order are captured without re-keying.
Yes. The dispensing pharmacy name and NPI, the Rx number, the issue date, and the expiration date after which the prescription is no longer valid are each read, along with the medication status and intent.
The extraction reads content rather than a fixed layout, so an e-prescription export and a scanned printed script both parse once saved as PDF, up to 10MB and 100 pages.
It is processed via the Talonic API for extraction only, is not retained for training, and is not shared. Redact identifiers where possible; for workflows that need a BAA, ask about the Talonic platform rather than the free tool.
The tool reads a single document. The platform reads the whole estate once and keeps it queryable — the same engine, with a memory.
See document data extraction if you run this for clinical and billing teams, or the extraction API if you are building it in.