Extract data from patient intake forms
Unstract reads patient intake forms filled in on a clipboard, scanned, faxed or photographed, handwriting included, and posts a checked registration record to your EHR or practice management system.
ins card front + back scanned w/ this - MA
REG-01 (REV 2025/07) · PAGE 1 OF 3
{ "patient": "Okafor, Rosalind", "date_of_birth": "04/17/1988", "phone": "541-555-0142", "emergency_contact": "Daniel Okafor", "payer": "Cascade Peak Health Plan", "member_id": "CPH884120573", "subscriber_relationship": "Spouse", "allergies": "Penicillin (hives)", "medications": "Lisinopril 10 mg daily", "confidence": 0.94}
Trusted by healthcare and revenue cycle teams around the globe
Patients fill in the form wherever they happen to be
Some patients type their answers into a portal PDF. Most of the stack at the front desk looks like this.
Faxed over by the referring office, then scanned again
Allergies and medications written in pen, one crossed out
Last year's form, this year's form and the portal version
Registration, history, privacy notice and insurance card in one scan
A pharmacy printout of medications stapled to the back
Front desk staff key every page into the registration screen by hand while the waiting room fills, and a mistyped member ID returns weeks later as a denied claim.
Unstract reads the intake packet, pulls the demographics, insurance and history fields you name, checks them against each other, and posts the record to your EHR or practice management system.
Read the clipboard form, check the record, register the patient
LLMWhisperer reads the form, Document Studio returns the registration record with its checks, and Flow carries it into your intake process. Each product works on its own, so a front desk can start with one day's forms.
Read patient intake forms with each handwritten answer next to its label
An intake form mixes printed labels with a patient's handwriting: a name in capitals, a date of birth squeezed into a small box, an allergy list that runs into the margin. LLMWhisperer keeps the layout, so the emergency contact's phone number stays with the emergency contact and never becomes the patient's own. It reports which boxes are ticked and which are blank, and reads clipboard forms that were scanned, faxed or photographed on a phone.
Send the text to your own LLM, or make it the first step of a full patient intake run.
Learn more about LLMWhispererTurn every patient intake form into one structured registration record
Describe the registration record once: demographics, emergency contact, primary insurance with subscriber and relationship, primary care physician, reason for visit, allergies, medications and the signed acknowledgment. Medical form data extraction then returns the same JSON whether the patient used your current form, last year's version or the portal PDF. Checks you set travel with each record: the member ID matches the insurance card in the packet, the subscriber's name and relationship agree, and the signature and date are present.
Deploy it as an API behind your patient portal, or as an ETL pipeline over the folder where the front desk scanner saves.
Learn more about Document StudioRun referral and patient intake from the fax to the work queue
Describe your patient intake forms, and the referrals and insurance cards they arrive with, in plain language, and Flow's agents build the intake workflow from that description. You approve the workflow, and every packet then runs through it the same way: picked up from the fax line, the portal or the scanner, split into its pages, read, matched to an existing patient or set up as a new one, and placed in the work queue of your EHR or practice management system.
An uncertain patient match, a missing page or an out-of-network plan stops for an intake coordinator, with the reason attached. Unstract reads what the patient wrote. It does not give clinical advice, review the history for a clinician or confirm that the coverage is active.
Learn more about FlowRead a day of intake forms today. Plan the referral run with us.
Start for free and extract a folder of registration forms. A run that feeds your EHR or practice management system starts with a consultation.
Registration forms, history questionnaires and the pages clipped to them
Documents
- New patient registration forms
- Patient information forms
- Medical history questionnaires
- Emergency contact forms
- HIPAA acknowledgment forms
- Consent to treat forms
- Financial responsibility agreements
- Insurance card copies, front and back
- Photo ID copies
- Medication and allergy lists
- Pediatric and guardian intake forms
- Any other intake paperwork your practice uses
Fields captured
Built for the people who register patients
Check-in without retyping a clipboard form, and a registration record waiting before the patient reaches the window.
One way of reading intake forms across every location and form version, with fewer registration errors reaching billing.
Registration packets from scheduled admissions and referrals read and matched to the right patient record before the visit.
Specialty history questions and dental history forms read with the same care as the registration page.
Less keying at check-in, cleaner registrations
Handled as protected health information from the first page
An intake form holds a patient's name, date of birth, address, insurance member ID, allergies and medications on one sheet. Exposed together, they give away who the patient is, how they are covered and what they are treated for.
- Encrypted in transit and at rest.
- Patient forms are never used to train models.
- Access by role, location and form type, with every correction recorded against the patient's record.
- Processed forms are deleted on the retention schedule your practice sets.
- Self-hosted deployment for health systems that keep PHI inside their own environment.
What front desks and practice managers ask first
Yes. You describe the fields for each document type once, so the same platform reads a bank statement, an ACORD application and a patient intake form, and each comes back in its own schema. A practice usually starts with registration and history forms and adds referral letters and insurance cards after that.
Check five things: it reads handwriting next to printed labels, it reports blank and ticked checkboxes, it keeps each answer with its own field, it sends unclear values to a person, and it delivers to your EHR or practice management system. LLMWhisperer covers the reading and Document Studio returns the fields, with human review built in.
Yes. LLMWhisperer reads handwriting alongside printed text and shows filled and unfilled checkboxes in its output, so a "No known allergies" box left blank is read as blank, not skipped.
Yes. Emergency contact form OCR returns the contact's name, relationship and phone numbers, and a HIPAA acknowledgment comes back with the checkbox state, the signature and the date. Uploaded inside a full packet, each page is classified first and read as its own document.
Three ways. Document Studio deploys an API endpoint per form type for your portal or your developers to call, or runs as an ETL pipeline over a scanner folder. Flow, the third, runs the whole intake and places each registration in the work queue of your EHR or practice management system.
Yes. POST a scanned intake form to the endpoint for that form type and the registration record comes back as JSON, with any flagged fields marked for review.
No. Unstract reads what the patient wrote and checks it against the rest of the packet, such as the member ID against the insurance card. Eligibility checks stay with your payer tools, and the history stays with your clinicians.
The form stops in a review queue. Front desk staff see the field and the spot on the page it came from, correct or confirm it, and the change is recorded against the patient. Clear forms keep moving.
LLMWhisperer reads printed text in more than 300 languages and handwriting in 12, so a registration form a patient completed in a language other than English goes through the same extraction and checks.
Unstract is SOC 2, ISO 27001, GDPR and HIPAA compliant. Intake forms are encrypted in transit and at rest, never used to train models, and kept only as long as your retention schedule allows. Health systems can self-host. The controls are listed in the Trust Center.
For extraction, a practice manager can start for free and upload a registration form the same day. For the full intake run, we build it with your team in a consultation around your forms and your EHR or practice management system.
Bring last week's intake packets to the consultation
Clipboard forms, faxed referrals, phone photos and the insurance cards clipped to them. We read them in the session and walk through every field that would have stopped for review.