Skip to main content
Most EHR-provided “sandbox” patients are little more than UI demos — they rarely resemble the volume, structure, or messiness of production data. Use Fasten’s official FooClinic test server and curated external datasets to validate ingestion, normalization, and downstream analytics before you onboard live connections. FooClinic provides predictable synthetic patient personas for end-to-end Fasten testing, while third-party datasets help you cover larger volumes, different formats, and messier clinical scenarios.

Official FooClinic Test Data

FooClinic is Fasten’s official sandbox test server. Use these synthetic patient personas to validate the Fasten Widget sign-in flow and downstream EHI export handling with predictable test data.
1

Select FooClinic

In the Fasten Widget, choose FooClinic (Sandbox) from the health system list.
2

Click Sign in

Start the sandbox portal flow by clicking Sign in.
3

Use a test patient

Sign in with one of the usernames and passwords in the table below.
FooClinic in the Fasten Widget Ages are calculated from fixture birth dates as of July 2026. Need a new synthetic test patient? Contact support@fastenhealth.com with:
  • Persona summary
  • Required FHIR resource types
  • Expected record size or volume
  • Edge cases needed for your testing workflow

TEFCA Test Fixtures

Fasten embeds these deterministic C-CDA fixtures for TEFCA API-mode testing. Pass a fixture name as fixtures.tefca_ccda when creating an EHI export in test mode through the EHI Export request’s fixtures option. Ages are calculated from fixture birth dates as of July 2026. The three Myra fixtures intentionally represent the same patient demographics in different C-CDA documents. This gives integrations duplicate-patient coverage for comparing document variants without inventing a synthetic identity.

External datasets

In addition to FooClinic, you can use curated external datasets to validate your ingestion, normalization, and downstream analytics workflows. These datasets are useful when you need broader coverage than the FooClinic personas, such as bulk FHIR exports for population health analysis, research datasets, or format conversion fixtures.

How to use synthetic patient data

1

Choose a dataset

Pick data that matches the workflow you want to mimic, such as FHIR Bulk exports, claims-heavy data, or pediatrics.
2

Convert it to NDJSON

If necessary, convert the dataset to newline-delimited JSON. Fasten’s /ehi_export endpoint provides FHIR resources in NDJSON format, with one resource per line.
3

Load it into your pipeline tooling

Drop NDJSON files into the same object storage bucket that you store Fasten exports in, or POST bundles against your local test endpoint.
4

Run your production validations

Run the exact conversions and validations you expect to run for real patients, including schema validation, de-identification, transformations, and downstream notifications.
5

Swap the input source

Use Fasten’s /ehi_export payloads when you are ready for end-to-end testing. No code changes should be required if your fixtures match the contract.
Keep the original archive of each dataset in version control or object storage so test runs are reproducible and easy to diff across releases.
Use these when you need broader coverage than the FooClinic personas, such as bulk FHIR exports, research datasets, or format conversion fixtures.

FHIR and synthetic patient datasets

Clinical research datasets

FHIR examples and tutorials

CCDA samples

IPS samples