Skip to content
English
Submit a Support Ticket
Go To Mursion Portal
  • There are no suggestions because the search field is empty.

Integrating with your LMS

This article reviews the Mursion SCORM integration allowing your participants to access Mursion simulations directly through your LMS.

SCORM Integration Guide Setting It Up

Mursion supports SCORM 2004 (3rd Edition) and SCORM 1.2 package versions. You must be using the New Admin and New Pathway experiences to configure SCORM.

To get started, work with your Customer Success Manager (CSM), who will enable SCORM for your organization. They'll need the following details from you:

We need What it means
Learning platform origin The address Mursion sends completion and outcome data back to. Include https:// and stop at the domain — no path or trailing slash.
SCORM version 1.2 or 2004 (3rd Edition)
Sign-in URL Where participant emails should direct people to reach your learning platform
Pathways to enable Which pathways you want delivered via SCORM. We recommend configuring SCORM on new pathways so that your data stays consistent for the life of the project.

Once SCORM is enabled:

  1. Log into the Mursion portal. Any pathway configured for SCORM delivery will show a SCORM tag, and will automatically get a SCORM cohort added to it.
  2. Click into the pathway to download its SCORM packages. Each activity (scenario) in the pathway has its own SCORM zip file.
  3. In your LMS, configure the activity and upload the corresponding zip file. Any settings you configure in your LMS — completion limits, access controls, and so on — will work as expected.

Accessing the Simulations

Participants with access to the course and activity in your LMS can launch the simulation directly from there.

  1. First-time access: Participants are prompted to accept the Mursion user agreement.
  2. Scenario page: Participants land on the scenario page for the activity they're accessing.
    • AI-powered simulations: Participants can review the scenario and start it immediately, without leaving the LMS.
    • Human-powered simulations: Participants schedule their session, then return to the course at the scheduled time to start it.
  3. Completion: After the scenario ends, Mursion sends a completion indicator back to your LMS. For AI-powered simulations, we can also send a Pass/Fail result based on the scenario's Goal Achieved score. To enable this, talk to your CSM — your data privacy agreement will need to cover individual performance data.

Reviewing Performance and Utilization

What Mursion can identify about your participants depends on your LMS setup. Either way:

  • Completion data is visible directly in your LMS.
  • Within Mursion, you'll see the number of participants and aggregate performance data for each pathway.

What Information We Capture

Mursion identifies each participant using whatever your LMS provides at launch. We check the following, in order, and use the first one available:

  1. Student ID — Passed automatically by your LMS through the SCORM standard. This is the primary way we match activity to a participant's Mursion account and will be recorded in the Employee ID field for your participants.
  2. Email address — SCORM doesn't include a standard field for email, so we only pick this up if your LMS adds it to the launch link, or if the student ID itself is formatted like an email address.
  3. Name — Captured once, when a participant's Mursion account is first created, to set their first and last name. It won't update on later logins, even if the name your LMS sends changes. 
  4. Generated ID — If no email address is available, Mursion creates a unique identifier from the student ID so each participant's records and progress stay consistent across sessions.