Table of Contents > Terminology


Various coded values which are used to describe clinical concepts within health records as well as codes used within messages to meet the structural requirements of interfaces.

*Please note that these are Code System and/or Value set created by eHealth Ontario

**Please note that access and use of SNOMED CT subsets on Canada Health Infoway Terminology Gateway requires an Infoway account with acceptance of the SNOMED CT license agreements 

Value Sets defined by this implementation guide:

Value Set Description Profile Binding Strength
AddressType Distinguishes between physical addresses (those you can visit) and mailing addresses (e.g. PO Boxes and care-of addresses). Most addresses are both. Organization: Organization.address.type
Patient: Patient.address.type
AddressUse The purpose of this address. Organization: Organization.address.use
Patient: Patient.address.use
AdministrativeGender The gender of a person used for administrative purposes. Patient: Patient.gender,
Practitioner: Practitioner.gender
AbsentorUnknownAllergies Absent or Unknown Allergies. Code for an allergy or intolerance statement (either a positive or a negated/excluded statement). This describes a categorical negated statement (e.g., "No known allergy"). AllergyIntolerance: AllergyIntolerance.absentOrUnknownAllergies Required
AllergyIntoleranceCode Code for an allergy or intolerance statement (either a positive or a negated/excluded statement). This may be a code for a substance or pharmaceutical product that is considered to be responsible for the adverse reaction risk (e.g., "Latex"), an allergy or intolerance condition (e.g., "Latex allergy"), or a negated/excluded code for a specific substance or class (e.g., "No latex allergy") or a general or categorical negated statement (e.g., "No known allergy", "No known drug allergies"). AllergyIntolerance: AllergyIntolerance.code Extensible
AllergyIntoleranceStatus The clinical status of the allergy or intolerance. AllergyIntolerance: AllergyIntolerance.clinicalstatus Required
AppointmentStatus The free/busy status of an appointment. Appointment: Appointment.status Required
BundleType Indicates the purpose of this bundle - how it is intended to be used. Bundle: Bundle.type Required
CommunicationBarrier * Contains codes required to identify if the patient speaks/understands an offical language (english/french), or if she/he does not and an interpretor is required. Patient: Patient.communication.extension:communication-barrier.valueCoding Extensible
CommunicationCategory * Codes for general categories of communications such as alerts, instructions, etc. Communication: Communication.category Extensible
CommunicationStatus The status of the transmission. Communication: Communication.status Required
ConditionCategory A category assigned to the condition. Condition: Condition.category Extensible
ConditionClinicalStatus The clinical status of the condition. Condition: Condition.clinicalStatus Required
ConditionCode** Represents the ‘Most Commonly Used’ clinical problems, conditions, diagnoses, symptoms, findings and complaints, as interpreted by the provider. Concepts from CHI HealthConcernCodeSubsetCommonlyUsed SNOMED CT Subset. Condition: Condition.code Extensible
ConditionSeverity A subjective assessment of the severity of the condition as evaluated by the clinician. Condition: Condition.severity Preferred
ConditionStage A simple summary of the stage such as "Stage 3". The determination of the stage is disease-specific. Condition: Condition.stage.summary Extensible
ConditionVerificationStatus The verification status to support the clinical status of the condition. Condition: Condition.verificationStatus Required
ConsentCategory A classification of the type of consents found in the statement. This element supports indexing and retrieval of consent statements. Consent: Consent.category Extensible
ConsentContentClass The class of information covered by this rule. The type can be a FHIR resource type, a profile on a type, or a CDA document, or some other type that indicates what sort of information the consent relates to. Consent: Consent.provision.class Extensible
ConsentScope This value set includes the four Consent scope codes. Consent: Consent.scope Extensible
ConsentStateCode Indicates the state of the consent. Consent: Consent.status Required
ConsentProvisionType How a rule statement is applied, such as adding additional consent or removing consent. Consent: Consent.provision.type Required
ContactEntityType Indicates a purpose for which the contact can be reached. Organization: Extensible
ContactRelationship The nature of the relationship between the patient and the contact person. Patient: Extensible
ContactPointSystem Telecommunications form for contact point. MessageHeader:
Organization: Organization.telecom.system
Patient: Patient.telecom.system
ContactPointUse Use of contact point. MessageHeader:
Organization: Organization.telecom.use
Patient: Patient.telecom.use
DaysOfWeek Indicates which days of the week are available between the start and end Times. Location: Location.hoursOfOperation.daysOfWeek Required
DocumentReferenceStatus The status of this document reference. DocumentReference: DocumentReference.status Required
HealthServiceCategory** A code that classifies the service for searching, sorting and display purposes (e.g. "Surgical Procedure"). ServiceRequest: ServiceRequest.category Extensible
HealthServiceOffering** A code that represents the care procedures performed by a Provider for a particular service (i.e. .procedure, diagnostic investigation, or panel of investigations) that have been requested. Concepts from CHI InterventionCodeSubsetCare SNOMED CT subset. ServiceRequest: ServiceRequest.code Extensible
HTTPVerb In a transaction or batch, this is the HTTP action to be executed for this entry. In a history bundle, this indicates the HTTP action that occurred. Bundle: Bundle.entry.request.method Required
HumanLanguages * Languages understood or supported by patients and organizations. Patient: Patient.communication.language,
Practitioner: Practitioner.communication
IdentifierType * Codes supported by eHealth Ontario that can be used to determine which identifier to use for a specific purpose. This is an extension of the core FHIR value set.. MessageHeader: MessageHeader.extension:ReferralIdentifier
Patient: Patient.identifier.type
LocationPhysicalType This example value set defines a set of codes that can be used to indicate the physical form of the Location. Location: Location.physicalType Example
LocationStatus Indicates whether the location is still in use. Location: Location.status Required
ManifestationOrSymptom A manifestation or symptom that led to the recording of this condition. Condition: Condition.evidence.code Extensible
MaritalStatus This value set defines the set of codes that can be used to indicate the marital status of a person.The specific meanings of these codes can vary somewhat by jurisdiction and implementation so caution should be used when determining equivalency. Patient: Patient.maritalStatus Extensible
MessageEventCode* Code that identifies the event this message represents and connects it with its definition. Events defined as part of the FHIR specification.Alternatively uri to the EventDefinition. MessageHeader: MessageHeader.eventCoding.code Required
MessageReasonEncounter Coded indication of the cause for the event - indicates a reason for the occurrence of the event that is a focus of this message. MessageHeader: MessageHeader.reason Example
NarrativeStatus The status of the narrative - whether it's entirely generated (from just the defined data or the extensions too), or whether a human authored it and it may contain additional data. Appointment: Appointment.text.status Required
OperationalStatus FHIR Value set/code system definition for HL7 v2 table 0116 (BED STATUS). Location: Location.operationalStatus Preferred
OperationOutcomeCode Describes the type of the issue. The system that creates an OperationOutcome SHALL choose the most applicable code from the IssueType value set, and may additionally provide its own code for the error in the details element. OperationOutcome: OperationOutcome.issue.code Required
OperationOutcomeDetails Additional details about the error. This may be a text description of the error or a system code that identifies the error. OperationOutcome: OperationOutcome.issue.details Example
OperationOutcomeSeverity Indicates whether the issue indicates a variation from successful processing. OperationOutcome: OperationOutcome.issue.severity Required
OrganizationContactPurpose Indicates a purpose for which the contact can be reached. Organization: Extensible
OrganizationType This example value set defines a set of codes that can be used to indicate a type of organization. Organization: Organization.type Example
ParticipationStatus Participation status of the actor. Appointment: Appointment.participant.status Required
PatientContactRelationship * The nature of the relationship between the patient and the contact person. Patient: Extensible
PractitionerQualification** A role type that is used to categorize an entity that delivers health care in an expected and professional manner to an entity in need of health care services. Examples: Registered Nurse, Chiropractor, Physician, Custodial Care Clinic. Concepts from CHI HealthCareProviderRoleType pan-Canadian subset. Practitioner: Practitioner.qualification.code Extensible
PractitionerSpecialty ** This is the code representing the clinical specialty of the clinician or provider who interacted with, treated, or provided a service to/for the patient. PractitionerRole: PractitionerRole.specialty Extensible
PractitionerRoleCode This value set defines a set of codes that can be used to indicate the role of a Practitioner PractitionerRole: PractitionerRole.code Extensible
QuestionnaireResponseStatus The position of the questionnaire response within its overall lifecycle. QuestionnaireResponse: QuestionnaireResponse.status Required
ReferralDocumentType Specifies the particular kind of document referenced (e.g. History and Physical, Discharge Summary, Progress Note). This usually equates to the purpose of making the document referenced. DocumentReference: DocumentReference.type Extensible
ReferralSourceTypes This value set is for Referral Source Type identification. Only one referral routing object is expected. MessageHeader: MessageHeader.type.extension:RoutingOptions Extensible
RequestIntent Codes indicating the degree of authority/intentionality associated with a request. ServiceRequest: ServiceRequest.intent Required
RequestPriority Identifies the level of importance to be assigned to actioning the request. ServiceRequest: ServiceRequest.priority Required
RequestStatus Codes identifying the lifecycle stage of a request. ServiceRequest: ServiceRequest.status Required
SearchEntryMode Why this entry is in the result set - whether it's included as a match or because of an _include requirement, or to convey information or warning information about the search process. Bundle: Required
TaskBusinessStatus * Contains business-specific nuances of the business state. Task: Task.businessStatus.coding.code Example
TaskCode* Codes indicating the type of action that is expected to be performed. Task: Task.code Extensible
TaskIntent Distinguishes whether the task is a proposal, plan or full order. Task: Task.intent Required
TaskStatus The current status of the task. Task: Task.status Required