Medical History Extractor

Turn a patient intake form into data: demographics, allergies, medications, past conditions, surgeries, and family history from a medical history PDF.

The full guide: Conditions with onset dates from a medical history form

How should we start?

Build with Talonic

Need to scale? Create an API key, then run this from your own code or an agent.

Create an API key

Free account required

Start with a document

Upload a file or pick a sample, and see the fields come back.

No signup · nothing stored

Questions about Medical History Extractor.

What does the medical history extractor capture?

The form date, patient identifier, name, date of birth, gender, marital status, address and contact, the emergency contact name, relationship and phone, and the provider and managing organization completing the intake.

How are allergies, conditions, and surgeries returned?

As their own tables. Allergies return the substance, reaction type, severity, and onset date; past medical history returns each condition with onset and resolution dates and status; and surgeries return the procedure name, date, surgeon, outcome, and facility.

Does it read the medications list?

Yes. The medications table returns one row per drug with the medication name, dose, dosing instructions, status, and the date it was started, alongside the free-text current medications summary.

Are family and social history captured?

The family history table returns each relative relationship, condition, onset age, and status, and the social history fields record tobacco, alcohol, and drug use, plus the review of systems narrative.

Is the intake form stored after extraction?

No. It is processed via the Talonic API for extraction only, is not retained for training, and is not shared. Handle identified PHI with care; for BAA-covered work, ask about the Talonic platform. PDF only, up to 10MB and 100 pages.

Doing this to one file, or to ten thousand?

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.