- BLOCKING Pressure test inspection became overdue 60 days ago.
- BLOCKING 1 open blocking fault report. The chamber must not be used until the fault has been repaired and the return to service recorded.
- ADVISORY 5 runs awaiting signature, the oldest 13 days.
Hyperbaric chamber operations logging and compliance
A record that withstands inspection.
Autobaric records every pressurisation, tracks the due dates of inspections and qualifications, and produces the regulatory record from the same entry. One form goes missing; one absent calibration certificate stops the chamber.
30 days of the Pro tier without a card. After that one chamber stays free.
The first view tells you what stops a chamber today
No activity feed and no welcome message. Every chamber, the most urgent first, and the finding in the language an inspector would write it in.
1chamber with a finding
2chambers require action
3chambers in order
- ADVISORY Calibration inspection falls due in 20 days.
- FOR INFORMATION The operations supervisor's qualification expires in 43 days.
An example. Severity is carried by shape and word as well, not by colour alone.
Four things a paper form leaves open
These are not gaps in recording. They are gaps in what it is possible to record on a form at all.
The chamber is not identified
The form says chamber 2. The register holds a serial number, a year of manufacture and a registration number. Putting them together is left to the inspector — and to their interpretation.
Inspection history sits in a different folder from use
The calibration certificate and the pressurisation log do not refer to each other. The question was the gauge calibrated during this run has no answer, even though both papers are in the cabinet.
An incident is free text
Small leak in the hatch cannot be searched, counted or reported to an authority. A recurring fault looks like an isolated one, because nothing counts the repetitions.
Nobody knows what may be deleted
The retention period depends on the type of data and on the country. Without that, everything is kept forever — or deleted at a point where it should not have been.
A run passes through four stages
The numbering is not decoration: it is the run's state machine. A stage cannot be skipped, and the previous one does not reopen.
-
01
Record
The run, the crew, the pressure profile and the checklists. The application installs on the device and opens without a network, and the run, the crew, the pressure profile and the checklists queue on the device and are sent when the connection returns. The chamber may be in a basement or on a vessel. An incident report requires a connection — without a network the application says so, and does not claim to have saved it.
-
02
Check
The qualification gate prevents a duty role from being assigned to a person who does not hold a valid qualification for it — and warns 90, 30 and 7 days before expiry. The due date is visible before the run, not at the inspection.
-
03
Sign
A signed run is locked. A correction is a separate entry and not a change: the original content and the original time remain visible. This is what German patient law requires of record-keeping, and it is a good rule elsewhere too.
-
04
Attest
The inspection bundle contains the records, the inspection history, the incident reports, the qualification register and the maintenance history — each as PDF/A-3B with canonical JSON attached — together with the audit chain and the specification of verification. The archival format was chosen with 120 years of retention in mind, not with today's ability to open it.
Audit chain
A record cannot be altered afterwards — not by us either
Every event receives a hash that is computed in a database trigger and binds the event to the previous one. The application cannot bypass it even by failing, because it does not compute the hash.
The numbering is gapless per chamber. A hole in the sequence is itself a finding, so none may arise even when an entry is cancelled. A Merkle root is computed from each day's events and anchored separately.
The export bundle contains the complete specification of verification: the structure of the hashes at byte level, the chaining rule, the Merkle tree and the relation of the timestamp to the root. It can be implemented in any language in a few dozen lines — and the result depends neither on us nor on our tools.
We also have a ready-made verification program, and it is available on request. It has not been published, and that is precisely why verification does not rest on it. If a record has been altered, the chain breaks at that hash, and the specification tells you where to see it.
#1041
run.signed
prev 3f9c…a071
this 8d2e…5cc4
#1042
inspection.recorded
prev 8d2e…5cc4
this 1b77…9e30
#1043
chamber.window_replaced
prev 1b77…9e30
this c50a…41f8
Merkle root 2026-08-24
e7a2…08bd
Changing one event changes every hash that follows it. It cannot be corrected back without rewriting the whole chain — and that is exactly what has been anchored.
The same entry, another country's record
Jurisdiction is data in the product, not a branch in the code: the unit of pressure, the required duty roles, inspection intervals, retention periods and the form template are all settings. A new country is specification work, not a new version.
| Country | Basis | Unit | Status |
|---|---|---|---|
| FI Finland | painelaitelaki 1144/2016, Tukes | msw | in production |
| DE Germany | MPBetreibV, DGUV Regel 9/2023 | bar | specified |
| GB United Kingdom | PSSR 2000, DWR 1997 | msw | specified |
There can be more than one profile within a country, because regulation differs according to how the chamber is used: Finland and Germany each have both a medical and a non-medical profile. The former also expects the signature of clinical staff on a run; the latter does not require a healthcare professional in the crew and does not recognise a patient record. The basis in both is the same pressure equipment regulation, and the choice is made at registration. Crew requirements also depend on the chamber: an inside attendant is not expected of a monoplace chamber that nobody else fits into.
A device's record is a different matter from a country's. Checklists, the maintenance interval and the displayed unit of pressure follow the device: the gauges of a BioBarica chamber read ATA in Finland too, and its checklists are the network's own. A chamber therefore follows the law of its own country and the record of its own manufacturer — and owes the inspections of both.
No profile has yet been through the review of a local expert, and the product says so itself: beta is written next to every country wherever the country is chosen. Finland is the one whose forms the product was built from and the only one in production use; the others are specified from public sources. We say this before you buy, not after.
The price comes from the chamber, because the obligation does too
No per-user fees. All staff sign in on every tier, including the free one — a run left unrecorded costs more than a licence.
Pro wellness and diving
49 €
per chamber per month
- All jurisdiction records
- Signatures and locking
- Inspection and maintenance module
- Audit chain and export bundle
- Device data ingest
- Unlimited chambers
Clinical
99 €
per chamber per month
- Patient tier and consent
- Recording of the intended purpose
- SSO and a data processing agreement
Not on sale yet. The clinical tier is built on separate infrastructure, and it is not sold before that exists.
Enterprise
By quotation
chains and device manufacturers
- Multi-site and SAML
- Own region or instance
- API and audit support
Not on sale yet.
Scope
Autobaric is not a medical device
It records what happened, shows the deviation from what was planned, and reminds of a due date.
- records the actual pressure profile
- shows the deviation from the planned table
- reminds of an expiring inspection
- does not calculate a decompression schedule
- does not recommend a treatment
- does not control the chamber's valves
The boundary is written into the intended-purpose document, and a build is rejected automatically if the code breaks it. Drifting across the boundary one feature at a time is, in this field, the commonest way of ending up regulated by accident.
Data protection and location
What we can demonstrate
- Server in Nuremberg, Germany. Records and backups stay in the EU, and the email delivery servers are in the EU too, in France. The provider is a Swiss company; the details are in the privacy policy.
- Customers are separated at the database level. Row-level policies, and the application's database role has no bypass privilege — the isolation does not rest on the code remembering to filter.
- No third-party tracking. No analytics, no external fonts. This page makes no request anywhere else; you can check that in your browser's network tab.
- The right to erasure and the duty to retain are settled separately. When erasure is warranted, it is carried out so that the audit chain stays intact and verifiable.
- No ISO 27001 or SOC 2 certificate. We say it here, because the first procurement form asks it in any case.
Record your first run today
Registering takes a minute and does not require a card. The chamber, the crew and the first pressurisation fit in the same sitting.