PerformanceHiX: The transition from EZIS to HiX

12 February 2018

The health care sector is dealing with radical changes in IT, which bring risks for the stability of applications. Imagine getting a new EPD (or upgrading an existing one); new workstations; security issues; or merging healthcare institutions and, with that, merging IT environments. The ever-increasing dependence on IT means that the impact of malfunctions is enormous, and the need for monitoring increases. One of the upcoming changes is the transition from EZIS to HiX. This transition from EZIS 5.2 to HiX is a radical migration, both technically and functionally. It is very important to monitor the going live and the performance accurately, so that swift action may be taken if necessary.

Risk management with HiX migration

Changes in the IT landscape constitute a risk by definition. When the change turns out well, it has positive results, and the patient also benefits from this. Unfortunately, the opposite also applies: when the environment is not performing well, it generates a variety of issues of which the patient becomes the victim. Frequently cited risks – also with the transition from EZIS to HiX – include:

  • Complaining doctors: arguments frequently start with users about whether the system really has got faster.
  • Interruption of the primary process: efficiently planned primary processes are disrupted, as a result of which incidents cost even more money.
  • Arguments with suppliers: how do you prove which supplier is responsible for the problem? And how do you ensure that they take responsibility?
  • Reputational damage: when malfunctions occur, the reliability of an institution is often questioned, and the media is often quick to jump in.

Preventing is better than curing

It’s a cliché, but it still holds truth. The above risks can be prevented by having an accurate validation program, embedding chain monitoring in existing processes, and cooperating with other hospitals. Ymor has years of experience with monitoring EPDs and other applications at healthcare institutions, including VieCuri, Reinier de Graaf Groep and Máxima Medisch Centrum. Ymor does this from an end-user’s perspective, across the entire chain. Several clients are working together with Ymor on the migration to HiX, which makes it possible to benchmark the processes and performance.

Ymor helps its clients to maintain control over the transition to HiX by taking the following steps:

  • Reference measurement based on the existing situation. It provides you with an objective means of guidance with respect to your suppliers and users.
  • Validation of the new environment through load, stress and performance testing.
  • Monitoring the process of going live through the deployment of various monitoring tools. You can see whether HiX has an impact on other applications, workplaces and security aspects and, if so, how.
  • Benchmarking your situation with colleague healthcare institutions. What benefits remain to be extracted for you?
  • Maintaining proactive control over the new situation with continuous IT chain monitoring. You can prevent incidents and see what effect your modifications have on the performance. But perhaps the most important result: you create ‘one single point of truth’ for your department, suppliers, users, and Board of Governors.

The results

  • Benchmarking with other Chipsoft houses.
  • A successful launch or hot fix.
  • Transparency towards the end user.
  • Prevention of the ‘blame game’ with Chipsoft and arguments with users.
  • Up to 50% fewer malfunctions through fast detection.
  • Keeping a structural grip on and control over your IT and Chipsoft!

Contact our expert!

More about this topic? Ask your questions now and get a clear answer!

Contact our expert ››

A little spark can lead to great things.
You just need to know how to ignite it.

Contact us using the form below or get in touch via +31 88 42 42 200 or

Start to lead the way »