/
Adopting the Experience API to work with the Virtual Patien Adopting the Experience API to work with the Virtual Patien

Adopting the Experience API to work with the Virtual Patien - PowerPoint Presentation

alida-meadow
alida-meadow . @alida-meadow
Follow
392 views
Uploaded On 2016-09-14

Adopting the Experience API to work with the Virtual Patien - PPT Presentation

why Matt Cownie Jonathan Wright University of the West of England Bristol Abstract The eXperience Application Programming Interface xAPI is a new s pecification that allows learning content to link with learning systems to track and share all types of learning experie ID: 466082

activity activities learning xapi activities activity xapi learning http lang verbs dirty lrs experience api profile virtual https media

Share:

Link:

Embed:

Download Presentation from below link

Download Presentation The PPT/PDF document "Adopting the Experience API to work with..." is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.


Presentation Transcript

Slide1

Adopting the Experience API to work with the Virtual Patient Standard - how, what and why?

Matt

Cownie

, Jonathan Wright

University

of the West of England, Bristol

Slide2

Abstract

The

eXperience

Application Programming Interface

(

xAPI

) is a new s

pecification

that allows learning content to link with learning systems to track and share all types of learning experiences. Learning activities can be tracked using combinations of a limited vocabulary of activities, verbs and subjects. While the specification provides a default profile of activities and verbs it allows for communities of practice to develop custom profiles of their own agreed activities and verbs. This presentation will have

main 3

parts. Slide3

XAPI

Slide4

Caveat EmptorTincan OR experienceAPI OR

xAPI

Versions 0.90-0.95-1.0-

1.01

Many

examples are ‘slightly wrong’Libraries for Java, JS and PHPNew .NET Library for the Tin Can API is Now Available!Refer to the final spec 1.0.1

Assumes

you are VP Standard awareSlide5

Part 1 - How

Firstly

it will demonstrate

how

to use the experience API to capture the stream of activities a learner generates while playing a Virtual Patient (VP). It will show technical examples that map VP concepts onto XAPI calls that can be used to populate a Learning Record System (LRS) with VP related learner data. Slide6

Simplest example (C#)

statement = actor +

verb

+ activity

Actor

Verb

Activity

Statement

LRS

Activity

TypeSlide7

We made a statement

http://tincanapi.com/public-lrs/

Statement in the LRSSlide8

JSON payload

URLSlide9

URI

URLSlide10

Simplest example (JavaScript)Slide11

More detail?

“verb” : { “display” : {“en-US” :”visited”}, “id” : ”http://medbiq/exapi/verbs/visited }

,

type” : http

://

medbiq/exapi/activites/virtualPatient/ } } }

COP Verb ?

COP Activity ?Slide12

Looks like, but Slide13

More detail with context (simple)

Tie everything togetherSlide14

sessionIdSlide15

XAPI - ContextActivities

XAPI provides four possibilities - ‘parent’, ‘grouping’, ‘category’, and ‘other’

Parent

- model the Virtual Patient as parent activity and set that as the context for all subsequent related activities. Further granularity would be a video and MCQ with a node as parent activity.

Grouping

- might want to group an activity within the VP with related activities in same VP or other VPs

Category

- “

Category SHOULD be used to indicate a "profile" of

xAPI

behaviors

- e.g.

PhysicalExam

, Medication? Other - none of the above, perhaps supporting learning material or making a branching decision?Slide16

Some ConcernsMedia Resources, Counters, CounterRules, DataItems,NodeRules

,

NodeAccessRules

Extensions

Exposing internal workings and Id’sName spacingVersioningWho’s the audience?Slide17

Part 2 - what

Secondly

it will review

what

this data looks like in an LRS and examples of querying it for meaning. It will outline what verbs and activities might be contained in a Virtual Patient specific profile and what use cases these could meet. Slide18

Simplest – manual get (c#)

query

resultsSlide19
Slide20
Slide21

DashboardSlide22

A Report BuilderSlide23

Statement ForwardingPainting by Eugene Delacroix, available under a Creative Commons Public Domain license

.Slide24

Verbs and Activities and URL’sSlide25

VP Activities + types

Page : page

MCQ : question

Video : video

audio : audio

Document : file

Short answer : note

Image : media

Flash activity : interaction

Unity activity : interaction

Html5 activity : interaction

YouTubeVid

: media

DataItems

: file?

Blood Test : media

Media

Resources : media

CounterRules

: event

DataItemRequest

: interaction

NodeRules

: event

NodeAccessRule

: event

CounterRules

: eventSlide26

VP Verbs

Started :

started

Visited :

was

at

Requested :

requested

Watched :

watched

Listened :

l

istened

Triggered: ?????

Altered:

updated?

Exited :

exited

Answered :

answered

Completed :

completed

Read :

read

Commented :

commented

Played :

played

restarted :

terminated?Slide27

Extensions and Profilefeedback : extension

counter : extensionSlide28

Part 3 – why (for VP’s)

Lastly

it will outline

why

the virtual patient community might want to adopt the experience API and ask whether a specific community profile is necessary. Influences for consideration include the “Internet of Things”, mobile learning, data-mining, combining virtual patients with other simulation activities, capturing the complete educational context of a learners VP experience and reporting into competency frameworks.Slide29

What were my use cases? ReportingBig Data

Learning

Management System(s)

LTI 1.1 &

outcomesSimulation Slide30

Other VP use cases? 3D & Games Multi-modal simulation

Team based

Platform transition (state API)

Learner Profiles Slide31

Wider reasons to adopt XAPITransversalTransparency

System silos

Simulation (non-linear)

Mobile

Innovation

Future proof Slide32

Answer the Question…Is a specific VP community profile necessary?Slide33

A friend in needhttp://www.adlnet.gov/tla/experience-api

https

://github.com/adlnet/xAPIWrapper

http

://nodejs.org/

https://www.npmjs.org/package/adl-xapiwrapper

https

://

github.com/LearningLocker/learninglocker

http://

thedesignspace.net/misc/xapi

https://

github.com/RusticiSoftware/TinCan.NET

https://

github.com/RusticiSoftware/TinCanJS

https://registry.tincanapi.com

/

http://tincanapi.com/public-lrs/http://scorm.com/scorm-solved/scorm-cloud-developers/