AviCennaX ICU
Bedside devices write directly into the record across entire intensive care networks.
A centralised platform for intensive care, capturing high-frequency data straight from ventilators, monitors and pumps, normalising it to clinical standards, and synchronising it with the hospital record and the national platform. Deployed across intensive care estates from single units to whole city hospital campuses.
- AviCennaX Link — direct one-to-one bedside device integration
- AviCennaX Change — central monitoring gateway aggregating whole wards
- Automated APACHE II and SOFA severity scoring
- Medication tracking and intake/output monitoring
- Automated vital sign verification
- Digital rounds and order management
- Bi-directional hospital information system synchronisation
- Real-time trend analysis for physicians
What clinicians actually see
The unit at the bedside
Link is not only a software module. It is a machined aluminium unit that sits at the bed, cabled to the ventilator or monitor, taking a one-to-one connection and handing back a normalised, patient-associated stream.
Plan view. Connector edge shown indicatively.
- Model
- AviCennaX Link — AXL4
- Power
- DC 5V 3A (USB-C)
- Enclosure
- Machined aluminium
- Placement
- One unit per bedside device link
- Capture
- High-frequency streaming
- Patient association
- Automatic
- Output
- Normalised to HL7 / FHIR, encrypted in transit
Live from the device
Link, Change and middleware
No single integration method reaches every device, so the platform uses three. Which one applies depends on how the equipment exposes its data, not on what it is called.
- Link opens a one-to-one connection at the bedside for high-frequency capture, and associates the stream with the patient automatically
- Change integrates with central monitor stations to aggregate whole wards at low latency
- Middleware covers infusion pumps and other equipment that exposes no direct interface
Closed ecosystems included
HL7 v2 and v3 are supported natively, but a great deal of intensive care equipment does not speak them. Support for proprietary manufacturer protocols is what makes vendor independence real rather than aspirational, and everything is encrypted in transit.
Both directions with the hospital record
Integration that only writes outward leaves the ICU as another island. Demographics, orders and results move both ways, ward transfers stay in step from admission to discharge, and nothing needs entering twice.
What standardisation is for
Mapping to shared terminology is not housekeeping. It is what makes a record legible outside the unit that produced it — to the next ward, to the national platform, and to anything trained on it later.
- One longitudinal record per patient, rather than one per department
- No manual transcription step between device and chart
- Standardised data that later AI work can actually be built on
What comes next
Years of high-frequency device data is the foundation for prediction rather than the point of it.
- AI-assisted decision support for predictive patient alerts
- Forecasting deterioration risk from historical device data
Three routes to one record
Different classes of equipment reach the record by different paths. Monitors arrive through the central station, ventilators and specialised monitoring one-to-one at the bedside, pumps through middleware — and all of it lands normalised.
GE B40, B450, B850 · Mindray BeneVision N15, N17
AviCennaX ChangeGE R860 · Hamilton · Maquet
AviCennaX LinkMasimo · Philips
AviCennaX LinkB. Braun Space · Alaris
Device MiddlewareMulti-vendor support via IEEE 11073
Capture- HL7 v2 / v3 native
- Proprietary vendor protocols
- Normalised to HL7 / FHIR
- Encrypted in transit
Measurements and observations mapped to shared terminology, so a reading means the same thing outside the unit that produced it.
One record per patient, whatever it was captured by.
- Demographics, orders and results
- Ward transfer sync
- No duplicate entry
Real-time synchronisation with e-Nabız, the national e-health platform.
Tell us what your health system needs to do
We work with ministries, hospital groups and funding agencies to scope national digital health programmes.