Skip to end of metadata
Go to start of metadata


Version: 1.0

Date: March 15th, 2016

Author: David Topps, Ellen Meiselman, Valerie Strothers

Author email:

Profile ID: (we should determine how to handle versioning with regards to the profile identifier. My guess is that we would either wait to assign or update whenever there is a substantive change.)

Version History

Version No.


Changed By

Changes Made




Initial draft




First official draft

MedBiquitous License and Terms of Use

(Note, Valerie will work with legal to develop a version that is not XML specific)

Acknowledgements (placeholder for later – will list all working group members)

Introduction (explain the need the profile is meeting, it’s scope, the relationship to xAPI, and the relationship to other profiles and or standards. Link to xAPI overview. We may want to reference any important publication tools the profile leverages, or that might be better in the verbs section.Cite the relationship between statement structure and what is possible with analytics.)



Can be categorized by situation type or by activity type, or whatever makes sense in context. 

Medbiquitous Virtual Patient (MVP) standard players

Basics/Core Recommendations

    • All statements include the Recipe ID in the 'category' context activity list.

    • Most statements include an Agent with the user as the 'actor' property.

    • Some statements may reference the System or Application as the 'actor' property where they system has updated a counter or made some other change.

    • Most statements include the virtual patient Activity as the 'object'.

    • All timestamps in statements must be compliant with ISO 8601 format. (this is part of the xAPI specification)

    • Virtual patient Activity Definition includes the following:

Has the 'type': 

The Actor object will be defined by the virtual patient player. The Actor object for most statements with defined verbs will be of type "Agent" and MUST contain an account object.

An Example of usage in a statement:

  "actor": {
    "objectType": "Agent",
    "account": {
        "homePage": "",
        "user_id": "1625"
  "verb": {...},
  "object": {...},
  "result": {...},
  "context": {...},
  "attachments": {...}



 Verb usage:


User has opened a case. Sent when the VP case starts to play.

Verb IRI: 

Includes a timestamp and identifier of the node in the VP when playing was started. Most VP cases will have a fixed starting node but this is not always true and is not a requirement for the statement to be true.  


User has completed the case. Reached a node designated by the case author as an endpoint. Does not indicate success or failure.

Verb IRI: 


User has paused a case. Suspended a case with the possibility to resume later.

Verb IRI:


User has restarted a case. Resumed a case that had been previously suspended.

Verb IRI:


User has left a case and does not intend to resume. Consider how you will be able to differentiate this from ‘abandoned’, 'suspended' or 'completed' because the VP player engine may not be able to determine whether the user is coming back again.

Verb IRI: 


User has visited a node within the VP case. Not necessarily same as 'read' or ‘experienced’ because an internal rule or trigger might immediately bounce them on to another node or activity. (See ‘Launched’). So, while the user may have landed on that node, if they are immediately redirected, they may not even see that page/node. Can be used for a physical or virtual location.

Verb IRI:  


User has read a document, page or paragraph. Similar to ‘interacted’ but used when the media is static or non-interactive

Verb IRI: 


User has responded to a question. Response to an item or question within a node, without moving off that node. (This is not quite the same as ‘answered’ which implies that the answer is correct.)

Verb IRI:


User has interacted with or manipulated an object or a video or similar multimedia that provides some sort of interactivity. Similar to 'experienced' for when the media is dynamic, like a video. For more detailed reporting on videos, we instead recommend the use of the Video Recipe:

Verb IRI: 


User has contributed to group activity. Used when an actor adds to a group activity for a compound effect. In some ways, this is not different from ‘responded’. But the net effect is different because you are not expecting that the single activity will necessarily produce some result by itself. The object might be a discussion thread. (Or in OpenLabyrinth, we have a question format called a Cumulative Question, where users contribute phrases to a single question/database field.)

Verb IRI: 


User has ignored a flag or other virtual patient data. This is a flag or action sent by either a facilitator or the VP player engine to indicate that an action was expected by this point in time and had not occurred. Sometimes this is a good thing, and while absent, is not necessarily a negative aspect - for example, if there is a distractor in place that the actor is supposed to ignore as irrelevant.




For the following activity statements, the Actor is more likely to be the Virtual Patient player engine or an object within that player engine:


VP player engine has changed a counter value. This may be triggered by arrival at a particular node, or by a rule within the case design created by the virtual patient author, or by a timer expiration point. Although the counter value may be regarded as a score, note that the ADL verb ‘scored’ is overall score for the case or exam (, which is not the same thing.



VP player engine has initiated an action such as redirecting the user to a new node, or triggered some other activity. This is not an action made by the user.

Verb IRI: 


To be used mainly if there are very specific activities being described by this profile. Otherwise, Activity types usually used instead.

Linked Identifiers



  • No labels