Resolved Discussions

With the impending plans to move to a more Frequent Delivery schedule of the SNOMED CT International Edition (starting with a monthly cycle within the next year), we are now considering the requirements for review and feedback periods inherent in the current Release schedule. Given the relative stability of recent releases, and the increased pressure that a Monthly release schedule would put upon the reviewers in the community, we are now considering removing the Beta and Member release p

Hi everyone Thanks again for all of your invaluable feedback - so helpful in fact that we've changed the proposal in line with your suggestions, and as Rory said we've now proposed a full interim International release to the Member Forum (as opposed to the original Delta package): https://confluence.ihtsdotools.org/display/MEMBERFORUM/URGENT%3A+Feedback+requested The plan is therefore to deploy the updated package next week, once we've received and managed any feedback from the MF or

A new tool is being developed to maintain and publish the MRCM, from the 20200731 release. Because the original tooling did not define a canonical attribute order when auto-generating the domain templates, the order of attributes in these domain templates will not be preserved. It is therefore proposed that any affected rows (whose domain template is reordered) is reversioned - i.e. a new row is created in the MrcmDomain refset, with the same UUID, a new effectiveTime and reordered domainT

I'm just revising our validations for the Refset Descriptor Refset. (Upon realising after realising we had none!). And have wondering if the entries should remain active for retired reference sets? The specs (5.2.4.1 Reference Set Descriptor) seem to be silent on the issue... (Unless noted elsewhere)? So I've looked for guidance in the data... The non-human refset is the only refset that I can think of that's been inactive. And it's descriptor history is a bit murky.. id effectivetime

Hi everyone Another topic for discussion in the face to face meetings - the standardisation of the SNOMED CT policy towards re-activation of RF2 records. For example, we have had instances where MRCM records were originally inactivated, and replaced with updated versions that were subsequently proven to be less valid than the original records. The question was then whether or not to re-activate the original records, or to inactivate the new (invalid replacements) and create new vali

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

In 2018 the Content Managers Advisory Group is looking to undertake a work item focusing on national pre-release processes. This work is aimed to support a collaborative understanding of what NRCs are including in their pre-release processes together with identification of potential opportunities to improve these processes. Given the remit of the Terminology Release Advisory Group, the Content Managers Advisory Group would like to raise the potential for this to be a joint Advisory Group a

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

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

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