CoeKPI

Context

Participating hospitals report Occupational Medicine Center of Excellence indicators across repeated reporting periods. The same measure has to mean the same thing in every entry, while administrators need to understand progress without rebuilding the report by hand.

Problem

Separate forms and spreadsheets make definitions, validation, access control, and reporting difficult to keep consistent. A value may be present but still be unusable if its period, hospital, denominator, or interpretation is unclear.

My role

I translated the reporting requirements into the information model, product workflow, interface, validation behaviour, dashboards, exports, and full-stack implementation.

What was built

• KPI forms with validation at the point of entry.
• Separate access paths for administrators and participating hospitals.
• Period and organisation context kept with each submission.
• Dashboards that summarise programme progress.
• Excel exports that fit established reporting workflows.

Design story

Make the next missing value visible

Recurring reporting is partly a completion problem. The current introduction leads with recorded and outstanding indicators, so the hospital's next action is as important as the finished dashboard.

Keep comparisons in context

Month-to-month, multi-year, hospital, and hospital-group views answer different questions. Those contexts remain explicit instead of being compressed into a single score. Excel export keeps the structured work useful beyond the application.

Key workflow

1. Enter the reporting period and relevant hospital context.
2. Complete each KPI using the defined structure.
3. Resolve validation issues before submission.
4. Review completion and performance through the dashboard.
5. Export the structured data for reporting and further analysis.

Constraints

The interface needs to carry dense information without turning every screen into a spreadsheet replica. Definitions must remain explicit, familiar controls are preferable to decorative novelty, and access must reflect the responsibilities of each participant.

Verified operational footprint

The snapshot verified on 29 August 2026 records 47 configured hospitals, 24 assigned to reporting, and 23 with submitted data. There were 3,067 submitted KPI values across 55 reporting periods containing data. These figures describe operational scope; they do not establish a causal improvement in efficiency.

Implementation recorded in the original case study

Front end: Blazor WebAssembly, Microsoft Fluent UI 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 introduction, October 2026. The illustration explains reporting; it does not show hospital records.

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