Skip to main content
PDF4me APIIntegrationsKnowledge BaseExtensionsAPI TesterBlog

AI-Health Card Parser in Power Automate

AI-Health Card Parser is a Power Automate action by PDF4me that reads a health insurance card with AI and returns member ID, group number, plan type, coverage dates, and prescription benefit data as structured JSON. Use it to automate patient registration, insurance verification, or pharmacy benefit checks without manual data entry.

What this action does

PDF4me AI-Health Card Parser reads a health insurance card (PDF, PNG, JPG, or JPEG) and returns memberId, groupNumber, planType, insuranceProvider, memberName, coverage dates, and prescription benefit fields inside a healthData object, along with per-field confidence scores. Optionally set Body/customFieldKeys to pull additional fields beyond the standard set.

Related Blog Posts
No blog post yet for this feature — coming soon.
In the meantime, browse the PDF4me blog for tutorials and workflows across every platform.
Visit the blog →

How Do I Authenticate My Power Automate Flow?​

Every PDF4me action in Power Automate requires a valid connection. Create or select one that holds your PDF4me API key so the flow can authenticate AI health card processing requests securely.

Get your API Key

Important Facts You Should Not Miss​

Only two fields are always required
Health Card File Content (the document bytes) and Health Card Name (the filename with extension). Body/customFieldKeys lives under Advanced parameters and is optional.
Output nests under healthData
Member, plan, and prescription fields all sit inside processedData.healthData. Reference the nested path when mapping fields into later flow actions.
Check confidence scores before trusting the output
The confidence object scores key fields from 0 to 1. Route low-confidence extractions to manual review in insurance verification or billing flows.
Power Automate AI - Health Card Parser action configured with File Content and Body/Document/Name fields

Map File Content and Body/Document/Name, then expand Advanced parameters for Body/customFieldKeys.

Parameters​

Required: Health Card File Content and Health Card Name must always be provided. Body/customFieldKeys is an optional Advanced parameter.

ParameterRequiredWhat it doesExample
Health Card File ContentRequiredBinary content of the health card, mapped from a previous action (Get file content, SharePoint, OneDrive, email attachment). Supports .pdf, .png, .jpg, .jpeg.body('Get_file_content')
Health Card NameRequiredFilename of the health card including its extension. Used for format detection and processing.health_card_2024.jpeg
Body/customFieldKeysOptionalAdvanced parameter. Array of additional field names to extract beyond the standard health card data set.["customField1", "customField2"]

Output Fields​

FieldTypeWhat it contains
successBooleantrue if the health card was processed successfully, false if extraction failed.
messageStringDescriptive message describing the result of the processing run.
processedData.healthData.memberIdStringThe unique member identification number extracted from the health card.
processedData.healthData.groupNumberStringThe group or policy number associated with the health insurance plan.
processedData.healthData.planTypeStringThe type of health insurance plan, for example PPO, HMO, or EPO.
processedData.healthData.insuranceProviderStringThe name of the insurance company or provider on the card.
processedData.healthData.memberNameStringThe full name of the insured member.
processedData.healthData.dateOfBirthStrStringThe member date of birth, formatted as YYYY-MM-DD.
processedData.healthData.effectiveDateStrStringThe date the health insurance coverage becomes effective, formatted as YYYY-MM-DD.
processedData.healthData.rxBinStringThe Bank Identification Number for prescription drug coverage.
processedData.healthData.rxPcnStringThe Processor Control Number for prescription drug coverage.
processedData.healthData.rxGroupStringThe group identifier for prescription drug coverage.
processedData.healthData.copayInfoArrayList of copay details by service, for example Primary Care or Specialist.
processedData.healthData.confidenceObjectPer-field confidence scores on a 0-1 scale for key extracted values.
processedData.statusStringOverall status of the health card processing operation.
processedData.errorsArrayAny errors encountered while processing the health card. Empty when none.
processedData.jobIdStringUnique identifier for the AI processing job, used for tracking and debugging.
processingTimestampStringISO 8601 timestamp indicating when processing completed.
{
  "success": true,
  "message": "Health card processed successfully using AI",
  "processedData": {
    "healthData": {
      "memberId": "M123456789",
      "groupNumber": "GRP001234",
      "planType": "PPO",
      "insuranceProvider": "Blue Cross Blue Shield",
      "memberName": "John Michael Smith",
      "dateOfBirthStr": "1985-03-15",
      "effectiveDateStr": "2024-01-01",
      "rxBin": "123456",
      "rxPcn": "ABC123",
      "rxGroup": "RXGRP001",
      "copayInfo": [
        { "service": "Primary Care", "copay": "$25" },
        { "service": "Specialist", "copay": "$50" },
        { "service": "Emergency Room", "copay": "$200" }
      ],
      "confidence": {
        "memberId": 0.95,
        "memberName": 0.98,
        "insuranceProvider": 0.92
      }
    },
    "status": "Success",
    "errors": [],
    "jobId": "11111111-2222-3333-4444-555555555555"
  },
  "processingTimestamp": "2024-01-15T10:30:45.123Z"
}

How Do I Set Up AI-Health Card Parser in Power Automate?​

  1. Add PDF4me → AI-Health Card Parser to your Power Automate flow.
  2. Map Health Card File Content from a previous action (SharePoint, OneDrive, Dropbox, or an email attachment).
  3. Set Health Card Name with the file's extension (.pdf, .png, .jpg, or .jpeg).
  4. Optionally expand Advanced parameters and set Body/customFieldKeys for any fields beyond the standard set.
  5. Run the flow. The parsed result returns as a healthData object nested inside processedData, with member, plan, coverage, and prescription fields plus confidence scores.

Typical Setups​

Workflow ExamplesCommon Power Automate flow patterns using AI-Health Card Parser.
Patient registration intake
  1. A flow triggers when a patient uploads a health card image through a portal or email.
  2. AI-Health Card Parser extracts memberId, memberName, dateOfBirthStr, and insuranceProvider.
  3. The extracted fields are written to a SharePoint list or patient management system.
  4. A Condition checks the confidence object and routes low-confidence rows to manual review.
Insurance verification
  1. A flow triggers when a health card is received via email or SharePoint upload.
  2. AI-Health Card Parser extracts groupNumber, planType, and effectiveDateStr.
  3. A verification record is created and linked to the patient's insurance profile.
Pharmacy benefit lookup
  1. A patient uploads a health card to a pharmacy intake flow.
  2. AI-Health Card Parser extracts rxBin, rxPcn, and rxGroup.
  3. The prescription identifiers feed a pharmacy benefit verification step, and copayInfo drives the patient copay estimate.

Practical Tips​

Reference the nested healthData path
Extracted fields live under processedData.healthData, not at the top level of the response. Map the full path in downstream actions.
Always branch on success and confidence
Check success before writing extracted data downstream, and inspect the confidence object for any fields scored below your review threshold.
Custom fields extend, they do not replace
Body/customFieldKeys adds extra entries alongside the standard healthData fields, it does not narrow or filter the standard set.
copayInfo is an array, not a flat field
Loop over copayInfo with Apply to each when writing copay amounts to a table, since a card can list several services.
Match the file extension to the real format
Health Card Name must carry the true extension (.pdf, .png, .jpg, .jpeg) of the mapped File Content, a mismatched extension can affect processing.

Cheat Sheet​

FieldValue
ActionAI-Health Card Parser
Required fieldsHealth Card File Content, Health Card Name
Optional advanced fieldBody/customFieldKeys
Supported file types.pdf, .png, .jpg, .jpeg
Output rootprocessedData.healthData
Key output fieldsmemberId, groupNumber, planType, insuranceProvider, memberName, dateOfBirthStr, effectiveDateStr, rxBin, rxPcn, rxGroup, copayInfo, confidence

Common Questions​

What data can the AI-Health Card Parser extract from a health insurance card?+
Member ID, group number, plan type, insurance provider, member name, date of birth, effective date, Rx BIN, Rx PCN, Rx group, and a copayInfo array listing copay amounts by service type.
Does the action tell me how confident it is in the extracted fields?+
Yes. The confidence object returns a 0-1 score for key fields such as memberId, memberName, and insuranceProvider, so flows can route low-confidence extractions to manual review before the data reaches a patient or billing system.
Can I extract fields beyond the standard health card data set?+
Yes. Set Body/customFieldKeys to an array of additional field names. Each key you list is extracted alongside the standard healthData fields, in addition to the built-in set.
What file formats does the AI-Health Card Parser accept?+
PDF, PNG, JPG, and JPEG. Health Card Name must include the matching file extension for correct format detection and processing.
How do I use the extracted Rx BIN and PCN in a pharmacy workflow?+
The rxBin, rxPcn, and rxGroup output fields map directly to the identifiers pharmacy systems use for prescription benefit verification and claims submission. See <a href="https://learn.microsoft.com/en-us/azure/ai-services/document-intelligence/prebuilt/health-insurance-card?view=doc-intel-4.0.0" target="_blank" rel="noopener noreferrer">Microsoft's health insurance card data extraction reference</a> for the kind of structured fields these cards typically expose.

Industry Use Cases & Applications​

  • Patient Registration: Automate patient registration with health card data extraction
  • Insurance Verification: Verify patient insurance coverage automatically
  • Benefits Verification: Check patient benefits and coverage eligibility
  • Appointment Scheduling: Link insurance information to appointment records

Same Task on Other Platforms​

Get Help​

PDF4me ConnectGet your API KeyPower Automate Documentation