> For the complete documentation index, see [llms.txt](https://docs.mdintegrations.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mdintegrations.com/partner/troubleshooting/technical-concepts/identity-verification.md).

# Identity Verification

Telehealth prescribing carries real risk if the person on the other end of an Encounter isn't who they claim to be. MDI gives partners two independent ways to verify a Patient's identity, and you can enable either or both, depending on your risk tolerance and the Offerings you sell.

## MDI Identity Cross-Check

MDI Identity Cross-Check is a managed verification service powered by [Vouched](https://vouched.id). Instead of integrating a third-party identity vendor yourself, MDI runs the check on your behalf as part of the clinical workflow — one less vendor relationship for you to manage.

* **How it runs**: Once enabled, the check fires automatically the first time a physician reviews an Encounter for a given Patient. It matches the demographic details the patient submitted (name, date of birth, address, etc.) against known identity records.
* **Enabling it**: In the Partner Portal, go to **Integration → Settings → Workflows** and turn on the Identity Cross-Check workflow.
* **Cost**: A per-check fee applies. Confirm current pricing with your MDI account contact before enabling it broadly.

Because the check runs automatically at physician review time, there's no API call for you to make on your end — enabling the workflow is the entire integration.

## Driver's License Verification

The second option is to have the partner collect and submit a photo of the patient's driver's license directly, giving the reviewing physician something concrete to check against.

1. Upload the license image via the Files API:

   ```
   POST https://api.mdintegrations.com/v1/partner/files
   Content-Type: multipart/form-data
   ```

   The response returns a `file_id`.
2. Pass that `file_id` as `drivers_license_id` when you create the Patient:

   ```json
   {
     "first_name": "Jane",
     "last_name": "Doe",
     "drivers_license_id": "{{ fileId }}"
   }
   ```

The uploaded license becomes part of the Patient's record, giving the reviewing physician a document to visually confirm against the submitted demographic details.

{% hint style="info" %}
All files referenced anywhere in the MDI platform — driver's licenses included — must be uploaded through the Files API first. You can't pass a raw external URL in place of a `file_id`. See Security & Data Handling for why.
{% endhint %}

## Choosing between them

Both methods can run independently or together, and the right choice usually comes down to how much integration effort you want to take on versus how much you want a human reviewing a document directly:

* **MDI Identity Cross-Check** is lower integration effort (no API work) and runs automatically, but adds a per-check cost and depends on third-party record matching.
* **Driver's License Verification** requires you to build an upload step into your intake flow, but gives a physician a direct document to review and doesn't depend on external record availability.

Higher-risk Offerings — controlled substances, higher-cost treatments — are good candidates for enabling both. Lower-risk Offerings may only need one, or neither, depending on your compliance posture.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.mdintegrations.com/partner/troubleshooting/technical-concepts/identity-verification.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.