01
Generate
Seeded outpatient-visit-v1 Bundle. Same seed, same case.
LAUNCH PRODUCT
Coherent synthetic FHIR R4 4.0.1. Not a mock server. The bytes on the wire are the product.
THE LOOP
Healthcare software developers and QA generate a clinically coherent
synthetic R4 collection Bundle from the pinned
outpatient-visit-v1 template and a seed, inspect the exact
JSON, then POST a transaction Bundle to their FHIR HTTPS endpoint.
01
Seeded outpatient-visit-v1 Bundle. Same seed, same case.
02
The JSON you see is the JSON you transmit. No pretty-print cousin.
03
POST when you are ready. Never regenerate on send.
THE OLD WAY
Hand-written Patient.json does not survive contact with a
real FHIR server. Mocks invent disconnected resources.
SimHealth projects one outpatient visit into a valid R4 Bundle you can actually POST — Patient, Encounter, Condition, ServiceRequest, Observation, Provenance.
PINNED TEMPLATE
One adult. One ambulatory encounter. One condition. One order. One observation. Provenance included. Bring your own dictionaries when we cannot ship one.
FOR INTEGRATION ENGINEERS
FHIR R4 application/fhir+json. Official validator. Fail
closed. Replayable from workspace + scenario + seed.
FOR QA
Exact payload bytes, payload hash, and certification findings — labeled synthetic, never clinical care.
OPEN SANDBOX
There is no fake generate console on this page. After sign-in,
/app is the one-page loop. Hosted generate, inspect,
and send are not advertised on /health yet — the app shows
that gap instead of a pretend Bundle.
curl -fsS https://api.simhealth.interoperabilitypro.com/health
● live GET /health
API host api.simhealth.interoperabilitypro.com
Synthetic data only. Output is labeled non-clinical. Engineering and QA tests — not diagnosis, not evidence of care.