Enterprise Architecture for Healthcare: A Practical Guide
A healthcare organisation runs electronic health records, laboratory, imaging, pharmacy, scheduling and billing side by side. Architecture describes these applications, their exchanges and their owners before any change.
Updated on
An application landscape inherited from several eras
A single hospital or care group can run dozens of specialised systems: electronic health records, laboratory, imaging, pharmacy, scheduling and billing. They were bought at different times from different vendors, each with its own data model.
A clinical system cannot be switched off to tidy the architecture: an interruption affects care. Enterprise architecture makes applications, their dependencies and their owners visible, so that each change is prepared before anyone touches it.
Interoperability and standards
HL7 publishes FHIR, a standard for exchanging healthcare information electronically. DICOM is the international standard for medical images and related information; NEMA acts as its secretariat. Real environments still mix versions, partial implementations and point-to-point interfaces that nobody fully documents.
An architecture model describes which applications hold which data, through which interfaces it moves and where the brittle integrations are. In ArchiLU, each interface connects a source application to a target application, with its protocol and the data it carries. A protocol such as FHIR is added to the protocol catalogue if it is missing, and an interface without a protocol is flagged as incomplete.
Modernising without interrupting care
Replacing every clinical system at once exposes care to an interruption. A capability and application map lets you phase modernisation: wrapping, replacing or retiring components in an order that protects clinical continuity and spreads cost and risk over time.
In ArchiLU, the 360 view of an application shows its flows, its interfaces, the processes it serves and the capabilities it realises. The application landscape carries the current state, the target and a dated roadmap.
- Connect each existing system to the capabilities it supports.
- Identify the applications and interfaces that depend on it before a replacement.
- Sequence changes to protect continuity of care.
Health data and the regulatory framework
The GDPR places data concerning health among the special categories of personal data: processing them is prohibited except in the cases set out in its Article 9. The NIS 2 Directive lists health among the sectors of high criticality and covers healthcare providers in particular. In Luxembourg, the law of 5 May 2026 transposes NIS 2.
These texts require knowing where data resides and which systems process it. The architecture repository documents applications, the data they exchange and their owners, which supports access and risk reviews. It describes this data without containing patient records.
This documentation does not guarantee compliance. Meeting the rules on health data and security remains the organisation’s responsibility, supported by its legal and security functions.
Getting started in ArchiLU
Each organisation has its own dedicated instance, hosted in the European Union. Deployment on your premises is available as an option, on quotation.
The application list records, for each application, its owner, criticality, lifecycle and supplier; the TIME view shows the support status of its technologies. These elements prepare a modernisation roadmap. To describe activities, a process catalogue such as APQC’s PCF for healthcare providers can serve as a starting point.
Frequently asked questions
- Why is interoperability so hard in healthcare?
- Healthcare organisations accumulate specialised systems from different vendors and eras. Even with FHIR and DICOM, versions and partial implementations differ. An architecture model makes systems and their exchanges explicit before interoperability is planned.
- Can enterprise architecture help modernise clinical systems?
- Yes. It connects each system to the capabilities it supports and to what depends on it, so replacements can be phased. The migration project still has to be run; architecture gives it the dependencies and a defensible order.
- Where is ArchiLU hosted, and does it hold patient data?
- Each organisation has its own dedicated instance, hosted in the European Union; deployment on your premises is available as an option, on quotation. The repository describes applications, their flows and the data they carry, not patient records. It does not replace the organisation’s own compliance analysis.