Skip to end of metadata
Go to start of metadata

System description

The Casus system consists of the following web-based components: 

  • player
  • authoring system
  • administration/course management inclduding evaluation, import/export
  • CME platform
  • assessment tool (currently piloting)

Supported SSO interfaces: Shibboleth, AICC/SCORM (-> SSO to LMS like moodle implemented)

Ped. approach


Due to the modular design Casus is also used in non-medical contexts such as law or Anglistics. For these settings the few special medical items are deactivated.


The navigation of Casus is linear/string of perls:

From the main cards the user can navigate to:

  • the next card
  • expert comment (optional)
  • hyperlinks (optional)
  • all previous cards (optional)

(todo: image)

Data representation

 The data representation is un-structured and completely up to the author. Cards can be grouped into chapters and subchapters. The latter can be labeled as "history", "phys. examination", "insprection",..., but this is optional. Each card can sonsist of the following items (all optional): 

  • text with hyperlinks (internal (-> text or multimedia) and external/www)
  • images (+ image maps) or video
  • question+answers+answercomment (including hyperlinks) with immediate feedback (either rated answer or peer group results)   supported questions types:
    • multiple/single choice, underline
    • freetext (rated/non rated), cloze,
    • sorting, mapping,
    • differential diagnostic network,
    • long menu,
    • lab answer.
  • expert comment (including hyperlinks)

 The number of cards is up to the author, VPs can be designed as key-feature cases or long cases or anything in between.


Import and export of VPs  as well as duplication of VPs within Casus is based on MVP.

The exported answers are implemented as QTI. Internal hyperlinks (currently not possible to implement meaningful in the MVP spec) and the image maps are currently not included in the export.

When importing VPs from other systems all VPD content is written to the cards as text, even if especially labeled (such as Physical Examination,...) -> labeling is lost during import! 

Branched VPs can be imported as linear VPs. All nodes of the branched VP are imported in a linear order, on each imported card, information about the potential next cards (or if it is a end node) is displayed for the author.This allows the import without losing information, the author can decide how to restructure the VP to be a useful linear VP.

  • No labels