Date: 2021-09-22
Time:
1730- 1900 UTC
1030-1200 PDT
Zoom Meeting Details
Topic: SNOMED Editorial Advisory Group Conference Call
Join from PC, Mac, Linux, iOS or Android:
https://snomed.zoom.us/j/94802932859?pwd=ZFJ5MCtKL0wreHVHR01QTFBoR2h4dz09
Password: 975767
Meeting ID: 948 029 32859
International numbers available: https://snomed.zoom.us/u/adgZ4WKXBh
Or Skype for Business (Lync):
https://snomed.zoom.us/skype/98780715599
Attendees
Chair:
AG Members
Observers:
Apologies:
Meeting Files:
Meeting minutes:
The call recording is located here.
Objectives
- Obtain consensus on agenda items
Discussion items
Item | Description | Owner | Notes | Action |
---|---|---|---|---|
1 | Call to order and role call | This meeting is being recorded to ensure that important discussion points are not missed in the minutes. The recording will be available to the SNOMED International community. If a majority of participants object to recording, only written minutes will be available, otherwise, anyone objecting to recording is requested to exit the meeting. |
| |
2 | Conflicts of interest and agenda review | None stated. | ||
3 | Reterming of "Angiography" procedures with PROCEDURE SITE of "X artery" | Monica Harry | EAG -Angiography_arteriography Briefing note September 1st 2021.docx Angiography_Arteriography EAG 20210901_MHA .pptx Discussion: 20210901: Over 500 procedures with a direct site of "Artery", but are named "Angiography". Propose to rename these as FSN using "Arteriography" with a PT of "Angiography". This will result in a sizeable number of changes to FSNs and descriptions. Question: Is there a pattern in where we have used Angiography, when we are focused on an artery? Is venography just a convenient by-product? Are we just using "angiography" as a convenient mechanism due to the general perceived synonymy in common use? Will it cause problems down the road if we need to make the distinction? Because of the use of both "angiography" and "arteriography" synonymously, should we have both represented as descriptions but not to make "angiography" the preferred term when the focus is an artery. Proposed that in the description that the artery be specified if the description contains "Angiography". Alternative proposal is that we do not use "Arteriography" in the FSN. Angiography would be used as long as the specific artery is specified. This would be the same for the PT. Arteriography would be added as a synonym where appropriate. Decision: Concepts with "arteriography" in the FSN will be renamed "Angiography of X artery", with "Angiography of X artery" as the PT. Arteriography of X artery will be added as a synonym. The presence of "angiogram" description has previously been approved for the ones that are present, but we will go out for comment prior to inactivation of these "-gram" terms. 2021-09-13: A revised document was circulated modifying the editorial proposal to retain the terms containing "angiogram" due to their high clinical usage and value for concept retrieval. |
|
4 | Concept inactivation workgroup update | Inactivation of Ambiguous Concepts - review of comments and problematic examples From Jim Case Ambiguous concepts identified by member 208493001 |Open fracture finger distal phalanx, multiple (disorder)| 208488004 |Open fracture finger middle phalanx, multiple (disorder)| 208482003 |Open fracture finger proximal phalanx, multiple (disorder)| These are confusing concepts and it is unclear from the current wording what is intended. As one would expect, these are most likely derived from ICD-9 (e.g. 816.13 Open fracture of multiple sites of phalanx or phalanges of hand), which is also open to interpretation. In the recent remodeling of these concepts, the representation in some cases is that multiple phalanges or digits are involved, in other cases such as abrasions and open wounds, they are modeled as multiple morphologies on a single digit. Given that the original source of these concepts was ambiguous as to whether one or more digits were involved, these concepts should be inactivated as ambiguous and replaced with concepts with more specific FSNs, i.e. "Open fracture of distal phalanx of multiple fingers" and "Multiple open fractures of distal phalanx of finger". The latter is an example of a concept that most likely would never occur, (multi-fragmentary fractures occur) but would need to be created in order to conform to the requirements associated with AMBIGUOUS inactivation reason from the concept inactivation workgroup. Thus it too would be inactive (Paul Amos, what would be the inactivation reason?) Useful references: Traumatic Finger Injuries: What the Orthopedic Surgeon Wants to Know and Distal phalanx, distal and shaft, multifragmentary Discussion: 20210901: Three options:
Issues with tooling prevents option 2. from being implemented at this time. Interim solution would be to inactivate with one replacement and then return to these after the tooling solution is implemented. Decision: No time for complete discussion. Will be carried forward to next call. 20210922: Continued discussion Discussion: Decision: | ||
5 | ECE Topics | Bruce Goldberg | Osteoarthritis: A majority of descendants of Osteoarthritis (disorder) are not kinds of osteoarthritis. Model needs to be revised. | |
6 | Complication remodeling | Jim Case | Issues have arisen with the remodeling of subtypes of 116223007 |Complication (disorder)|, based on earlier agreed decisions from EAG. Proposal for revision of the “Complication” hierarchy Based on agreed proposals, editorial guide will need to be updated. Discussion: Decision: | |
7 | Maternal vs. fetal periods of life | See attached document for review: Modeling issues related to maternal periods Complications related to pregnancy Discussion: Decision: | ||
8 | Review of requirement for external editors | Jim Case | A draft document for review that outlines the requirements for external editors (non-SNOMED staff) to work within the International release is available for review. This docuemnt will also be provided to the Member Forum and the CMAG. Requirements for external editors of SNOMED CT International Release Discussion: Decision: | |
9 | X (person) vs. X of subject (person) | Jim Case | A question from a member country on when to use "X (person)" vs. "X of subject (person)" has exposed issues with determination of equivalence in information models that either split the relationship from the condition vs. using a precoordinated Situation concept to represent the SUBJECT RELATIONSHIP CONTEXT. Discussion: Decision: | |
10 | AOB | EAG | ||
11 | Next meeting | EAG | Next conference call is scheduled for the annual business meeting October 18, 2021 1600 - 1930 UTC | |