Study type · Hearing aid trialsUpdated October 20, 2026

Hearing aid clinical study software

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.

  • Audiometry by ear and frequency
  • Fitting and device-use records
  • Questionnaires on the phone

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

Pure-tone audiometry, right ear (demo study)
Participant 001-0027 · Visit 2 (Fitting)Draft

Air conduction threshold

500 Hz

AC500R
35dB HL

1000 Hz

AC1000R
40dB HL

2000 Hz

AC2000R
50dB HL

4000 Hz

AC4000R
65dB HL

Query: outside the range set for this study (demo)

Masking used

MASKR
NoYes
Demo data only.Save
Left ear is a second section. Each frequency is its own field, so thresholds export as separate variables.

What a hearing aid study needs from its data collection

  • Two ears, many frequencies: audiometry gives a grid of values per participant per visit, and the design must keep ear, frequency and test condition unambiguous.
  • Device as intervention: model, settings, fitting method, verification measurement and any later adjustment are the dose of the intervention.
  • Real-world use: hours worn per day and listening environments matter, and they come from device logs or diaries.
  • Mixed outcomes: clinic tests (thresholds, speech in noise) and questionnaires about hearing in daily life are both primary or key secondary outcomes.
  • Blinding is hard: a participant knows when they are wearing an aid, so blinding often rests on the tester or on comparing settings.

The data

How to structure audiometry and speech tests in an eCRF

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 records and device-use logs

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

Hearing aid trials against neighbouring pages

QuestionThis pageNeighbouring page
What kind of study?Audiology: thresholds, speech tests, fittingMedical device trials in general
Where does the device data come from?Fitting software readouts and wear-time diaries entered by staff or participantsWearable device studies with connected consumer devices
What is the main outcome?Threshold change, speech-in-noise score, self-reported benefitPROMs for questionnaire-led studies
How is the blind kept?Tester blind to settings where possible; participant often cannot beBlinding guide
Who takes part?Often older adults, sometimes with cognitive declineLAR consent when capacity is in doubt

Build an audiometry form and test it with mock thresholds

Create the ear-by-frequency sections, set the range checks and enter a few test participants. Free sandbox, no credit card.

Build your hearing study free

Outcomes and design

Questionnaires, blinding and older participants

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

From audiology protocol to a running study

  1. 1

    List the tests

    Write down every test, ear, frequency, condition and device setting the protocol requires.

  2. 2

    Draft the forms

    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.

  3. 3

    Build audiometry and speech forms

    Add ear sections, one numeric field per frequency with range checks, and a repeating speech-test table with a condition field.

  4. 4

    Build the fitting and device log

    Add model, serial, settings, verification and adjustment rows, plus the follow-up wear-time readout.

  5. 5

    Set questionnaires and the blind

    Create the phone questionnaires and test the tester and analyst views in the sandbox.

  6. 6

    Approve and go live

    Approved forms lock for live use. Real participants start the paid live phase.

Before the first fitting

Hearing aid study readiness checklist

Frequency list and units fixed

Ears, frequencies, dB scale and test conditions match the protocol and the audiometer.

Average calculation decided

Whether the pure-tone average is entered or derived in export, written in the data management plan.

Fitting record designed

Device, serial, settings and verification fields, with a deviation field.

Wear-time method chosen

Device log readout, diary or both, and the visit it is read at.

Instrument licences filed

Rights-holder terms for each questionnaire kept in the study documents.

Export tested

CSV or Excel with the data dictionary opened in the statistics package.

FAQ

Questions teams ask before they switch

Something not covered here? Ask us directly.

Can I enter audiometry for each ear and frequency?

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.

Does Capture calculate the pure-tone average?

Not as a built-in formula. Enter the average from the audiometer or compute it from the exported frequency fields in your statistics package.

Does it connect to audiometers or fitting software?

No integration is claimed. The audiologist enters results, and device log readouts are transcribed with the date of the readout.

Can participants complete hearing questionnaires at home?

Yes. Questionnaires open from a secure link in the phone browser, with reminders. Licences for copyrighted instruments stay with your study documents.

Can I run a crossover between two programmes?

Yes. Epochs and randomization support a crossover design; your statistician supplies the sequence and washout rules.

Is this for cochlear implants as well?

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.

How much does it cost?

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.

Start your hearing study free

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

Build your hearing study free