Study type · Photobiomodulation and red lightUpdated October 12, 2026

EDC for red light and photobiomodulation studies where the dose has to be reported

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.

  • Dose parameters per session
  • Sham device allocation masked
  • Home-use session diaries

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

Light session record (demo data)
Subject 003-0008 · Week 3 · Session 9Approved form

Device and dose

Device unit code

LTUNIT

Coded; arm not revealed to blinded roles

U-0417

Wavelength setting

LTWAVE
Setting 1

Treatment area

LTAREA
Knee

Distance from skin

LTDIST
10cm

Exposure time

LTDUR
10min

Fluence (calculated from protocol irradiance)

LTFLU
12.0 J/cm² Calculated

Tolerability

Skin warmth, redness or eye discomfort

LTAE
NoneWarmthRednessEye discomfort
Demo values only. Fluence equals irradiance times time; the numbers come from your own device specification and protocol.

What a photobiomodulation study needs from its data system

  • Dose is the whole argument: wavelength, irradiance, fluence, treatment area, pulse settings and timing are the parameters reviewers look for, so they need dedicated fields.
  • A sham that has to be inert: reduced-output or switched-off sham modes need documentation, and the unit identity must not reveal the arm.
  • Many short sessions: clinic or home-use schedules mean hundreds of small records per study.
  • Subjective, slow-moving outcomes: pain, skin, sleep, mood or function scores taken at set intervals, often by the participant.
  • Low-risk but real safety events: eye discomfort, skin heating or redness, photosensitizing medicines.

The study design

Why dose reporting drives the data model

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

Sham devices: masking the unit and documenting the sham

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.

Session adherence by site (demo data)

Participants

48

Sessions planned this month

576

Logged

511

Missing diary entries

65

Site A (clinic sessions)188/192

98%

Site B (home use)169/192

88%

Site C (home use)154/192

80%

Demo numbers only. Adherence thresholds come from your protocol.

Protocol to build

Photobiomodulation study needs and where they live in Capture

NeedWhat the data looks likeWhere it lives in Capture
Dose per sessionWavelength setting, irradiance, time, calculated fluence, area, distanceSession eCRF form with a calculated read-only fluence field
AllocationActive or sham, stratification factorsRandomization in the system; masked views for blinded roles
Home session logsDate, duration, area, problemsePRO diary opened from a phone link with reminders
OutcomesPain, sleep, skin or function scoresePRO tasks and site forms, e.g. VAS pain scale structure
Concomitant treatmentPhotosensitizing medicines, other therapiesConcomitant medications form
SafetySkin, eye and heat eventsAdverse event form
Sleep contextSleep and recovery data from the participant's own accountOptional 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.

Check that your dose fields survive a practice course

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.

Build your light-therapy study free

Regulatory and wearables

Device status, safety and optional Oura context

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

Photobiomodulation study readiness checklist

Dose parameters defined

Wavelength, irradiance, time, fluence, area, pulse settings and schedule written in the protocol.

Sham specified

What the sham output is and how its inertness is justified.

Unit coding

Device serials coded so they do not reveal the arm.

Home vs clinic flag

Each session row records who delivered it.

Device regulatory status

Checked against current regulator guidance for your intended use.

Eye safety plan

Eye protection and event handling documented.

FAQ

Questions teams ask before they switch

Something not covered here? Ask us directly.

Can we record wavelength, irradiance and fluence per session?

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.

Does Capture connect to the light device?

No. Capture does not read device output or connect to light panels. Parameters are entered by staff or by the participant.

How is the sham unit kept blind?

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.

Can participants log home sessions?

Yes. Home sessions can be a short ePRO diary opened from a phone link, with reminders. No app install is needed.

Can we add Oura sleep data?

The study team can enable the native Oura connection per study and participants connect their own account. No other device is claimed.

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 light-therapy study free