Implementing a PDA Requirement: The Good,

the Bad, and the Successful

May 12, 2005 - Spring CSG Meeting

Brian BostonGeorgetown University

School of Medicine Key Facts

700 Medical Students No student computer requirement Medical library is central technology

provider Wi-Fi network on campus Clinical sites off-campus Physicians using handheld devices

Pre-PDA Requirement

“Unofficial” requirement PDA potpourri PDA station Limited support and training Device recommendations

Pre-PDA Requirement Issues

Difficult to support multiple devices Syncing personal information on public

PC Application installation is time intensive Device funding not allocated Varying levels of student PDA

adoption/use Lack of driving purpose

Why a PDA Requirement?

Meet LCME student clinical encounter requirement

Further informatics curriculum objectives

Manage support issues Lower student costs Formalize institutional commitment

Patient and Clinical Encounter System

Components of PDA Requirement

Make the case Set timeline and notify users Select hardware Purchase devices Deploy software Provide support/training

Making the Case

School of Medicine formed Informatics PDA Committee

Committee coordinated with Information Services

Committee drafted formal PDA Requirement stating need

Committee on Medical Education approved plan

Setting Timeline and Notifying Users

Requirement must be in place in year prior to be included in financial aid

Notified users well in advance of mandatory device

Distributed PDAs to 2nd-year students in March

Students used devices in spring course prior to 3rd-year clinical rotations

Selecting HardwareWhy Palm Tungsten C?

PACE ran best on this Palm

PDA with Wi-Fi, SD slot, and keyboard

IMAP SSL email Within price range Familiarity with device History of supporting

Palm OS

Purchasing Devices Device cost part of student technology fee Included in student financial aid package PDA Bundle:

Tungsten C SD Card Palm Extended Warranty Medical Dictionary

Reduced price through volume discounts (CDWG, PalmOne, and Stedman’s)

Deploying Software

Used CardBackup for installing software Capture image of PDA applications on

master device to an SD card Retain application configurations Select applications to backup Quick and easy restoring of backup Shareware No advance setup of hardware needed

Providing Support/Training

Library created help guides for PDA support site

Library distributed quick start guide with PDAs

Information Services posted instructions for configuring email

Library offered drop-in help sessions Students shared tips among each other

Keys to Success

Assess need in light of curricular goals Identify driving application/purpose Integrate with institutional applications

(email, calendar) Limit platforms/devices Test hardware/software Tailor support/training

Future Goals/Options

Evaluate new devices Review/evaluate Wi-Fi access Integrate PACE with LDAP Add content channels Facilitate faculty adoption of PDAs Investigate Blackboard PDA version Offer course lecture podcasts

Website/Contact

Dahlgren Library PDA Site:http://dml.georgetown.edu/pda

Contact:Brian BostonAcademic Technology Coordinator, Medical CenterCenter for New Designs in Learning & ScholarshipGeorgetown Universitybostonb@georgetown.edu