Project follow-up

The Apotti project began in 2012, with a policy decision taken at this time to build the Apotti client and patient information system around a core system with fully integrated supplementary specialist systems ensuring data sharing and open interfaces.

The core system was acquired through a negotiated procedure in 2013–2016, with Epic Systems Corporation eventually selected as System Supplier on the proposal of the project steering group in August 2015.

Design 2012−2013

The project began with a design stage in 2012 that outlined the basis for the project and determined its objectives, timetabling and resources.

Procurement 2013-2016

The procurement stage selected Epic Systems Corporation as the Apotti System Supplier and Fujitsu Finland Oy as the supplier of data centre and other operating services.

90%
Specifications 2013-2018

Users played a key role throughout the project process, which involved thousands of health and social services professionals together with other specialists and users.

75%
Implementation 2016-2020

The completed system is currently being adapted and tested on the basis of approved specifications. This stage also includes implementing integration with other information systems.

10%
Deployment 2018-2020

The Apotti system will be deployed in three stages, beginning with deployment in November 2018 in Vantaa and HUS Peijas Hospital.

 

The project implementation and deployment stages are currently ongoing

The completed system is being adapted at the implementation and deployment stages for the needs of the project organisation. System deployment will prepare for major operational change, and will therefore focus strongly on building operational capacity within project organisations.
The key implementation functions will be:
  • adapting the completed system to client requirements (e.g. hundreds of workflows, prescription packages and therapy recommendations)
  • implementing numerous integrations with national, regional and individual client systems
  • implementing technical environments
  • validating translation work and terminology
  • testing
  • planning and launching a system maintenance and support organisation

The implementation process will ensure realisation of the features and guiding principles required for operational change with respect to both functionality and the overall system.

The system functionalities required for benefits identified in a utility analysis will be constructed in the course of implementation. The common service formats will also be agreed.

Agility in system adaptation

The selected core Epic system includes readymade workflows and content based on the best practices of more than 300 customers of Epic Systems Corporation. These features have played an important role in enabling system agility. It is much easier for social affairs and heath professionals to comment on completed examples than to set about specifying functionalities from scratch.

Having these professionals work with the application developers in the same team on a daily basis is also a key facilitator of agility, with most communication mediated through direct personal contact and not through documentation.

The implementation of the electronic health record system will begin towards the end of 2018 and continue through to the end of 2020

The first implementation will happen November 9th to 11th, 2018, and will concern the Peijas Hospital, as well as the Vantaa primary health care, and parts of the Vantaa social care services. The remaining Vantaa social care services will be incorporated in the next implementation.