Innovation

BridgePoint4: sterile services, under control

A modular, multi-tenant platform for NHS and independent decontamination units. BridgePoint4 replaces paper logbooks, spreadsheets and closed on-premise tools with one auditable system of record.

BridgePoint4
The distinction that matters

It enhances your track and trace system rather than replacing it

BridgePoint4 reads from the systems a department already runs, keeps its own protected copy, adds the machine and maintenance evidence those systems don't hold, and gives you one place to search, prove and report across all of them. Your existing system stays authoritative, and the connection is read-only by design.

  • Machine evidence: every washer-disinfector and steriliser cycle, captured automatically.
  • Maintenance and test records that prove the estate is fit to process.
  • A protected copy of tray traceability data that is never deleted.
  • Quality investigations when something goes wrong.
  • Management information drawn from all of the above.
What changes

The difference on an ordinary Tuesday

Not the feature list. What a department stops having to do once the record keeps itself.

  • Proving a cycle happened means finding the printout.The answer to "prove it" is a search, not a week in a filing room.
  • Evidence exists only if somebody remembered to file it.Cycle data arrives from the machine automatically, whether anyone remembers or not.
  • A mistake in a logbook becomes an argument about what it says.A correction is a new signed entry, and the original stays exactly as it was.
  • An at-risk lookback means pulling records and hoping they are complete.It is a query against a protected copy that was never allowed to be deleted.
How it works

From the machine to the audit, without the paper

Follow one cycle through the platform, from the moment the machine finishes to the moment someone has to prove it happened.

BridgePoint4Machine monitoringMachinesDashboardHealthActivityCyclesMaintenanceAsset RegisterPPM ScheduleWeekly Tests
Example SSDDemonstration data
MachinesCycle activity across the estate
Washer 01Washer-disinfectorPass
Washer 02Washer-disinfectorPass
Endo washer 01Endoscope washerPass
Steriliser 01Steam steriliserPass
Steriliser 02Steam steriliserPass
Steriliser 03Low temperaturePass
Cycle #1048Washer 01 · instruments programme · auto-released
TemperaturePressureConductivity
Hold temperatureWithin tolerance
ResultPass
Source fileRetained and downloadable
Weekly testsRecord a Bowie-Dick test against its cycle and e-sign it
Machine result · PassParametric · PassIndicator reading entered by user
DateMachineIndicatorSigned
18 NovSteriliser 01PassAuthorised user
17 NovSteriliser 02PassAuthorised user
16 NovSteriliser 03PassAuthorised user
RecordImmutable and fully audited
Machines dashboardUtilisation and cycle activity across machines
452cycles, 30 days
13machines reporting
98%pass rate
0tests overdue
Step 01

Every machine, in one place

Washer-disinfectors, endoscope washers and sterilisers all report into the same view, with their last cycle, last programme and last result visible without opening anything.

Step 02

And the estate answers for itself

Utilisation, pass rates and cycle activity across every machine, updated as the integrations run. The answer to "prove it" becomes a search rather than a week in a filing room.

Step 03

The cycle captured in full

Every parameter the machine emits is kept, including the complete temperature, pressure and conductivity trace. The original source file stays downloadable, and the cycle report exports as a print-ready PDF.

Step 04

Weekly tests, signed and immutable

BridgePoint⁴ pulls the supporting evidence from the test cycle itself. The user enters the indicator reading, which remains the legal pass, and e-signs it. Mistakes are corrected by recording a new test, never by editing history.

Modules

Switch on only what you need

No two departments need the same mix. A small unit might run two modules; a multi-site operation might want most of them. Each organisation gets its own isolated workspace, and you pay for and see only what is switched on. It runs in the browser, so there is nothing for your users to install.

01

Machines

Automatic cycle capture straight from the machine, release and reject sign-off, machine health scoring and utilisation.

02

Maintenance & Asset Care

Asset register, planned maintenance, maintenance logs and weekly tests including Bowie-Dick and the full A–F set.

03

Integration Hub

Read-only connectors, scheduled pulls, file import and a read-only API. Core to every workspace, not a paid extra.

04

Traceability Archive

An independent, protected copy of tray traceability data. Find a tray across every source, and run an at-risk lookback in seconds.

05

BI

Estate, facility, utilisation and archive health dashboards, updated automatically as the integrations run.

06

Quality

Complaints and Corrective & Preventive Actions, raised against a specific tray with its full handling history attached.

07

Trolley Tracking

Trolley locations read from the CCTV a department already has, using a QR code on each trolley. No images are ever stored: the code is read and the frame discarded at once.

08

Finance

Interfacing with finance systems such as Xero and Sage, built on the same Integration Hub.

Where the record comes from

Three layers between the work and the record

BridgePoint4 sits at the top of a stack. Something happens on the floor, the data crosses a network that has to be built to let it, and only then does it become a record. That is true of a cycle, a tray, a weekly test or a corrective action alike. We build all three layers, which is why connecting a department is usually not a project on your side.

BridgePoint4→

One auditable record of what happened, captured as the work happens.

The network→

Segmented and monitored, with machines and cameras isolated from the internet.

The department→

Rooms, machines and workflow, designed and built to validate first time.

The dashed lines follow data from the floor, through the network, to the record it ends up in. A cycle takes that route, and so does a tray scan, a weekly test or a maintenance job. Every layer it passes through is designed, built and run by the same team, so there is no join where it can stop being anybody's problem.
Integration

Works with the systems you already run

There is more than one way in, and all of them are read-only. Most departments are connected without a project on their side.

Track and traceREST connectorSpreadsheetsCSV and Excel importMachinescycle file ingestOther systemsscheduled pullIntegration Hubread-only by designcore, always onBridgePoint4one place to search
The Hub reads from the systems a department already runs, whichever way in suits them. Your system stays authoritative, BridgePoint4 cannot write back into it, and there is no project required on your side.Select a source to see what is involved.

Track and traceREST connector

The instrument tracking system a department already runs.

How it connects
A connector that asks for data over the system's own interface on a schedule, rather than reading its database directly.
What you have to do
An account with read access. Nothing changes in the system itself, and it stays the authoritative record.

SpreadsheetsCSV and Excel import

The logs that live in a shared folder because nothing else held them.

How it connects
Import, with the file validated on the way in so a bad column is reported rather than silently stored.
What you have to do
Send us a file. This is usually how a department starts, before any connector exists.

Machinescycle file ingest

Washer-disinfectors, endoscope washers and sterilisers.

How it connects
An on-site service collects the cycle files the machines already produce and sends them out. Outbound only, with nothing exposed to the internet.
What you have to do
The machines stay on their own isolated network. They are never reachable from outside, and nothing is installed on them.

Other systemsscheduled pull

Anything else holding evidence: asset registers, maintenance logs, finance.

How it connects
A scheduled read against whatever interface it offers, or a file drop if it offers none.
What you have to do
A conversation about what it can expose. If the answer is nothing, a file drop still works.
Security & data protection

Built to pass an NHS information governance review

Designed to align with ISO 27001, Cyber Essentials Plus, the NHS DSPT and UK GDPR, in the HTM 01-01 decontamination domain.

Tamper-evident by design

Every event is recorded and chained to the one before it. Cycle decisions, weekly tests and the quarantine ledger cannot be edited or deleted, only superseded.

Isolated per organisation

Tenant isolation is enforced in the database itself, so it holds even if application code were to make a mistake. Every module is off until enabled.

Strong sign-in

Microsoft Entra ID single sign-on, passkeys, authenticator-app two-step verification and organisation-wide MFA enforcement.

UK-hosted on Microsoft Azure

Encrypted in transit and at rest. GM61 acts as processor and the customer remains controller. Patient-identifiable data is screened out of imports.

Questions

What people ask before they book a demo

Do we have to replace our track and trace system?

No. BridgePoint4 surrounds it rather than replacing it. The connection is read-only by design, your existing system stays the authoritative record, and BridgePoint4 cannot write back into it. What it adds is the machine and maintenance evidence those systems do not hold, and one place to search across all of it.

Can someone edit or delete a record?

No. Every event is chained to the one before it, so cycle decisions, weekly tests and the quarantine ledger can be superseded but never overwritten. A correction is recorded as a new entry and the original stays, unchanged and signed. There is a demonstration of exactly that further up this page: you can try to alter a record and watch the chain stop verifying.

Where is our data held, and who controls it?

UK-hosted on Microsoft Azure, encrypted in transit and at rest. GM61 acts as processor and you remain the controller. Patient-identifiable data is screened out of imports rather than relied on being absent.

Who inside our organisation can see what?

Tenant isolation is enforced in the database itself, so it holds even if application code were to make a mistake, and every module is off until you enable it. Sign-in is Microsoft Entra ID single sign-on, passkeys or authenticator-app two-step verification, with MFA enforceable across the organisation.

What do we actually have to do to connect a department?

Usually far less than people expect. A read-only connector, a scheduled pull or a file import covers most systems, and machine cycles come through an on-site service that is outbound only with nothing exposed to the internet. Departments frequently start with a spreadsheet import before any connector exists. Select a source on the integration diagram above and it will tell you what is involved for that one.

Next step

See BridgePoint4 on your own machines

We'll walk through how cycle capture works with the washers and sterilisers you actually run, and what the records look like at audit.