Programs
Bring EMS decision training into Moodle and Canvas
Assign scenarios like graded coursework, launch with LTI identity, and pass performance artifacts back to the gradebook where your stack supports it — without rebuilding your sim lab every term.
- Integration
- LTI 1.3
- OIDC launch + platform registration
- Platforms
- Moodle · Canvas
- Patterns your LMS admin already speaks
- Fallback
- Native classes
- Same scenarios without LMS wiring
Why it lands
Simulation that scales like coursework
Programs win when every cohort gets the same vitals pressure, the same consequence model, and the same debrief artifacts — without cloning binders or burning lab hours.
Lab-grade fidelity outside the lab schedule.
One scenario version across campuses and terms.
Graded items your accreditation reviewers can trace.
Less instructor time on setup, links, and hand-scoring.
Repeatable remediation loops for at-risk learners.
Single vendor thread from authoring to LMS gradebook.
Pipeline
How the LMS handoff works
Four checkpoints — from course shell to defensible grades.
-
01
Map the LMS course to a BranchMedic class or roster context.
-
02
Publish scenarios as assignments with attempt rules your team controls.
-
03
Learners launch inside Moodle or Canvas with LTI identity — no extra passwords where SSO applies.
-
04
Attempts, scores, and debrief artifacts return on the rails your LMS already exposes.
Technical path: enable `/lti`, register platforms, map deployments — see docs/lti_data_flow.md in this repository.
Licensing
Choose how the institution buys
Student-funded
Bookstore codes or direct purchase. Best when learners carry software cost or CE is open enrollment.
Class-funded
Instructor buys a seat pack for the term. Best when the program wants predictable spend per cohort.
Site license
Pooled entitlements for many instructors and LMS courses. Best for academies and multi-campus systems.
No LMS?
Native classes still ship the same runs
Invites, seat caps, assignments, and debrief exports run entirely on BranchMedic. Add Moodle or Canvas later without rewriting scenarios.
- Roster control stays in your admin tools
- Same Drug Box and vitals fidelity as LMS launches
- Upgrade path: connect LTI when procurement catches up
Control plane
Administration that matches enterprise expectations
- Org-wide policies for seats, instructors, and scenario access
- Instructor dashboards for attempts, remediation, and reassignment
- Central pushes when scenarios update — no email blasts with ZIP files
- Concurrent classes and packs without duplicating content
- Roadmap: competency exports and deeper analytics
Deliverables
What procurement is actually buying
LMS-grade launches
Deep links, secure OIDC/LTI, roster-friendly contexts — not “email a PDF.”
Assignable simulation
Attempts, timers, and artifacts that belong in the gradebook conversation.
Medication fidelity
Drug Box draw-up and response when scenarios opt in.
Debrief with teeth
Critical misses, rationale, and repeat loops for mastery.
FAQ
Program leadership asks
No — class and site licenses let the institution carry cost. Student-pay remains for CE or open enrollment.
Yes. Native classes cover the same scenarios; LMS is additive when procurement and identity are ready.
Admins distribute join codes, bulk invites, or LMS-driven entitlements depending on tier — no single brittle spreadsheet workflow.
That is the design: pooled seats and policies instead of retail SKUs per faculty member.
Yes — map separate graded items to different scenarios or attempt policies.
Follow your institutional DPA. BranchMedic stores attempts, scores, and progress required for simulation; tune retention and identity per deployment.
Start with a class pack, prove outcomes, then expand to a site license without rebuilding content.
Close
Operationalize simulation like any other course system
We meet you at one pilot class, one LMS integration, or a full-site rollout.