Hello Everyone, A new project has been created call the ... - This is project born of the ongoing frustration the ideas encompassed by "sex" and "gender" have never been easy to capture consistently within health models. This project is going to try use some tried and true approaches to how to model information (data elements, value sets, code systems) and use them define/harmonize some aspects, likely not all, for representing sex/gender. Here is the project participation list - ... To get the conversation started, I would like to ask how are jurisdictions in Canada currently handling capturing sex/gender? I think sharing our thoughts will help us come up with a unified approach. Thanks, Joel

Hi Joel, If the goal is to help implementers use the appropriate code system URIs, I recommend that in addition to OIDs, that the code system URIs be made available also (both pre-R4 and R4/post-R4). Otherwise, implementers will have to search for the appropriate FHIR URIs which may or may not be available somewhere else. It will make it easy for implementers (one-stop shop). Thanks Finnie

Hi Finnie, Thanks for the comment. I agree with your statement and in order to maintain a version agnostic repository, I think the CodeSystem OID is more suitable for listing than the HL7 CodeSystem FHIR URI. After discussion with LLoyd McKenzie, I understand that if an implementation is using a version of FHIR, then the implementation must use the ValueSet and CodeSystem URIs present in the specification for that version. Therefore in that sense an implementation shouldn't migrate URIs if they have been changed in a latter version of FHIR unless the implementation is migrating to that latter version. This helps us conclude that FHIR URIs are version specific. Fro the purpose of the Terminology Gateway, having the HL7 CodeSystem OID listed is more appropriate as it hasn't changed from FHIR R3 to R4 ex: http://hl7.org/fhir/v3/ActCode VS http://terminology.hl7.org/CodeSystem/v3-ActCode. Here the OID remained unchanged - 2.16.840.1.113883.5.4 and therefore listing the OID helps maintain a version agnostic repository. Also LLoyd helped clarify that a change in URI can be treated as a change in the CodeSystem content but in fact the change in R4 is merely a change in the Canonical URL. Thanks, Joel

Hello all, Please join us February 19 at 11 am ET for our regular monthly meeting. We have some very interesting and important topics this month. Here is the agenda: 1. Welcome 2. Presentation 1: Intro to FHIR Terminology Infrastructure – Lloyd McKenzie, Gevity Consulting 3. Presentation 2: SNOMED CT Description Logic Changes – Guillermo Reynoso, TermMed 4. Call for Topic Suggestions 5. Jurisdictional Outreach 6. Upcoming Items of Interest 7. Adjournment Meeting link: Monthly meeting for the Health Terminologies community. Third Tuesday of every month 11:00 - 12:00 ET Add to your calendar here: https://zoom.us/meeting/947195893/ics?icsToken=977d7e1127e535e754f4c85d8fe8a74c65dfd5a4a7aab6da409a2d6b51ec39e6 Webinar: Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/947195893 Dial-in numbers: Dial (for higher quality, dial a number based on your current location): Canada: +1 647 558 0588 or +1 855 703 8985 (Toll Free) US: +1 669 900 6833 or +1 646 558 8656 or +1 877 853 5257 (Toll Free) or +1 855 880 1246 (Toll Free) Meeting ID: 947 195 893 International numbers available: https://zoom.us/u/c93xnYbQz Or iPhone one-tap : Canada: +16475580588,,947195893# or +18557038985,,947195893# (Toll Free) Regards, Marc & Francis

Hello all, The presentations from the January 15, 2019 meeting have been posted to the community's Meeting Materials folder here: https://infocentral.infoway-inforoute.ca/en/resources/docs/health-terminologies/ht-mtg Regards, Marc

The February 2019 Complete OWL file DEMONSTRATION release of the SNOMED CT® International Edition is now available to SNOMED International Members. This DEMONSTRATION release provides Members with the opportunity to have an early view of the proposed OWL file changes, in order to help our community to evaluate their tooling, systems and release processes. The new OWL Axiom reference set (contained in the OWLExpression files) represents all stated relationships and all new description logic features, such as general concept inclusion (GCI) axioms and additional axioms. Please note that the content modeling is still a work-in-progress and these examples are being provided for demonstration purposes only and are not necessarily reflective of content that will be in the July 2019 International Edition Release. The complete OWL Axiom refset will be mandatory from the July 2019 release onwards. The DEMONSTRATION release package is distributed for evaluation purposes only. It must not be used in production clinical systems or in clinical settings, or distributed to Affiliate Licensees or any third parties at this time. The SNOMED CT DEMONSTRATION release contains SNOMED CT files in Release Format 2 (RF2) only, distributed in a zipped file archive. The SNOMED CT DEMONSTRATION Release Notes can also be accessed online: https://confluence.ihtsdotools.org/display/RMT/SNOMED+CT+COMPLETE+OWL+FILE+DEMONSTRATION+package+Release+Notes+-+February+2019 Please see the Early Visibility confluence page, to remind yourselves of all of schedule of the upcoming changes in this release: https://confluence.ihtsdotools.org/display/RMT/Early+Visibility+Release+Notices+-+Planned+changes+to+upcoming+SNOMED+International+Release+packages If you are interested in getting these files, please contact Standards@infoway-inforoute.ca If you have any questions about the February 2019 DEMONSTRATION release, or have difficulties downloading this file, please contact SNOMED International at support@snomed.org with “February 2019 Complete OWL file DEMONSTRATION release question” in the subject line. Any feedback on the DEMONSTRATION release files must be submitted as early as possible, but certainly before 5th March 2019.

If your SNOMED CT implementation requires classification or rely on relationships and subsumptions, you may be affected by the coming changes. To lean more about the SNOMED CT important description logic enhancements, you are invited to attend the next Health Terminologies Community meeting on February 19. Guillermo Reynoso, Director of Terminology Services at TermMed and a SNOMED International Certified Consultant Terminologist will explain the changes, how these changes will impact existing implementations, if stakeholders will have access to converting tools and how should one transition from current to future state… ...