Nordhealth's system, Nord, built in web components with a strong accessibility focus for clinical software used under pressure.
Why we like it
Nord is proof that a strict web-standards approach holds up for high-stakes software. It's built as framework-agnostic web components with Lit, so it runs from a static HTML page to a React or Vue app, or no framework at all, and it favors composing fine-grained parts over piling on configuration props, its July 2026 release alone added eighteen components made of fifty-six individual parts.
The detail that gives it weight is that these are the same components Nordhealth ships its real clinical and veterinary software with, products used by large veterinary groups, rather than a showcase built to impress. Tooling extends past the components too, with an ESLint plugin, a Tailwind integration and a Figma toolkit.
Where it fits
Nord fits multi-framework or long-lived product teams, especially in regulated or clinical settings, who need one component set that outlives framework churn.
On accessibility, Nordhealth frames WCAG 2.1 AA as something they work toward rather than a certified claim, so verify the specifics for your own compliance needs.
Ideas to borrow
- 01.
Architecture
Build the system as framework-agnostic web components (Lit), so one library serves every stack and survives framework churn.
- 02.
Contribution
Expose fine-grained component parts to compose with, rather than piling on configuration props, so consumers assemble what they need.
