AudiogramIQ

Context

Occupational hearing-conservation programmes depend on repeated audiograms, baseline comparisons, follow-up rules, and reports that can still be reviewed after the examination day. When those steps live in separate files, the clinician spends time rebuilding the evidence before deciding what it means.

Problem

Raw thresholds are not the end of the workflow. The reviewer needs to see the audiogram, understand which baseline was used, identify meaningful changes, and keep the underlying values available when an automated interpretation needs to be checked.

My role

I defined the clinical workflow, product scope, interpretation requirements, interface direction, and full-stack implementation. The work joins occupational-medicine knowledge with software design rather than translating a finished specification from another team.

What was built

• Hearing-test entry and structured Excel import with a preview before changes are committed.
• Employee test history and comparison against the selected baseline.
• NIOSH and OSHA interpretations within the same review workflow.
• Yearly confirmation and investigation status for follow-up.
• Individual DOCX reports and grouped XLSX exports.
• Employee, examiner, and organisation records.

Design story

Keep the evidence beside the interpretation

An audiogram's thresholds, chosen baseline, and possible shift findings need to remain understandable together. The review connects successive tests to the selected baseline and shows NIOSH and OSHA interpretations in that context. A generated finding remains something to check against the source values, alongside professional judgement.

Make the next action visible

Baseline, monitoring, and confirmation describe different points in the review. The workflow keeps those states visible and brings confirmation and investigation status into yearly follow-up lists. This gives the reviewer a path from an interpretation to the work still needing attention.

Carry that context into reporting

An individual DOCX report and a grouped XLSX list serve different follow-up tasks. Both belong to the same sequence as entry, baseline comparison, and review. The public introduction follows that order too, so teams can understand the workspace before signing in.

Key workflow

1. Record the hearing thresholds or preview a structured Excel import.
2. Select and verify the relevant baseline.
3. Review the test history and NIOSH and OSHA interpretations.
4. Review confirmation and investigation status for follow-up.
5. Prepare an individual report or grouped export for the hearing-conservation process.

Constraints

Clinical review must remain possible at every step. Automated analysis supports judgement; it does not replace it. Source values, baseline choices, and the reasoning behind a finding must remain easy to inspect.

Verified operational footprint

The snapshot verified on 29 August 2026 covers 28 organisation records, 2,986 person records, 18,196 audiogram records, and 32,703 generated interpretations. Person records are not claimed to be unique people across every data source, and these figures are not clinical outcomes.

Implementation recorded in the original case study

Front end: Blazor WebAssembly, Microsoft Fluent UI for Blazor and ECharts. Back end: ASP.NET Core (.NET 8), PostgreSQL and Entity Framework Core. Authentication: Suttisak.Blazor.Identity and Passkey.

These implementation details are retained from the original case study; this content refresh does not establish the application's current package versions.

Image and source notes

Public homepage, October 2026. The hearing-test scene introduces the workflow; no employee records or individual test results are shown.

Content refreshed on 7 November 2026 from the published Quack & Honk AudiogramIQ page.