Thresholds for each ear at each frequency, the fitting you chose, how many hours the aid was worn and how the participant says it helps. Capture holds each as structured data with a field-level audit trail. Build free, no credit card.
Free sandbox · No credit card · 21 CFR Part 11 aligned
Air conduction threshold
500 Hz
AC500R1000 Hz
AC1000R2000 Hz
AC2000R4000 Hz
AC4000RQuery: outside the range set for this study (demo)
Masking used
MASKRWhat a hearing aid study needs from its data collection
The data
Pure-tone audiometry records the quietest tone a person hears at each tested frequency, in dB HL, separately for each ear and for air and bone conduction. Typical protocols test standard octave frequencies from low to high, and may add interoctave points; take the exact list from your protocol. Build one section per ear and one numeric field per frequency, with units in the field and a range check so impossible values raise a query at entry. Masking, test equipment and the test room are worth a field each, because they explain unexplained differences between sites.
Capture's built-in calculated fields cover a list of clinical formulas (BMI, BSA, MAP, eGFR, QTc, age from date of birth, time between two date-times), and a pure-tone average is not on it. Enter the average from the audiometer, or compute it in your statistics package from the exported frequency fields, and say which in the data management plan. Likewise, Capture does not claim an integration with audiometers or fitting software: results are entered by the audiologist, or transcribed from a printout, and every change keeps its audit trail with old value, new value and reason.
Speech tests need the same care. Record the test name, the listening condition (quiet, in noise, aided or unaided, sound field position), the list used and the score or signal-to-noise ratio. A condition field per row lets one repeating table hold aided, unaided and different-settings results for a participant, each row with its own audit trail. Pair it with a visit schedule so the exports are tidy: baseline, fitting, a few weeks of use and final outcome visits. For the generic issues of device studies, see EDC for medical device trials and how to run a medical device clinical study.
Fitting is where the intervention is delivered, so record it as data: device model and serial number, fitting formula or method, verification measurement (such as real-ear measurement) where the protocol requires it, programme settings and the date of each adjustment. Device data logging (for example average hours of use per day) is usually read from the fitting software at follow-up visits; enter the reported value and the date of the readout. Alternatively, ask participants to report wear time on a daily diary and compare. Hearing aids have also entered a new regulatory category in the US, with over-the-counter air-conduction aids for adults with perceived mild to moderate hearing loss (FDA final rule, effective October 2022); check which category and regulation your study device falls under before designing the protocol.
Where this fits
| Question | This page | Neighbouring page |
|---|---|---|
| What kind of study? | Audiology: thresholds, speech tests, fitting | Medical device trials in general |
| Where does the device data come from? | Fitting software readouts and wear-time diaries entered by staff or participants | Wearable device studies with connected consumer devices |
| What is the main outcome? | Threshold change, speech-in-noise score, self-reported benefit | PROMs for questionnaire-led studies |
| How is the blind kept? | Tester blind to settings where possible; participant often cannot be | Blinding guide |
| Who takes part? | Often older adults, sometimes with cognitive decline | LAR consent when capacity is in doubt |
Create the ear-by-frequency sections, set the range checks and enter a few test participants. Free sandbox, no credit card.
Outcomes and design
Self-reported benefit is often as important as the audiogram. Hearing questionnaires can be sent to the participant's phone through a secure link with reminders, completed at home between visits, and compared with the clinic result. Several widely used hearing questionnaires are copyrighted or carry conditions; Capture does not supply the instruments or verify licences, so the licence stays with your study documents and you should check the rights holder's terms before use. See ePRO for patient-reported outcome studies.
Blinding a hearing aid trial is rarely complete. The wearer knows whether the device is on. What can be blinded is the tester (who does not know which setting or device was used for a given test), the data analyst and sometimes the participant, in a crossover comparing two programmes that sound different but are not labelled. Capture's blinded roles never receive treatment-arm values, enforced by masked database views and row-level security, and a crossover can be built as epochs with randomization; see the blinding guide.
Many participants are older, and some have cognitive impairment or limited dexterity with phones. Offer a clinic-completed version of every questionnaire, and where a participant cannot consent for themselves, use the legally authorised representative step in eConsent. Large print and a person nearby are practical measures, not features the platform claims. Hearing loss also affects consent itself: allow time, written information and a quiet room, and record how consent was explained.
Build sequence
Write down every test, ear, frequency, condition and device setting the protocol requires.
Upload the protocol (PDF, DOCX or DOC) so the AI study builder can propose visits and forms. Nothing is saved until a person reviews it.
Add ear sections, one numeric field per frequency with range checks, and a repeating speech-test table with a condition field.
Add model, serial, settings, verification and adjustment rows, plus the follow-up wear-time readout.
Create the phone questionnaires and test the tester and analyst views in the sandbox.
Approved forms lock for live use. Real participants start the paid live phase.
Before the first fitting
Ears, frequencies, dB scale and test conditions match the protocol and the audiometer.
Whether the pure-tone average is entered or derived in export, written in the data management plan.
Device, serial, settings and verification fields, with a deviation field.
Device log readout, diary or both, and the visit it is read at.
Rights-holder terms for each questionnaire kept in the study documents.
CSV or Excel with the data dictionary opened in the statistics package.
Yes. Build a section per ear with one numeric field per frequency, units shown, and range checks that raise an auto-query when a site enters a value outside your limits.
Not as a built-in formula. Enter the average from the audiometer or compute it from the exported frequency fields in your statistics package.
No integration is claimed. The audiologist enters results, and device log readouts are transcribed with the date of the readout.
Yes. Questionnaires open from a secure link in the phone browser, with reminders. Licences for copyrighted instruments stay with your study documents.
Yes. Epochs and randomization support a crossover design; your statistician supplies the sequence and washout rules.
The forms are general enough for other hearing devices, but implant studies bring surgical and safety data too. Combine this with the medical device trial guidance and build the extra forms you need.
The sandbox is free with every feature, no credit card and no time limit. You pay only once you go live with real participants. Pricing is not published on the site, so ask for terms for your study.
Keep exploring
EDC for medical device trials
General device study set-up.
How to run a medical device clinical study
The process end to end.
EDC for wearable device studies
Connected devices and sync.
ePRO for patient-reported outcomes
Questionnaires on the phone.
How to blind a clinical trial
Blinding when the device is visible.
Adverse event template
Device-related events and sign-off.
Pricing
Free sandbox, pay at go-live.
Free sandbox with every feature. No credit card, and you pay only when you go live.