Mobile Incident Registrations and Reflection

Mobileincident registrations

and ReflectionJeroen ten Haaf: ja.tenhaaf@maastrichtuniversity.nl

Maastricht University Library

Tuesday 9 April 2013

2

3

4

5

6

7

• Founded 1974 > Problem Based Learning• 16.000 students, 4.000 staff• 44% students, 30% teaching staff from abroad• 6 Faculties

– LAW– Business & Economics– Medical & Health Sciences (associated with academic hospital)– Psychology & Neurosciences– Arts & Social Sciences– Human Sciences > subfaculties (e.g. U-college, knowledge

engineering)

Maastricht University

8

• Blackboard 9.1, SP 11• Blackboard Content System• Every:

– Faculty– Teacher– Student– Course (content, information, functionalities (e.g. webconference))– Tutor group

in Blackboard…

• User creation, enrollments & Course creation triggered by SAP Student Lifecycle Management

Maastricht University / Blackboard

9

Maastricht University / Blackboard

Logins / day Hits / day

September / October 2012

10

Maastricht University / Problem Based Learning

11

• Real life situation (disease, conflict, project)• Self directed > develop ones own style:

“I'm not afraid to let people follow their own paths”

• Collaboration• Formative tests• Evaluation, Reflection

– Essential, however..:– difficult to meet the needs of students and teachers

Maastricht University / Problem Based Learning (as from 1974…)

12

Problem Based Learning

• 8 – 12 cases in a six (to eight) week course

Typical Case:

A 60-year-old man visits your general practice. He is worried. When he was driving, an insect flew in his left eye. When he tried to wipe it out, he noticed a very poor vision in his right eye.

1. Brainstorm: clearify terms, concepts, define & analyze the problem (case)

2. Inventory of explanations

3. Learning objectives

4. Search for additional information

5. Report and synthesize the new information

Problem Based Learning (PBL)

Tutor-group meeting

}

Tutor-group meeting

14

• Real life situation?... Conditions are not always perfect…

– Time pressure– Complexity– Not so nice colleague– Very nice colleague… but not now please!– Unexpected events… incidents take place

• Event, Incident -------- needs Reflection, Feedback, Evaluation

Maastricht University / Problem Based Learning

15

• Reflection: a systematic and critical analysis of events– Serves as guideline for future behaviour (Driessen, van Tartwijk, & Dornan,

2008)

– Is specifically important in complex and unusual situations (Mamede, Schmidt, & Penaforte, 2008)

• Reflection is a crucial part of the learning process, so:

1. Dedicate some time to register an event / incident: preferably right away

2. Plan one or more reflection sessions: meeting(s) with peers and tutors

Maastricht University / Problem Based Learning

16

• Think of a tool / setup that would help you:1. To register any event / incident in any situation

2. To provide access to these registrations for peers and tutors prior to and during the sessions

• Create a list of requirements for such a reflection tool to be used in the hospital nursing department

– Use your imagination!– Keep things simple, specifically at the critical moment the event / incident

takes place

• Groups present their list of requirements

The ‘Birmingham’ case of today:

17

• Mobile device connected to internet• Creates reports, video txt• Upload to “knowledge base” accessible to

everyone• Metatagging option• Provide a form, template with fields to describe• On the spot registration > upload to database

Requirements Group 1:

18

• About the same requirements as Group 1 +• Private data is a point of attention, ask

permission beforehand (patient, participants)• A time tag on the registrations

Requirements Group 2:

19

• About the same requirements as Group 1 and 2 +• Sync to Blackboard differentiated permissions• Registrations should be shareable right from the

moment of creation• Use mobile device (small, so less impact on

environment)• Recordable archive• Automatic ID• Push notifications (reminder system)

Requirements Group 3:

20

• One app (β version): – Event registration in any format (no switch between e.g. camera and

notes app)– Upload files to Blackboard (My Content folder)– File storage on device and…– Upload My Content only when in wifi– Reminder system (notification after 1 OR 2, 3, 4, 5, 6, 7 days) to be set by

investigators

• Why Blackboard?– Integration in course or organization– Grant different levels of permission to different users: user can restrict

access to just viewing content, or allow full rights, such as editing the content or even deleting content

– Functionalities for follow up (blog, discussion, grading …)

How we did it:Mobile Reflection App 1 (MRA1)

21

• Demo…

How we did it:Mobile Reflection App (MRA)

22

• MRA 2: – Same as MRA1 (β version) except:– Upload files to Dropbox (instead of Blackboard)– No reminder system– App for free “Reflection App”– DEMO

• MRA 3:– Same as MRA 2 plus:– More clouds available (Google)– Option to build in other institution Blackboard application (requires

coordination with individual institutions)– Reminder system (optional): in-app payment model– Free? We don’t know yet…;-)

Mobile Reflection App (MRA)Future steps

23

Mobile Reflection App (MRA)How about it works

Blackboard

24

Mobile Reflection App (MRA)How about it works

CloudCloud says: OK / NOK

‘Reminder’Server

If OK then R(eminder)set to zero

If R > x days then notification

25

Let’s reflect!

ja.tenhaaf@maastrichtuniversity.nl

Well…