For hospitals, medical centres & practices

When IT stops, treatment waits.

Medical organisations run one of the most heterogeneous IT landscapes there is — and are the least able to interrupt it. octoja monitors around the clock, patches in genuine maintenance windows and documents every access.

  • At night the alert goes to the on-call engineer, not into a mailbox
  • Sensitive systems get their own maintenance windows
  • Every access to a workstation is documented
24/7

alerting with an on-call rota

50

service checks from SQL to print queues

9

backup vendors monitored

SNMP

for equipment without an agent

Starting position

Sound familiar?

In hospital operations, each of these has a time of day at which it hurts most.

A service fails on Friday night — and is noticed on Monday morning.

A restart in the middle of a clinic is not an option, yet it happens anyway.

No agent is allowed to run on specialist systems — but they still need monitoring.

Backups run, but nobody checks nine vendor consoles every day.

Access to workstations holding patient data is sensitive and barely evidenced.

Scenario

Friday, 23:40. The database service behind the hospital information system is no longer responding properly — the check fails for the second time in a row.

Because service hours are configured, the alert does not go into a mailbox but by phone call and SMS to the on-call engineer. The alert latch stops the next 40 check runs making the same phone ring.

The administrator on duty opens the session in the browser, reviews service status and the event log, and restarts the service. At the next successful check run, the automatically raised ticket closes itself. On Monday the incident appears in the report — with timestamp and person.

In use

Operational safety around the clock

The features that matter when nobody can afford to wait out an outage.

Alerting with an on-call rota

Service hours per channel — including across midnight. Escalation by failure rate, an alert latch against alert floods, automatic all-clear including ticket closure.

Core systems in view

Microsoft SQL, PostgreSQL, MySQL and MariaDB, Hyper-V, VMware, IIS application pools, terminal sessions and print queues.

Patching without stopping treatment

Separate maintenance windows per ring, an approval workflow, exclusion of known problem updates, restarts deferrable more than once.

Check backups across vendors

Veeam, Acronis, Cove, Altaro, Arcserve, Xopero, TERRA CLOUD, Synology and Windows Server Backup in a single status view.

Access limited and evidenced

17 separate action permissions, enforceable consent, automatic screen lock, a complete device log.

Help without the travel time

Screen, terminal, files, services and event log in the browser — across multiple sites too.

And that is not all

  • UPS monitoring including switchover events
  • Evidence of encryption per drive
  • Checks for open network shares
  • Wallboard for the control room
  • Certificate expiry with advance warning
  • Scheduled report delivery

What counts in an emergency shows itself in your own on-call scenario, not in a list.

Get trial access
Alerting & connectivity

The alert lands where your team already works.

An alert is only worth something once it reaches the right person at the right time — and closes itself again when the problem has gone.

Ticketing systems & PSA

Alerts raise a ticket where your team already works — and close it again on all-clear. Customer records can be imported.

  • DocBee
  • TANSS
  • TOPdesk
  • c-entron Service-Board
  • HaloPSA
  • Autotask
  • Jira Service Management
  • Freshservice
  • Inserve
  • Odoo Helpdesk
  • Codemeta

Alerting

Separate service hours per channel. Into the ticketing system during the day, by phone call to the on-call engineer at night — alerts outside those hours are held back, not discarded.

  • Microsoft Teams
  • E-Mail
  • Signierte Webhooks
  • SMS
  • Sprachanruf
  • WhatsApp
  • App-Push
  • Internes Ticket

Documentation & ITAM

The device estate is mirrored into your existing documentation rather than creating a second register.

  • Hudu
  • IT Glue
  • woasi
  • Jira Assets

Antivirus, EDR & vulnerabilities

Protection status and vulnerabilities come together in the same view as the rest of the estate — regardless of whose security software the customer runs.

  • Microsoft Defender
  • Bitdefender GravityZone
  • SentinelOne
  • CrowdStrike Falcon
  • Sophos
  • ESET
  • G DATA
  • Securepoint Antivirus Pro
  • ThreatDown (Malwarebytes)
  • Lywand Schwachstellenaudit

Backup — monitored across vendors

Firewalls & appliances

Hardware, storage and network without an agent

Server workloads

Evidence

Requirements and matching evidence

octoja is not a medical device and holds no certification. The platform produces the technical evidence required in these contexts.

GDPR Art. 32

Protecting special categories of personal data

Encryption status per drive, checks for open shares, account audit, logged remote access with consent.

NIS2 / KRITIS

Evidencing availability and vulnerability handling

Availability metrics in the SLA report, documented patch cycles and an incident report.

Internal quality assurance

Evidenced recoverability

Cross-vendor backup monitoring with a status report and alerts on failed runs.

Let us talk about your on-call scenario

We will show you in a trial access how alerting, maintenance windows and evidence would look in your organisation.