-
Notifications
You must be signed in to change notification settings - Fork 40
Synthetic Data Guide
Note: this is in draft state - don't consult this for official use or publicize widely yet.
For development and testing purposes, the following claims data APIs:
- CMS Blue Button 2.0 (BB2.0)
- Beneficiary Claims Data API (BCDA)
- Data at the Point of Care (DPC)
- Medicare Claims Data to Part D Sponsors API (AB2D)
provide a set of public synthetic beneficiary and claims data, captured in synthetic Patient, Coverage, and ExplanationOfBenefit (EOB) resources. This is a resource that you can use as you explore and develop against the APIs in the sandbox environments. The synthetic data contains no personally-identifiable information (PII) or personal health information (PHI).
Our synthetic data will persist unchanged so that you can rely on it for ongoing use. That is, you can write tests, demos, etc. against this data, and the underlying data should not change later and produce unexpected results.
This data is intended for use in development and testing activities, e.g. building out an application prior to getting production access and having a safe set of data to use for ongoing development activities. It's also a great resource when demoing your application, giving you a safe way to do that without exposing any beneficiary PII or PHI.
The synthetic data will be available in each API's sandbox environment. Refer to specific API documentation for details.
- CMS Blue Button 2.0 (BB2.0)
- Beneficiary Claims Data API (BCDA) - Guide
- Data at the Point of Care (DPC)
- Medicare Claims Data to Part D Sponsors API (AB2D)
It's easy to distinguish the synthetic data from production data: all synthetic records have Patient.id and ExplanationOfBenefit.id values that are negative. All production records have positive values for those fields.
Please note that, while we are working to improve the coverage and quality of our synthetic data, there are absolutely still differences between it and our production data. In general, you should expect that:
- Not all fields will be present in the synthetic data.
- Some of the fields that are present may not have realistic values.
- The various releases of synthetic data (see below) will have differences from each other.
| Title | Beneficiary ID Ranges | Characteristics |
|---|---|---|
| Sample A? | -88888888888888 |
A single synthetic beneficiary with exactly one claim for each of the following EOB profiles:
|
| tbd | tbd | tbd |
| tbd | tbd | tbd |
| Time | Description | Details |
|---|---|---|
| Coming soon in 2021 | 10,000 Enhanced synthetic beneficiaries | Adding 10,000 more synthetic beneficiaries to the sandbox environment (not production yet) with more realistic and robust data in response to user requests. For example, this set will contain:
|
| Early 2021 | Additional Synthetic Beneficiary | A single synthetic beneficiary was added with exactly one claim for each of the following EOB profiles:
|
| Early 2021 | Added outpatient claims | Enhanced the initial set of beneficiaries to include outpatient claims, bringing the full list of EOB profiles to:
|
| 2017 | Initial 30,000 Synthetic Beneficiaries | 30,000 synthetic beneficiaries and about 1,000,000 synthetic claims that covered the following Explanation of Benefits (EOB) profiles:
|
For further questions on this synthetic data, please see the FAQ.
- Home
- For BFD Users
- Making Requests to BFD
- API Changelog
- Migrating to V2 FAQ
- Synthetic and Synthea Data
- BFD SAMHSA Filtering