SereneDiagnostics

Serene Cloud

Where the system runs, and how it is kept safe.

Serene LIS runs on a secure cloud server, not on a PC under the reception desk. Every counter, bench and collection centre works from the same record over an encrypted connection, and the analysers in the laboratory never touch the internet at all.

The shape of it

One locked door, and nothing reaching in.

Counters and collection centresBrowsers, over HTTPS
Serene CloudThe application and the database. One public hostname, behind an encrypted tunnel.
Laboratory gatewayOn the lab network. Connects outward only.
AnalysersNo route to the internet
  • The analysers never touch the internet

    They have no route out. A small gateway on the laboratory's own network speaks to them and is the only thing that crosses the boundary, which is what makes an analyser running an old operating system safe to keep.

  • Nothing reaches into the laboratory

    The gateway connects outward to the cloud. There is no port forwarded, no public address at the lab and no hole in its firewall for anyone to find.

  • The database is never public

    One hostname is published, through an encrypted tunnel with the certificate handled at the edge. The database sits on a private network the internet cannot see.

Run for you

What looking after it involves.

  • Every site, one record

    A new collection centre is added as a site in minutes, with no server work. The owner sees every site; a centre's own staff see that centre's patients and nobody else's.

  • Your own deployment

    Each laboratory has its own database, its own files, its own backups and its own domain. Nothing is shared with another laboratory except the code.

  • Backups that prove themselves

    Encrypted before they leave the server and copied off it, then read back and counted to prove they hold what they should. A backup that fails says so loudly, because a silent one is the same as none.

  • Updates on your schedule

    Every laboratory runs the same release, and it can be held to that lab's quiet window, so nothing changes under somebody in the middle of a busy morning.

  • A check before the doors open

    At half past six every morning, ten checks, among them messages that failed, a low SMS balance, stuck print jobs, reports unsigned for a day, transfers not received, rejected QC, stock at zero and analysers that have gone quiet. Silent when all is well.

  • Access checked on every request

    Nine roles, read from the database each time rather than trusted from a login, so removing somebody's access takes effect at once.

  • Crash reports carry no patient

    Error reporting is off unless a laboratory chooses it, and when it is on, names, identity numbers, telephone numbers and report links are stripped before anything leaves.

  • Logs that name nobody

    No patient name, result or identity number is ever written into an operational log. An engineer fixing a fault never needs to see one.

What it is not

It is not offline first. A counter or collection centre needs a working connection to register and bill, and we would rather tell you that here than have you find out the morning the line goes down. Ask us how your sites are connected and we will tell you what we would do about it.

CallWhatsApp