Solutions Nubiss Clinical
Nubiss Clinical
Two jobs at once: run the treatment unit day to day, and record what happened in a structure you can still analyse in three years.
For medical directors, unit leads, clinic operators — and clinicians who want their follow-up data to be usable.
Each step writes into the same structured record, kept in a change history.
The problem
Most units already document carefully — but for justifying the visit, not for answering a question later. The fix is deciding the structure before the work starts, and keeping to it.
Sessions written down as they happen, filed by date, and readable only by whoever kept the folder.
Free text and personal shorthand mean two colleagues describe the same treatment differently.
Nothing lines up across patients, so a year of careful work answers no question at the end of it.
With Nubiss
The same work, recorded once into a structure that still answers questions three years later.
Each session records against a frozen copy of that day's protocol, with the safety check mandatory.
Nurse and doctor work from the same structured history rather than reconstructing it from notes.
Units recording the same fields the same way can compare outcomes instead of comparing anecdotes.
What it does
The scheduling and the science read from the same records — which is why the evidence half costs no extra effort.
Running the unit
Sessions booked against a chamber and a clinician, plus patient-initiated booking requests.
Chamber and cylinder records, with a change log for every cylinder swap and a warning as a cylinder approaches its change threshold.
Company, clinic and chamber form a hierarchy; each role sees only its own organisation's data.
A referral intake wizard, and referral tracking through sent, received, in treatment and completed. Clinic profiles for discovery are enabled per company.
A guardian manages a linked account for a child and signs for them, recorded as such. Staff can issue a patient a single-use sign-on link by SMS code or email.
Email and SMS with quiet hours — off by default, enabled per company.
Building the evidence
Pressure in bar, oxygen fraction, sessions, frequency — the database refuses an incomplete protocol.
Health declarations with risk flags, vitals, ICD-10 coded diagnoses and an explicit fitness decision.
EQ-5D with country value sets, FSS, EPIC-26, VAS pain and an LRTI symptom check-in, recorded before and after treatment.
Required forms become dated tasks; a treatment gap automatically raises the assessments to close it.
Old and new values with user and timestamp, plus a hash-chained log where tampering shows.
The clinical workflow
The order the clinical work already happens in — the software follows it rather than asking for it a second time.
From your unit's library, or a shared catalogue as a starting point.
Treatment reason with ICD-10 code, health declaration, baseline measures.
Against a frozen copy of that day's protocol, with a mandatory safety check.
Repeat measures fall due automatically and stay open as tasks until done.
One timeline: sessions, protocol changes, outcome scores, unit activity by indication.
From referral to recovery
A referral is not a message into the dark. The referring doctor and the treating clinic work on one record, and the referral carries a status the whole way through.
With an ICD-10-coded indication; codes are looked up against the WHO ICD API.
Health declaration with risk flags and an explicit fitness decision before treatment starts.
Sessions against the day's protocol, readings and outcome scores as they happen.
The referral moves through sent, received, in treatment and completed — the referrer sees where each one stands.
Worth being clear about
Beyond hyperbaric oxygen
A configurable registry lets a unit keep every therapy it delivers in one place, with each clinic enabling the types it runs. How deeply each one is modelled differs — so each carries its real status.
Typed clinical fields — pressure in bar, oxygen fraction, sessions, frequency — with database-level validation.
Typed dose fields — FiO2, simulated altitude, session type, work and recovery intervals, cycles — enforced by a database constraint. Described here as a protocol the software records; Nubiss makes no claim about what the therapy achieves.
A seeded registry type; its parameters are schema-defined per type rather than purpose-built clinical fields. Listed without any claim of clinical effect.
Any further therapy a unit runs can be registered, with free-form parameters and the same mandatory per-session safety check.
Each clinic switches on exactly the therapy types it delivers.
Whatever the type, a session cannot be recorded without its per-session safety check.
Worth being clear about
Getting the data out
Nubiss Clinical exposes its record as FHIR R4, so an analysis environment or a hospital system can read it in a standard shape rather than through a bespoke extract.
Eight resource types are served
Vital signs are LOINC-coded, diagnoses carry their ICD-10 codes, and organisations and chambers appear as Organization and Location.
The shape of it, precisely
One unit, one team
Doctor, nurse and reception act on the same record — and the software keeps track of who has seen what.
Health declarations arrive with risk flags, and the doctor records an explicit fitness decision before a session can go ahead.
Session notes from the doctor wait for the nurse until they are acknowledged — the handoff is a recorded step, not a hallway conversation.
A doctor assigned to several clinics sees their patients and today's capacity in one place, still scoped to what each role may see.
Governance
Versioned, role-targeted document templates. A signature records signer, method, time and a verification hash, with a checkable certificate.
Data is scoped by company and clinic. A request for another organisation's record returns not-found — never confirming the record exists.
National identifiers and insurance numbers are encrypted in the database, searchable only through a separate hashed value.
The full account — including what is not yet documented — is on the security and compliance page.
We will walk through your protocols and follow-up model and show you how they map onto Nubiss Clinical. Please do not include any patient information in your message.
