Generate synthetic FHIR patient records for EHR testing
John
Generate realistic synthetic patients as FHIR R4 bundles for EHR testing, no privacy risk. Returns demographics, conditions, medications, procedures.
Input
Output fields
Sign up on Apify or log in
The Synthea - Create Synthetic FHIR Compliant Health Records Actor is ready to run with the inputs already set for "Generate synthetic FHIR patient records for EHR testing". Sign up or log in and you'll land in Apify Console with a copy of this exact task.
Start the "Generate synthetic FHIR patient records for EHR testing" task
The Synthea - Create Synthetic FHIR Compliant Health Records Actor will start running based on the input automatically. You can also change all the input fields, like population size and use us core implementation guide, to match your specific use case.
Receive the "Generate synthetic FHIR patient records for EHR testing" output
Monitor the progress in real time. You will be notified as soon as your dataset is complete and ready for review. Each result includes data such as patient count, generation timestamp, generation summary, and more.
Integrate into your workflow
The final output is delivered in JSON, CSV, or Excel format, ready to be plugged into your workflow. You can also run the "Generate synthetic FHIR patient records for EHR testing" task via API.

Integrate "Generate synthetic FHIR patient records for EHR testing" into your workflow
Connect "Generate synthetic FHIR patient records for EHR testing" with 100+ integrations, or run it via API or MCP.
Webhook
n8n
Make
Zapier
Airbyte
Keboola
IFTTT
Hubspot
GDrive
Gmail
Apify MCP
GitHub
Slack
LangChain
LlamaIndex
Flowise
Pinecone
OpenAI
Mastra
Clay
Generate synthetic FHIR patient records for EHR testing writes one dataset item with patient_count, generation_timestamp, summary and generated_files. The FHIR R4 bundles, all fabricated by Synthea, sit in the run's key-value store.
population_size 2 and exporter_fhir_use_us_core_ig true, so both synthetic patients come as US Core R4 profiled bundles. Add a seed to get the same patients back on every run, which keeps EHR test assertions stable.
Start the task from its run endpoint on the Apify API or with apify-client in Python or Node, then read each key_value_store_key from the dataset item and fetch that FHIR Bundle from the run's key-value store.
In the Apify Console open the task, choose Actions, then Schedule, and set 0 2 * * * for two in the morning. Leave seed empty so each run fabricates new patients, and point the test suite at the latest run's key-value store.
Add https://mcp.apify.com/?tools=actors,docs,johnvc/synthea-medical-record-generator-api in Claude or any other MCP client and ask for two synthetic US Core patients for an EHR test. The agent runs the Synthea API.
The Synthea Actor uses pay-per-event pricing: a fee per patient record generated plus an Actor Start charge when the run begins, so population_size sets most of the cost. Current rates are on the Actor page.
Every patient, encounter, condition and medication in Generate synthetic FHIR patient records for EHR testing is fabricated by Synthea, so no real PHI is involved. Create FHIR test data for healthcare app development works the same way.