This fragment is available on index.html
This publication includes IP covered under the following statements.
| Type | Reference | Content |
|---|---|---|
| web | browser.ihtsdotools.org |
The adverse reaction event, from the NZ COVID-19 immunisation reaction refset Binding: SCT Reference Set 61231000210108 ( required ) |
| web | www.tewhatuora.govt.nz |
IG © 2026+ Health New Zealand | Te Whatu Ora
. Package tewhatuora.nzhts#0.9.0 based on FHIR 4.0.1
. Generated 2026-08-17
Links: Table of Contents | QA Report |
| web | browser.ihtsdotools.org |
The codes SHALL be taken from For example codes, see
SCT Reference Set 61231000210108
http://hl7.org/fhir/ValueSet/observation-codes|4.0.1
( required to http://snomed.info/sct/21000210109?fhir_vs=refset/61231000210108
)
|
| web | browser.ihtsdotools.org |
The codes SHALL be taken from SCT Reference Set 61231000210108
( required to http://snomed.info/sct/21000210109?fhir_vs=refset/61231000210108
)
|
| web | snomed.info | SNOMED CT Concept Domain Binding |
| web | github.com | This is not decoration. It is what lets a validator - or any consumer - determine which terminology server can answer questions about the code . The terminology server registry declares NZHTS authoritative for the pattern: |
| web | browser.ihtsdotools.org | SCT Reference Set 61231000210108 |
| web | github.com |
Setting the version is not merely documentation. It is what allows a validator, or any consumer, to
work out which terminology server can answer questions about this code
. The
terminology server registry
declares NZHTS authoritative for http://snomed.info/sct|http://snomed.info/sct/21000210109*
- a
match on system and version
. A coding that omits the version is just unqualified SNOMED CT, and
will be routed to a general-purpose server that does not hold the NZ edition and cannot resolve NZ
edition content.
|
| web | www.healthnz.govt.nz | This IG provides guidance on using NZHTS with FHIR. It focuses on the integration of terminology with FHIR tooling and how to use NZ terminology in FHIR IGs, rather than the clinical governance of individual terminologies or other NZHTS capabilities (such as the authoring platform). For more general NZHTS information, see the NZHTS home page . |
| web | nzhts.digital.health.nz |
The production FHIR terminology endpoint is https://nzhts.digital.health.nz/fhir
. The included NZHTS CapabilityStatement
describes the server's supported functionality. This can also be retreived directly from https://nzhts.digital.health.nz/fhir/metadata
|
| web | www.healthnz.govt.nz | Health New Zealand NZHTS overview |
| web | nzhts.digital.health.nz | NZHTS Ontoserver Dashboard |
| web | github.com | NZHTS API examples on GitHub |
| web | www.healthnz.govt.nz | HNZ Digital Services Hub |
| web | nzhts.digital.health.nz | obtaining versioned terminology content through the NZHTS syndication feed for loading into downstream terminology services. |
| web | github.com | This page provides background on how the terminology ecosystem works: the actors involved, how the IG Publisher decides which terminology server to call, and what happens end to end during a build. It is not strictly necessary to understand how the terminology co-ordination service and registry work in detail, but it is helpful when building IGs to understand at a high level where terminology is being sourced, validated, and expanded from. The full documentation is available in the Github terminology server registry docs and accompanying FHIR IG . |
|
tree-filter.png
|