Less noise. More relevant information.
A hospital does not need more alerts
Modern hospitals generate vast amounts of data: laboratory results, orders, observations, hospitalisation data, changes in a patient’s condition and events recorded across multiple departmental systems.
The challenge is no longer access to information alone. It is recognising which information requires attention, how urgent an event is, who should receive the message, how it should be delivered and what should happen if the first person does not respond.
MedAlert is an intelligent hospital-notification system designed to help detect, classify, route and deliver information about events that may require a healthcare professional’s attention. Its purpose is to reduce information noise rather than create another source of mass alerts.
- Does the event require attention?
- How urgent is it?
- Who should receive the message?
- How should it be delivered?
- What should happen if there is no response?
How MedAlert works
Five stages turn data into a controlled communication process
The workflow starts with events already available in hospital systems and ends with delivery, acknowledgement, escalation and process analysis.
- 01
Collects information
Uses data available in HIS, LIS and other departmental systems relevant to the configured process. The integration method depends on the hospital’s architecture and available interfaces.
- 02
Detects and categorises an event
The AW-KZM algorithm helps identify events that may require attention and assigns a category and urgency level, potentially using a broader context rather than a single value.
- 03
Selects the appropriate recipient
ASA-K takes account of role, responsibility, organisational structure, shift pattern, urgency and the first recipient’s response or lack of response.
- 04
Selects the delivery method
ADP-K supports the way a message is delivered and presented. Related events can be grouped to limit redundant notifications and make their meaning easier to understand.
- 05
Supports escalation and traceability
The process can record generation, recipient selection, delivery, acknowledgement, lack of response, escalation and completion of an event.
Three intelligent mechanisms
The algorithms behind MedAlert
Each mechanism addresses a different part of the information path: understanding the event, choosing the recipient and selecting the form of delivery.
AW-KZM
Detection and categorisation of critical medical events
Analyses data from hospital systems and helps determine the meaning and urgency of an event.
ASA-K
Message-recipient selection
Selects a recipient based on role, hierarchy, working mode, organisational context and the response to an earlier notification.
ADP-K
Delivery and presentation method
Helps decide how information should be presented so that a user can quickly understand its significance without increasing information noise.
Configurable scenarios
What types of events can MedAlert support?
The final scope is agreed with each hospital and depends on available data, processes and integration configuration. An implementation does not have to begin with the most complex clinical scenarios.
- Critical or significantly changed laboratory results
- Results requiring assessment in the context of previous measurements
- An order not completed within an expected period
- New results, observations or information requiring communication to the responsible person
- A change of unit, bed or hospitalisation status
- Events associated with preparation for a procedure
- Information relevant when transferring a patient between units
- No response to an earlier message
- Several related events occurring within a short period
More than a standard notification system
- A specific recipient
- A message can be directed to a person selected by role and organisational context instead of being sent to everyone.
- Different priorities
- The system helps distinguish routine information from an event requiring a rapid response.
- Response-aware workflow
- The process can repeat a notification or pass it to another person when no acknowledgement is received.
- Existing systems remain the source
- MedAlert does not replace HIS or LIS; it creates an intelligent communication layer over available data.
Benefits across the organisation
Relevant information for staff and an analysable process for management
MedAlert supports day-to-day users while giving a hospital a clearer view of how important events are communicated and handled.
Healthcare professionals
Fewer irrelevant messages and clearer responsibility
Doctor
- Less need to search for relevant information manually
- Messages aligned with role and responsibility
- Fast access to the event context
Nurse
- Clear information about an event requiring attention
- A defined acknowledgement and escalation path
- Messages aligned with a unit or scope of duties
Laboratory professional
- Support for communicating results requiring urgent review
- Less manual effort contacting successive people
- A record of message delivery
Management and process owners
A measurable communication process
- Faster flow of relevant informationLess dependence on monitoring another screen or making a sequence of telephone calls.
- Better use of existing dataHIS and LIS events can automatically trigger defined communication processes.
- Clear escalation pathsThe hospital can define what happens when a recipient does not acknowledge a message.
- Process analysisRecorded stages support analysis of delivery and handling times and help identify recurring delays.
- Better use of existing infrastructureMedAlert builds on the systems and data already present in the hospital.
Hospital-system integration
An intelligent communication layer over HIS, LIS and departmental systems
During R&D work, data from the AMMS HIS and InfoMedica LIS systems were analysed. The production integration architecture is always established after examining the hospital environment, software versions, available interfaces and security requirements.
Integration methods are selected for the hospital
Depending on source-system capabilities, an implementation may use available APIs, HL7 messages, FHIR resources, database mechanisms, exchange files or other interfaces supported by the software provider.
No universal connector is assumed
Every hospital has a different system architecture and configuration. The integration scope is therefore confirmed after a technical and process analysis.
Human oversight
MedAlert supports staff — it does not replace a clinical decision
MedAlert should not be presented as a system that independently diagnoses a patient or makes treatment decisions. It analyses data, identifies events that may require attention, organises information, indicates priority, routes a message and supports controlled escalation.
Implementation path
Start with one process in which important information is currently difficult to manage
The implementation is built around a defined hospital scenario rather than a generic list of technologies.
- 01
Process analysis
We identify events that currently require manual monitoring or communication.
- 02
Scenario selection
We define which data trigger a message, its priority and the person responsible for responding.
- 03
Integration design
We examine HIS, LIS and other sources and establish the information-exchange method.
- 04
Roles and escalation
We configure recipients, deputies, hierarchies, shift modes and the response to a lack of acknowledgement.
- 05
Tests using demonstration data
Scenarios are verified in a controlled environment using synthetic or appropriately prepared test data.
- 06
Pilot
The system can initially operate within a limited scope or in observation mode without affecting the live process.
- 07
Launch and monitoring
After approval, the production workflow is launched and its results are monitored and refined.
Product based on completed R&D work
From an integrated prototype to repeatable hospital deployments
MedAlert was developed under the project “Development of intelligent algorithms controlling the selection and routing of critical messages for medical processes in inpatient care”, no. FENG.01.01-IP.02-1046/23.
R&D work has been completed. Its results include the AW-KZM, ASA-K and ADP-K algorithms, an integration layer, a data model and an integrated system prototype. The final payment application was approved and the project audit was completed with a positive result.
Infotower Business Solutions is now preparing MedAlert for repeatable deployments, commercial sales, licensing, maintenance, diagnostics and scaling in hospital environments. Market introduction is planned by 31 December 2026.
A scenario for your hospital
Where does important information currently arrive too late?
Let us examine a process that requires manual monitoring, repeated telephone calls or has no clear escalation path. Together, we will assess whether MedAlert can improve it and what data would be required.