MediSynth Open console
Synthetic patient cohorts

Clinical test data for systems that need to survive the real mess.

Generate synthetic patients across simulated upstream HIE/provider feeds, including mismatched identifiers, partial availability, stale addresses, and FHIR exports.

medisynth.generate
Generated patients 250,000
Source records 1.04M
FHIR resources 5.7M
{ "scenario": "mpi-hard-matches" } { "duplicateRate": 0.15 } { "export": "FHIR R4 NDJSON" }
Live cohort signal

Watch one synthetic cohort split into realistic upstream records.

Patient identities, source records, clinical resources, and exports move as a visible system instead of a black-box fixture dump.

Cohort seed 300312 patients shown
Platform

Built for product teams testing healthcare data workflows.

01

Native cohorts

Deterministic generation for patients, clinical facts, demographics, and upstream provider records.

02

Messy upstream feeds

Control duplicate rates, address drift, missing phones, upstream availability, and provenance.

03

FHIR output

Export Bundle and Bulk-style NDJSON artifacts for downstream integration tests. Saved exports expire after 30 days to keep accounts lean.

How we work

How we work with teams.

Start with the patient population your product needs to prove, then keep every cohort repeatable enough for demos, regression tests, and implementation handoffs.

01

Define the cohort

Pick geography, demographics, source systems, conditions, prevalence, and identity-variance controls.

02

Generate repeatably

Use deterministic seeds so the same scenario can be rerun by sales engineering, QA, and product teams.

03

Inspect and export

Review patient summaries, source records, quality signals, FHIR Bundles, and NDJSON artifacts before handoff.

04

Manage usage

Track API keys, credits, coupon-backed usage, retained cohorts, and 30-day artifact windows from the console.

Usage

Account credits and metered API usage are part of the console.

The app is designed for paid API access: tenants, API keys, patient quotas, usage ledgers, credit top-ups, and secure email authentication.

PlanDeveloper
Monthly quota100k patients
Credit balance$50
API keys3 max
API

Simple calls, generated data, inspectable outputs.

Use the console when you want to design visually, or use the API when your test suites, demo environments, and migration tooling need synthetic cohorts on demand.

POST /workspace/tenants/{tenantID}/cohort-jobs
Authorization: Account session
X-API-Key: ms_live...

{
  "name": "diabetes-ckd-ed",
  "population": 500,
  "hie": { "sourceSystems": ["north-hie", "county-clinic", "claims-feed"] }
}