Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is Laboratory Information System Security?

Laboratory information system security protects the platform that holds pathology orders, analyser results, and reports, where an integrity failure changes clinical decisions rather than merely leaking data.

Illustration for the cybersecurity term Laboratory Information System Security
Home / Blog / Cybersecurity Terms / What Is Laboratory Information System Security?
17 November 2026

What Is Laboratory Information System Security?

What Is Laboratory Information System Security?

The laboratory information system is the record of truth for pathology. It receives the request, tracks the specimen, pulls the numeric result off the analyser, applies reference ranges and flags, holds the authorising scientist’s sign-off, and pushes the report back to the ordering clinician. Laboratory information system security is the work of protecting that chain, and it has an unusual emphasis: in most health IT the dominant concern is confidentiality, while here the dominant concern is integrity. A leaked result is a serious breach. A wrong result is a clinical incident.

Availability runs a close second. Modern medicine does very little without blood sciences, and when the system stops, so do transfusions, chemotherapy, and most elective surgery.

What Makes These Systems Fragile

Integrity Is the Real Threat Model

Think about what an attacker with write access could change rather than what they could read. Altering a potassium result, a cross-match outcome, an INR, or a histopathology conclusion produces clinical harm without any obvious indicator that an attack took place. Even benign-looking tampering with reference ranges, analyser calibration data, or the mapping between a specimen identifier and a patient record can produce the same effect at scale.

Controls that address this directly include append-only audit logging of result changes with the identity of the person who made them, reconciliation between analyser output and stored values, cryptographic integrity checks on interface messages where the vendor supports them, alerting on bulk edits, and delta checks that flag a result inconsistent with the patient’s history.

Ransomware and the Synnovis Lesson

On 3 June 2024 the Qilin group attacked Synnovis, the pathology partnership serving Guy’s and St Thomas’ and King’s College Hospital NHS Foundation Trusts in south-east London. The consequences ran far beyond IT. Blood test processing collapsed, thousands of outpatient appointments and elective procedures were postponed over the following weeks, hospitals could not match blood reliably and fell back on type O supplies, and NHS Blood and Transplant issued a national appeal for O-type donors. In June 2025 King’s College Hospital confirmed that a patient death had been linked in part to the disruption.

The case made several points that security teams had been arguing for years. Pathology is a single point of failure for an entire regional care system; a laboratory service provider is critical national infrastructure in all but name; and manual fallback for a high-volume laboratory is not a realistic substitute for more than a few hours. It belongs in any discussion of ransomware in healthcare.

Practical Controls

  1. Segment the analyser network so instruments and middleware can reach only the system they need, and nothing can reach them from the general hospital network.
  2. Keep an inventory of every instrument, middleware server, and interface engine, including the operating system and support status.
  3. Replace shared bench accounts with individual identities, using badge or smartcard sign-on so that it does not slow clinical work.
  4. Protect the interface engine as a crown jewel; it holds credentials and routing for every connected system.
  5. Back up the database and the configuration separately, store copies offline, and rehearse restoring to a known clinical state, not just to a working server.
  6. Write and practise a downtime plan with the clinical teams, covering paper requesting, result reporting, and the reconciliation afterwards.

The UK Regulatory Picture

Medical laboratories in the UK are accredited by UKAS against ISO 15189, whose 2022 revision strengthened expectations around information management, data integrity, and continuity of service. NHS organisations and their pathology partners also work to the Data Security and Protection Toolkit, now being aligned with the NCSC Cyber Assessment Framework, and to the clinical risk management standards DCB0129 and DCB0160 when deploying health IT. Test results are health data and therefore special category personal data under the UK GDPR, and larger providers fall within the Network and Information Systems Regulations 2018.

Where a laboratory needs to know what an attacker could actually reach across its analyser and middleware estate, our infrastructure and architecture review services examine the segmentation and interface design before anything is tested actively.

FAQ – Frequently Asked Questions

Why Is Integrity More Important Than Confidentiality Here?

Because clinicians act on the numbers. A disclosed result harms privacy and must be reported, but an altered result changes a transfusion, a dose, or a diagnosis, and nothing in the workflow is designed to catch it. Confidentiality controls are still required; the point is that integrity controls deserve equal engineering attention and usually get far less.

Can Analyser Interfaces Be Encrypted?

Sometimes, and increasingly so on newer instruments that support HL7 over TLS or a secure middleware connection. Much installed equipment cannot, and replacing it for that reason alone is rarely justifiable. The standard answer is compensating controls: a dedicated analyser VLAN, strict allow rules, physical port security, and monitoring of the interface traffic for anomalies.

How Long Can a Laboratory Run on Paper?

Hours rather than days, for a hospital laboratory handling thousands of specimens a day. Manual requesting and telephone reporting can keep urgent and life-critical work moving, but throughput falls sharply and the reconciliation afterwards is itself error-prone. Downtime planning should therefore focus on rapid, verified restoration as much as on paper fallback.

Does ISO 15189 Cover Cybersecurity?

Not as a dedicated chapter, but its requirements on information management, data integrity, record control, and continuity reach much of the same ground, and the 2022 revision sharpened them. Accreditation assessors increasingly ask how a laboratory controls access to its information system and how it would continue to report results during an IT outage.

Related Terms

You May Be Interested In These

What Is HackRF?

Cybersecurity Terms

17 November 2026

What Is HackRF?

Read More
What Is the Terrapin Attack?

Cybersecurity Terms

17 November 2026

What Is the Terrapin Attack?

Read More