This is the first issue of a monthly series with one purpose: making the claim that iatroX Simulations is continuously improved something a reader can check, month by month, rather than an assertion made once at launch. Each issue documents what has actually changed and what is being evaluated next.
The launch
iatroX Simulations launched with eighteen examination-specific tracks and 1,114 clinician-reviewed cases: MRCGP SCA, PLAB 2, UKMLA CPSA, MRCP PACES, MRCPsych CASC, MRCEM OSCE, MRCOG Part 3, ORE Part 2, CCFP SOO, NAC OSCE, ABEM Certifying Exam, ABA APPLIED, NBOME C3DO, USMLE Step 3 CCS, RACGP CCE, ACEM Clinical, RACP DCE and AMC Clinical. Every case passed the seven-point clinician-review process described in the methodology article, with reviewers matched to each examination's profession and specialty.
What the launch includes
Responsive voice and text interaction. Practice mode, exam mode and full mock circuits. Transcript-linked, domain-organised feedback. Tutor-led remediation connected to each attempt. Prescribed next cases and longitudinal readiness tracking. Web and native app availability with shared progress. One complete free simulation before subscribing, and unlimited access within the existing all-access subscription.
Design principles established at launch
Exam-sensitive design, with tracks built around what each examination actually tests rather than one spoken-patient template applied everywhere. Explicit scoping for hybrid examinations, PACES, RACP DCE, ORE Part 2, C3DO, stating what remains bedside or hands-on. Readiness tracked as trajectory and pattern, not presented as validated pass prediction. And the claims hierarchy this launch's content follows throughout: clinician-reviewed, never examination-body endorsed; broad, never claimed as the largest library where competitors advertise more.
Being evaluated next
Session-start and completion rates across web and app. Median response latency and reconnect rate. Voice-to-text correction rate, including across accents, so that any future accent-performance statement rests on measurement. Disputed-feedback frequency, as a direct quality signal. Tutor follow-through and repeat performance after remediation, the most direct evidence that the loop works. And case coverage gaps identified through early use and clinician re-review.
How to contribute
Report any case behaviour, feedback point or technical issue directly; reports enter the investigation, clinician review, regression testing and release process described in the continuous-improvement article, and material changes will appear in subsequent issues of this series.
Why this series exists in this specific form
A single launch announcement, however thorough, cannot itself demonstrate ongoing improvement, since improvement is only visible over time. This monthly format exists specifically so that the continuous-improvement claim made throughout this cluster's launch content remains something a reader can verify issue by issue, rather than trust on the strength of a single article's promise. Readers who want to hold this platform to its own stated standard should check back here rather than take the launch commitment on faith alone.
What readers should expect from future issues
Future issues will follow the same structure consistently: what changed, why, and what is being evaluated next, avoiding vague language like improved experience in favour of specific, checkable statements, this case type was revised because of this identified issue, this metric moved in this direction over this period. Where a change turns out, on reflection or on further data, to have been the wrong call, that will be reported here too, since a change log that only ever reports success would not be the honest, checkable record this series exists to provide.
The series exists as a standing invitation to hold this specific claim accountable over time, month by month, rather than a promise made once and left unchecked. Readers are encouraged to check back monthly, and to treat any future issue that reports nothing of substance as itself informative about the pace of change during that period. A launch with no subsequent activity documented would itself be a signal worth reading, and this series is built specifically so that signal, whichever direction it points, is always visible. Case-by-case decisions about scope and coverage will continue to be made by clinicians with the relevant expertise, exactly as they were at launch, and any expansion into a nineteenth track or beyond will be documented here with the same specificity as every other change.
Frequently asked questions
Will case counts be updated in this series?
Yes: each issue will state current case numbers per track where they have changed, with the date checked, so the launch figure is understood as a starting point rather than a fixed total.
Will performance data be published here?
Aggregate performance learnings will be published only once a methodology exists to support population-level claims, in a separate series, rather than prematurely in these product-update issues.
How often will this series appear?
Monthly, documenting new coverage, revised cases, conversational and feedback changes, reliability improvements and what is being evaluated next.