Skip to main content
PDF4me APIIntegrationsKnowledge BaseExtensionsAPI TesterBlog

AI-Health Card Parser for Zapier

What this action does

PDF4me — AI-Health Card Parser in Zapier uses AI-powered machine learning to extract structured data from health insurance cards. Connect a patient portal upload, Gmail attachment, or cloud storage file as your trigger — the action returns member ID, plan type, group number, prescription BIN/PCN, copay details, and coverage dates as mapped fields ready for downstream Zap steps. No manual data entry. No custom OCR templates to configure.

Authenticating Your API Request​

Every PDF4me action in Zapier requires a connected account. Connect using your PDF4me API key when you add the action for the first time.

Get your API Key

Important Facts You Should Not Miss​

Supports PDF, PNG, JPG, and JPEG — include the right extension
The action accepts health card files in PDF, PNG, JPG, and JPEG formats. Always include the correct file extension in the Health Card Name field — the AI uses it to select the processing pipeline. Front-of-card images work for most fields; include the back if prescription Rx BIN/PCN fields are printed there.
Confidence scores let you build conditional routing logic
Every extracted field comes with a confidence score (0–1) in the output. Use Zapier Paths or Filters to branch your workflow — route low-confidence extractions to a manual review queue in Airtable or Slack instead of writing directly to your EHR or billing system. Only high-confidence records should flow automatically downstream.
Custom Field Keys extract non-standard card fields
Standard fields (member ID, plan type, copay) are extracted by default. Use the optional Custom Field Keys parameter to extract plan-specific or regional fields not in the standard set — pass them as a JSON array like ["deductible","outOfPocketMax"]. The AI will attempt extraction and return results with confidence scores.
Zapier PDF4me AI-Health Card Parser action showing Health Card File required field mapped from prior step, Health Card Name field with filename including extension, and optional Custom Field Keys field

Map Health Card File from your trigger or download step and set Health Card Name with the correct extension. The action returns all insurance fields as individual mappable tokens.

Parameters​

Required: Health Card File and Health Card Name. The Custom Field Keys parameter is optional and only needed for non-standard card fields.

ParameterRequiredWhat it doesExample
Health Card FileYesThe health card to parse. Map the binary file output from your Zap trigger or a prior download step. Accepts PDF, PNG, JPG, and JPEG formats. Hint: "Map the PDF file to be parsed."File from Gmail attachment
Health Card NameYesFilename of the health card including the correct extension (.pdf, .png, .jpg, or .jpeg). The AI uses the extension to select the processing pipeline — a wrong extension causes a format mismatch error. Map from the filename output of your source step.health_card_2024.jpeg
Custom Field KeysNoOptional JSON array of custom field keys to extract beyond the standard set. Use for plan-specific or regional fields not included by default. Pass as a JSON array string.["deductible","outOfPocketMax"]

Output Fields​

FieldTypeWhat it contains
memberIdStringUnique member identification number printed on the card. Map into patient records or use in a Filter to look up existing members.
groupNumberStringGroup or policy number. Used in insurance verification API calls and claims submissions.
planTypeStringType of health plan — PPO, HMO, EPO, Medicare, Medicaid, etc. Use in a Paths step to branch logic per plan type.
insuranceProviderStringName of the insurance company (e.g. Blue Cross Blue Shield, Aetna, UnitedHealth). Map into EHR or billing records.
memberNameStringFull name of the insured member as printed on the card.
dateOfBirthStrStringMember date of birth in ISO 8601 format. Cross-verify against registration data.
effectiveDateStrStringDate when coverage became or becomes effective. Use in a Filter to reject expired coverage before scheduling.
rxBinStringPrescription BIN number for drug coverage routing through pharmacy networks.
rxPcnStringPrescription PCN (Processor Control Number) for pharmacy claims.
rxGroupStringPrescription group identifier for pharmacy benefit management.
copayInfoArrayArray of copay entries — each with a service type (e.g. Primary Care, Specialist, Emergency) and copay amount.
confidenceObjectPer-field confidence scores from 0 to 1. Use in a Filter or Paths step to route low-confidence results to manual review.
successBooleanWhether the AI extraction completed without errors.

Quick Setup​

  1. In your Zap, click + to add a new action and search for PDF4me.
  2. Select AI-Health Card Parser as the event.
  3. Connect your PDF4me account using your API key.
  4. Map Health Card File to the binary file output from your trigger or download step.
  5. Set Health Card Name — include the correct extension (.pdf, .png, .jpg, or .jpeg).
  6. Optionally add Custom Field Keys as a JSON array if you need non-standard fields.
  7. Click Test action — expand the output to see all extracted fields as individual tokens.
  8. Map memberId, planType, copayInfo, and other fields into subsequent Zap steps. Add a Filter or Paths step using confidence scores to route uncertain records to manual review.

Workflow Examples​

Workflow ExamplesCommon Zapier workflow patterns using AI-Health Card Parser.
Patient portal upload → extract → create EHR record → confirm
  1. A new patient uploads their health card image via a Typeform or JotForm intake portal, triggering the Zap.
  2. AI-Health Card Parser extracts memberId, planType, insuranceProvider, and copayInfo from the uploaded image.
  3. A Paths step routes by planType — PPO patients go to one EHR workflow, HMO patients to another.
  4. An HTTP module creates a new patient record in the EHR system with all extracted insurance fields pre-populated.
  5. Gmail sends a confirmation to the patient listing their copay amounts for Primary Care, Specialist, and Emergency visits.
Email attachment → parse → verify eligibility → prep appointment
  1. Gmail triggers when a patient emails their health card before an appointment.
  2. AI-Health Card Parser extracts memberId, groupNumber, effectiveDateStr, and rxBin.
  3. A Filter blocks the Zap if effectiveDateStr is in the past — an automated email asks the patient for updated coverage.
  4. An HTTP module calls the insurer's eligibility API with memberId and groupNumber to confirm active benefits.
  5. A Slack message posts the copay amounts and plan type to the front-desk channel before the patient arrives.
Annual re-verification batch → re-extract → update records → flag changes
  1. A scheduled Zap triggers at the start of each year for annual insurance re-verification.
  2. Google Drive lists all health card images in an "annual-reverification" folder and loops over each file.
  3. AI-Health Card Parser re-extracts insuranceProvider, planType, effectiveDateStr, and groupNumber for each card.
  4. An Airtable step updates the patient record with the refreshed insurance data.
  5. A second Filter flags records where the insurer or group number changed since last year for manual review by the billing team.

Frequently Asked Questions​

What file formats does the AI-Health Card Parser accept?+
The action accepts PDF, PNG, JPG, and JPEG files. Pass the binary file output directly from your Zap trigger or a prior download step — do not pass a URL string. Always include the correct file extension in the Health Card Name field. Passing a PNG with a .pdf extension causes a format detection error because the AI selects its processing pipeline based on the extension.
What fields does the AI extract from a health insurance card?+
Standard fields include memberId, groupNumber, planType, insuranceProvider, memberName, dateOfBirthStr, effectiveDateStr, rxBin, rxPcn, rxGroup, and copayInfo (an array listing copay amounts for service types such as Primary Care, Specialist, and Emergency). Each field also has a confidence score from 0 to 1. Fields absent from a particular card return as empty strings rather than causing an error.
How should I use confidence scores in my Zap?+
The confidence object returned by the action contains per-field scores from 0 to 1. Add a Zapier Filter or Paths step immediately after this action. Route records with low-confidence memberId or insuranceProvider values (e.g. below 0.80) to a manual review queue in Airtable or a Slack alert channel. Only allow high-confidence records to flow automatically into your EHR, billing, or scheduling system — this protects data quality without blocking all automation.
What are Custom Field Keys and when should I use them?+
Custom Field Keys is an optional parameter that lets you extract plan-specific or regional card fields not included in the standard output set. Pass them as a JSON array string — for example ["deductible","outOfPocketMax","networkType"]. The AI will attempt extraction and return results with confidence scores for each custom key. Use this when your partner insurers print non-standard fields that your downstream patient management or billing system requires.
How accurate is the extraction on low-quality or blurry card photos?+
For clear, well-lit front-of-card photos or high-resolution scans, accuracy on core fields typically exceeds 90%. Blurry, overexposed, or low-contrast images produce lower confidence scores on the affected fields. If your intake channel consistently produces poor-quality images — for example, photos taken under fluorescent lighting — add an image enhancement step before this action. In all cases, use the confidence scores to route uncertain results to human review rather than writing them directly to sensitive clinical or billing systems.

Get Help​

Zapier IntegrationGet your API KeyZapier Documentation