Study type · Hyperbaric oxygenUpdated October 12, 2026

EDC for hyperbaric oxygen therapy studies, from chamber log to symptom score

A hyperbaric study is a long run of chamber sessions, each with a pressure, a duration, a gas and a list of small things that can go wrong. Capture records every session next to the outcome scales and the safety events, keeps the sham arm masked, and exports a clean dataset. Build it free in the sandbox.

  • Session-by-session chamber log
  • Sham arms kept blinded
  • Ear and pressure events on file

Free sandbox · No credit card · 21 CFR Part 11 aligned

Hyperbaric session record (demo data)
Subject 001-0014 · Session 17 of 40 · Chamber BDraft entry

Session

Session date

HBSTDT
2026-03-12

Chamber

HBCHAM
Chamber B

Programme code

HBPROG

Code only; the arm is not shown to blinded roles

P1

Time at pressure

HBDUR
90min

Session completed as planned

HBCOMP
YesNo, stopped early

Tolerability

Ear or sinus discomfort

HBEAR
NoneMildModerateSevere

Mild: add to AE log if the protocol requires it

Claustrophobia or anxiety in chamber

HBANX
NoYes
Demo form only. Pressure, gas and session count follow your own protocol.

What a hyperbaric study needs from its data system

  • A session is the unit of exposure: pressure, time at pressure, gas and completion are recorded per visit, so dose delivered can be compared with dose planned.
  • A sham that has to stay credible: sham designs depend on nobody who handles the data being able to tell which arm a participant is in.
  • Barotrauma and tolerability events on a short leash: ear and sinus problems, claustrophobia and early terminations are common enough to need their own fields.
  • Outcomes on a different clock: symptom scales, cognitive tests or wound measures are taken at baseline, mid-course and follow-up, often at home.
  • Staff who cover shifts: chamber operators and attendants change, so the record must show who ran each session.

The study design

What makes a hyperbaric oxygen trial different to capture

Hyperbaric oxygen therapy (HBOT) delivers oxygen at a pressure above normal atmospheric pressure in a sealed chamber, usually over a course of daily sessions. Published trials vary widely in how they define the dose: the pressure in atmospheres absolute (ATA), the time at pressure, the number of sessions and the gas breathed. Because the course is often long, a protocol can specify dozens of sessions over several weeks, and the participant is expected to attend nearly all of them. That makes the session record the spine of the dataset.

The obvious data-capture consequence is that exposure is a stream of rows, not a single dispensing event. Each session needs a date, a chamber, a protocol programme code, the time at pressure, whether it finished as planned, and who operated it. If sessions are logged as free text in a spreadsheet, the analysis of adherence and dose received becomes a clean-up project. In Capture, build the session as a repeating eCRF form with required fields and edit checks, so a missing duration or an impossible date raises an auto-query at entry.

Published sham-controlled hyperbaric trials have used air or low-oxygen mixes at a low pressure, with a simulated pressurization and depressurization so participants feel something happen. Whether a given sham is credible is a design and biology question for the protocol team. A recent volunteer study even tested whether the minimum workable pressure could blind people to a higher active exposure. Capture does not decide that for you. What it does is keep the allocation out of reach of anyone who should not see it, which is the data-system half of keeping the blind.

Blinding and sham

Keeping the sham arm masked in the data

Randomization and allocation are held in the system, and blinded roles never receive treatment-arm values, enforced by masked database views and row-level security rather than a hidden column. See blinded and unblinded role management for how roles are set, and clinical trial randomization software for allocation and stratification.

The practical leaks in hyperbaric studies are physical, not digital. A chamber operator has to set a pressure, so the operator is usually unblinded to the programme even if the participant and the outcome assessor are not. Build the operator log as a form that records a programme code and not the pressure in clear, restrict who can open it, and make the outcome assessments separate forms completed by a blinded role. Test the setup in the sandbox with a colleague playing the assessor, and look for any screen, filter or export that reveals the arm. The same logic applies to other sham devices; compare EDC for PEMF and magnetic field therapy studies and EDC for tDCS and TMS neuromodulation studies.

Demo HBOT course: sessions and assessments
AssessmentBaselineWk 1Wk 2Wk 4Wk 8 (end)Month 3
Chamber sessions (5 per week in this demo)SSSS
Symptom scale (participant)PPPP
Clinician assessment (blinded rater)
Ear and tolerability check
Concomitant medications review

S = session block, P = participant task, x = site form

Illustrative schedule. Course length, session count and visit dates follow your protocol.

Protocol to build

Hyperbaric study needs and where they live in Capture

NeedWhat the data looks likeWhere it lives in Capture
Session logDate, chamber, programme code, time at pressure, completed or stopped, operatorRepeating site eCRF form with required fields and edit checks
Allocation and shamActive or sham, stratification factorsRandomization held in the system; blinded roles never see arm values
Symptom outcomesPain, sleep, fatigue, mood or cognitive scores at set pointsePRO tasks from a phone link, plus site forms such as the numeric pain rating scale structure
TolerabilityEar and sinus events, anxiety, early terminationSession tolerability fields and the adverse event form
Safety reviewSerious events, relationship, outcomeSAE report form and adverse event reporting software
ScreeningEligibility, contraindication checks, medical historyEligibility screening and medical history forms
ConsentParticipant consent, any optional elementseConsent with on-screen signature and countersignature

Capture is a data capture system. It does not control or read the chamber, and it does not connect to chamber hardware.

Log forty practice sessions before you submit to ethics

Build the session form, the sham masking and the tolerability fields in the free sandbox and step a practice participant through a whole course. No credit card.

Build your HBOT study free

Safety monitoring

Barotrauma, tolerability and who decides what is an adverse event

Meta-analyses of randomized hyperbaric trials have reported more adverse effects with hyperbaric oxygen than with control, with ear discomfort or barotrauma the most frequent, claustrophobia the next, and the rate rising with higher pressure and longer courses. Exact rates differ between reviews and populations, so treat any number as a planning input to be confirmed against current literature, not a promise. The data-capture point is that mild, expected events happen at high frequency in a long course, and the protocol should say which of them are recorded as adverse events and which only as session tolerability notes.

Build both. A per-session tolerability field is fast for the chamber attendant to complete, and a protocol-defined threshold (for example, anything moderate or worse, or anything causing a missed session) can create an adverse event record using the standard adverse event form. Edit checks can raise a query when a session is marked stopped early but no reason or event is recorded. Pre-treatment checks that your protocol requires, such as ear examination or contraindication screening, belong on a physical exam form or the screening form, and the clinical decision to proceed with a session remains with the clinical team.

Every change carries a field-level audit trail with timestamp, user, old value, new value and reason, and the trail cannot be edited. That matters in long courses, where a corrected session duration weeks later has to be traceable. Query handling is described on the query management page.

Outcomes and wearables

Symptom scales, home measures and optional Oura data

Hyperbaric trials in neurological, wound-healing or wellness settings measure outcomes that do not need the chamber: pain, sleep, fatigue, mood, cognition or function. Participant-reported measures can run as ePRO tasks opened from a link in the phone browser, with reminders you set, so there is no app to install. See BYOD ePRO with no app download. Sleep structure is a common secondary outcome, and the structure of a sleep instrument is shown on the PSQI template page. Template pages show structure and scoring only, and you remain responsible for any instrument licence.

If sleep or recovery context matters, the study team can enable the native Oura connection per study, mark it required, and participants connect their own account; data then syncs with a last-sync time visible. It is wearable context for your analysis, not a clinical measurement of the chamber exposure, and no other device is claimed. A broader view of wearable designs is on EDC for wearable device studies, and a consent template for sharing device data is the wearable data sharing consent template.

Before first participant

Hyperbaric study readiness checklist

Dose definition

Pressure, time at pressure, gas, session count and allowed missed sessions written in the protocol.

Blinding plan

Who runs the chamber, who sees the programme, and who rates outcomes.

Sham description

What the sham is, and how participants are kept from guessing.

Adverse event rules

Which tolerability events become AE records, and who classifies them.

Contraindication screening

Entry checks documented on a screening form.

Device status

Regulatory status of the chamber for your use, checked against current regulator sources.

FAQ

Questions teams ask before they switch

Something not covered here? Ask us directly.

Can Capture log each hyperbaric session?

Yes. Build the session as a repeating eCRF form with date, chamber, programme code, time at pressure, completion status and operator. Edit checks raise auto-queries for missing or implausible values.

Does Capture connect to the chamber?

No. Capture does not read or control chamber hardware. Session values are entered by staff on the eCRF form.

How is a sham arm kept blinded?

Randomization is held in the system and blinded roles never receive treatment-arm values, enforced by masked database views and row-level security. Whether the sham itself is credible is a protocol question.

Can we record ear and sinus events?

Yes. Use a per-session tolerability field plus the adverse event form for events that meet your protocol threshold. Serious events follow the SAE workflow.

Is there a free way to test the build?

Yes. The sandbox includes every feature with no credit card and no time limit. You pay only when you go live; see the pricing page.

Start building your study free

Free sandbox with every feature. No credit card, and you pay only when you go live with real participants.

Build your HBOT study free