Customer story · Workplace emergency response training

How CURA BHV brings its emergency response e-learning into its clients' own learning management systems

CURA BHV trains its clients' employees in workplace emergency response, with online theory and practical training. More and more clients, especially in healthcare, wanted CURA BHV's e-learning inside their own learning management system (LMS). The learning platform behind its portal couldn't do that. Linqur replaced it. Clients now get the course in their own LMS through LTI, and learners who book on CURA BHV's portal still click a button and start. Both routes lead to Linqur, so CURA BHV manages everything in one place.

At a glance

Organization: CURA BHV
Sector: workplace emergency response training
Learners: employees of CURA BHV's business clients, including healthcare organizations
Interviewed: Danny Vaessens, Core Systems Architect
Linqur products: LTI Tool Dispatch, Sign-up URLs, the Linqur API and webhooks
Connected to: clients' LMSs, CURA BHV's own portal and CURA BHV's instructor app
2 routes into the same courses, through the client's LMS or through CURA BHV's portal
3 ways to mark a course as passed, through webhooks, LTI or the instructor app
Under 1 hour for a reply from Linqur support, and often much faster

Clients wanted CURA BHV's courses in their own LMS. The old setup couldn't put them there.

CURA BHV runs workplace emergency response training for organizations, with online theory and practical training led by an instructor. The online part used to work one way: learners came to CURA BHV's portal, clicked a button and started their course.

Then clients started asking for something else. Especially in healthcare, they wanted to offer the course in their own LMS. Danny Vaessens, Core Systems Architect at CURA BHV, saw the trend and raised it more and more often. In the end, CURA BHV decided it was time to look for a platform that could do it.

TalentLMS behind the portal

The courses ran in TalentLMS. It was simple: an e-learning was either not done or completed. The link with CURA BHV's instructor app even worked slightly better than it does now.

No route into a client's LMS

Clients who wanted the course in their own LMS couldn't get it. In the old situation, that just wasn't possible.

What they looked for

CURA BHV's courses inside the client's LMS, with results the client can see

1

Courses opened through LTI in the client's LMS

Clients, many of them healthcare organizations, wanted to open the course through LTI in their own LMS. That was the reason CURA BHV started looking.

2

Qualifications visible to the client

Clients want everything in their LMS, so learners start there and managers see who holds which qualification.

3

Room to grow

CURA BHV expects significantly more learners in the coming years and wanted a solution that grows with it. On TalentLMS, that growth would have meant a serious step up in costs. Linqur's pricing tiers give CURA BHV plenty of room.

Why Linqur

It matched almost immediately

A colleague found Linqur through LinkedIn, and Danny took it from there. Building a platform of their own wasn't considered at the time. The team clicked through a few other vendors without it ever getting concrete. One that had come up earlier was ruled out on price.

What decided it was the fit with Linqur: the way of communicating, and the speed at which questions were picked up.

See how the LTI Tool Dispatch works
“

There was simply more and more demand, especially in healthcare, to offer the course through LTI in their own LMS.

Portrait of Danny Vaessens
Danny VaessensCore Systems ArchitectCURA BHV
Results

Courses inside clients' LMSs, two routes to the same course and fast support

1

LTI: CURA BHV's e-learning inside the client's own LMS

With the LTI Tool Dispatch, CURA BHV's course sits in the client's LMS. Learners enroll there and follow the e-learning from there. The clients who asked for this at the time now have it, and Danny says they're very happy with it. New clients often bring their own wishes and requirements, so CURA BHV is still finding out what works best for each of them. Result: every client that asked to run the courses in its own LMS can now do so.

2

Tenders: meeting the requirement to have everything in one LMS

Larger clients want all training in their LMS. Learners start from there, and managers see which qualifications each person has. Danny thinks two large clients CURA BHV won, one of them a big healthcare organization, chose CURA BHV partly because it could connect to their LMS. "I can imagine we'd have been 2-0 down if we hadn't been able to offer this," he says. Result: CURA BHV can now meet a requirement it could not meet before.

3

Portal, Sign-up URLs and webhooks: one course, several ways to finish it

Learners who book through CURA BHV's own portal are signed in to Linqur through the Linqur API and get a Sign-up URLs to their course. For courses that are fully online, completion goes back through a webhook or through LTI. For practical training, the instructor marks the learner as passed in CURA BHV's own instructor app, and CURA BHV then completes a "course passed" module in Linqur. Result: online theory and practical training both end in the same completion, whichever route the learner took.

4

Scale: room for the growth CURA BHV expects

Day to day, the switch saved no extra time, because the old flow worked as it was. The difference is in cost over time. TalentLMS would have been somewhat more expensive in the longer run, and growing there would have been a serious step. CURA BHV now has a lot of room in its Linqur tier. Within the wider group, more clients are expected to move to CURA BHV's own training route, and Danny expects learner numbers to grow significantly within about two years. Result: growth that doesn't require a new platform.

5

Support and custom work: answers within the hour

At the start, Linqur made a number of custom adjustments for CURA BHV. CURA BHV's IT partner handled much of that contact, and Danny remembers that Linqur communicated proactively and kept them informed throughout. Day to day, questions go to Linqur's support team, which replies within an hour at most, and often much sooner. Result: issues get picked up quickly, whether they turn out to sit with Linqur, CURA BHV or the client.

What took getting used to

From "done or not done" to a course with several parts

In TalentLMS a course was done or not done. At CURA BHV, a course in Linqur consists of a SCORM package built in Articulate plus a "course passed" module for the practical training. Because most learners only complete the SCORM package, the progress bar stayed below 100%. CURA BHV's instructional design team hid the percentage, and Linqur is renewing the course layout this year with a clearer view of progress.

LTI also takes some getting used to: a grade sent back can mark a learner as passed in the client's LMS, separately from the completion module. That is partly down to the protocol and to how each LMS implements it. Would Danny still recommend Linqur to a similar organization? "Yes."

“

Overall, the experience is really great. Especially the speed at which things get picked up when something doesn't work, or seems not to work.

Portrait of Danny Vaessens
Danny VaessensCore Systems ArchitectCURA BHV
What's next

More learners through the same flow

When clients from elsewhere in the group move to CURA BHV’s own training route, their learners will follow the same flow through Linqur, through the LTI Tool Dispatch or through CURA BHV’s portal with Sign-up URLs.

On Linqur’s side, the new course layout planned for this year should make progress easier to see, which matters for courses like CURA BHV’s that combine e-learning with practical training.

Plan a demo

Do your clients want your training inside their own LMS?

Offer your courses in your clients' LMSs with LTI, keep your own portal running with Sign-up URLs, and send completions back with webhooks or the Linqur API. We'll go through your situation in a 30-minute call. Linqur is ISO 27001 and ISO 9001 certified and hosted in the EU, on servers not owned by AWS, Google or Microsoft.