Display Tender TSER0179MH 

If it's a selective tender, only the person that received the email notification and was invited to view the tender, can view and access it.

Use the forgot password feature, to access your account credentials at https://www.tenders.vic.gov.au/person/resetPassword

Melbourne Health is seeking to procure a Patient Flow Management System (PFMS) that is integrated with (as a minimum) both IPM the Patient Administration System (PAS) and Symphony the Emergency Department Information System (EDIS) to capture and display both global and ward based views of the hospital’s current capacity and projected demand. The procurement of a global hospital Patient Flow Management System will assist with patient flow management and discharge planning by displaying timely and accurate patient flow information transparently across the organisation. All those involved in the treatment and management of patients will have access to patient information thus reducing the time spent gathering and disseminating information through other communication media.

The PFMS would become a common presentation layer for patient flow related information that would be visible on large LCD screens on wards and in departments, on desktop PCs and mobile devices.  PFMS will provide the focus for patient flow management decision making and prompt a focus upon timely discharge planning through the presentation of key information from underlying Melbourne Health systems. 

To optimise the overall benefit to users and to allow the PFMS to grow within the Melbourne Health IMT environment, the PFMS will need to be capable of integrating with other Melbourne Health clinical system web portals such as eMR Clinical Viewer, ED Web View, Medical Handovers, Theatre Tracker, TRAC Queue, ICU Bed Board, and Emergency Theatre Booking System (ETBS).

The iSOFT iPM and Ascribe Symphony systems should remain the primary systems for patient demographics and patient administration.  The PFMS should not create a parallel or subsidiary data gathering system that could lead to confusion or diminish the importance of updating the core systems with key information required for patient administration, coding, reporting, clinical costing… etc. Should a vendor application propose capability of direct write back to the underlying iPM or Symphony systems, this must be established and demonstrable capability and satisfy all components of data entry edit checking, tightly coupled transaction control, HealthSMART Statewide footprint messaging / transaction management and satisfy all statutory minimum data set and business rules for Victorian DoH VAED, ESIS and VEMD reporting. 

The PFMS should be viewable hospital wide within the secure IT network of Melbourne Health and must support secure protocols to allow access to select users from outside our network (eg clinicians working at home or mobile).  The PFMS will be installed on servers within the Melbourne Health IT&T Services server room as per hardware compatibilities and operate within the Melbourne Health Standard Operating environment outlined in Function 30.

The PFMS should be largely data display with data entry occurring through primary systems. Patient flow information not stored in other systems such as hospital capacity alert information, bed status (closed with reasons; bed cleaning), comments relating specifically to patient flow, status of referrals, can be entered and stored as necessary. Access to the system should be achievable via fixed pc, laptops or portable tablets and touch screens. PFMS information will be displayed on large LCD screens in wards and departments to inform clinical meetings, discharge planning and general overview of current and incoming patients. The anticipated benefits will be a better informed workforce with real time patient flow data and reduced reliance on paper reports, telephone calls and face to face meetings.  

The PFMS should provide both global and ward based views of real time current and predicted patient flow activity, including: current inpatients, booked electives, unplanned referrals and direct admissions, requested emergency admissions, boarders, outliers, expected discharges, patient transfers and bed closures. Integrated ward and/or unit centric views with the ability to generate associated reports should assist clinicians with communication and day to day activities such as referrals and handover of patient information including alerts. 

The PFMS should provide (but not be limited to) an overview of Ward and Emergency Department activity and include interfaces with other referral and administrative systems such as ISOFT’s eReferral (HealthViews) system and other Melbourne Health web based portals mentioned earlier to reduce duplication and ensure integration of all information related to patient flow.