IP statements¶
This specification's own text and definitions are licensed CC0 1.0 Universal. The terminology it binds is not. The statements below are the licence terms of the code systems and classifications this specification actually references -- collected from the compiled IG by the FHIR IG Publisher, plus the licensors' own terms for the systems the publisher's registry does not carry.
Read this page before implementing. Not every entry is merely a notice -- SNOMED CT content requires an appropriate SNOMED International Affiliate licence in your jurisdiction, and ICD-10-CA and CCI require a licence from CIHI -- and those obligations pass through to anyone deploying against this specification. Nothing here grants you a licence you do not already hold.
This page is generated, so it lists what the current release binds and nothing else. If a code system stops being referenced, its statement disappears from here with it. Every code system bound in the compiled specification is checked against this list at build time; a bound system with no statement fails the build rather than publishing a page that understates an obligation.
What this release binds¶
Every terminology below is referenced by this release. Obligation separates the entries that are a notice to reproduce from the ones you must hold a licence for; each row links to the statement in full, and each statement links to the artifacts of ours that bind it.
| Terminology | System | Obligation |
|---|---|---|
| ISO 3166 country codes | inherited, not bound directly | Notice |
| CDC / ATSDR content | inherited, not bound directly | Notice |
| UCUM | http://unitsofmeasure.org |
Notice |
| OHIP Schedule of Benefits | https://fhir.apps.health/CodeSystem/on-ohip-schedule-of-benefits |
Notice |
| DICOM Content Mapping Resource | inherited, not bound directly | Notice |
| LOINC | http://loinc.org |
Notice |
| SNOMED CT | http://snomed.info/sct |
Licence required |
| HL7 Terminology (THO) | http://terminology.hl7.org/CodeSystem/consentactionhttp://terminology.hl7.org/CodeSystem/data-absent-reasonhttp://terminology.hl7.org/CodeSystem/v2-0203http://terminology.hl7.org/CodeSystem/v3-ActCodehttp://terminology.hl7.org/CodeSystem/v3-ActReasonhttp://terminology.hl7.org/CodeSystem/v3-NullFlavorhttp://terminology.hl7.org/CodeSystem/v3-ObservationValue |
Notice |
| Base FHIR R4 code systems | http://hl7.org/fhir/request-intenthttp://hl7.org/fhir/task-status |
Notice |
| CCI (Canadian Classification of Health Interventions) | http://cihi.ca/fhir/CodeSystem/cihi-cci |
Licence required |
| Health Canada DIN | http://hl7.org/fhir/NamingSystem/ca-hc-din |
Notice |
| ICD-10-CA | http://hl7.org/fhir/sid/icd-10-ca |
Licence required |
| HL7 Patient Request for Corrections | http://hl7.org/fhir/uv/patient-corrections/CodeSystem/PatientCorrectionBusinessStatus |
Notice |
| HL7 Patient Request for Corrections | http://hl7.org/fhir/uv/patient-corrections/CodeSystem/PatientCorrectionCommunicationTypes |
Notice |
| HL7 Patient Request for Corrections | http://hl7.org/fhir/uv/patient-corrections/CodeSystem/PatientCorrectionTaskTypes |
Notice |
| CCDD (Canadian Clinical Drug Data Set) | http://terminology.hl7.org/CodeSystem/hc-CCDD |
Notice |
| AIGC (DPD active-ingredient group code) | http://terminology.hl7.org/CodeSystem/v3-hc-aigc |
Notice |
| AIGN (DPD active-ingredient group number) | http://terminology.hl7.org/CodeSystem/v3-hc-aign |
Notice |
| ATC (Anatomical Therapeutic Chemical) | http://www.whocc.no/atc |
Notice |
| Ontario nurse licence number | https://fhir.infoway-inforoute.ca/NamingSystem/ca-on-license-nurse |
Notice |
| Ontario physician licence number | https://fhir.infoway-inforoute.ca/NamingSystem/ca-on-license-physician |
Notice |
ISO 3166 country codes¶
ISO maintains the copyright on the country codes, and controls its use carefully. For further details see the ISO 3166 web page: https://www.iso.org/iso-3166-country-codes.html
Where this specification uses it: through terminology it inherits from a dependency rather than binds itself, so there is no artifact of ours to point at. The publisher reports it because the resolved terminology graph reaches it.
CDC / ATSDR content¶
Most of the information on the CDC and ATSDR websites is not subject to copyright, is in the public domain, and may be freely used or reproduced without obtaining copyright permission. For information and exceptions regarding use of CDC material please see https://www.cdc.gov/other/agencymaterials.html
Where this specification uses it: through terminology it inherits from a dependency rather than binds itself, so there is no artifact of ours to point at. The publisher reports it because the resolved terminology graph reaches it.
UCUM¶
The UCUM codes, UCUM table (regardless of format), and UCUM Specification are copyright 1999-2009, Regenstrief Institute, Inc. and the Unified Codes for Units of Measures (UCUM) Organization. All rights reserved. https://ucum.org/trac/wiki/TermsOfUse
Where this specification uses it: MedicationRequest Profile · UCUM units of measure -- all codes
OHIP Schedule of Benefits¶
The system URI is defined by this specification. The Schedule of Benefits itself is published by the Ontario Ministry of Health and is Crown copyright of the King's Printer for Ontario. It is incorporated by reference into R.R.O. 1990, Reg. 552 under the Health Insurance Act, and the King's Printer permits any person to reproduce the text contained in Ontario's regulations without seeking permission and without charge, provided the reproduction is accurate and is not represented as an official version. Fee codes shown on this specification's rendered page are reproduced on that basis and are NOT AN OFFICIAL VERSION: they are a sample, they are not maintained against the Ministry's amendment cycle, and the edition in force at ontario.ca governs. This artifact itself enumerates no codes.
Where this specification uses it: Invoice Profile
DICOM Content Mapping Resource¶
These codes are excerpted from Digital Imaging and Communications in Medicine (DICOM) Standard, Part 16: Content Mapping Resource, Copyright (c) 2011 by the National Electrical Manufacturers Association.
Where this specification uses it: through terminology it inherits from a dependency rather than binds itself, so there is no artifact of ours to point at. The publisher reports it because the resolved terminology graph reaches it.
LOINC¶
This material contains content from LOINC. LOINC is copyright (c) 1995-2020, Regenstrief Institute, Inc. and the Logical Observation Identifiers Names and Codes (LOINC) Committee and is available at no cost under the license. LOINC(R) is a registered United States trademark of Regenstrief Institute, Inc.
Where this specification uses it: DocumentReference Profile · Observation Profile · LOINC -- all codes · Composition Kind Value Set · Composition Section Value Set · Composition Classification Value Set · Note Classification Value Set (retired) · Personal Pronouns Value Set
SNOMED CT¶
You must hold a licence
Reproducing the notice is not enough. Deploying against this specification with SNOMED CT content requires the licence named below, in your own jurisdiction.
This material contains content that is copyright of SNOMED International. Implementers of these specifications must have the appropriate SNOMED CT Affiliate license - for more information contact https://www.snomed.org/get-snomed or info@snomed.org.
Where this specification uses it: SNOMED CT -- all codes · Gender Identity Value Set · Indigenous Identity Value Set · Racialized Group Value Set
HL7 Terminology (THO)¶
This material derives from the HL7 Terminology (THO). THO is copyright (c)1989+ Health Level Seven International and is made available under the CC0 designation. For more licensing information see: https://terminology.hl7.org/license.html
Where this specification uses it: App Consent Profile · Patient Profile · Data absent reason -- all codes · HL7 NullFlavor codes -- all codes · HL7 identifier type codes (v2-0203) -- all codes · Consent Override Grounds Value Set · Disclosure Completeness Labels Value Set · Disclosure Control Labels Value Set · Indian Act Registration Status · Indigenous Identity Value Set · Racialized Group Value Set · Privacy Exception Purposes Value Set · Privacy Restriction Actions Value Set
Base FHIR R4 code systems¶
This specification binds code systems defined by the base FHIR R4 specification (for example http://hl7.org/fhir/request-intent). The FHIR specification is published by HL7 International under Creative Commons "No Rights Reserved" (CC0); see https://hl7.org/fhir/R4/license.html. HL7(R), HEALTH LEVEL SEVEN(R) and FHIR(R) are registered trademarks of Health Level Seven International and are not licensed by that designation.
Where this specification uses it: Clinical Task Intent Value Set · Clinical Task Statuses
CCI (Canadian Classification of Health Interventions)¶
You must hold a licence
Reproducing the notice is not enough. Deploying against this specification with CCI (Canadian Classification of Health Interventions) content requires the licence named below, in your own jurisdiction.
The CCI is property of the Canadian Institute for Health Information © 2001-2022 Canadian Institute for Health Information
That notice is CIHI's own, published for this product and reproduced here unaltered. This specification pins the code system URI only and enumerates no codes; using CCI content requires a licence from CIHI. For licensing see https://www.cihi.ca.
Where this specification uses it: Procedure Profile · Canadian Classification of Health Interventions (CCI) -- all codes
Health Canada DIN¶
Drug Identification Numbers (DINs) are assigned and published by Health Canada. This specification pins the code system URI only and enumerates no codes. See the Drug Product Database at https://health-products.canada.ca/dpd-bdpp/.
Where this specification uses it: Medication Dispense Profile · MedicationRequest Profile · Medication Statement Profile · Drug Identification Number (DIN) -- all codes
ICD-10-CA¶
You must hold a licence
Reproducing the notice is not enough. Deploying against this specification with ICD-10-CA content requires the licence named below, in your own jurisdiction.
ICD-10-CA is based upon the International Statistical Classification of Diseases and Related Health Problems, Tenth Revision (ICD-10) Copyright © World Health Organization 1992. All rights reserved. The Canadian version, ICD-10-CA, was modified with permission for Canadian Government purposes. The ICD-10-CA is property of the Canadian Institute for Health Information © 2001-2022 Canadian Institute for Health Information
That notice is CIHI's own, published for this product and reproduced here unaltered. This specification pins the code system URI only and enumerates no codes; using ICD-10-CA content requires a licence from CIHI. For licensing see https://www.cihi.ca.
Where this specification uses it: Condition Profile · ICD-10-CA -- all codes
HL7 Patient Request for Corrections¶
See the statement for the correction task-type code system: the same HL7 International publication (Patient Request for Corrections, STU1 1.0.0) under CC0.
Where this specification uses it: Correction Business Status Value Set
HL7 Patient Request for Corrections¶
See the statement for the correction task-type code system: the same HL7 International publication (Patient Request for Corrections, STU1 1.0.0) under CC0.
Where this specification uses it: Statement of Disagreement Profile
HL7 Patient Request for Corrections¶
Correction task types, correction communication types and correction business statuses are published by HL7 International in the Patient Request for Corrections implementation guide (STU1, version 1.0.0). HL7 publishes the FHIR specification and its implementation guides under Creative Commons "No Rights Reserved" (CC0); see https://hl7.org/fhir/R4/license.html and https://hl7.org/fhir/uv/patient-corrections/. HL7(R), HEALTH LEVEL SEVEN(R) and FHIR(R) are registered trademarks of Health Level Seven International and are not licensed by that designation.
Where this specification uses it: Correction Task Types Value Set
CCDD (Canadian Clinical Drug Data Set)¶
The Canadian Clinical Drug Data Set (CCDD) is published by Health Canada; its FHIR representation is developed and served by Canada Health Infoway and is freely available for use in digital health solutions. The code system identity is published through HL7 Terminology (THO). This specification pins the code system URI only and enumerates no codes. See https://terminologystandardsservice.ca/fhir.
Where this specification uses it: AllergyIntolerance Profile · Medication Dispense Profile · MedicationRequest Profile · Medication Statement Profile · Canadian Clinical Drug Data Set (CCDD) -- all codes
AIGC (DPD active-ingredient group code)¶
The Drug Product Database active-ingredient group code (AIGC) is published by Health Canada; the code system identity is published by HL7 Canada through HL7 Terminology (THO). This specification pins the code system URI only and enumerates no codes. See the Drug Product Database at https://health-products.canada.ca/dpd-bdpp/.
Where this specification uses it: AllergyIntolerance Profile · DPD active-ingredient group code (AIGC) -- all codes
AIGN (DPD active-ingredient group number)¶
The Drug Product Database active-ingredient group number (AIGN) is published by Health Canada; the code system identity is published by HL7 Canada through HL7 Terminology (THO). This specification pins the code system URI only and enumerates no codes. See the Drug Product Database at https://health-products.canada.ca/dpd-bdpp/.
Where this specification uses it: Medication Dispense Profile · MedicationRequest Profile · Medication Statement Profile · DPD active-ingredient group number (AIGN) -- all codes
ATC (Anatomical Therapeutic Chemical)¶
The Anatomical Therapeutic Chemical (ATC) classification is maintained by the WHO Collaborating Centre for Drug Statistics Methodology on behalf of the World Health Organization. This specification pins the code system URI only and enumerates no codes; reuse and redistribution of ATC/DDD content is governed by the Centre's own terms. See https://www.whocc.no/atc_ddd_index/.
Where this specification uses it: AllergyIntolerance Profile · Medication Dispense Profile · MedicationRequest Profile · Medication Statement Profile · WHO ATC classification -- all codes
Ontario nurse licence number¶
Ontario nurse registration numbers are assigned and published by the College of Nurses of Ontario (CNO), which maintains the public register they come from. The namespace they are carried in was registered by the Ontario Ministry of Health and Long-Term Care, with eHealth Ontario as the responsible party, in Canada Health Infoway's Canadian URI Registry; the address above is the preferred form that registry publishes for it. One namespace carries the nurse practitioner, registered nurse and registered practical nurse credentials, so a number alone does not say which. This specification declares the namespace only and enumerates no numbers. For the register see https://www.cno.org, and for the namespace entry see https://simplifier.net/canadianuriregistry.
Where this specification uses it: Practitioner Profile
Ontario physician licence number¶
Ontario physician registration numbers are assigned and published by the College of Physicians and Surgeons of Ontario (CPSO), which maintains the public register they come from. The namespace they are carried in was registered by the Ontario Ministry of Health and Long-Term Care, with eHealth Ontario as the responsible party, in Canada Health Infoway's Canadian URI Registry; the address above is the preferred form that registry publishes for it. This specification declares the namespace only and enumerates no numbers. For the register see https://www.cpso.on.ca, and for the namespace entry see https://simplifier.net/canadianuriregistry.
Where this specification uses it: Practitioner Profile
Where else these terms travel¶
The licence statement for this specification as a whole is carried in the ImplementationGuide.copyright element, which compiles into every StructureDefinition and ships inside package.tgz. A tool that loads the package without ever visiting this site still gets it. The per-terminology statements above are rendered from the specification's terminology usage and are published here and on the IG Publisher render.