You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 14
Next »
Date: 2019
1800 - 1930 UTC
1100-1230 PDT
1400-1530 EDT
1600-1730 Argentina time
Zoom Meeting Details
SNOMED Int'l Editorial Advisory group
Please join my meeting from your computer, tablet or smartphone:
Topic: SNOMED Editorial Advisory Group Conference Call
Time: Mar 19, 2019 1900 UTC; 1100 PDT
https://snomed.zoom.us/j/464312001
Attendees
Chair:
AG Members
Meeting recording
The folder containing the meeting recordings is located here.
The recording for this meeting is located here.
Objectives
- Obtain consensus on agenda items
- Provide resolution for outstanding issues
Discussion items
Item | Topic | Owner | Description | Discussion | Action |
---|
1 | Call to order and role call Conflicts of Interest | JCA | GRE - Contractor to SI, Principal in TermMed | Start recording |
|
| ECE Update | BGO | | - Injury discussion
- Damage and injury are often used synonymously
- ICD definition for injury is more specific to traumatic injuries
- Trauma is more of a process than a morphology
- Non-traumatic is difficult to define
- There is a gray area between traumatic and non-traumatic
- Is this a false dichotomy -what is the use case for making the distinction?
- What are we trying to distinguish? External causes? Suggestion to consider using DUE TO = Event as opposed to a pathological process
- There is not much difference in treatment base don whether traumatic or non-traumatic
- Consider using the mechanism of injury rather than trying to distinguish trauma vs. non-trauma
- Initial step WRT non-traumatic brain injury proposed to create intermediate primitive
| - Test the use of DUE TO = event to model traumatic events Bruce Goldberg
- Create a new primitive term "Non-traumatic injury" as a stop gap to address the obstacles to defining this notion Bruce Goldberg
|
| Substance role groups | TMO | Product role disposition Product role options Product role affected concepts | - Five options discussed
- Concern expressed by KCA that ignoring option 4 is not based on correct representation and does not address the true issue.
- What should be modeled in the core? Most of the modeling of therapeutic roles should occur in extensions.
- Recommend that option 4 be reworded to state that it would be an evolutionary approach
- The main problem is that the core is currently not modularized so it is not possible to segregate these relationship outside of the core module.
- The secondary issue is that the association of clinical drug to the product roles is jurisdictionally dependent.
- Suggestion is that these associations be placed in a separate module
| - Test the potential for creation of a new attribute within a new International release module. This would be part of the International release, but could be excluded if desired (i.e. there is an extension replacement) - refer to MAG and TRF AGs for testing
- Test use of non-defining attribute for future movement towards modularization - requires tooling change?
- Maintain a role hierarchy without defined subtypes as part of the international release, except for those that can be identified as universally accepted, requiring national extensions to maintain differences. Use existing drug terminologies. Potential issues exist with leveraging the classifier for this.
|
| SNOMED CT Clinical Core | JCA | Background on proposed "SNOMED Clinical Core" Discussion on mechanism to identify content for the core | Continued to the April Business meeting | - Jim Case to present new content strategy in detail at the April Business meeting
|
| Future meetings | JCA | Development of agenda topics for April Face-to-face meeting | Will be handled by email exchange |
|