Health Terminologies

InfoRMS (JIRA) and InfoScribe (Confluence) are currently unavailable. Your Requests for Change (RFCs) are important to us, so as an interim solution, please send your RFCs to [email protected] All RFCs (SNOMED CT, pCLOCD, LOINC, SC code systems, subsets) will continue to be triaged and prioritized to make every effort to meet your implementation timelines. If you are looking for a document on InfoScribe, please email us at [email protected] and we will send you the link as soon as service is restored. We apologize for the inconvenience and will provide more information as it becomes available.

Hi Fariba, Thank you for your feedback. The two concerns you’ve described (appropriate subset & use of SNOMED CT values) will be taken into consideration. Any updates to our proposal will be provided in the forum once we have completed our community engagement period. Regards, Marie Tran

Hi Anne, Thank you for your feedback. We appreciate your concerns about interoperability and we will be taking your suggestion about the SNOMED code list into consideration. Any updates will be provided in the forum once we have completed our community engagement period. Regards, Marie Tran

Hi Gabor, Thank you for taking the time to report your findings which I'm sure took a long time. There is certainly a lot to "unpack" in this message. We are currently assessing the potential sources of the issues you reported. We would like to take this opportunity to have a conversation with you, on these issues and the previous ones you have reported, so we are ensuring the highest quality of product for the Canadians stakeholders. Would you be able to send an inquiry to the Infoway helpdesk at [email protected] ? Thank you!

Hello, We would like to thank Anne Randorff Højen and Alejandro Lopez Osornio for coming to the May HTC Meeting and presenting and providing a demo of the SNAP2SNOMED mapping tool. ... We would also like to thank Kelly Davison for providing a refresh of the Request for Change process. ... Thank you all for joining us at the meeting. See you at the June 21, 2022 meeting where we will have LOINC present on the RELMA mapping tool. The written answers to the chat questions & response here ... A reminder that there will not be an HTC meeting in August. Best regards Alana and Anil

Hi all, I would also like to share our findings regarding the latest SNOMED CT Canada Edition release. While investigating Debbie's loading issue we found a few discrepancies in the package. Although they are not strictly related to the previously mentioned cases, I hope that sharing this information here will benefit everybody in the community. Release package naming and Delta content The latest release package was named as SnomedCT_Canadian_EditionRelease_PRODUCTION_20220331T120000Z.zip . This filename gives the impression that this package is an Edition release, meaning it contains both the International Edition and the Canada Extension content. It still sounds valid when reading the readme file within the archive: ... The metadata file (release_package_information.json) in the package also suggests that the Delta contains everything that is necessary to perform an upgrade: ... However, the Delta files do not contain any International SNOMED CT content since 2021-09-31. This fact renders the package to be a mix-up of an extension and an edition release, breaking the contract the official SNOMED CT Release Format specification offers. According to the ...: ... The individual filenames also contain the word "Edition", see: ... I see the good intentions with keeping the Delta files within the release package, but this way it could be dangerous to those who got used to consuming Delta files. Since the introduction of Frequent Delivery releases, all the toolings had to prepare for release packages without Delta files. This means that - ideally - the Full files should be sufficient for any consumers going forward. A good example of this approach is the SNOMED CT US Edition, where the latest release package follows the same format as SNOMED International, no Delta is included. I have to add though, that using the Full files is also somewhat tricky in this case, which I'm describing below why. Unfortunate timing of content donation 147 concepts became the first "victims" of the International Frequent Delivery releases. These concepts were all introduced first in the Canada Extension with the effective time 2021-09-30. Then they were donated to the International Edition, where they got accepted and released with an effective time of 2021-09-30. Let me show you through an example why this situation is a bit worrying. 30421000087105 - Corynebacterium mustelae (organism) All corresponding RF2 rows in sct2_Concept_Full_CanadianEdition_20210930.txt: ... All corresponding RF2 rows in sct2_Concept_Full_CanadianEdition_20220331.txt: ... The historical information of these concepts has disappeared between the 2021-09-30 and the 2022-03-31 Canada Edition releases. The modules of these concepts are not represented properly within Snowstorm either. See the modules ... in the International Edition: https://browser.ihtsdotools.org/?perspective=full&conceptId1=30421000087105&edition=MAIN/2022-04-30&release=&languages=en ... in the Canada Edition: https://browser.ihtsdotools.org/?perspective=full&conceptId1=30421000087105&edition=MAIN/SNOMEDCT-CA/2022-03-31&release=&languages=en,fr The official ... cannot be used here because of the clashing effective times. On the other hand, ... says: ... Using the module dependency reference set could be a potential solution, but that alone does not fix the issues within the RF2 files. The latest Canadian Full files do contain the correct International version of those concepts, yet it breaks the RF2 standard itself. Missing components between releases Last but not least, a less critical issue has also been identified. As the specification says, rows from the RF2 release files should not disappear ever, yet there is content that was part of the 2021-09-30 Full release and is not present in the 2022-03-31 Full release files. We have found: - 4468 Simple Map reference set members - 1 module dependency reference set member that is missing from the latest release package, but was present in the previous one. We will help Debbie to import the latest Canadian release into their authoring environment, but in case there is a possibility for a patch release, please let us know. Regards, Gábor B2i Healthcare