---
title: "Test Account Disclaimer: Read This Before Using a Test Account"
slug: "test-account-disclaimer-read-this-before-using-a-test-account"
updated: 2026-07-16T19:21:08Z
published: 2026-07-16T19:21:08Z
canonical: "docs.claim.md/test-account-disclaimer-read-this-before-using-a-test-account"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.claim.md/llms.txt
> Use this file to discover all available pages before exploring further.

# Test Account Disclaimer: Read This Before Using a Test Account

Claim.MD test accounts are intended for development, integration testing, and training purposes only. Before entering information or submitting transactions, review the requirements in this article carefully.

Never Enter Real Data

**Never enter real patient, provider, NPI, Tax ID, enrollment, claim, or payment information into a test account.**

Test environments are not intended for live production data. Always use fictional information created specifically for testing.

  

## Purpose of a Test Account

The primary purpose of a Claim.MD test account is to allow developers and vendors to verify that electronic transactions can successfully pass through Claim.MD.

A test account may be used to confirm that:

- A connection to Claim.MD is working.
- Files or requests are being transmitted successfully.
- Claim data is formatted correctly.
- Claim.MD can receive and process the submitted test transaction.
- API, SFTP, X12, XML, CSV, or JSON workflows are functioning as expected.

Testing Does Not Send Claims to a Payer

A test account is used to evaluate the connection and formatting of test transactions. It is not intended for submitting live claims or transmitting real healthcare information.

  

## Requesting a Test Account

Test accounts are not created through the standard self-service account registration process.

To request a test account:

1. Submit a test account request through the appropriate Claim.MD contact or internal process.
2. Provide the requested company, vendor, developer, and integration information.
3. Wait for the Claim.MD team to create and configure the test account.
4. Use the credentials and setup instructions provided for that account.

New API test accounts may automatically display the API Quick Start Guide when the user signs in.

Review the [API Quick Start Guide](https://docs.claim.md/docs/test-account-quickstart-guide)API developers should review the Quick Start Guide before generating credentials, submitting requests, or testing transactions.

API developers should review the Quick Start Guide before generating credentials, submitting requests, or testing transactions.

## Test Data Requirements

All information entered in a test account must be fictional. Do not copy information from a real provider, patient, claim, enrollment, ERA, or production account.

Do not enter real:

- Patient names or demographic information
- Dates of birth
- Member or subscriber identification numbers
- Provider names
- National Provider Identifiers
- Tax Identification Numbers
- Claim information
- Enrollment information
- Banking or payment information
- Electronic Remittance Advice information

Use Fictional Information Only

Even when testing a screen or feature that requests provider, patient, enrollment, or payment information, do not enter real information. You may review the available fields, but do not complete or submit the form with production data.

## Existing Sample Information

Test accounts may already contain sample providers, claims, payer information, credentials, or other test records. These records may be required for the test environment to function correctly.

Do Not Change Existing Sample Numbers

Do not edit, replace, or delete the sample NPI, Tax ID, payer, provider, or account values already included in the test account unless Claim.MD specifically instructs you to do so.

Changing established sample values may prevent test claims or integrations from working properly.

## Enrollment Warning

Enrollment pages and enrollment links may connect to live external websites or services. Information submitted through those external systems may be treated as real enrollment information, even when the user began in a test account.

Do Not Submit Test Enrollments

Do not complete or submit an enrollment from a test account. Enrollment information may be sent outside the Claim.MD test environment to an external system.

You may review the enrollment workflow, but do not enter or submit real provider, contact, banking, or organization information.

Submitting real enrollment information or using real provider identifiers in a test environment may cause live ERA, payer, or enrollment activity to become associated with the test account.

## Adding a Test Provider

You may practice adding a provider or create a provider record for use with test claims. However, the provider information must be fictional and must follow the approved test-data format.

Before adding a provider, review the existing provider list:

- If a test provider already exists, use the provider information already listed.
- If no test provider exists, use **1111111112** for the NPI and **741111111** for the Tax ID.
- Do not create another provider using these values if they are already assigned to an existing provider in the account.

When you reach the **Add Provider** screen:

1. Review the provider list to determine whether a test provider already exists.
2. If a test provider exists, use the provider information already available.
3. If no test provider exists, enter a fictional provider or organization name.
4. Enter **1111111112** for the NPI.
5. Enter **741111111** for the Tax ID.
6. Do not use an NPI or Tax ID belonging to a real provider or organization.
7. Save the provider and use it only for test transactions.

| Field | Required Test Value |
| --- | --- |
| Provider Name | Use a clearly fictional name, unless an existing test provider is already available. |
| NPI | Use **1111111112** only if a provider with this NPI does not already exist. Otherwise, use the existing test provider. |
| Tax ID | Use **741111111** only if a provider with this Tax ID does not already exist. Otherwise, use the existing test provider. |
| Address | Use a fictional or approved test address. |
| Contact Information | Use approved test contact information. |

Check for an Existing Test Provider First

Before adding a provider, review the existing provider list. If a test provider is already available, use that provider instead of creating another one.

If no test provider exists, use **1111111112** for the NPI and **741111111** for the Tax ID. ![](https://cdn.document360.io/367e6528-88da-4443-9da1-fcdd7e6d4d49/Images/Documentation/image-1784213154953.png)

## Testing Claim Submissions

Test claims should be designed to verify the transmission method and claim formatting. They must not represent an actual patient encounter or billable service.

Developers may submit fictional test claims through supported methods such as:

- Claim.MD API
- SFTP
- X12 837 files
- XML
- JSON
- Other approved test formats

The test should confirm that the transaction:

1. Successfully reaches Claim.MD.
2. Uses the correct account credentials.
3. Meets the required file or request structure.
4. Contains the required segments, fields, and values.
5. Can be parsed and validated by Claim.MD.
6. Returns the expected response or status information.

Review Before Every Submission

Before submitting a test claim, verify that every patient, subscriber, provider, payer, claim, and service value is fictional or part of the approved Claim.MD sample data.

## Test and Production Accounts

A Claim.MD test account cannot be converted into a production account.

When you are ready to begin submitting live transactions, you must create or obtain a separate production account. A test account and production account may remain open at the same time.

| Test Account | Production Account |
| --- | --- |
| Used for development, integration testing, and training. | Used for real healthcare transactions. |
| Must contain fictional or approved sample information only. | Contains actual provider, patient, claim, enrollment, and payment information. |
| Does not replace a production account. | Requires its own registration, configuration, and approval. |
| Cannot be converted into a production account. | Remains separate from the test environment. |

Keep Credentials Separate

Test and production accounts use separate credentials and environments. Confirm that your application is connected to the correct environment before transmitting any information.

## Test Account Dos and Don’ts

| Do | Don’t |
| --- | --- |
| Use the test account for development, training, and integration testing. | Do not use a test account to submit live claims. |
| Use fictional or Claim.MD-approved sample data. | Do not enter real patient or provider information. |
| Use the approved test NPI and Tax ID formats. | Do not enter a real NPI or Tax ID. |
| Leave existing sample numbers unchanged. | Do not edit or delete established sample data without instructions. |
| Review enrollment screens without submitting information. | Do not submit enrollment forms from the test account. |
| Verify whether your integration is using the test or production environment. | Do not use production credentials in a test connection. |
| Create a separate production account when you are ready to go live. | Do not expect the test account to be converted into production. |

Final Reminder

**Never enter real data into a Claim.MD test account.** Use only fictional information and approved test values. When you are ready to process real healthcare transactions, use a separate Claim.MD production account.