visit the hl7 website
Ontario Provincial Consent Override Interface HL7® FHIR® Implementation Guide v1.0.0-draft1
fhir-logo
  • Index
  • Home
    • Home
    • Introduction
    • Relationship to Other Specifications
    • Scope
    • Glossary
  • Business Context
    • Business Context
    • Business Model
    • Business Data
    • Use Cases
    • Business Rules
  • Technical Context
    • Technical Context
    • Implementer Responsibility
    • Conformance Rules
    • Connectivity Summary
  • FHIR Artifacts
    • FHIR Artifacts
    • Interactions
    • Profiles
    • Extensions
    • Terminology
    • System URIs
    • Examples
    • Capability Statement
    • Response Handling
    • Downloads
  • Change Log
    • Change Log
    • Known Issues & Future Developments
    • Revision History
    1. Index
    2. FHIR Artifacts
    3. Terminology

For a full list of available versions, see the Directory of published versions

4.4. Terminology

This section lists the coded value sets that are referenced by the FHIR profiles in this implementation guide. These coded values are used to describe and standardize clinical concepts and other data content within health records.

4.4.1. Usage Guidance

Several ValueSets are not available at their canonical URL (e.g., Canada Health Infoway-published value sets) or on the terminology servers used in implementation guide publication (e.g., tx.fhir.org). Primarily, this impacts validation against Canada Health Infoway-hosted ValueSets during the development of derived Implementation Guides. This does not affect deployed systems as these instances will be validated against loaded terminology. For several of these ValueSets, "stub" resources have been created to stand-in for the unresolvable ValueSets. These stub ValueSets include pointers to the locations where the full value sets can be downloaded. Current guidance is to manually download the value sets from, for example, Infoway's Terminology Server, or Health Canada (e.g. Licensed Natural Health Products). When terminology is not readily available as FHIR® Release 4 ValueSets or CodeSystems, implementers should work with terminology producers to identify options.

  • Please note that these value sets and/or code systems are created by Ontario Health.
  • Use of terminology subsets hosted on Canada Health Infoway Terminology Server is required in order to comply with this interoperability specification. Access to and use of SNOMED CT and other subsets on Infoway's Terminology Server requires an Infoway account with acceptance of the SNOMED CT license agreements.

4.4.2. Value Sets Referenced by this IG

Value Set (Code System Source) Description Profile Binding Strength
AdministrativeGender (HL7 FHIR) The gender of a person used for administrative purposes. Patient  - Patient.gender RelatedPerson  - RelatedPerson.gender Required
AddressType (HL7 FHIR) The type of an address (physical / postal). RelatedPerson  - RelatedPerson.address.type Required
AddressUse (HL7 FHIR) The use of an address. RelatedPerson  - RelatedPerson.address.use Required
ContactPointSystem (HL7 FHIR) Telecommunications form for contact point. Practitioner  - Practitioner.telecom.system RelatedPerson  - RelatedPerson.telecom.system Required
ContactPointUse (HL7 FHIR) Use of contact point. Practitioner  - Practitioner.telecom.use RelatedPerson  - RelatedPerson.telecom.use Required
ConsentContentClass* (Ontario Health) Codes representing data domains for PCOI including OH Clinical Data Foundation, and legacy repositories. Consent  - Consent.provision.class Required
ConsentState (HL7 FHIR) Indicates the state of the consent. Consent  - Consent.status Required
ConsentScopeCodes (HL7 FHIR) This value set includes the four Consent scope codes. Consent  - Consent.scope Extensible
ConsentCategoryCodes (HL7 FHIR) This value set includes sample Consent Directive Type codes, including several consent directive related LOINC codes. Consent  - Consent.category Extensible
ConsentProvisionType (HL7 FHIR) How a rule statement is applied, such as adding additional consent or removing consent. Consent  - Consent.provision.type Required
IssueSeverity (HL7 FHIR) How the issue affects the success of the action. OperationOutcome  - OperationOutcome.issue.severity Required
IssueType (HL7 FHIR) A code that describes the type of issue. OperationOutcome  - OperationOutcome.issue.code Required
Mime Types (HL7 FHIR) This value set includes all possible codes from BCP-13 (http://tools.ietf.org/html/bcp13). Binary  - Binary.contentType Required
SecurityRoleType (HL7 FHIR) This value set contains example structural roles. In general, two types of roles can be distinguished: structural roles and functional roles. Structural Roles reflect human or organizational categories (hierarchies), and describe prerequisites, feasibilities, or competences for actions. Functional roles are bound to the realization or performance of actions. Consent  - Consent.provision.actor.role Extensible
OverrideReason* (Ontario Health) The basis upon which the health information custodian is collecting personal health information, despite the contents of a privacy consent directive, as allowed by HIPA (Ontario Bill 119, Section 55.7). Consent  - Consent.provision.purpose Required
Version: 1.0.0 FHIR Version: R4.0.1

Powered by SIMPLIFIER.NET

HL7® and FHIR® are the registered trademarks of Health Level Seven International