Page tree
Skip to end of metadata
Go to start of metadata

Resolved Discussions

Status: All
Creators: All Date: All

We've finalised a plan for the next two International Releases, and so any feedback you have on the viability of the plan is needed urgently - thanks! The plan is as follows: January 2019: The International Edition package (let’s call it packageA) will include both active Stated Rel’s + partial OWL file (combined) We will also publish a separate optional package (packageB) containing a complete set of OWL records (including all axioms - sufficient, transitivity etc) set to Jan 2019 effec

Status: In discuss 119 View 25 Comment Comments enabled In the category: Resolved Discussions
Comment Last contribution, Dec 4, 2018. All contributions
Thanks for all of your input everyone - I sent the comms out last week, so please let me know if there were any questions raised by anyone, or confusion caused by the message? Also if we think that we need to put out any additional comms please let me know - otherwise we'll discuss the progression of the plan in the next face to face in April... Thanks!

Hi everyone Fairly straight-forward one here - the Association Reference file has historically been named slightly inaccurately, called 'der2_cRefset_AssociationReferenceSnapshot_INT_*.txt' etc, which implies it's name to be "Association Reference Reference Set" rather than the correct "Association Reference Set".  So the proposal is to simply rename the file(s) to something like 'der2_cRefset_AssociationSnapshot_INT_*.txt', or similar? I'm guessing that some re-work would be required fo

Status: Resolved 92 View 7 Comment Comments enabled In the category: Resolved Discussions
Comment Last useful answer, Oct 14, 2018. All contributions
RESOLUTION:  This was implemented it in the Jan 2018 International Edition release, plus in the various derivative products based on this release.

Hi everyone Another conundrum for you :-) We have found some examples, in this case in the US edition, of concepts that were promoted to the International Edition, but remain in the US maintained module in the US branch. There are 5 concepts found to be in this situation ie concept table updated in the US module after the concept has been promoted to core: id core_effectiveTime core_activeFlag us_effectiveTime us_activeFlag term 11000119105 20150131 0 20150301 0 History of peanut all

Status: Resolved 123 View 11 Comment Comments enabled In the category: Resolved Discussions
Comment Last useful answer, May 22, 2017. All contributions
RESOLUTION:  Peter Williams resolved this issue in the code as per the agreed approach with the TRAG.  We also raised the long term discussion on the "Negative Delta" proposal, so please post any future comments on this to the new page here:  "Negative Delta" file approach

Hi everyone We've found several AttributeValue records (193 pairs) which have 2 states in the files for the same effectiveTime - one Active and one Inactive. For example: id effectivetime active moduleid refsetid referencedcomponentid valueid 34105af2-75df-4851-bb1b-10481862a050 20170131 1 900000000000207008 900000000000490003 2475924014 900000000000495008 402ef83b-0033-5802-b73e-a9d92c98fa48 20170131 0 900000000000207008 900000000000490003 2475924014 900000000000495008 Our fi

Status: Resolved 83 View 4 Comment Comments enabled In the category: Resolved Discussions
Comment Last useful answer, Oct 14, 2018. All contributions
RESOLUTION: Matt and Mikael confirmed that this is a valid situation, and therefore no action is required.  TRAG agreed unanimously.

This was an issue introduced in the January 2017 International Edition - https://ihtsdo.freshdesk.com/helpdesk/tickets/16240 https://ihtsdo.freshdesk.com/helpdesk/tickets/16240. We have fixed the content for the July International Edition, and are now turning our focus to the requisite improvements to the RVF. The question for the TRAG is: are there any other similar scenarios that we should attempt to pre-empt by adding validation to cover them, before they occur? Thanks very much A

Status: Resolved 74 View 5 Comment Comments enabled In the category: Resolved Discussions
Comment Last useful answer, Oct 14, 2018. All contributions
RESOLUTION:  The content fix was implemented in the July 2017 International Edition release, and the RVF improvement ticket has been raised (RVF-273).

Hi everyone We're proposing to open-source the RF2 to OWL Perl script (tls2_StatedRelationshipsToOwlKRSS_Script_INT_20170131.pl), in order to make it more widely available. We'd like to do this sooner rather than later (as there are people in the community who would like access to it for the Implementation course, etc) - so if you could please send any objections (or confirmation that you don't have any) immediately that would be greatly appreciated? Thanks very much Andrew

Status: Resolved 117 View 9 Comment Comments enabled In the category: Resolved Discussions
Comment Last useful answer, Oct 14, 2018. All contributions
RESOLUTION: Given the updates to the OWL approach (with the imminent addition of the OWL Axiom and OWL Ontology refsets), this discussion became naturally obsolete, as the old PERL script becomes redundant, and the new SNOMED OWL Toolkit is already open-sourced: https://github.com/IHTSDO/snomed-owl-toolkit https://github.com/IHTSDO/snomed-owl-toolkit aatkinson to therefore include a link to the new SNOMED OWL toolkit in the all future International Edition Release Notes instead.

As I'm sure you've already seen, we've sent out several reminders that as of April 26, 2017 the antecedent SNOMED works will no longer be licensed. Please see here for the various reminders (we've also just reminded everyone in the latest Member Forum meeting): http://www.snomed.org/news-articles/timetable-for-the-withdrawal-of-legacy-snomed-codes http://www.snomed.org/snomed-ct/what-is-snomed-ct/previous-versions-of-snomed-ct As we all know, the SNOMED CT International Edition includes

Status: Resolved 132 View 7 Comment Comments enabled In the category: Resolved Discussions
Comment Last useful answer, Oct 14, 2018. All contributions
RESOLUTION:  TRAG agreed on the cleanest method of removing the SNOMED RT Identifier refset:  a) remove it from the Release completely b) Create the standard static package separately. We also discussed at great length with the Legal team, and agreed that due to the fact that by its very inclusion in the International Edition package we are continuing to licence the SNOMED Identifier refset, we would be significantly increasing the risk of legal liability due to unauthorised use of the unlicensed content.  We therefore agreed that the best practice approach was to remove the SNOMED Identifier refset in its entirety, rather than merely inactivating the content. Communication:   aatkinson communicated the decision to the members who raised the issue of our contravention of the RF2 standard, in order to explain to them why this is preferable to increasing our legal liability. aatkinson successfully removed the SNOMED Identifier refset from the July 2017 International Edition release package, and create the distinct static package as per the previous comms. To provide a shared resource and a single source of truth on these antecedent issues we created a set of FAQs available at our SNOMED International website here: https://ihtsdo.freshdesk.com/support/solutions/folders/4000013539 https://ihtsdo.freshdesk.com/support/solutions/folders/4000013539 No issues were reported by any parties since the change was made, and therefore this discussion can be closed down as complete.

Hi everyone, As discussed in the separate AG discussion "Additional, non-defining Relationships", we need to create a new SEP Refset in the International Edition. This is both to assist with the interim solution for the Additional, non-defining Relationships, and also to enable us to further improve our Quality Assurance processes. Please see the following page for details of the proposed new Refset: https://confluence.ihtsdotools.org/display/IAP/SEP+maps+and+refset And here for some

Status: Resolved 102 View 3 Comment Comments enabled In the category: Resolved Discussions
Comment Last useful answer, Oct 14, 2018. All contributions
RESOLUTION: This change was successfully implemented in the July 2017 International Edition.

With derivative packages, we currently build first time releases so that all Delta files are empty, and Snapshot and Full files contain identical content, which comprises of all of the new content. This is opposed to the normal situation where the Full file contains all content, the Snapshot only the most recent statuses, and the Delta file only the new content. However, there is a school of thought that suggests that the Delta files in these first time releases should also be populat

Status: Resolved 107 View 8 Comment Comments enabled In the category: Resolved Discussions
Comment Last useful answer, Oct 14, 2018. All contributions
RESOLUTION: TRAG agreed on the best approach, which was then documented in the Release Packaging conventions document.

Hi everyone Great to see most of you again at the conference - we have a quick (and unfortunately urgent) question for you: We’ve just had a very late submission for potential inclusion in the January 2017 International edition, and I was hoping to quickly get your thoughts on it before discussing with everyone. A large scale batch change needs to be applied to the International content as soon as possible - approximately 770,000 descriptions would had their case significance chan

Status: Resolved 194 View 14 Comment Comments enabled In the category: Resolved Discussions
Comment Last useful answer, May 3, 2017. All contributions
RESOLUTION:  This has now been confirmed for implementation in the July 2017 International Edition, so please advise all relevant parties of the upcoming change.
1 2 3 ... Next Last �

  • No labels