Docyield's insurance card scanner reads a health insurance card into the fields a front desk or billing system actually needs. Upload a photo or scan and you get back the member name, the insurer, the member ID and group number, the plan name and type, the coverage effective date, the pharmacy RxBIN, RxPCN and Rx group, and the customer service phone number — as JSON, CSV, or Excel. The cluster of codes that makes an insurance card so fiddly to copy becomes a clean, labelled record.
Insurance cards are notorious for cramming a dense grid of codes into a small space, and no two insurers lay them out the same way. The pharmacy benefit codes in particular — RxBIN, RxPCN, RxGroup — hide among similar-looking numbers and are easy to mis-key. Docyield reads the card in context, recognising what each code is rather than relying on its position, so it pulls the right value into the right field even when the layout is unfamiliar.
What an insurance card scanner captures
A health insurance card carries two layers of information. The first identifies the patient and their coverage: the member or subscriber name, the insurer, the member ID, the group number, the plan name, the plan type such as PPO or HMO, and the date coverage took effect. The second governs pharmacy claims: the RxBIN that routes the claim, the RxPCN that identifies the processor, and the Rx group. A customer service phone number rounds it out. The scanner captures each of these and assigns it to its own field.
That separation is the whole value. On the card the codes sit side by side and look almost identical, so a manual copy easily swaps the RxBIN for the RxPCN. By labelling each one, Docyield hands back a record where the member ID is unmistakably the member ID and the pharmacy codes are exactly where a claims system expects them.
Why structured extraction beats raw OCR
Plain OCR reads an insurance card as a string of words and numbers with no idea which code does what. You are left holding a list of digits and acronyms and the task of matching each to its meaning — precisely the step where pharmacy benefit codes get crossed.
Structured extraction settles that up front. The member ID, group number, and each Rx code arrive as named fields, so a billing or eligibility system can read them by name rather than parsing free text. With stable field names across every card, a batch of cards becomes a uniform dataset you can load directly instead of a pile of transcripts to reconcile by hand.
Pharmacy benefit codes done right
The RxBIN, RxPCN, and Rx group exist to route a prescription claim to the correct processor, and getting them wrong means a rejected claim at the pharmacy counter. Because they are short, numeric, and clustered together, they are the single most error-prone part of manual card entry.
Docyield treats them as first-class fields, reading each one in context and returning it under its own key. Where a card omits one — not every plan prints all three — that field comes back empty rather than borrowing a nearby value, so you never silently inherit the wrong code. Always confirm the pharmacy codes against the card before a claim, since the cost of an error here is concrete.
Who uses an insurance card scanner
- Medical and dental front desks capturing coverage details at patient check-in.
- Billing and revenue-cycle teams recording member and pharmacy data for claims.
- Pharmacies entering RxBIN, RxPCN, and Rx group to process prescriptions.
- Telehealth and patient-intake apps that ask new patients to photograph their card.
- Developers adding card capture to a healthcare app through the API.
Accuracy, limitations, and review
No scanner reads every insurance card flawlessly, and the honest position is to make the failure modes clear. Glossy laminates throw glare, small print and dense code grids strain OCR, and a creased card or an angled photo distorts the text. A flat, sharp, well-lit image of the card gives the cleanest read, and many cards carry the customer service number and additional codes on the back, so capturing both sides is often worthwhile.
When a field is absent or unreadable, Docyield returns it empty rather than guessing, because a wrong member ID or pharmacy code causes a real downstream problem. The sensible workflow keeps a review step: confirm the member ID, group number, and the Rx codes against the card before using them. Docyield transcribes what the card shows and does not check eligibility, coverage, or whether the card is current.
Privacy and sensitive health data
An insurance card carries personal and health-related data, and Docyield treats uploaded files accordingly: they are used only to produce your result and are not used to train models. The fields come back exactly as printed, with no enrichment or lookups against any external record, so nothing is added beyond what is on the card.
Returning the member ID, group number, and pharmacy codes as discrete fields makes it straightforward to store, mask, or drop each according to your own data-handling rules once extraction is complete. Docyield provides no legal or compliance advice and makes no verification guarantees — how the data is handled is your decision.
Output formats and the API
Each scan exports as JSON, CSV, Excel, or XML from the same result. JSON suits developers feeding a healthcare application; CSV and Excel suit billing teams keeping records in a spreadsheet; XML fits older practice-management imports. The free tool reads one card at a time, which covers occasional check-ins.
When you need to capture cards at volume, the Docyield API and batch dashboard return the same schema shown here, so you can process many cards, receive results by webhook, and apply your own validation. The field names stay identical between the free tool and the paid plans.
What the insurance card scanner extracts
Each card is returned against a fixed schema, with values transcribed exactly as printed. Codes the card does not carry come back empty rather than guessed.
- Member name
- The member or subscriber name on the card.
- Insurer name
- The insurance company name.
- Member ID
- The member or subscriber ID.
- Group number
- The group number for the plan.
- Plan name
- The name of the plan.
- Plan type
- The plan type, such as PPO or HMO.
- Effective date
- The date coverage takes effect.
- RxBIN
- The pharmacy RxBIN that routes the claim.
- RxPCN
- The pharmacy RxPCN identifying the processor.
- Rx group
- The pharmacy Rx group.
- Customer service phone
- The customer service phone number printed on the card.
How to scan an insurance card into structured data
- 1Upload the card — drop a PDF, PNG, JPG, or WEBP onto the box above, or click to choose a file.
- 2Use a flat, sharp, well-lit image; capture the back too, since codes and the service number often live there.
- 3Wait a moment while Docyield reads the card and sorts the values into fields.
- 4Review the result, confirming the member ID, group number, and the Rx codes against the card.
- 5Choose your output tab — JSON, CSV, Excel, or XML — then copy or download the data.
Frequently asked questions
Processing documents at scale?
Batch upload, an extraction API, and webhooks for 100+ documents a month.