New Zealand ICP Implementation Guide, published by Accident Compensation Corporation. This guide is not an authorized publication; it is the continuous build for version 1.0.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/acc-fhir-publisher/icp/ and changes regularly. See the Directory of published versions

IG Home

Official URL: http://hl7.org.nz/fhir/ImplementationGuide/hl7.org.nz.fhir.ig.icp				Version: 1.0.0
Active as of 2024-09-08				Computable Name: icp

New Zealand ICP Implementation Guide

This is the Integrated Care Pathways Implementation Guide (IG) for New Zealand, provided by ACC, and contains the profiles and extensions used for PMS Vendors to create and manage ICP claims. This IG also includes relevant terminology. More information for ICP can be found on the ACC ICP website.

The following tabs are available from the navbar at the top.

Profiles

This tab lists all the profiles defined in this guide. A profile is a set of constraints on a Resource or Data Type - for example, the ICP Case Create resource has a profile defined for it in this guide. The profile defines which elements are required, and which are optional, and may also define additional constraints on the data in those elements. The ICP Case Create profile also defines that the 'patient' element must have a contained ICP Patient resource.

Extensions

This tab lists all the extensions defined in this guide, where an extension is an additional element that can be recorded in a resource. The extension definition describes the purpose of the extension, its name and dataType/s.

Clicking on the link in the 'id' column will display the detail page for that extension. Extensions can have a single value, or can be composed of multiple 'child' elements - an example is the Exceptional Funding Extension extension. The snapshot tab in the details page (about halfway down) lists all the parts of the extension - including a link to the ValueSet if the element is coded.

Terminology

This tab lists the terminology artifacts defined in this guide. There are 2 artifacts that will be found here:

• ValueSets are sets of codes, drawn from one or more code systems, intended for use in coded data elements in Resources, as defined by a particular conformance rule - such as an Extension or Profile. The ValueSets in this Guide are 'recommended' values, but it may be possible for implementers to use additional concepts if the rules defined by a particular Extension or Profile permit this.
• CodeSystem resources are used to declare the existence of and describe a code system, its key properties, and optionally define a part or all of its content. Wherever possible, the use of international terminologies, such as SNOMED CT, is recommended; however, a number of New Zealand-specific code systems are included in this Guide to meet unique, local requirements.

These resources can be used by Terminology Servers (like Terminz or Ontoserver ) to provide terminology operations of use to implementers, such as the ValueSet $expand operation.

There is a lot more detail on terminology in the FHIR specification. The section on Terminology Services is also useful.

Identifiers

This tab lists the NamingSystem resources defined in this guide, which are used to define the identifiers used in the guide.

Identifiers are used to unambiguously identify something. Examples in New Zealand are the NHI (National Health Identifier) or HPI (Health Practitioner index). Each type of identifier has a url that uniquely identifies it - for example The ACC 45 number is https://standards.digital.health.nz/ns/acc-45-number. This url will be present in the 'system' value in a resource instance. Note that the url will not necessarily 'resolve' - entering it into a web browser will not result in anything.

Artifact Index

This is a tab automatically generated during the build of the Implementation Guide, and lists all the FHIR artifacts defined by the guide with a link to the details.

Support

Contains links to the main FHIR specification, as well downloads for the full IG or the artifacts defined in the guide (Extension Definitions, ValueSets and CodeSystems.)

If you would like to make any feedback on this Implementation Guide, email digitaloperations@acc.co.nz