How Does Biopharma Institute Issue SCORM Packages to Clients?

Biopharma Institute issues SCORM dispatches for its clients to use to deliver training from their LMS. See below for more details on dispatches and how they work. We can also provided a dispatch for clients to load and quality test from their LMS. They are easy to use and install, same as using any SCORM package.

About SCORM Cloud Dispatches: Biopharma Institute provides training modules packaged as SCORM 1.2 dispatches. These dispatches can be added to any LMS, just as you would a standard SCORM package. There is no difference from the student’s perspective. However, because the course is being delivered from our SCORM Cloud account, there are some network settings which may need to be changed for students to view the course from a client’s LMS. Here are the requirements:

• Cloud Client LMS Requirements
  • Client’s LMS needs to communicate with the domain app.cloud.scorm.com. Thus, the domain: app.cloud.scorm.com address may need to be whitelisted (or not blocked) by network security / firewall. Note: If the client experiences any issues, there are additional settings in the SCORM Cloud which Biopharma Institute could manipulate to optimize course delivery for any system, including whether the course pops-up in a new window or not.
    • See more information here: Cloud Client LMS Requirements

 How does the SCORM Dispatch Work?

• When a student launches the course from client’s LMS the dispatch will send the student ID to app.cloud.scorm.com. This allows the seat to be issued, the course to open, and activities to be tracked in the client’s LMS. The SCORM Cloud system will keep track of the number of seats issued and expiration dates. The system can limit the number of students who can access the course and the length of time the course is available for delivery to a client. Number of students and length of enrollment can be easily increased or decreased, if necessary, without issuing a new SCORM dispatch to the client. Note: app.cloud.scorm.com sends tracking information and completion status back to the dispatch, which adds it appropriately into the client’s LMS, just as any SCORM package would do.