Terminology > 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.
* Please note that these value sets are created by Ontario Health
** Please note that use of terminology subsets hosted on Canada Health Infoway Terminology Gateway is required in order to comply with this interoperability specification. Access to and use of SNOMED CT and other subsets on Canada Health Infoway Terminology Gateway requires an Infoway account with acceptance of the SNOMED CT license agreements
Value Sets referenced by this implementation guide:
| Profile - Element | Binding Strength | Value Set (Code System) | Description |
|---|---|---|---|
| Patient - Patient.gender RelatedPerson - RelatedPerson.gender | Required | AdministrativeGender (HL7 FHIR) | The gender of a person used for administrative purposes. |
| RelatedPerson - RelatedPerson.address.type | Required | AddressType (HL7 FHIR) | The type of an address (physical / postal). |
| RelatedPerson - RelatedPerson.address.use | Required | AddressUse (HL7 FHIR) | The use of an address. |
| Practitioner - Practitioner.telecom.system RelatedPerson - RelatedPerson.telecom.system | Required | ContactPointSystem (HL7 FHIR) | Telecommunications form for contact point. |
| Practitioner - Practitioner.telecom.use RelatedPerson - RelatedPerson.telecom.use | Required | ContactPointUse (HL7 FHIR) | Use of contact point. |
| Consent - Consent.provision.class | Extensible | ConsentContentClass* (OH) | This value set includes the FHIR resource types, along with some other important content class codes. |
| Consent - Consent.status | Required | ConsentState (HL7 FHIR) | Indicates the state of the consent. |
| Consent - Consent.scope | Extensible | ConsentScopeCodes (HL7 FHIR) | This value set includes the four Consent scope codes. |
| Consent - Consent.category | Extensible | ConsentCategoryCodes (HL7 FHIR) | This value set includes sample Consent Directive Type codes, including several consent directive related LOINC codes. |
| Consent - Consent.provision.type | Required | ConsentProvisionType (HL7 FHIR) | How a rule statement is applied, such as adding additional consent or removing consent. |
| OperationOutcome - OperationOutcome.issue.severity | Required | IssueSeverity (HL7 FHIR) | How the issue affects the success of the action. |
| OperationOutcome - OperationOutcome.issue.code | Required | IssueType (HL7 FHIR) | A code that describes the type of issue. |
| Binary - Binary.contentType | Required | Mime Types (HL7 FHIR) | This value set includes all possible codes from BCP-13 (http://tools.ietf.org/html/bcp13). |
| Consent - Consent.provision.actor.role | Extensible | 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.purpose | Required | OverrideReason (HL7 v3) | 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). |
Powered by SIMPLIFIER.NET