Clinical operations platform

One record.Every role.

Sentrion is the unified clinical workspace for hospitals: one secure patient record, one workflow, and the right level of access for every person who touches it.

One record, at the centre.

Every role works on the same patient record instead of a copy of it, so the picture is whole wherever it is opened.

Typed once, at the front desk.

Identity, allergy, appointment. Everything downstream inherits what reception entered rather than asking for it again.

Today

08:30
09:00
09:30
10:30Arrived

The guard clears before the chart opens.

A wrong-patient guard the clinician confirms first. Nothing sensitive renders until identity is settled, and the access is written down.

Identity confirmed

6.4 against a range of 3.5 to 5.1.

Outside its range, so it is marked Critical and counted. A normal result stays quiet, which is what makes the loud one mean something.

Potassium

6.4 mmol/L

3.55.1
Critical

One record. Every role.

Personal doctors and radiology are running today. The rest arrive one department at a time, each behind the same audit trail.

Personal doctorsRadiologyLaboratoryPharmacyCardiologyEmergency

The problem

Hospitals run on fragments.

Patient history sits in systems that do not talk to each other, so the person in front of the patient is rarely the person holding the whole picture.

Reception

Identity

Typed once

Ward

Allergy

Iodinated contrast

Already there

Lab

Result

K 6.4 mmol/L

Already there

15systems

Some NHS staff log in to as many as fifteen different systems to do their job.

UK Department of Health and Social Care, 2020

5.2hours a shift

At a Swiss university hospital, medical residents spent 5.2 hours of an average day on a computer and 1.7 hours with patients. Day shifts ran 11.6 hours.

Wenger et al., Annals of Internal Medicine, 2017

15%of consultations

Key clinical information was missing in 15% of outpatient consultations at UK surgical clinics. In 32% of those, care was delayed or disrupted.

Burnett et al., BMC Health Services Research, 2011

42%of health incidents

Between 2021 and 2023, hospitals absorbed 42% of reported cyber incidents in the EU health sector, where ransomware accounted for 54% of threats.

ENISA Health Sector Threat Landscape, 2023

The product

Built for the people who run the hospital.

Reception

The day, in one view.

Arrivals, appointments and registration in a single agenda. Reception starts the record, and every role downstream inherits it instead of retyping it.

Today

AppointmentsNew appointment
08:30Follow-up
09:00Office visit
09:30First visit
10:00Blood draw
10:30Arrived

Reception starts the record; every role downstream inherits it.

Doctors

The whole patient, on one sheet.

Problems, medications, allergies and history together, opened under a wrong-patient guard that asks the clinician to confirm identity before anything sensitive renders.

Patient record

Identity confirmed
Guard cleared
Iodinated contrast mediaAtrial fibrillationEssential hypertension

Problems

Medications

Results

Every value against its range.

A potassium of 6.4 against a range of 3.5 to 5.1 is marked Critical and counted. A normal result stays quiet. The clinician sees what needs attention without hunting for it.

Results

Potassium6.43.5-5.1Critical
Creatinine1.00.6-1.2Normal
Haemoglobin13.412.5-16.5Normal
Sodium140135-145Normal

A normal result stays quiet. An abnormal one is marked and counted.

One login, every role

The queue knows who you are.

A doctor signs in and gets the results waiting on them, ranked by what is critical. Reception signs into the same record and gets the day's arrivals. One system, one login, and a different job on the other side of it.

Signed in as doctor

Results to review4
Critical6.4 mmol/L
High1.7 mg/dL
Low11.9 g/dL
High84 mg/L

Ranked by what is critical, scoped to the clinician signed in.

Every product illustration on this page is drawn from the real interface. Identity is always shown as a shape, never a name: no patient record, real or synthetic, appears anywhere on this site.

One platform, every clinic

Departments plug into the same record.

Each clinic gets the view built for its job, at the right level of access, on the one record the hospital already keeps. The first two are running; the rest arrive one department at a time, each behind the same audit trail.

Personal doctorsRunning

The day, the chart, the queue: the clinic workflow end to end.

RadiologyRunning

Worklist, imaging viewer, reporting and PACS operations.

LaboratoryPlanned
PharmacyPlanned
CardiologyPlanned
EmergencyPlanned

A department goes live only when its workflow is ready, never by switching everything on at once.

Security posture

Security is the architecture, not a badge.

Sentrion has not completed a third-party audit, and this page will not pretend otherwise. What it can show is how the system is built.

Hosting
EU infrastructure. Patient data never leaves the EU.
Access
Four clinical roles, each scoped to what that job needs. Least privilege is the default.
Audit
Every record access writes an entry. No silent reads.
Identity
Directory-backed login, and a wrong-patient guard the clinician clears before any chart opens. Single sign-on and a second factor are planned, not shipped.
Data protection
GDPR Article 9 special-category handling by design.
Resilience
Built with the NIS2 obligations for essential health entities in view.
Development
Synthetic data only. No real record reaches a development machine.

Scope

A record system. Not a medical device.

The boundary is drawn in the product, not in a disclaimer at the bottom of a page. Every verb here is an operational one, which leaves clinical judgement with the clinician, where it belongs. Software that stays inside its competence is software a hospital can actually trust.

What it does

  • Records
  • Schedules
  • Routes
  • Reports
  • Audits

What it will not do

  • Diagnoses
  • Decides
  • Recommends treatment

Where we are

Early, and honest about it.

Sentrion is being designed in conversation with people working inside the Cypriot public health system, in a personal capacity and not on behalf of any institution. It is Greek-first, because that is the language the work happens in. We are looking for one department to run a pilot with. A hospital-wide rollout is not something we have earned yet.

The pilot path

Three steps, each one reversible.

  1. 01

    A walkthrough

    Forty-five minutes on synthetic data, following your department's actual workflow. You pick the scenario.

  2. 02

    A scoped pilot

    One department, agreed success criteria, and a DPIA and data processing agreement signed before a single real record is touched.

  3. 03

    A decision

    You keep the records and the audit trail whatever you decide. If it has not earned the next department, it stops here.