Synthetic healthcare/Synthetic
Patient flow
Operational flow for a synthetic care setting. Each encounter records when it arrived, which department it moved through, how long it stayed, and how it ended. There are no real patients. This set is the pathway, not the clinical chart. Coded diagnoses and procedures live on the patient-record and claims sets.
- Volume
- 500,000encounters
- Formats
- CSV · Parquet · JSONL
- Label
- Synthetic
Purchase
Sold on Datarade. This site does not take payment.
Placeholder — listing URL not set
Schema
Column preview for the launch specification. Names and types describe the file. They are not a sample of rows.
- encounter_idstring
Identifier for one encounter.
- patient_idstring
Synthetic patient identifier. Not a real person.
- arrival_timetimestamp
When the encounter started.
- departmentstring
Department the encounter moved through.
- acuityinteger
Coarse acuity level.
- length_of_stay_mininteger
Length of stay in minutes.
- dispositionstring
How the encounter ended, such as discharged or admitted.
Use
- Test patient-flow and capacity models
- Simulate department movement without real operational data
Generation
Synthetic encounter flow from arrival to disposition. There are no real patients.
- Every dataset is 100% synthetic. It is not copied from real customers, cardholders, or patients.
- Each product is labeled as synthetic in the title, the description, and the file metadata.
- Delivery includes a generation note: the methods and algorithms used, the schema, and known limitations.