Handbook¶
Practical guidance for working with the Nexus IG: learning material, implementation patterns, and the design record behind each feature area. The formal artifacts themselves — profiles, extensions, terminology, examples — live in the Reference.
Learning FHIR¶
New to FHIR (or to this spec)? Start here:
- FHIR Basics — FHIR concepts as this project uses them
- FSH Basics — FHIR Shorthand, the language the spec is written in
- External Resources — the wider FHIR world
Implementation patterns¶
Task-oriented guidance for the decisions every integration hits:
- Primary Care Reality — the data landscape the spec has to survive
- Identifiers and Identifier Migration
- Resource Relationships — how the resource graph hangs together
- Salient Fields — the per-profile contract behind typed accessors and LLM contexts
- Locations and Organization References
Clinical criteria¶
Working with the CQL criteria this specification publishes:
- Clinical Criteria (CQL) — start here: what CQL is for in this specification, the four activities, and which of the pages below you want
- Criteria Artifacts — what a compiled criterion is, and why consuming one needs a JSON parser rather than a CQL compiler
- For One Patient — compiling a rule, reading its refusals, and the retrieve that silently matches nothing
- Across a Population — generating the pack that a query or SQL generator consumes
Feature designs¶
The design record for each feature area — why the profiles look the way they do:
- Scheduling — schedules, slots, appointments, the booking flow
- Oscar Billing — invoices and the billing write-back
- Clinical Tasks — task management, including AI-agent workflows
- Consent — patient consent for third-party app data sharing
- Rostering — primary care attachment
- Templates — reusable prototype graphs, starting with clinical letters
Contributing and feedback¶
- Contributing and feedback — how to reach us (email, Teams,
#discuss-fhir), what is most useful to report, and the contributor track for editing FSH - Release Process — how a merged change becomes a published version