...
Infoway's Canadian Standards Release Centre maintains ValueSets in partnership with with Provincial, Territorial, and Federal e-Health agencies from across Canada working towards the successful implementation of National digital health solutions. These ValueSets are hosted on the Terminology server for jurisdictions and organizations to utilize. ValueSets are hosted on Infoway's FHIR Terminology Server.
ValueSets vs Subsets
The term “Subset” is used to identify a set where all elements are also contained in another set. In other words, if you have a set A, a subset of A (denoted B) includes only elements that are also in A. These subsets include constrained lists of allowable values or terminology from the source code systems (i.e. SNOMED CT Canadian Edition, pCLOCD, UCUM, SCP or HL7).
The terms “ValueSet” and “Subset” are used interchangeably. Specific to SNOMED CT (Systematized Nomenclature of Medicine Clinical Terms), a reference set (or refset) is a standardized format used to maintain and distribute a curated list of references to SNOMED CT components.
Types of ValueSets
ValueSets can be grouped into categories. The categories listed below are different ways of looking at ValueSets and are not mutually exclusive:
...
- Manual inclusion, using search and browse methods
- An existing ValueSet, used as a starting point for further manual inclusion and update
- Lexical queries, to identify candidate members, followed by manual verification and update
- Hierarchical queries, to identify descendants of a given concept (e.g. descendants of <73211009 |diabetes mellitus|)
- Attribute queries, to identify concepts with a specific attribute value (e.g. disorders with a finding site of 80891009 |heart structure|
- SNOMED CT queries, using the SNOMED CT Expression Constraint or Query languages, which offer additional query functionality.
pan Canadian ValueSets Maintenance
pan-Canadian ValueSet Maintenance
The ongoing maintenance of Pan-Canadian value sets is a critical component of ensuring their quality, relevance, and effectiveness in supporting national interoperability. Managed by the CSRC, this process involves regular updates against standards release cycles. The process is responsive to change requests from implementers to ensure terminologies continue to evolve and remain fit for purpose.
Pan-Canadian guidelines specify how value sets should be created, curated, and maintained to ensure their accuracy and relevance across jurisdictions. They must include concepts that are applicable to at least two or more provinces or territories and align with nationally or federally mandated initiatives, such as the Pan-Canadian Health Data Content Framework or the Shared Pan-Canadian Interoperability Roadmap.
Infoway has many ValueSets that have been developed over time by Canadians for Canadians. These “fit for use” ValueSets are intended to be a pan-Canadian “starter set” of content. The ValueSets are maintained by Infoway, published in the Terminology Gateway. The pan-Canadian ValueSets may contain content from international terminologies and content specific to Canada, which is dependent on the international version. The pan-Canadian ValueSets are reviewed on an annual basis, SNOMED CT Canadian edition ValueSets updated are aligned to the release of SNOMED CT Canadian edition releases.
Two ValueSets HealthCareProviderRoleType and QualifiedRoleType use the SC code systems (SCPQUAL, SCPTYPE) (the "SC Code Systems") which was a code system developed by Canada Health Infoway Inc. (Infoway) to address local requirements in Canada. SC was an abbreviation for "Standards Collaborative"
...
- In the first year, the ValueSet will be inactivated (Depreciated) if not used in the previous year and no objections are received to an announcement is made on the Health Terminologies and HL7 forums. It will still be published on the Terminology Gateway, but not visible unless the ‘Inactive’ subset status is specifically chosen. If we do not receive a response to the request for a status of a ValueSet after 30 Days, we will mark it for inactivation after 30 days and inactivate it.
- At the end of the first year, if the ValueSet is still no longer in use, it will be marked as retired and no longer available in the Terminology Gateway
Additional Terminology Subsets
Infoway supports organizations and Jurisdictions to publish their Terminology Artefacts on the Terminology Gateway. Once published, jurisdictions are requested to maintain their ValueSets as part of the Infoway Maintenance Cycle.
These ValueSets may be leveraged by other organizations and jurisdictions to support interoperability EHR solutions in their organization or jurisdiction.
The ValueSets developed are vendor-neutral, they support interoperability and decrease the cost of creating and maintaining a new ValueSet.
The ValueSet maintenance for Additional Terminology Content is also a two-year process
- Jurisdictions and organizations are accountable for the quality and maintenance of ValueSets or other artifacts shared on the Terminology Gateway
- Each year, the Infoway SME will contact the ValueSet owner named for the ValueSet listed on the Terminology Gateway
- The contact will be asked to review their respective ValueSet and asked if this is all good. If it is still good, then the reviewed date is updated. If there are changes then the ValueSet owner will make the changes to the ValueSet and submit them. If we do not receive a response to our request for a status of a ValueSet, we will mark it for inactivation after 30 days
Where to find the ValueSet Template
Download the ValueSet Template from Informs Informs or from here
How to create New ValueSets
- Download the ValueSet Template from InfoRMS Subset RFC project
- Complete the Subset Definition template. Refer to the "How to Complete" tab for guidance or contact [email protected] for assistance
- All Field in Red are mandatory and must be completed
- Refer to the Naming Convention for pan-Canadian Subsets Sets and Valuesets to create a name for the subset definition
- Request the Subset ValueSet ID which is an OID, but if you are the owner of the Subset, you may provide your own unique identifier
- Ensure that the Subset ValueSet name and ID is not used in used by checking the OID's for subsets
- If the subsets is owned by you ( Additional Terminology Content) then a logo can be added which must be a .png or .gif which should be attached to the Subset request
- Select the Codesystem(s) (SNOMED CT Canadian edition, LOINC, UCUM, HL7) You may have more than one to cover a clinical domain in some cases and if you need further guidance, contact [email protected]
- Submit in InfoRMS for Review
How to Change a
...
Valuesets
- Download the subset ValuSet from the Terminology Gateway in Server in Excel format
- Update the fields in the downloaded file with the new information on the Subset Definition Tab
- An update can be done to achieve the following: Add a new code, modify a term or a code and inactivate a term or a code
- If Changes are made to the display names, the terminology Gateway will provide you with a Change Log,there is an option to view the comparison from last version of the valueset which should reflect all changes applied to the subset.
- It may be required to validate the status of all other codes and terms in the subset before re-publishing if the terminology has been updated since the last release
- If the changes were only on the Concept Tab, change the «Subset version» to reflect the date of publication
- If the terminology versions have changed, update the «Terminology version» field
- If the change is to the Subset name or Subset ID (OIDS), which is always unique to each subset, contact the HL7 OIDS resource at [email protected] , to confirm the OID s unique. If the OID is unique then it can be assigned by the Subset RFC SME
- In InfoRMS, select the "Update Subset" as the issue type and complete the mandatory fields identified with an asterisk "*"
- Attach the completed Subset RFC template
- Once the subset ValueSet is updated and finalized, it will be copied into the be loaded to the UAT environment of the Terminology GatewayServer for QA
How to Retire a
...
ValueSet
- Download the subset from the Terminology GatewayServer in Excel format
- Create a new Subset RFC by selecting the «Create» button
- Fill in the UI information and attach the Batch template
- Complete the mandatory fields for the Requestor in InfoRMS
- Add a comment on the Subset RFC, the subset will be deprecated in one (1) year from now.
- When the one year is reached, add a comment on the RFC this subset is now Deprecated
- Use the InfoScribe page to identify the Inactivated subsets that will be deprecated the following year
- After one year ask IMT will remove the subset from the database
...
Please refer to the Naming Convention for pan-Canadian Subsets and Valuesets.pdf document for detailed rules for consistent naming of pan-Canadian Subsets and value setsValueSets