Cochlear Implant Atlas
CI Atlas · Tuning the Electric Ear: Activation and Programming the Implant · Module 15

15Longitudinal Care, Datalogging and Verification

Activation is the start of programming, not its conclusion. Over the first weeks the cochlea, the nerve and the listener all change, so the map is chased toward stability rather than set once. Datalogging now reports how the device is actually lived with, remote sessions reach patients who cannot travel, and sound-field and speech verification turn a map that looks reasonable into a recipient who can hear soft speech.

CThe schedule of mapping visits

Visits are dense early and thin out later: typically weekly to monthly through the first few months, then quarterly, settling to annual reviews once performance is stable. Impedances are low at surgery in the perilymph, rise over the first few weeks as protein and fibrous tissue build on the contacts, and then stabilise, so they are checked at every early session. Children are seen on roughly a quarterly basis until about age 7 because their levels keep shifting during development. Each session begins with a physical check of the ear and equipment plus a datalogging review before any level is changed.[2020][2009][2014]

T & C levels and impedance over the first year — scrub the timeline

highlowact.13w26w39w52wweeks since activation →T levelC levelimpedance
Visit cadenceEvery 2–4 weeksPhaserapid change

Impedance climbs over the first few weeks then stabilises, while T (threshold) and C (comfort) levels are mapped repeatedly as tolerance grows; in children the levels typically settle somewhere between 3 months and 1 year. Visit frequency simply follows the rate of change — weekly to monthly early on, then quarterly, then annual once the map holds steady. Scrub to early weeks and the curves are still moving; scrub to the end and they have flattened. Illustrative.

THow T and C levels stabilise

Threshold and comfort levels are not fixed at activation; they typically rise over the first weeks to months as the recipient acclimatises to electric hearing. Children's T levels increase through the first few months and generally stabilise somewhere between three months and one year after implantation. Because stimulation itself lowers impedance and re-shapes loudness perception, an under-set first map is expected and is deliberately advanced session by session. Loudness balancing across electrodes is repeated as levels stabilise so that equal-percentage stimulation sounds equally loud across the array, preserving the intensity cues of speech.[2020][2013][2014]

Datalogging report — what the processor recorded

listening environments (% of on-air time)38%Quiet27%Speech in noise20%Speech10%Noise5%Music
Daily wear11.5 hCoil-off4.5 h/dayTarget10+ h/day
On target — tune the map

The device is worn full time, so the datalogging tells you the map is being given a fair test — coil-off time is low and the environment mix is rich. Now any complaint can be addressed by adjusting the program, because reduced benefit is unlikely to be a wear problem. Illustrative.

TDatalogging and remote care

Datalogging reports hours of use per day, time the coil is off the head, the programs and listening environments used, and accessory use, turning counselling from guesswork into evidence. For children, the target is genuine full-time wear (often expressed as at least about 10 hours a day), and a shortfall in logged hours redirects the visit toward use and retention rather than fine-tuning. Remote programming lets the audiologist measure and adjust over a connection, sparing elderly, rural, ill or paediatric recipients repeated travel during the busy first months. Studies of remote programming have found remotely obtained settings comparable to in-clinic maps with high recipient and clinician satisfaction, supporting tele-audiology as routine care.[2020][2014][2018]

Aided sound-field thresholds vs the 20–30 dB HL target band

02030507020–30 dB HL target2505001k2k!4kfrequency (Hz) →
Points flagged1 / 5Statusrecheck

Aided sound-field thresholds confirm the map is delivering audibility across the speech spectrum. The paediatric target is the 20–30 dB HL band — at least 30 dB HL at 250 and 500 Hz and within roughly 25 dB through the mid-to-high frequencies — ideally verified by one month post-activation. Any point sitting outside the band (flagged in red) prompts a level or microphone check rather than being accepted, because a single inaudible band can blunt speech understanding. Illustrative.

CVerifying the fit and deciding when to re-map

Aided sound-field warbled-tone thresholds verify audibility; the goal is access to soft sound, broadly in the 20 to 30 dB HL range across the speech frequencies. A common paediatric target is detection no poorer than 30 dB HL at 250 and 500 Hz and within 25 dB HL through the mid-to-high frequencies, measured by no later than one month post-activation. Elevated aided thresholds prompt the fitter first to rule out a faulty or obstructed microphone, then to raise T levels or adjust the input dynamic range to restore low-level audibility. Speech testing with open-set words and sentences in quiet and in noise confirms that audibility translates into intelligibility and tracks progress over time. A re-map is triggered by reported difficulty with soft or loud sounds, falling speech scores, datalogging that contradicts the complaint, or aided thresholds drifting outside target, not by the calendar alone.[2020][2013][2009]

Case 17.15 · Longitudinal Care, Datalogging and
A 4-year-old returns six weeks after activation. The caregiver reports he often ignores soft speech. Datalogging shows 11 hours of daily use across varied environments. Aided sound-field thresholds are 40 dB HL at 250 and 500 Hz; the microphone cover is intact and clean.

What is the most appropriate next step?

Self-assessment — Module 152 questions
Question 1

Aided sound-field warbled-tone thresholds are used after implantation primarily to verify that the recipient:

Question 2

Children's threshold (T) levels typically stabilise:

Tracked locally in your browser — see /progress for the dashboard.