The Forgotten Purpose of Evidential Friction

Introduction

Why would a laboratory deliberately preserve evidence of its own mistakes? At first glance, the question appears almost absurd. 

 In modern operational environments, errors are typically corrected, records updated, workflows synchronised, and information presented in its most current form. Efficiency is rewarded. Friction is removed. Processes are streamlined. 

Yet for decades, mature laboratory environments often adopted a very different approach. It went like this (and in fact it still does): 

•  A laboratory scientist discovers an error in a handwritten testing record. 
•  The original entry is not erased. 
•  The original wording remains visible. 
•  A single line is drawn through the incorrect entry. 
•  The amendment is recorded. 
•  The date and time are added. 
•  The amendment is signed. 
•  A second individual countersigns the correction. 
•  The original record remains preserved. 

Now years later, a regulator may still inspect the entire sequence. The obvious question is: Why? 

Why preserve the mistake? 

Why preserve the superseded entry? 

Why preserve evidence that an error occurred at all? 

The answer reveals something important. These procedures were never merely administrative. They were evidential. 

These controls were not created because previous generations enjoyed administrative complexity. They evolved because previous generations repeatedly encountered evidential failure. 

Long before cloud platforms, integrated traceability systems, workflow engines, dashboards, metadata repositories and paperless governance environments existed, mature laboratory systems had already encountered a difficult problem. And that problem is expressed in the question: “How do you preserve trust in information that may one day be challenged?” 

The challenge was never merely and exclusively scientific. It was also evidential. 

And that distinction may be becoming increasingly important as healthcare, testing, certification and compliance environments continue their rapid transition toward digitally mediated operational ecosystems. 

The Forgotten Purpose of Evidential Friction

Modern discussions concerning digital transformation often present historical paper-based systems as administrative relics waiting to be replaced by more sophisticated technology. But it is my firm suggestion such a prevalent perspective may overlook something important. 

Many mature analogue governance systems were not primitive. 

In some respects they were highly evolved. Indeed, some of their most cumbersome features appear to have evolved in direct response to evidential risk including: 

• Visible amendments. 
• Retention of originals. 
• Countersignatures. 
• Bounded custody. 
• Chronological continuity. 
• Documentary traceability. 
• Independent inspection. 
• Preservation of physical artefacts. 

These are not merely operational controls. They are evidential controls. Importantly, the paper itself was never the point. Paper was simply the medium through which certain evidential functions were achieved. 

Those functions included: 

• making alteration visible;
• preserving chronology;
• attributing authorship;
• retaining originals; 
• resisting undetectable retrospective change;
• preserving independent review.

In other words, mature governance systems embedded “evidential friction” directly into operational processes. And that ‘friction’ served a number of key purposes. For example Evidential Friction made: 

• invisible alteration difficult. 
• retrospective reconstruction difficult. 
• uncertainty easier to detect. 

 And over time these systems evolved under pressure from precisely the forms of scrutiny that testing and certification environments may eventually encounter: 

• regulatory challenge;
• patient-safety investigations;
• scientific reproducibility demands;
• litigation;
• institutional accountability; and 
• forensic examination.

The obvious question therefore becomes: Were these controls solving problems that modern systems still face today? Or have those problems quietly disappeared? 

The Question Not Being Asked

Modern digital systems are extraordinarily capable. They can improve: 

• visibility. 
• workflow. 
• interoperability. 
• operational speed. 
• coordination. 
• traceability. 

In many circumstances they represent genuine advances. Now this Article is not an argument against digital transformation. Nor is it an argument in favour of returning to paper. 

The issue lies elsewhere. 

The question is whether digital transformation has preserved the evidential protections that earlier governance systems evolved over decades of operational and regulatory experience. 

Because operational success and evidential resilience are not necessarily the same thing. 

A system may appear to be functioning perfectly as it: 

• passes audits. 
• supports certification. 
• generates management confidence. 

It may become to be perceived as commercially indispensable. 

And yet entirely different questions may emerge once legal scrutiny begins. Questions such as: 

•  Can the original state of the record be reconstructed? 
• Can authorship be proven? 
• Can record chronology be demonstrated? 
• Can retrospective alteration be detected? 
• Was the record created contemporaneously? 
• Can the original artefact be examined? 
• Was the operational environment stable at the time the record was created? 

Again – these are not operational questions. They are questions of Evidence. Evidence that might be crucial an effective defence. 

And it is my firm opinion that computer software driven operational functionality does not automatically answer the questions I have just put. 

Organisations rarely discover Evidential Weaknesses during ordinary operations. As I have made out before: systems continue functioning; audits continue to be passed; certifications continue to be  issued. And institutional Confidence continues to grow. 

The weakness often becomes visible only when a regulator, claimant, prosecutor, expert witness or Court begin asking questions the system was never designed to answer. 

The Sterilisation Indicator Problem

Consider a simple example. 

Within many decontamination and sterilisation environments, chemically reactive indicators change colour after exposure to specified sterilisation conditions. The colour change forms part of the assurance process. And historically, physical indicators were often retained alongside associated records. 

Accordingly (and crucially) the physical artefact itself became part of the assurance architecture. 

Now consider a different environment structured as follows:- 

• The indicator is scanned. 
• A digital record is created. 
• The image is uploaded. 
• The computer-recorded workflow progresses. 
• The software’s dashboard updates, and 
• The physical indicator is discarded. 

Operationally, the process may appear entirely satisfactory from an operational view-point. But is it actually satisfactory as litigation arises and the party using the Indicator Label is put to proof. 

As a matter of logic (and experience) let us examine what is to happen when a Patient-Safety Incident Question arises. 

And the worst of all worlds is when the Laboratory is finding itself in an aggressive situation. Perhaps during litigation. Perhaps during a regulatory investigation. Perhaps during a contractual dispute. 

The organisation seeks to rely on the digital record. But then a challenge in Court arises: – “Where is the original indicator label?”  

The answer may be uncomfortable. Perhaps it no longer exists. 

Or perhaps it exists but has faded. 

Or perhaps its appearance has changed. 

Or perhaps nobody can establish its condition at the relevant time. 

At that point, an extremely important evidential transition has occurred. A Primary Artefact (which might prove a valid sterilisation occurred) has been replaced by a secondary representation of it. Whether anything has been lost during that transition may depend entirely upon how the transition was designed and documented. 

The issue is not whether the representation is useful. The issue is whether the Evidential Characteristics of the Original Artefact have been preserved. 

That is a very different question. And it is precisely the kind of question that mature governance systems historically evolved to address. 

The Courtroom

To understand why this matters, imagine a hospital is seeking to defend itself against a determined litigant. Let us imagine the litigation involves whether instruments were properly decontaminated.  

Naturally, the hospital will seek to rely on its Sterilisation Records. Their records indicate successful processing. The digital system appears complete. But the Claimant challenges the records. And here we see the compelling shift that Litigation produces. The Claimant neither challenges the content of the records nor their integrity. 

Attention of the Court shifts dynamically. The Argument before the Court is no longer “Were the instruments sterile?”  

The Legal Challenge pivots and the argument generated by the Claimant becomes: “How do you know?” 

Ordinarily, the Court will begin by examining the evidential chain That is the chain of possession and forensic examination of individual evidence to see where the Evidence went, who had it and what happened to it. Notice that the discussion has moved away from sterilisation entirely. The instruments are no longer the immediate subject of examination. The record itself has become the object under scrutiny. 

Therefore the Court will require satisfaction with respect to Evidential Artefacts upon which a side is going to rely. The Court will require satisfaction on subjects such as:

• Where is the original artefact? 
• How was it preserved? 
• Who controlled it? 
• How was it controlled?
• Can its condition at the relevant time be demonstrated? Usually, in these cases, the ‘relevant time’ was the tie the digital record was created.
• Can the transition from physical event to digital record be reconstructed? 

At that moment, the issue is no longer operational performance. The issue is Proof. 

The danger is not that the process failed. The danger is that years later the organisation may be unable to prove that it succeeded. The organisation may discover that information it regarded as operationally complete is evidentially incomplete.  

The distinction may appear to be subtle ‘Lawyer’s Chatter’. Whether subtle or not, I am certain that the consequences in Court are unlikely to be subtle at all. 

The House of Cards Nobody Sees

A certification report may appear to be a single conclusion. A reader may see only the final document, the laboratory logo, the signature and the stated outcome. 

The conclusion appears settled and the certification appears complete. All that is to be relied upon (like the Report) appears self-contained. 

In reality, however, the visible conclusion may depend upon a large number of underlying evidential layers that remain largely unseen. A manufacturer may rely upon the report when placing products on the market. Hospitals may rely upon it when purchasing equipment. Patients may ultimately rely upon it without ever knowing it exists. 

Yet the visible conclusion may depend upon evidential foundations that few people ever examine. And those foundations may include: 

• calibration histories;
• environmental monitoring records;
• instrument maintenance records;
• technician competency records;
• laboratory procedures;
• sample handling records;
• audit trails;
• supporting test data;
• and numerous other evidential artefacts. 

Operationally, these dependencies often remain invisible. After all the Report exists and the conclusion is accepted. The certification is relied upon. 

Few people ever look beneath the surface. Until a question arises concerning one of the underlying layers. 

A downstream conclusion is not necessarily stronger than the records upon which it depends. This creates a hidden structural dependency. Which means operationally the structure appears to be robust. But, Evidentially, it may resemble something rather different. 

The litigants reliance is placed upon a “House of Cards”. 

Please bear in mind that the issue is not that the structure lacks sophistication. The issue is that hidden evidential weaknesses may remain invisible for years. 

And finally, suddenly, your protagonist invites the Court to exercise a serious degree of Scrutiny. 

They require the Court to apply pressure to the Foundational Layer of this House of Cards. Once again, and I have mentioned this in earlier Articles – the ‘fight’ has shifted from who did what and when; to other issues which support your Evidence. The challenge may begin moving upwards through the structure. The visible conclusion may be only as strong as the least resilient evidential layer beneath it. And that reality often remains hidden until scrutiny is applied to a layer nobody previously thought to question. 

And down will come the House of Cards. 

Scientific Validity And Evidential Validity

The Testing And Auditing of Computer Software Systems  are generally designed to establish:

• technical conformity;
• repeatability;
• efficacy;
• calibration reliability;
• process control;
• scientific consistency.

All of those things matter enormously. There can be no gainsaying that. But Legal Scrutiny applies a different lens. 

Courts do not merely examine whether a process worked. 

Courts also examine whether the resulting evidence can be demonstrated to possess integrity, continuity, traceability and reliability. 

Now those are not identical questions. For a scientifically valid process may still encounter evidential difficulties if the mechanisms necessary to demonstrate continuity, chronology, preservation and authenticity cannot be established. 

This distinction may become increasingly important as software-mediated operational ecosystems continue expanding throughout healthcare, certification and compliance environments. 

The Forgotten Analogue History

Historically, evolved analogue systems embedded evidential safeguards through visible continuity, retained originals, constrained alteration pathways and procedural friction. 

As operational ecosystems become increasingly digital, cloud authoritative, interoperable and software-mediated; it is my contention that those same safeguards may need to be consciously re-engineered rather than simply assumed.  

In my opinion that may prove to be one of the most important hidden governance questions facing healthcare and patient-safety-critical environments over the next decade.  

The future issue is therefore not whether digital systems replace paper. That question has largely been answered. The future issue is whether digitally transformed operational ecosystems preserve the evidential safeguards that earlier governance cultures evolved in response to hard-learned experience. Because those earlier systems were not merely preserving information. They were preserving Trust. 

Closing Thoughts

Someone learned these lessons. 

Somewhere. 

Under pressure. 

Following challenge. 

Following dispute.  

Following failure.  

Lawyers see them in early Law Reports around the time of the beginning of the railways. And those earlier generations responded by building safeguards intended to preserve trust, continuity, traceability and proof.  

Over time those safeguards became so familiar that many came to regard them as ordinary administrative procedure.  

They were not.  

Again – they were evidential. 

As healthcare, testing and compliance environments continue pursuing ever-greater operational efficiency, the critical question may therefore not be whether digital transformation succeeds. It may be whether, in the pursuit of efficiency, organisations have quietly abandoned protections that previous generations learned they could not afford to lose. 

The difficulty is that such weaknesses often remain invisible. 

As I have said before: Systems continue functioning; Audits continue passing; Certifications continue being issued; and Confidence continues growing. 

Until one day a regulator, claimant, prosecutor, expert witness or Court begins asking questions the System was never designed to answer. 

And by then, the issue may no longer be whether the process worked. The issue may be whether anybody can still prove that it did.  

Missed the earlier parts of the series?

Read the first two articles by Dr. Brian Bandey:

When Compliance Data Enters the Courtroom – and Fails

Why Most Compliance Systems Cannot Prove Data Integrity in Court

Disclaimer. The views and opinions expressed in this article are solely those of the author and do not necessarily reflect the official policy or position of Test Labs Limited. The content provided is for informational purposes only and is not intended to constitute legal or professional advice. Test Labs assumes no responsibility for any errors or omissions in the content of this article, nor for any actions taken in reliance thereon.