Patient Registration Extractor

Read patient demographics, contact details, emergency contacts, and insurance information from a patient registration form. Extraction only, PHI-aware.

The full guide: Policy and group number on a patient registration 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 Patient Registration Extractor.

What does the patient registration extractor capture?

It reads a patient registration or demographics intake form: the patient identifier (MRN or national ID), first and last name, birth date, administrative gender, marital status, and the deceased indicator, plus the managing organization that is custodian of the record and whether the record is active.

Which contact and address fields come out?

The street, city, state, and postal code of the patient's address, the primary phone number and email, and the emergency contact name, relationship, and phone. The Social Security number or national identifier is captured when present and treated as sensitive PII.

Does it capture insurance information?

Yes. The insurance provider name, the policy or member ID number, and the group number for employer-sponsored plans come back as their own fields, so registration and coverage detail are structured together.

How is this different from a clinical or medical-history record?

Patient registration captures demographics, contact, and insurance for record-keeping and check-in — it does not carry clinical findings, diagnoses, or treatment. The extractor also returns four tables: patient demographics, patient contact, emergency contacts, and insurance information, each keyed by the patient identifier.

What are the file limits and privacy terms?

One PDF up to 10MB and 100 pages. The form contains PHI and PII; it is processed via the Talonic API for extraction only, is not retained for training, and is not shared. Export as CSV, XLSX, or JSON.

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.