This version of the PS-CA Implementation Guide has been superseded by a newer version. Other releases of the PS-CA Implementation Guide may be found on a table on the Home Page of this Project.
Terminology
The profiles in this specification leverage value sets from both the IPS-UV guide as well as value sets that have been developed according to the principles identified in the Terminology Approach.
Usage Guidance:
Several ValueSets are not available at their canonical URL (e.g., CVC published value sets) or on the terminology servers used in implementation guide publication (i.e., 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, the Terminology Gateway or Canadian Vaccine Catalogue. When terminology is not readily available as FHIR® Release 4 ValueSets or CodeSystems, implementers should work with terminology producers to identify options.
Terminology owners often evolve their code systems and value sets over time: retiring concepts, adding new ones, modifying relationships, etc. Terminology content should be "current at time of use," except when specific versions of CodeSystems or ValueSets are identified within PS-CA. Implementations should be cautious of recognizing only the terminology in effect at the time of publication of the PS-CA Implementation Guide, or only the terminology in effect at time of system implementation. PS-CA Patient Summary documents should use current-at-time-of-creation terminology. However, since Patient Summary documents may have an extended life, recipient systems should be lenient in accepting out-of-date codes.
Value Sets
The table below indicates the various levels of terminology included in PS-CA. Value sets are grouped under three columns:
Global Value Sets: These are value sets that are either required by the HL7® FHIR® specification or are proposed by the IPS-UV specification due to their increased likelihood to be recognized/accessible internationally.
- HL7: Value sets required for data to be exchanged in FHIR are indicated by an (*). In cases where the value is captured from a different terminology, the captured terminology would be supplied as an alternative coding
- IPS: Value sets proposed by the IPS that leverage existing multilingual, globally accessible terminologies that are intended to facilitate interoperable international exchange. IPS defines SNOMED CT as a primary terminology, but also applies other international terminologies (LOINC, EDQM, etc.) in cases where they are deemed more appropriate for progressing the goals of the IPS. Implementers are encouraged to review IPS General Principles.
Proposed Pan-Canadian Value Sets: These are value sets that are proposed by the PS-CA as the national standardized terminologies that implementers are encouraged to align to. SNOMED CT Canadian Edition (SNOMED CT-CA) is the terminology generally recommended for use in Canada, but in some cases the PS-CA will also propose the use of other terminologies (e.g., CVC, CCDD, etc.) that have widespread adoption across Canada.
- Note: The Pan-Canadian value sets are identified as the preferred value sets for this release (except where another value set is required by HL7 FHIR). While adoption of the global value sets is critical for global interoperability, recent feedback from participating jurisdictions has outlined the need to prioritize domestic jurisdictional exchange over global exchange in early versions of the specification. Implementers should align to the proposed pan-Canadian value sets with an understanding that later releases of PS-CA and IPS may apply unique terminology preferences and expectations for systems acting as gateways or portals for international exchange.
Local Value Sets: These are examples of value sets and local terms or non-standardized value sets that were noted in use within the participating jurisdictions. While implementers are encouraged to align to the proposed pan-Canadian value sets, they should be aware that patient summaries may contain concepts from these terminologies.
- Note: This column excludes terminologies that have established mappings to proposed value sets (e.g., DIN codes included in CCDD, or First Data Bank codes mapped to CCDD as part of established workflows) as well as terminologies that are considered local terms/non-standardized value sets. Jurisdictions that require assistance in hosting their local value sets in a location that vendors and implementers can easily review should reach out to standards@infoway-inforoute.ca.
Bolded notes are used in the below to relay where value sets included in previous releases have been folded into an existing slice.
| Profile | Element | Global Value Sets (if applicable) | Proposed Pan-Canadian Value Sets | Local Value Sets |
|---|---|---|---|---|
| AllergyIntolerance (PS-CA) | clinicalStatus |
AllergyIntoleranceClinicalStatusCodes* (HL7) (Required) | AllergyIntoleranceStatusCode (SNOMED CT-CA) (Slice) | v3.ActStatus (HL7 v3) (Slice) |
| AllergyIntolerance (PS-CA) | verificationStatus |
AllergyIntoleranceVerificationStatusCodes* (HL7) (Required) | AllergyIntoleranceStatusCode (SNOMED CT-CA) (Slice) | - |
| AllergyIntolerance (PS-CA) | code |
AllergyintolerancesubstanceconditionGPS (IPS/SNOMED CT GPS) (Slice) | SubstanceAndPharmaceuticalBiologicProductCode (SNOMED CT-CA) (Preferred Slice) | ICD10CAAllCode (ICD-10 CA) (Slice) |
| NoAllergiesInfoUvIps (IPS) (Slice), Note A | ||||
| AllergyIntolerance (PS-CA) | reaction.manifestation |
AllergyReactionGpsUvIps (IPS/SNOMED CT GPS) (Slice) | ClinicalFindingCode (SNOMED CT-CA) (Preferred Slice) | - |
| Condition (PS-CA) | severity |
ProblemSeverityUvIps (IPS/LOINC) (Slice) | SeverityCode (SNOMED CT-CA) (Preferred Slice) | - |
| Condition (PS-CA) | code |
CoreProblemListFindingSituationEventGpsUvIps (IPS/SNOMED CT GPS) (Slice) | ClinicalFindingCode (SNOMED CT-CA) (Preferred Slice) | ICD9CMAllCode (ICD-9 CM) (Slice) |
| NoProbsInfoUvIps (IPS) (Slice) | ICD10CAAllCode (ICD-10 CA) (Slice) | |||
| BC Health Concerns and Diagnosis Value Set uses values covered under SNOMED CT, ICD-9 CM, ICD-10 CA slices | ||||
| Condition (PS-CA) | bodySite |
- | AnatomicalOrAcquiredBodyStructureCode (SNOMED CT-CA) (Preferred Slice) | - |
| Immunization (PS-CA) | vaccineCode |
VaccinesUvIps (IPS/SNOMED CT) (Slice) | CVCTradename (CVC) (Preferred Slice) OR | - |
| VaccinesGpsUvIps (IPS/SNOMED CT GPS) (Slice) | CVCGeneric (CVC) (Preferred Slice) | |||
| WhoAtcUvIps (IPS/WHO) (Slice) | ||||
| NoImmunizationInfoUvIps (IPS) (Slice) | ||||
| Immunization (PS-CA) | site |
TargetSiteCodeUvIps (IPS/SNOMED CT) (Slice) | CVCAnatomicalSite (CVC) (Preferred Slice) | HumanSubstanceAdministrationSite - V3 (HL7 v3) (Slice) |
| Immunization (PS-CA) | route |
RouteOfAdminUvIps (IPS/EDQM) (Slice) | CVCRouteOfAdmin (CVC) (Preferred Slice) | v3.RouteOfAdministration (HL7 v3) (Slice) |
| Immunization (PS-CA) | protocolApplied .targetDisease |
TargetDiseasesUvIps (IPS/SNOMED CT) (Slice) | CVCDisease (CVC) (Preferred Slice) | - |
| TargetDiseasesGpsUvIps (IPS/SNOMED CT GPS) (Slice) | ||||
| Medication (PS-CA) | code |
WhoAtcUvIps (IPS/WHO) (Slice) | PrescriptionMedicinalProduct (PrescribeIT/CCDD) (Preferred Slice) | HCNPN (Health Canada) (Slice). Use of DIN, FDB (HICL/HIC4/SEQN), etc. is covered under CCDD, BC Medication Superset still in development |
| MedicationSnomedCodesUvIps (IPS/SNOMED CT) (Slice) | ||||
| Medication (PS-CA) | form |
DoseFormUvIps (IPS/EDQM) (Slice) | PharmaceuticalDoseFormCode (SNOMED CT-CA) (Preferred Slice) | PrescriptionDrugForm (PrescribeIT/HL7 v3) (Slice) |
| Medication (PS-CA) | ingredient .itemCodeableConcept |
Note B | DrugOrMedicamentSubstanceCode (SNOMED CT-CA) (Preferred Slice) | Use of DIN, FDB (HICL/GCN), etc. which is covered under CCDD |
| MedicationRequest (PS-CA) | medicationCodeableConcept |
- | PrescriptionMedicinalProduct (PrescribeIT/CCDD) (Preferred Slice) | - |
| MedicationRequest (PS-CA) | dosageInstruction.route |
RouteOfAdminUvIps (IPS/EDQM) (Slice) | RouteOfAdministration (SNOMED CT-CA) (Preferred Slice) | PrescriptionRouteOfAdministration (PrescribeIT/HL7 v3) (Slice) |
| MedicationStatement (PS-CA) | medicationCodeableConcept |
NoMedsInfoUvIps (IPS) (Extensible Slice) | Note C | HCNPN (Health Canada) (Slice). Use of DIN, FDB (HICL/HIC4/SEQN/GCN), etc. is covered under CCDD |
| MedicationStatement (PS-CA) | dosage.route |
RouteOfAdminUvIps (IPS/EDQM) (Slice) | RouteOfAdministration (SNOMED CT-CA) (Preferred Slice) | PrescriptionRouteOfAdministration (PrescribeIT/HL7 v3) (Slice) |
| Patient (PS-CA) | contact.relationship |
PatientContactRelationship (HL7) (Extensible) | - | - |
| PersonalRelationshipUvIps (IPS) (Required) | ||||
| Procedure (PS-CA) | code |
NoProceduresInfoUvIps (IPS) (Slice), Note D | ProcedureCode (SNOMED CT-CA) (Preferred Slice) | CCIAllCode (Slice) |
| ICD9CMAllCode (ICD-9 CM) (Slice) | ||||
| ICD10CAAllCode (ICD-10 CA) (Slice) |
Note A The AllergyIntoleranceSubstanceConditionUvIps value set put forth in IPS-UV was not included in the table above because it is made up of SNOMED CT values are included in the SNOMED CT-CA slice
Note B The ActiveSubstancesUvIps value set put forth in IPS-UV was not included in the table above because it is made up of SNOMED CT values are included in the SNOMED CT-CA slice
Note C The NoMedsInfoUvIps value set put forth in IPS-UV is carried over on MedicationCodeableConcept for alignment purposes. Because the IPS-UV value set on this slice is extensible, it can be used to supply other medication codes when only a simple code is available (e.g., a medication resource is not possible). See list of value sets used for medication.code
Note D The ProceduresUvIps value set put forth in IPS-UV was not included in the table above because it is made up of SNOMED CT values are included in the SNOMED CT-CA CTCA slice
Code Systems
The following code systems were developed in the PS-CA Implementation Guide:
Additional Terminology Resources
Global Patient Set (GPS) Value Set
For the convenience of implementers, the full SNOMED CT Global Patient Set (GPS) is available on the HL7 terminology server terminology.hl7.org (THO) as an extensionally defined (i.e., enumerated) FHIR ValueSet resource.
An intensionally defined (i.e., query based) FHIR ValueSet resource and contents (value set expansion results) of the FHIR implicit value set based on the SNOMED CT GPS set may also be obtained from the SNOMED International Snowstorm FHIR server via: https://snowstorm-fhir.snomedtools.org/fhir/ValueSet?url=http://snomed.info/valueSet/GPS&_pretty=true https://snowstorm-fhir.snomedtools.org/fhir/ValueSet/$expand?url=http://snomed.info/sct?fhir_vs=refset/787778008&_pretty=true
Note: Be aware of potential version differences between the GPS value set representations and value sets hosted by HL7 and SNOMED International. See Terminology Management on Terminology Approach
Concept Maps
Implementers are encouraged to review the ConceptMaps defined in the IPS-UV Implementation Guide: