Document the current baseline
Each public research tool should show its stage, status, data handling, outputs, and version note before use.
Tool governance
Tool Version Log
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 toolsSeparate 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
Public assessment-tool register
LiveSpeech-in-noise assessment
integrated Digit-in-Noise Test
A browser-based screening workflow with calibration, device checks, adaptive SNR testing, and server-backed data capture.
- Version note
- Active deployment
- Data boundary
- Responses are submitted to the project backend for study use.
LiveStimulus optimization
Digit Optimization Test
A fixed-SNR single-digit workflow for estimating PI functions and generating correction levels for sequence synthesis.
- Version note
- Noise calibration enabled
- Data boundary
- Runs in the browser; individual and pooled results are exported by the researcher.
In validationEveryday functioning PROM
HFEQ-Mandarin Research Preview
An ICF-based questionnaire workflow for Mandarin-speaking adults, covering hearing, communication, participation, support, personal resources, and health.
- Version note
- Manuscript-linked preview
- Data boundary
- Browser-only completion and export for research preview use.
In developmentAI in hearing care
AI-Guided Hearing-Care Workflows
Planned tools for AI-supported questionnaire guidance, triage, interpretation, and care-pathway support, developed with human oversight.
- Version note
- Concept stage
- Data boundary
- No public tool yet; future tools will separate research data, generated outputs, and review records.
Release notes
Recent platform and tool-facing changes
Released2026-05-20NeuraHear platform
Public version log established
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.
- Added a research contact page and connected it to navigation, footer, sitemap, and structured data.
- Added tool study-planning cues so researchers can check versioning, calibration, export format, and backup expectations before use.
- Established this version log as the place to record future tool-facing releases.
Data boundary: Static website content only; the iDIN server data directory and study records are not modified by this release.
Baseline2026-05-20Assessment tools
Current assessment-tool baseline captured
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.
- iDIN remains the operational server-backed speech-in-noise workflow.
- Digit Optimization is listed as a live stimulus-development workflow with noise calibration enabled.
- HFEQ-Mandarin is listed as an in-validation PROM research preview.
Data boundary: The baseline is a documentation snapshot; individual tool behavior remains governed by each tool page and deployment route.
Released2026-05-20NeuraHear platform
Discovery metadata and sitemap hardened
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.
- Added site-wide metadata defaults and page-level metadata helpers.
- Added robots and sitemap generation for primary public routes.
- Added public social-card metadata for shared links.
Data boundary: Static discovery metadata only; no participant records or test data are touched.
Before a study release
Log behavior changes before new data collection starts.
Calibration flow, audio stimuli, scoring, export fields, server routes, and backup assumptions should be recorded here before a protocol uses a new version.