Trust and data handling
Last updated: August 2026
ClinicalSim is intended for training and assessment. It does not diagnose patients, recommend treatment, or create clinical documentation. Every case uses a synthetic patient written from clinical literature, not a patient record.
Every case uses a synthetic patient. The product still handles learner recordings, transcripts, account data, and institutional data, so those records require protection.
1. Intended use
ClinicalSim is intended for clinician training and assessment. The platform produces no patient-facing output, makes no diagnostic or treatment recommendation, and does not create clinical documentation.
What it produces is a rubric-scored record of how a clinician handled a simulated conversation, mapped to the competency standard or communication framework approved for the case.
2. Every patient is synthetic
Every patient in every ClinicalSim case is authored from the clinical literature, not adapted from a real chart. Case development does not require a patient record or a de-identification step.
A case written from the literature can be versioned and reviewed by the physicians responsible for it. How cases get built is documented on our methodology page.
3. Cases, rubrics, and scoring prompts are versioned and locked
Once a case is published, its case text, its rubric, and its scoring prompts are versioned and locked. A program can identify the exact materials used for a learner's report and inspect the transcript evidence behind the score.
4. Learner voice data
Learners speak their side of the conversation out loud, which makes their voice data sensitive. The platform also handles transcripts, account data, and institutional data. Voice collection is consent-gated, and learners can request erasure.
A learner's recording exists to generate that learner's feedback. Our privacy policy covers visitors to this website; learner data inside the product is governed by the institutional agreement and by the practices on this page.
5. Product boundaries
ClinicalSim does not price malpractice risk or benchmark one institution against another. It extends standardized patient programs and does not replace live assessment.
We also don't claim our scoring is more accurate or more valid than a faculty member's read. We don't have the validation data to say that, and we won't claim it until we do.
6. Questions from privacy and procurement reviewers
What is ClinicalSim's intended use?
ClinicalSim is intended for clinician training and assessment. It produces no patient-facing output, makes no diagnostic or treatment recommendation, and does not create clinical documentation.
Does ClinicalSim use patient records to build cases?
No. Every patient in a ClinicalSim case is synthetic and written from clinical literature rather than a patient record. The product still handles learner recordings, transcripts, account data, and institutional data, which require protection.
What happens to a learner's voice recording?
Learner voice data is consent-gated and learners can request erasure. A recording exists to generate that learner's feedback.
Can a program review the scoring materials after the fact?
Yes. Published cases, rubrics, and scoring prompts are versioned and locked, so a program can identify the exact materials used for a learner's report.
Does ClinicalSim price malpractice risk or benchmark our institution against others?
No. ClinicalSim does not price malpractice risk or benchmark one institution against another. The platform produces timestamped practice records scored against expert-authored rubrics.
If your security review needs something this page doesn't cover, ask us.
We'll tell you what exists and what doesn't. You can also read how cases get built on our methodology page, work through the rest of the buying decision on evaluating ClinicalSim, or see how we handle website data in our privacy policy.