210 likes | 606 Views
Bed Management Presenter: Denise Manning Hospital: Auckland City Hospital. 14 November 2007 - Sydney. OVERVIEW. Electronic Bed Management System created to better support acute/unplanned bed management at Auckland City Hospital. KEY PROBLEM SOLVED.
E N D
Bed ManagementPresenter: Denise ManningHospital: Auckland City Hospital 14 November 2007 - Sydney
OVERVIEW • Electronic Bed Management System created to better support acute/unplanned bed management at Auckland City Hospital
KEY PROBLEM SOLVED Excessive number of communications necessary to achieve bed placements Replacement of largely paper based system
REQUEST A BED (from patient whiteboard) …..As simple as 1,2,3 System invokes bed request screen with patient in context User clicks ‘OK ‘ Bed is requested User is returned to whiteboard bed booking is visible in the next column User highlights the patient’s row and selects ‘Request a bed’ 1 2 3
COMPLETE REQUEST (Bed manager) 1 Bed Manager Completes the request (scheduling the next location) 2 Requests appear on BMS instantaneously The newly scheduled ward and bed ready time is displayed back on patient whiteboard 3
COSTS • Developed in 2 phases • Development costs have been included under the annual IMTS budget for CMS (the patient management system) • Extrapolated cost of BMS including analysis, development, testing & release to production estimated at $152k • Customised for ADHB – not commercially available • No associated training costs so far
Next Phase • Phase 3 currently in the analysis stage includes: • A constant capacity snapshot and alert broadcasting tool • A means to activate a ‘a major incident state’- for multiple admissions eg changed triage, rapid registration and transfer, overflow whiteboards etc • A method to highlight and capture data around transfer delays • A Resourced beds tool for Bed managers to easily input actual resourced bed data
EVALUATION • Bed management system must interface with patient management system • Keep it simple - needs to be quicker and simpler that existing processes • When designing system requirements always consider the data gains • Ensure business rules are sound to minimise error