Your scenarios.
Bring existing teaching material, review the extracted details beside their source and approve the version you want to use.
Your sim.
Connected.
The scenario. The session. The debrief.
Bring your clinical teaching into one workflow. Prepare the patient journey, guide a live session, then return to the moments that matter.
Hosted demo · fictional patient dataLocal-first software · Windows / Chrome & Linux MVP
Your scenario, connected to your room.
BAY 03 · ACUTE ASTHMA
SIMULATIONArrival from triage
SpO₂ %89
Pulse bpm118
Resp. /min28
Simulated patient observations
Explore the patient journey
00:00
Session begins. The patient arrives breathless.
Try it: choose a state, then flag a moment. Interactive preview · illustrative data
See the workflow.
Keep the context.
Follow the educator’s path from reviewed scenario to live session and debrief, with fictional teaching data.
Captions, transcript and tutorialsBuilt around
your teaching.
Your scenario may begin in a Word document. Your session unfolds across people, devices and screens. Your debrief needs the story behind the numbers.
OpenHealthSim connects that work through a local runtime and replaceable plugins, so your room can be configured without rewriting the patient journey.
Follow the first-session guideThe source repository is currently private. Public licensing and distribution remain separate release steps.
Your room.
Choose roles, learner stations and output routes for each session. Keep manual charting and console delivery available when equipment is not connected.
Your models.
Choose compatible cloud or local providers for the AI tasks you use. Review suggestions before they become part of an approved scenario.
Your extensions.
Add a panel, device mapping or workflow through the plugin interfaces. Inspect its requirements and permissions before installation.
Explore the developer guideTested Windows and Linux MVP.
Windows with Chrome and Linux are the tested MVP scope. macOS and actual Safari / iPad checks remain open.
Run the session locally.
The runtime, database and application can live on your machine. Chosen cloud AI features need internet access. The hosted clinician demo lets you explore the workflow first.
A working app.
A real workflow.
Prepare a session or return to one already in progress. The console, learner record and debrief stay connected to the saved session.
Open the clinician demo
One workflow.
End to end.
Prepare the scenario, configure the room, explicitly start the session and debrief with its saved history. Keep the teaching decisions in your hands.
Start with the work
you’ve already done.
Start with a Word document, Markdown file or pasted text. A configured AI provider proposes patient states and learning outcomes for your review. PDF results depend on the document.
Review the source, correct the details, then approve a scenario version before it runs.
.DOCX.PDF.MDTEXT
Acute asthmaFacilitator guide.docx
SOURCEPATIENT PRESENTATION
A 29-year-old with known asthma arrives breathless and hypoxic on room air.
“Learners assess, apply oxygen, escalate with SBAR and give a nebuliser.”
Patient journeyReady for your review
Shape every
turning point.
Review the extracted patient journey. Adjust states, set the expected actions and choose what happens when learners respond, wait or change course.
Source-backed fields and AI suggestions stay distinguishable until you approve them.
Patient journeyREVIEW
ENTRY POINTAcute asthmaSpO₂ 89% · pulse 118 bpm
Oxygen applied
RespondingSpO₂ 94% · pulse 112 bpm
Time elapses
DeterioratingFacilitator can intervene
Keep your attention
in the room.
Create a prepared session, then start it explicitly from the console. Guide the patient journey, route configured outputs and follow learner activity as the story unfolds.
Pause a session, hold a state or take manual control whenever the teaching moment calls for it.
Try the interactive previewBay 03EXAMPLE ROUTING
One patient state
VitalsBedside monitor
Patient dialogueRoom speaker
Actor cuesConfederate’s phone
ObservationsLearner record
Return to the
moments that matter.
Follow the path learners took through the scenario. Bring together recorded actions, patient observations and flagged moments to guide a focused debrief.
Recording and transcription add context when configured and consented. The facilitator reviews the material before using it in a debrief.
Session debriefEXAMPLE
00:00
Arrival from triage
Baseline observations established
02:14
Oxygen applied
Patient enters the responding state
05:32
Patient improving
Reassessment becomes the teaching focus
Flag a moment in the preview to add it here.
Your room.
Your equipment.
Connected.
Every lab has its own setup. Keep your scenario focused on the patient, and map its outputs to the screens, speakers and interfaces you use.
Talk through your setupSIMULATION LABEXAMPLE CONFIGURATION
DISPLAYBedside
monitorPatient observations
monitorPatient observations
AUDIOThe patient’s
voiceRouted dialogue
voiceRouted dialogue
OpenHealthSimThe scenario connects the room.
TABLETLearner
patient recordCharted observations
patient recordCharted observations
INTERFACEConnected
lab equipmentMapped inputs & outputs
lab equipmentMapped inputs & outputs
Your site profile defines what connects.
A familiar screen becomes part of the sim.
Pair browser-based displays and actor views with the session. Give each person the information their role needs.
The scenario travels with you.
Define channels such as patient voice and bedside monitor once. Each room routes them to its own equipment.
The session runs locally.
The runtime, database and interface live on your machine. Cloud AI is used when your chosen import or voice provider requires it.
Device connectivity depends on the interface or adapter configured for your equipment.
Build your own.
Bring your agent.
Describe a useful extension to your coding agent. The plugin-creation skill guides it through the public interfaces, lifecycle tests and a package you can review.
From a need to an integrationEXAMPLE WORKFLOW
“Connect our monitor. Here are three messages it sends.”
The plugin-creation skill guides your agent through creating the mapping, testing the sample messages and configuring your room’s routes.
Device mappingTestsSite configuration
Build and test in a development profile. Review before installing in your lab.
Connect a device
Turn sample messages into a tested mapping.
Create a plugin
Build a custom panel, interface or workflow with the SDK and testkits.
Add your scoring
Translate a local score table into tested rules for clinical review.
Set up your site
Describe the room. Configure its outputs and routes.
The developer guide includes the plugin-creation skill, a fictional example and the review and packaging workflow.
Get the plugin-creation skill Private source repository · no public npm release assumedExtend the lab.
Review every
installation.
The plugin workflow makes requirements, permissions and compatibility visible. Review a package, install it, configure it and choose when to activate it.
Read the plugin guideTry it first.
Go deeper
at your pace.
Take the guided route through a fictional clinical scenario, or head straight to the instructions you need.
Send an overview to a colleagueBefore you
get started.
Who is OpenHealthSim for?
Simulation educators, clinical facilitators and lab teams who prepare scenarios, run teaching sessions and lead debriefs. The clinician demo uses fictional patient data for education.
What can I try in the demo?
Explore a prepared fictional scenario, create a session, explicitly start it in the console and review its debrief. Follow the linked quickstart for the guided route. The animated example at the top of this page is illustrative; the clinician demo is the separate working application.
Can I use my own scenarios and equipment?
Word and text-based import support source review and human approval. PDF extraction depends on the document. Equipment needs a compatible, configured interface or mapping; there is no blanket hardware-compatibility claim.
Does it need the internet?
The application, session runtime and database can run locally. Paired devices need access to the lab network. Optional cloud AI tasks require the relevant provider and an internet connection. The hosted demonstration needs internet access.
Which platforms have been tested?
The tested MVP scope covers Windows with Chrome and Linux. macOS and actual Safari / iPad checks remain open. Clinical validation and real-device verification are separate from these software checks.
Is the source code public?
The repository is currently private. The Apache SDK and plugin skill are available as downloads; the private application and general npm distribution have not been released. The developer guide explains the available plugin skill and artifacts without assuming a public npm package.
Your next sim.
Start exploring.
See the workflow with a fictional patient scenario.
Then bring the questions that matter to your lab.
Try the clinician demo Hosted demonstration · fictional patient dataDiscuss your lab with Innov2Learn