Document the current baseline
Each public research tool should show its stage, status, data handling, outputs, and version note before use.
A public baseline for NeuraHear assessment tools, release notes, data-boundary statements, and future study-facing changes.
Why this matters
Research tools change over time. Version notes help future users know which calibration, stimuli, scoring, export, and data-handling assumptions applied.
Back to toolsDocument the current baseline
Each public research tool should show its stage, status, data handling, outputs, and version note before use.
Separate interface updates from study data
Static site releases should not overwrite server-backed records such as iDIN participant results.
Record meaningful behavior changes
Calibration, stimuli, scoring, export format, and backend changes should be logged before a tool is used for new data collection.
Current baseline
A browser-based screening workflow with calibration, device checks, adaptive SNR testing, and server-backed data capture.
A fixed-SNR single-digit workflow for estimating PI functions and generating correction levels for sequence synthesis.
An ICF-based questionnaire workflow for Mandarin-speaking adults, covering hearing, communication, participation, support, personal resources, and health.
Planned tools for AI-supported questionnaire guidance, triage, interpretation, and care-pathway support, developed with human oversight.
Release notes
iDIN 2026.06 upload queue
The iDIN results page now protects completed test records from being lost when server upload is interrupted.
Data boundary: Result upload reliability and metadata changed only; audio files, fixed-noise-gain application, SNR logic, adaptive scoring, randomization behavior, and existing server-side result records are unchanged.
iDIN 2026.06 test-state UX
The iDIN test page now uses clearer playback and response states so participants cannot enter responses before audio playback is complete.
Data boundary: Front-end interaction safeguards and deployment trigger behavior changed only; audio files, fixed-noise-gain application, SNR logic, adaptive scoring, randomization behavior, and existing server-side result records are unchanged.
iDIN 2026.06 calibration-confirmation UX
The iDIN calibration flow now requires participants to play the noise and explicitly confirm audibility before starting the formal test.
Data boundary: Front-end calibration gating and metadata changed only; audio files, fixed-noise-gain application, SNR logic, adaptive scoring, randomization behavior, and existing server-side result records are unchanged.
iDIN 2026.06 readiness-check UX
The iDIN setup flow now asks participants to confirm key device and environment conditions before calibration begins.
Data boundary: Front-end setup metadata changed only; audio files, SNR logic, adaptive scoring, randomization behavior, and existing server-side result records are unchanged.
iDIN 2026.06 calibration ready-state UX
The calibration page now makes audio loading explicit and prevents users from pressing calibration controls before noise playback is ready.
Data boundary: Front-end calibration interaction changed only; audio files, SNR logic, adaptive scoring, randomization behavior, and existing server-side result records are unchanged.
iDIN 2026.06 stable keypad UX
The iDIN landing and test pages now use more consistent controls, with a stabilized response keypad that stays in place during playback and answer entry.
Data boundary: Front-end interaction and styling changed only; audio mixing, SNR logic, adaptive scoring, randomization behavior, and existing server-side result records are unchanged.
iDIN 2026.06 flow and dashboard UX
The iDIN workflow now has clearer noise calibration controls, smoother in-test transition messages, and stronger researcher dashboard filtering and export tools.
Data boundary: Front-end workflow and dashboard UI changed only; audio mixing formulas, adaptive scoring, and existing server-side result records are unchanged.
iDIN 2026.06 SNR documentation
The iDIN implementation notes now explicitly define SNR matching as a corrected sequence-level operation, not per-digit SNR matching.
Data boundary: Documentation and version metadata changed only; the mixing algorithm, adaptive rule, and existing server-side results are unchanged.
iDIN 2026.06 setup refinement
The integrated DIN setup page now requires participant IDs, and the researcher dashboard has fully English action wording.
Data boundary: Static iDIN front-end files changed only; existing server-side JSONL results and backend storage are not modified by this release.
iDIN 2026.06 condition-order release
The integrated DIN setup page now supports optional randomization of selected test conditions and exposes a researcher dashboard entry from the iDIN landing page.
Data boundary: Static iDIN front-end files changed only; existing server-side JSONL results and backend storage are not modified by this release.
iDIN 2026.06 stability release
The integrated DIN workflow now has stronger playback-state handling, cache-busted static assets, clearer formal/practice export metadata, and shorter noise files for faster loading.
Data boundary: Static tool files and audio assets changed; the server-side iDIN results JSONL data directory is not modified by this release.
Site release 2026.05.20
A public version and credibility layer now records the current tool baseline, release notes, contact route, and data-boundary statements.
Data boundary: Static website content only; the iDIN server data directory and study records are not modified by this release.
Baseline 2026.05
The public tool registry now makes each tool's stage, validation status, data handling, outputs, and version note visible from the Tools page.
Data boundary: The baseline is a documentation snapshot; individual tool behavior remains governed by each tool page and deployment route.
SEO release 2026.05
The site now publishes route metadata, canonical URLs, robots rules, sitemap entries, and social-card metadata for better indexing and sharing.
Data boundary: Static discovery metadata only; no participant records or test data are touched.
Before a study release
Calibration flow, audio stimuli, scoring, export fields, server routes, and backup assumptions should be recorded here before a protocol uses a new version.