Solutions Nubiss Clinical HBOT

Nubiss Clinical for HBOT

Structure HBOT protocols. Follow outcomes across every treatment journey.

Capture protocols, observations and longitudinal outcomes in one consistent format — so follow-up is responsible and results are comparable across units.

HBOT protocol · as defined Synthetic example
Pressure 2.4 bar required
Oxygen 100% FiO₂ required
Sessions 40 · 5 per week schedule
Breaks 2 air breaks · 5 min schedule
Safety Check required per session mandatory
Reactions Coded list · countable structured
Follow-up Day 40 · Day 90 outcome

An HBOT protocol without a pressure is rejected by the database, not by a reminder.

The shape of an HBOT protocol as the software holds it. Illustration of the data model with synthetic values.

The problem

Hyperbaric medicine has an evidence problem it can fix itself.

Units accumulate real clinical experience every day — recorded in ways that cannot be pooled. Nubiss makes what your unit already does legible.

Illustration: a clinician surrounded by paper binders and loose session logs
01 Every session in a binder.

Chamber logs, safety checks and outcome scores kept on paper, in the order they happened to arrive.

Illustration: two staff members at different chambers, each recording notes their own way
02 Each clinician records it their own way.

Pressure, session count and indication described in prose, differently by each clinician on the rota.

Illustration: a doctor puzzling over disconnected charts and papers that do not line up
03 Outcomes nobody can compare.

Real clinical experience accumulates every day, in a form that cannot be pooled or examined later.

With Nubiss

The same work, made legible.

Nothing about the treatment changes — only the form the record takes when the session is over.

Illustration: a nurse recording a chamber session into structured fields on a tablet
04 Sessions captured at the chamber, structured.

Pressure, oxygen fraction, breaks and the safety check captured at the chamber as defined fields.

Illustration: a nurse and a doctor reviewing one shared, structured patient record
05 One record, reviewed together.

One patient timeline: protocol changes, sessions delivered and outcome scores in a single history.

Illustration: clinicians at several units connected around one shared dataset
06 Units connected around comparable data.

The same instruments, recorded the same way, so units can put their results side by side.

The HBOT workflow

Five steps, in the order the clinical work happens.

Nothing here asks for the work to be described twice — each step writes into the structure the next one reads from.

  1. Define or select the HBOT protocol

    Pressure, oxygen, sessions, breaks — incomplete protocols are rejected.

  2. Capture indication and baseline

    ICD-10 indication, declaration and baseline scores first.

  3. Record each chamber session

    Each session freezes that day's protocol; safety check required.

  4. Record safety observations

    Adverse reactions come from a coded list, so they count.

  5. Collect follow-up and review

    Measures fall due as tasks; one timeline shows it all.

What your patients see

The patient side of the same record.

Your patients work in the same system your unit does — which is why nothing they submit has to be chased, retyped or re-asked.

  1. Find the clinic

    Clinic profiles for discovery, where a company has enabled them.

  2. Register

    Their own account — or staff issue a single-use sign-on link.

  3. Declare and be assessed

    Health declaration in; the doctor records the fitness decision.

  4. Sign consent electronically

    Signer, method, time and a verification hash on every document.

  5. Request bookings

    Patients request sessions; the protocol itself is the clinic's decision.

  6. Follow their progress

    Outcome and progress charts in the patient's own account.

What happens to what they fill in.

Nothing a patient submits goes into a drawer. A declaration lands in front of the care team with its risk flags, the doctor's decision is recorded against it, and the result is visible in the record the patient sees — the loop closes in the software, not in someone's inbox.

Messages between patient and care team stay inside the platform and are stored encrypted.

One declaration · submission to decision Synthetic example
09:12 Health declaration submitted · P-104205 patient
09:12 Risk flag raised · answer 7 flagged
10:41 Fitness decision recorded · approved doctor
10:41 Result visible in the patient record record

Outcome measurement

Instruments that mean the same thing everywhere.

Established, published instruments — not Nubiss-invented scores — which is what makes results comparable between units.

EQ-5D

Quality of life in five dimensions plus VAS, with country value sets and a computed index.

FSS

The Fatigue Severity Scale, where fatigue is the dominant complaint.

EPIC-26

Six-domain scoring, relevant to late radiation tissue injury.

VAS pain

Recorded with its context, so pre- and post-treatment scores are never confused.

Clinical indications

Classified by evidence, not by enthusiasm.

Nubiss is software — it supports evaluation and outcome monitoring rather than establishing that HBOT works for any condition. The classification reflects European consensus recommendations, reproduced from Nubiss's own clinical one-pager.

Before publication

The exact citation and revision date for the consensus recommendations below must be confirmed against the current published source, and the section given a content review date, before this page goes live. Recorded in the claims register as an outstanding item.

Accepted indications, by strength of recommendation and level of evidence.
Evidence Condition
Strong agreement
Level B Late radiation tissue injury — cystitis and proctitis
Level B Osteoradionecrosis of the mandible
Level B Carbon monoxide poisoning
Level B Open fractures with crush injury; prevention of osteoradionecrosis after dental extraction
Level B Sudden sensorineural hearing loss
Level C Decompression illness; gas embolism
Level C Anaerobic or mixed bacterial infections
Agreement
Level B Diabetic foot lesions
Level B Femoral head necrosis
Level C Crush injury without fracture; compromised skin grafts and musculocutaneous flaps
Level C Central retinal artery occlusion; refractory chronic osteomyelitis
Level C Second-degree burns over 20% of body surface area; ischaemic ulcers; surgery and implant in irradiated tissue (preventive)
Level C Osteoradionecrosis other than mandible; radiation-induced soft tissue lesions
Level C Pneumatosis cystoides intestinalis; stage IV neuroblastoma
Selected patients only. Recommended for carefully selected patients rather than as a general indication. These are areas where outcome monitoring matters most.
Evidence Condition
Level C Brain injury — acute and chronic traumatic brain injury, chronic stroke, post-anoxic encephalopathy
Level C Radiation-induced lesions of the larynx and of the central nervous system
Level C Reperfusion syndrome after vascular procedure; limb replantation
Level C Selected non-healing wounds secondary to systemic processes
Level C Sickle cell disease; interstitial cystitis

What we do not claim

  • Nubiss makes no claim that hyperbaric oxygen therapy is effective, safe or appropriate for any particular patient. That is a clinical judgement for the treating physician.
  • Applications outside the tables above — including oncology, post-viral conditions, immune modulation and stem cell mobilisation — are research areas, not established indications, and are not presented here as benefits.
  • Nubiss is software for recording and following up treatment. It does not diagnose, does not recommend a therapy, and does not replace clinical judgement.

Working across units

The value grows with every unit recording the same way.

One unit gets immediate value on its own patients. Several units recording identically produce something none of them could alone — comparable evidence.

Being straight about the mechanics

  • Data is scoped to your organisation — nothing crosses to another company's records inside the software.
  • There is no automated pooling, federation or cross-unit benchmarking feature today; collaboration is arranged and governed between the parties.
  • There is no bulk data export to CSV or Excel. Any sharing arrangement needs to account for that.

Questions

Common questions from HBOT units

Every answer here is the honest one — including the things the product does not do yet.

Is this an electronic health record?

No. Nubiss Clinical covers the treatment pathway — protocols, sessions, assessments, outcomes — and the operations around it. It is not a general-purpose EHR.

Why is pressure recorded in bar rather than ATA?

Because that is the unit the software stores. The conversion from atmospheres absolute is direct, but the field itself is bar and the interface says so.

Can we use our own protocols?

Yes. Protocols belong to your organisation; a shared catalogue is available as a starting point.

What happens when we change a protocol mid-course?

Each session keeps a frozen copy of the protocol as it was that day, and the change is logged with who made it and when. A later change never silently rewrites earlier sessions.

Can we get our data out?

Not in bulk today. There is no CSV or Excel export; PDF output exists for electronically signed documents. If export is essential to you, tell us — it is on the roadmap rather than in the product.

Do you support languages other than English?

The application ships German, Spanish, Swedish, French, Polish and Czech translations, and clinical content such as indication lists is language-specific.

See it against your own protocols.

Tell us the protocols you run and the outcomes you follow, and we will show you how they map onto the software. Please do not include any patient information in your message.