Follow a course sequence
Open the sequence from your classroom on My cases. The overview shows activities and your progress. Earlier activities must be complete before later ones unlock.
Start, resume, and complete
| Activity | Completion action |
|---|---|
| Clinical case | Explicit case completion after handover |
| Survey or test | Confirm final submission |
| Learning class | Submit the module |
| Group seminar | Join the shared run; supervisor concludes it |
Opening or previewing the overview does not start every activity. The same template can occur more than once; each position is a distinct task.
Your course version
The first activity you actually start assigns the published course version to your account. If the teacher later publishes a new version, your started course normally stays on the original one.
Do not create another account to change versions. Students do not have a self-service reset, retake, or repinning control.
Timed activities
Cases, surveys, and tests can be timed. Read the start confirmation. Depending on configuration, reaching the limit may only change the visual timer, warn you, or lock actions. Time calculation may include idle handling; do not assume minimizing the browser pauses the timer.
For a survey/test configured with Lock, reaching the limit automatically submits the available answers, including an incomplete response.
Resuming uses the existing attempt and timer. Cancelling the start confirmation does not create a patient.
A group seminar has a separate shared soft timer. Reaching zero does not complete it: you must join and the supervisor must conclude. See joining a seminar and continuing afterward.
A task stays locked
Confirm that you completed the correct earlier occurrence, not a separate patient made from the same template. Check final submission versus a saved draft, seminar conclusion, account expiry, schedule, and consent state.
A low test score does not block the next activity: progression depends on submission, not passing a score threshold.
Keep any save error visible for support. On an assessment version conflict, reloading resumes the server draft but loses unsaved local changes.