> For the complete documentation index, see [llms.txt](https://docs.mindee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mindee.com/use-cases/extraction-models/us-healthcare-card.md).
# US Healthcare Card
Automatically parse US healthcare cards and extract structured healthcare provider data using the US Healthcare Card model template available in the Catalog.
## US Healthcare Card
Documentation for the data schema of the US Healthcare Card model template.
## Create Your US Healthcare Card Model
* Click on "Create your document AI model" in your dashboard, then select **"US Healthcare Card"**.
* The US Healthcare Card model template comes pre-configured with [standard fields](#us-healthcare-card-fields).
* Once your model is created, you can immediately [test](/models/live-test.md) with your own documents.
* Optionally, you can adjust the model's [Data Schema](/extraction-models/data-schema.md) if you need to modify fields.
## US Healthcare Card Fields
Documentation for all fields present in the data schema.
Field *accessors* are used as the keys for accessing the values in the returned data. On the data schema interface, this is the "Field Name".
Field *value types* indicate how the value is returned by the API. On the data schema interface, this is the "Field Type".
Company Name
The name of the company that provides the healthcare plan
Accessor: `company_name`\
Value Type: `string`
Has a single value.
Plan Name
The name of the healthcare plan
Accessor: `plan_name`\
Value Type: `string`
Has a single value.
Member Name
The name of the member covered by the healthcare plan
Accessor: `member_name`\
Value Type: `string`
Has a single value.
Member ID
The unique identifier for the member in the healthcare system
Accessor: `member_id`\
Value Type: `string`
Has a single value.
Issuer 80840
The organization that issued the healthcare plan
Accessor: `issuer_80840`\
Value Type: `string`
Has a single value.
Dependents
The list of dependents covered by the healthcare plan
Accessor: `dependents`\
Value Type: `string`
Can have multiple values (is a list/array).
Group Number
The group number associated with the healthcare plan
Accessor: `group_number`\
Value Type: `string`
Has a single value.
Payer ID
The unique identifier for the payer in the healthcare system
Accessor: `payer_id`\
Value Type: `string`
Has a single value.
Rx BIN
The BIN number for prescription drug coverage
Accessor: `rx_bin`\
Value Type: `string`
Has a single value.
Rx ID
The ID number for prescription drug coverage
Accessor: `rx_id`\
Value Type: `string`
Has a single value.
Rx Grp
The group number for prescription drug coverage
Accessor: `rx_grp`\
Value Type: `string`
Has a single value.
Rx PCN
The PCN number for prescription drug coverage
Accessor: `rx_pcn`\
Value Type: `string`
Has a single value.
Copayments
Copayments for covered services.
Accessor: `copayments`
**Subfields**
* **Service Name**\
Service name\
Accessor: `service_name`\
Possible Values: `primary_care`, `emergency_room`, `urgent_care`, `specialist`, `office_visit`, `prescription`
* **Service Fees**\
Service price\
Accessor: `service_fees`\
Value Type: `number`
Can have multiple values (is a list/array).
Enrollment Date
The date when the member enrolled in the healthcare plan
Accessor: `enrollment_date`\
Value Type: `date`
Has a single value.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.mindee.com/use-cases/extraction-models/us-healthcare-card.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.