Say goodbye to monoliths – Modular clinical applications offer flexibility and speed

The idea is simple. Instead of replacing an entire system at once - doing the “big bang” - you can introduce focused clinical applications gradually, based on the organization’s clinical needs. These applications are designed to work together, follow open standards, and can scale and evolve with the needs of the organization. 

A modular platform allows a gradual shift from a monolithic system to modern clinical applications. Both legacy and new applications can run side by side with synchronized data, making it possible to confirm the integrity of a new application with the legacy system minimizing the risks.   

What makes modular applications different? 

Modular clinical applications aren’t just pieces of software, they represent a new way of thinking about healthcare IT. Each application is designed to do one job well—like documentation, viewing observations, task management, or ordering. And because they are built on open standards, they connect through a centralized database –a Clinical Data Repository – and share all the necessary information.  

This approach allows: 

• Step-by-step development – You can introduce new tools gradually, without having to replace your whole EHR. 

• Built-in interoperability – The apps speak the same language (openEHR, FHIR), so the data is available anytime and anywhere in the system. 

• Freedom to choose – Data and logic aren’t tied to a single vendor, so you’re not locked in.If you don’t like it – change it.  

Built in practice with clinicians  

Our Lifecare clinical applications haven’t been developed in isolation or just as technical demos. They have been shaped over the years in real clinical environments, in close collaboration with doctors, nurses, and other professionals. They’re used in everyday care, across both primary and specialist services from small clinics to large hospital setups.  

From this work, a few lessons stand out: 

• Applications need to reflect how clinicians think and work—not just how data is stored. 

• Flexibility and configurability are key, especially when working across different care settings. 

• Even modular and open standard apps need to meet medical safety and regulatory requirements. 

We have also invested heavily to ensure that even with a modular approach, our clinical solutions act as an umbrella that provides a unified user experience across clinicians. 

Moving beyond the Nordics: Productized and localized 

One of the big challenges in scaling clinical apps is adapting them to different countries and systems. Healthcare looks different from one place to another—different workflows, languages, documentation rules, regulatory requirements and so on. But the underlying needs and especially the patients are the same. 

The applications we’ve worked on are designed to be ready for use outside the Nordics. They’re based on standard openEHR templates and archetypes. At Tietoevry Care, we are proud of our experience in localizing these applications quickly, making them configurable for different languages, regulations, and care models. In many cases, local partners play a key role in helping us successfully implement clinical modules in new countries. They bring essential knowledge of local healthcare practices, regulatory requirements, language, and clinical workflows ensuring our solutions are truly fit for purpose. At the same time, we also work through other models when entering new markets, depending on the context and market specific needs. 

openEHR is no longer just a promising concept. It is ready to scale and  replace existing EHR systems and finally deliver the flexibility, usability and clinical value that care professionals  deserve. So, the real question is – are you ready to break the monoliths and scale openEHR beyond pilot projects? 

You can read more about our clinical modules – Journal View and Observations and Data Entry – on our website, and I am happy to share more details and spar with questions and ideas!