Agenda topics for April 2016 meeting

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.

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.

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.

@Former user (Deleted) to pull together background information/examples.