Extract data from insurance cards and verification forms
Unstract reads medical and dental insurance cards, front and back, and the verification forms your staff fill in, from scans, faxes and phone photos, and posts the payer, member ID and benefits to your EHR or practice management system.
call ref 4471902 - prior auth not req for visit
IV-02 (REV 2026/01) · PAGE 1 OF 2
{ "patient": "Vance, Teodora", "date_of_birth": "09/22/1979", "payer": "Halden Ridge Health Plan", "plan_type": "PPO", "member_id": "HRH55301847", "group_number": "G48816", "subscriber_relationship": "Spouse", "specialist_copay": "$45", "deductible": "$1,500", "confidence": 0.93}
Trusted by healthcare and revenue cycle teams around the globe
Patients hand over a card, and the card never comes in the same way twice
A few patients upload a clean scan through the portal. The rest show up at the window with a phone photo, a worn plastic card or a fax from the referring office.
A card copy faxed twice, the member ID half lost to toner
Benefits written down during the payer call, one copay corrected
Every payer prints the member ID in a different spot
Card front, card back, photo ID and the worksheet in one file
A benefit summary printout clipped behind the form
Staff copy the member ID, group number and plan type off a card photo by hand, and one swapped digit sends the claim back denied weeks after the patient has gone home.
Unstract reads the card and the verification form, pulls the payer, subscriber and benefit fields you name, checks them against each other, and posts the record to your EHR or practice management system.
Read the card, check the coverage details, hand the record on
LLMWhisperer reads the card and the form, Document Studio returns the insurance record with its checks, and Flow carries it into your intake process. A front desk can start with the parsing alone and add the rest when it suits.
Read insurance cards and verification forms with each value beside its label
An insurance card packs a payer logo, a member ID, a group number, plan codes and three phone numbers into a space the size of a credit card, and the back carries the claims address and the provider line. LLMWhisperer keeps that layout, so the group number stays a group number and the pharmacy BIN never lands in the member ID. On the verification form it reads the typed card details, the benefits a staff member wrote in pen during the payer call, and which plan type box is ticked.
Phone photos taken at an angle, glare on a plastic card and a card copy faxed twice all come through as text. Send it to your own LLM, or use it as the first step of a full intake run.
Learn more about LLMWhispererTurn each insurance card and verification form into one coverage record
Describe the coverage record once: patient, payer, plan type, member ID, group number, subscriber and relationship, effective date, the provider phone line, and the copay, coinsurance and deductible exactly as the payer quoted them. Document Studio returns the same JSON for a medical card, a dental card or a handwritten worksheet. Checks you set travel with each record: the member ID on the form matches the card image, the subscriber's date of birth is present when the patient is a dependent, and the effective date falls before the appointment.
Deploy it as an API behind your patient portal, so a card photo posted at online check-in comes back as fields, or as an ETL pipeline over the folder your front desk scanner saves to.
Learn more about Document StudioRun referral and patient intake with the insurance card read first
Describe your insurance cards and verification forms, and the referrals and registration pages they arrive with, in plain language, and Flow's agents build the intake workflow from that description. You approve it, and every packet then runs the same way each time: picked up from the fax line, the portal or the scanner, split into pages, read, matched to the patient, and placed in the work queue of your EHR or practice management system.
An uncertain patient match, a card that disagrees with the form or an out-of-network plan stops for an intake coordinator, with the reason attached. Unstract reads what the card and the form say. The eligibility check itself stays with your clearinghouse or the payer portal.
Learn more about FlowRead a folder of card photos today. Plan the intake run with us.
Start for free and extract a batch of insurance cards and verification forms. A run that feeds your EHR or practice management system starts with a consultation.
Insurance cards, verification forms and the benefit sheets behind them
Documents
- Medical insurance cards, front and back
- Dental insurance cards, front and back
- Insurance verification forms
- Dental insurance verification forms
- Medical insurance verifications
- Verification of insurance eligibility forms
- Patient eligibility and benefit information sheets
- Patient insurance information forms
- Secondary insurance forms
- Benefit summaries printed from payer portals
- Coordination of benefits questionnaires
- Any other insurance paperwork your front desk keeps
Fields captured
Processes these forms feed
Built for the people who check coverage before the visit
Card photos from online check-in turned into payer, member ID and group number fields, ready to run through your eligibility check.
One coverage record format across every location, with fewer denials traced back to a mistyped member ID.
Cards and verification sheets for scheduled admissions read and attached to the right registration before the patient arrives.
Dental verification forms read with annual maximums, frequency limits and waiting periods kept as the payer stated them.
Fewer cards retyped, fewer claims back for a wrong member ID
Member IDs and coverage details treated as PHI from the first scan
An insurance card ties a patient's name and date of birth to a member ID, a group number and an employer's plan. That pairing is what someone needs to bill a payer in the patient's name, so a card copy is protected health information the moment it is scanned.
- Encrypted in transit and at rest.
- Card images and verification forms are never used to train models.
- Access by role and location, with every corrected member ID recorded against the patient's account.
- Card copies are deleted on the retention schedule your practice sets.
- Self-hosted deployment for hospitals and groups that keep PHI inside their own network.
What front desks ask about reading insurance cards
Insurance card OCR reads the text on a photo or scan of a medical or dental insurance card: payer, plan type, member ID, group number, subscriber and the phone lines on the back. Unstract then returns those values as named fields, so nobody types them into the registration screen.
Unstract is software, not an insurance card scanner device. It reads insurance cards, front and back, from photos and scans, and it reads verification forms. It does not check eligibility with the payer in real time. The extracted data feeds your own eligibility check through your clearinghouse or the payer portal. Developers call it as an insurance verification API in that sense: POST a card image or a form, get the coverage fields back as JSON for the eligibility step.
Yes. LLMWhisperer handles photos taken at an angle, glare on a plastic card and low-contrast prints. Upload the front and back as two images or one file, and the record combines both sides.
Yes. Dental insurance verification form OCR returns the same payer and subscriber fields plus the dental benefits your staff wrote down: annual maximum, frequency limits for cleanings and X-rays, waiting periods and coverage percentages by service class.
Three ways. Document Studio exposes an API endpoint your portal or developers call, or runs as an ETL pipeline over a scanner folder. Flow runs the full intake and places each coverage record in the work queue of your EHR or practice management system.
The record stops in a review queue. A staff member sees the field next to the spot on the card it came from, confirms or corrects it, and the change is logged against the patient's account. Clear cards keep moving.
Yes, when the form or the cards say so. A patient insurance information form that lists two plans comes back with a primary and a secondary block, each with its own payer, member ID and subscriber.
Yes. Benefits are returned as written on the form, "$1,500 / $620 met" included, so your billing team sees what the payer told your staff on the call and not a rounded figure.
Unstract is SOC 2, ISO 27001, GDPR and HIPAA compliant. Card images are encrypted in transit and at rest, never used to train models, and deleted on your retention schedule. Hospitals can self-host. The full list of controls is in the Trust Center.
A practice manager can start for free and upload a card photo the same day. For the intake run into your EHR or practice management system, we build it with your team in a consultation around your own cards and forms.
Bring a week of insurance cards and verification worksheets
Phone photos, faxed card copies, dental verification forms and the benefit printouts stapled to them. We read them in the session and show which member IDs would have stopped for review.