VR training can be designed to send agreed learning records using xAPI, but an LMS connection is not automatic. The VR application, receiving systems and reporting requirements must be assessed together. This article focuses on the records you want to receive, rather than treating every LMS as compatible.
Define a useful learning record
Decide which events matter: starting an exercise, completing a scenario, selecting an answer or reaching an agreed outcome. An event such as completing a hazard exercise needs a consistent learner identifier and activity name if it is to appear meaningfully in reports.
Understand where the records go
xAPI uses statements sent to a Learning Record Store, often called an LRS. An LMS may include an LRS or need a separate integration. Ask your LMS supplier how it accepts and displays these records before assuming results will appear in its normal course dashboard.
Test the complete reporting journey
Use a small sample exercise to test identification, delivery and report presentation. Agree how interrupted sessions and offline use should behave if those features are required. Authentication, hosting and access permissions also form part of the integration scope.
Discuss your project with High5VR
Bring your LMS details and a sample report to High5VR. We can review the reporting requirement before committing to a specific connection or promising data that the application does not collect.
Contact High5VR to discuss your audience, objectives and scope.
Further information: ADL learning record store information.
Featured image: illustrative image.