Photobiomodulation papers are judged on whether the dose is documented: wavelength, irradiance, time, area. Capture holds those parameters per session beside the outcomes, keeps the sham unit masked, and syncs optional Oura sleep data. Build it free in the sandbox.
Free sandbox · No credit card · 21 CFR Part 11 aligned
Device and dose
Device unit code
LTUNITCoded; arm not revealed to blinded roles
U-0417Wavelength setting
LTWAVETreatment area
LTAREADistance from skin
LTDISTExposure time
LTDURFluence (calculated from protocol irradiance)
LTFLUTolerability
Skin warmth, redness or eye discomfort
LTAEWhat a photobiomodulation study needs from its data system
The study design
Photobiomodulation (PBM), often marketed as red light or low-level light therapy, applies red or near-infrared light to tissue, and studies range from oral mucositis and musculoskeletal pain to skin and cognitive outcomes. Across that literature, one criticism recurs: papers that do not report the parameters cannot be compared or pooled. Commonly recommended items are the wavelength, the irradiance (power per unit area), the fluence or energy density (irradiance multiplied by time), the treatment area, any pulsing, and the timing and number of sessions. Dosimetry reporting recommendations from the laser-therapy community exist, and you should check the current version against your own protocol.
That literature shapes the build. Do not bury dose in a notes field. Create a session form with a dropdown or numeric field for each parameter, store the planned values in the protocol, and record the delivered values per session. A calculated field can show fluence from irradiance and time read-only at entry, like Capture's other derived fields, so a mis-keyed duration is visible immediately. Where the device itself sets the output, record the programme or setting code and keep the physical specification in the device documentation.
Studies range from supervised clinic sessions to home-use panels used daily. In a home design, the participant logs each session on their phone as a short ePRO diary, and staff review the adherence by site. See digital patient diary software for the diary model and epro compliance reminders by SMS and email for reminder structure. Treat self-reported home sessions as a different quality of exposure data than a staff-run clinic session, and record which kind each row is.
Blinding
A sham light must look and feel like the active one. Journal correspondence on a light-therapy trial raised exactly this point: a sham mode that reduces output should reduce it uniformly, and the team should be able to show that the reduced output is biologically inert. That is a device and biology question for your protocol, not something software can settle. The data-system half is to keep the arm out of sight. Randomization is held in Capture and blinded roles never receive treatment-arm values, enforced by masked database views and row-level security.
Check the practical leaks. If the unit serial number or the dial setting reveals the arm, restrict that field to the unblinded device manager and give everyone else a coded unit. If a participant can see a heat difference, a blinding-assessment question at the end of the course (which arm do you think you received) is a useful field to collect from participants and raters. The wider logic is described in blinded and unblinded role management. Related sham-controlled device designs are described in EDC for PEMF and magnetic field therapy studies and EDC for tDCS and TMS neuromodulation studies.
Participants
48
Sessions planned this month
576
Logged
511
Missing diary entries
65
98%
88%
80%
Protocol to build
| Need | What the data looks like | Where it lives in Capture |
|---|---|---|
| Dose per session | Wavelength setting, irradiance, time, calculated fluence, area, distance | Session eCRF form with a calculated read-only fluence field |
| Allocation | Active or sham, stratification factors | Randomization in the system; masked views for blinded roles |
| Home session logs | Date, duration, area, problems | ePRO diary opened from a phone link with reminders |
| Outcomes | Pain, sleep, skin or function scores | ePRO tasks and site forms, e.g. VAS pain scale structure |
| Concomitant treatment | Photosensitizing medicines, other therapies | Concomitant medications form |
| Safety | Skin, eye and heat events | Adverse event form |
| Sleep context | Sleep and recovery data from the participant's own account | Optional native Oura sync, enabled per study |
Capture does not connect to light panels or read device output. Session values are entered by staff or the participant.
Build the session form with a calculated fluence field in the free sandbox, run practice participants through clinic and home sessions, and open the export. No credit card.
Regulatory and wearables
Many light devices on the consumer market are sold as general wellness products, while some are cleared for narrow, device-specific indications. Which category your device is in changes what regulators and ethics boards expect, whether an investigational device application is needed, and what claims you can make. Check the device label and current regulator guidance; this page does not state any device's status. The broader device pathway is described in EDC for medical device clinical trials and early feasibility and pivotal device study EDC.
Safety is usually low-risk, and still needs structure. Eye protection, skin warmth or redness, headaches and interactions with photosensitizing medicines are commonly considered. Capture the protocol-defined events on the session form and the standard adverse event form, and record eye-protection use as a field if the protocol requires it. Every change carries a field-level audit trail.
If sleep is an outcome or an explanatory variable, the study team can enable the native Oura connection per study, mark it required, and have each participant connect their own account; data syncs automatically with a visible last-sync time. It is context for your analysis. No other wearable is claimed. See EDC for wearable device studies and the wearable data sharing consent template.
Before first participant
Wavelength, irradiance, time, fluence, area, pulse settings and schedule written in the protocol.
What the sham output is and how its inertness is justified.
Device serials coded so they do not reveal the arm.
Each session row records who delivered it.
Checked against current regulator guidance for your intended use.
Eye protection and event handling documented.
Yes. Build them as typed fields on a session form, with a calculated read-only field for fluence if your protocol defines it from irradiance and time.
No. Capture does not read device output or connect to light panels. Parameters are entered by staff or by the participant.
Randomization is held in the system and blinded roles never receive treatment-arm values. Use coded unit identifiers and restrict the true unit field to unblinded roles.
Yes. Home sessions can be a short ePRO diary opened from a phone link, with reminders. No app install is needed.
The study team can enable the native Oura connection per study and participants connect their own account. No other device is claimed.
Keep exploring
EDC for PEMF and magnetic field therapy
Sham-controlled home device sessions.
EDC for tDCS and TMS studies
Neuromodulation sham designs.
EDC for wearable device studies
Optional Oura sync.
EDC for medical device clinical trials
Device study pathway.
Digital patient diary software
Session diaries on the phone.
Pricing
Plans for live studies.
Free sandbox with every feature. No credit card, and you pay only when you go live with real participants.