Page History

...

1. Download the subset Template from InfoRMS Subset RFC project
2. Complete the Subset Definition template. Refer to the "How to Complete" tab for guidance or contact [email protected] for assistance
3. All Field in Red are mandatory and must be completed
4. Refer to the Naming Convention for pan-Canadian Reference Subsets Sets and Valuesets to create a name for the subset definition
5. Request the Subset ID which is an OID, but if you are the owner of the Subset, you may provide your own unique identifier
6. Ensure that the Subset name and ID is not used in used by checking the OID's for subsets
7. 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 
8. Select the Codesystem(s) (SNOMED CT, 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] 
9. Submit in InfoRMS for Review

...

1. Download the subset from the Terminology Gateway in Excel format
2. Update the fields in the downloaded file with the new information on the Subset Definition Tab
3. 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
4. If Changes are made to the display names, the terminology Gateway will provide you with a Change Log, which should reflect all changes applied to the subset
5. 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
   1. If the changes were only on the Concept Tab, change the «Subset version» to reflect the date of publication
   2. If the terminology versions have changed, update the «Terminology version» field
   3. If the change is to the Subset name or Subset ID (OIDS), which is always unique to each subset, contactJoannie Harper  the HL7 OIDS resource at [email protected] , to confirm the OID s unique. If the OID is unique  unique then it can be assigned by the Subset RFC SME ( Anil Patel)
6. In InfoRMS, select the "Update Subset" as the issue type and complete the mandatory fields identified with an asterisk "*"
7. Attach the completed Subset RFC template
8. Once the subset is updated and finalized, it will be copied into the be loaded to the UAT environment of the Terminology Gateway for QA

How to Retire a subsets

1. Download the subset from the Terminology Gateway in Excel format
2. Create a new Subset RFC by selecting the «Create» button
3. Fill in the UI information and attach the Batch template 
4. Complete the mandatory fields for the Requestor in InfoRMS
5. Add a comment on the Subset RFC, the subset will be deprecated in one (1) year from now.
6. When the one year is reached, add a comment on the RFC this subset is now Deprecated
7. Use the InfoScribe page to identify the Inactivated subsets that will be deprecated the following year
8. After one year ask IMT will remove the subset from the database

...

QA check covers the subset's metadata information and the terminology values, which include the correctness of concepts selected and the appropriate representation of the components as per the subset's template. It also covers basics data 

1. For pan Canadian Subset which is found in the Terminology Gateway under the Subsets section. The QA is done by the Subset SME only and the standards team. It does not involve any external stakeholder.
2. Additional Terminology Content Subsets in the Terminology Gateway require the Subset owner to validate the contents, in the UAT environment of the Terminology Gateway.
   1. Subset owners will need to be provided access to UAT for QA purposes.
   2. The Subset owner will check the subset loaded in the Terminology Gateway UAT environment (see Staging ribbon in yellow in bottom right) correctly and represents the request. Any errors must be logged in the InfoRMS Ticket and commented. A corrected template must be attached to the InfoRMS ticker and loaded in QA UAT.
   3. Once QA is complete in the UAT. sign off in InfoRMS is required before it will be promoted to the Production environment.
   4. The subset owner will check the subset has been correctly loaded in TG Prod and sign off in the InfoRMS (Release form)

Naming Convention for pan-Canadian

...

Subsets and ValueSets 

Please refer to the Naming convention for pan-Canadian Reference sets and Value sets.pdf document for detailed rules for consistent naming of pan-Canadian reference sets Subsets and value sets