Use of hyphen and parentheses in descriptions containing acronyms. There are issues with conditional statements about when to use parentheses and when to use hyphens depending on whether there is additional text or not. Need to identify this issues around having only one way to handle this.
From earlier email:
One example where the use of parens vs. hyphen might cause a problem is where the acronym is at the end of the description. example 229310001 | Periodic continuous positive airway pressure (regime/therapy) | has the synonym "Periodic CPAP" which should then be expanded to "Periodic CPAP (continuous positive airway pressure)" where the description will end in a parens. WIll that cause an error to be thrown? So while there seems to be agreement on this, I think once it is fully implemented we will run into other technical issues.
Discussion about modularity of SNOMED CT. What type of content is suitable, eligible for modularization? How will these modules be maintained? How will they be represented (and enforced) in the tooling.
Discussion regarding extending the concept model to include the use of Product concepts as attribute values to define concepts in other hierarchies. There are known discrepancies between the Editorial Guide and the MRCM.
Toni Morrison to pull together background information/examples.
In relation to ideas for the April meeting I've done a review of the Content Tracker issues that are impacting SIRS requests being progressed. This review has shown that quite a number of these trackers actually have assignees and a number are the bigger projects e.g. Substances. There are a couple that have no-one assigned but they are impacted by other projects. There are a small number that could be progressed by a single Consultant through the normal process and these would need pre-work if brought to the Editorial Panel.
Given that the Pre coordination Roadmap pattern trackers that are impacting SIRS progressing were looked at. Excluding those already being worked on e.g the Laterality issue, there are several that have between 11 and 27 SIRS on hold and they are listed below.
There are also some Content tracker items that have been identified as Editorial Issues that the group might like to consider reviewing and updating and/ or closing as required. In some cases the decision may have been made though not formally documented. These did not have SIRS related issues.
4 Comments
Jim Case
Use of hyphen and parentheses in descriptions containing acronyms. There are issues with conditional statements about when to use parentheses and when to use hyphens depending on whether there is additional text or not. Need to identify this issues around having only one way to handle this.
From earlier email:
One example where the use of parens vs. hyphen might cause a problem is where the acronym is at the end of the description. example 229310001 | Periodic continuous positive airway pressure (regime/therapy) | has the synonym "Periodic CPAP" which should then be expanded to "Periodic CPAP (continuous positive airway pressure)" where the description will end in a parens. WIll that cause an error to be thrown? So while there seems to be agreement on this, I think once it is fully implemented we will run into other technical issues.
Jim Case
From EAG conference call 2/29/2016:
Discussion about modularity of SNOMED CT. What type of content is suitable, eligible for modularization? How will these modules be maintained? How will they be represented (and enforced) in the tooling.
Toni Morrison
Discussion regarding extending the concept model to include the use of Product concepts as attribute values to define concepts in other hierarchies. There are known discrepancies between the Editorial Guide and the MRCM.
Toni Morrison to pull together background information/examples.
Cathy Richardson