Nexus IG

The Nexus FHIR implementation guide: the contract for how clinical data from heterogeneous EMR systems is represented, validated, and exchanged. Application-agnostic, built on the Canadian baseline (CA Core+), deliberately profile-light. The site has two halves:

Reference →

The specification itself. Every profile, extension, value set and code system the IG guarantees — each one browsable as a set of views: narrative overview, element tables, conforming examples (hyperlinked as a graph), the authored FSH, its salient-field contract, and the generated TypedFhir API in Python / TypeScript / C#.

Start at the artifacts index, or jump straight in: Patient · Encounter · Appointment · Observation · DocumentReference

Handbook →

How to work with it. Tutorials for FHIR and FSH newcomers, implementation patterns (identifiers, locations, resource relationships, salient fields), per-feature design docs (scheduling, billing, consent, clinical tasks, rostering), and how to contribute or reach us.

---

For machines: validators and code generators consume the FHIR NPM package, never this website. The package, its id and the full release list are on IG metadata.

What changed: every release is documented, reader-first, in the Changelog.

Source & discussion: the spec is authored in FSH under doc/fhir in WellServices; questions, corrections and proposals are welcome from implementers and WELL staff alike -- email shawn.vincent@well.company, or see Contributing and feedback for every route in (Teams, the #discuss-fhir Slack channel, or a pull request against the FSH).