110 likes | 253 Views
Annual Conference 2014. Maternal and Child Health System Project. Denis Wilson Manager Information Technology Moreland City Council. M&CH System Issues. Concern about M&CH data management Growing risk of using outdated systems Difficulty in aggregating data in decentralised model
E N D
Annual Conference2014 Maternal and Child Health System Project Denis WilsonManager Information TechnologyMoreland City Council
M&CH System Issues • Concern about M&CH data management • Growing risk of using outdated systems • Difficulty in aggregating data in decentralised model • Ancillary systems for vulnerable children • Lack of support for mobile and off-line access • Lack of integration to other systems • National eHealth changes – PCEHR services
Way forward • Identified as major project for MAV Technology to support with resourcing and funding and act as a catalyst • MCH IT Steering Committee formed and workshops organised • EOI released in October 2013 to ascertain vendor interest • 65 Councils identified interest at first stage • Shared State-wide system to deliver a standardised approach across Victoria • Key stakeholders- Councils- Department of Education & Early Childhood Development (DEECD)- State Government- Federal Government
Expected Benefits • Provide enhanced capabilities to better monitor vulnerable children • Better data to support family assistance, factual reporting and completion of all ages and stages visits • More relevant health referrals • Higher quality reporting to better support future demand planning • Reduction in disadvantage in health and education • Higher quality aggregated population health data • Higher nurse productivity with mobility and off-line access • Victorian MCH service to continue to be regarded as a world leader in children’s health and development
Post EOI Activities • EOI identified a short list of vendors who could feasibly deliver a fully functional system for the likely funding that could be available • Project Manager appointed - Karen Darling from ROI Solutions • MCH Project Control Board formed in April 2014 • Business Case completed in April 2014 – needed to source formal funding commitment from State Govt • Minister Wendy Lovell announces $2m funding for the project in June 2014 • Business Analyst appointed to develop detailed requirements specification document with key input from MCH reps at Council and State levels and IT reps from Councils
Project Control Board • Project Sponsor – Rob Spence, MAV CEO • Project Manager – Karen Darling, ROI Solutions • Senior User Rep – Clare Hargreaves, MAV Manager Social Policy • MCH User Rep – Joanne Fittock, MAV Policy Advisor • State Govt Supplier Rep – Pippa Proctor, DEECD • MAV Supplier Rep – Cameron Spence, MAV Commercial Manager • MAV Supplier Rep – Jo Cross, MAV Procurement • ICT Rep – Denis Wilson, IT Manager
M&CH IT Infrastructure Survey • Background data needed on IT Infrastructure in Councils supporting MCH Service to confirm content in requirements document • Distributed to managers responsible for IT on July 29 with one week to respond • 41 responses - 26 Rural- 15 Metro- 52% was an excellent response at short notice
M&CH Survey Results • Ave per Council of 16 MCH staff/admin- 11 have mobile phones- 12 desktop PCs, 3 laptops, 1 tablet • Mobile phones – 50% are smartphones (55% iPhones) • Browsers – 98% IE, 30% Chrome, 20% Firefox, 19% Safari • MCH system used – 78% MaCHS, 20% Xpedite • 50% of Xpedite users have integration to other modules • Very little integration of MaCHS to other systems (SMS only) • 80% have support agreements in place
M&CH Survey Results • 95% use IRIS – enhanced MCH system • 15% use the Birth Notice database • 7% of MCH Centres do not have internet access • eDMS – 40% TRIM, 15% TechOne ECM, 15% RecFind • 25% planning on changing eDMS • Email/calendar – 84% Exchange, 14% Lotus Notes • 32% use SMS messaging to clients • Business Continuity – Maximum Allowable DowntimeVaried from 2 hours to 2 weeks
Next Steps • Complete detailed requirements specification mid Aug 2014 • Release tender (open for 4 weeks) end Aug 2014 • Select preferred vendor Oct 2014 • Commence system build/configuration Nov 2014 • Data load and system testing Mar 2015 • Pilot implementation May 2015 • Post-pilot review Jun 2015 • Commence limited selective rollout July 2015 • Comprehensive rollout Q4 2015 / 2016