Page tree

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

Date

01/20/2017

1600-2200 UTC 

 

GoToMeeting Details

https://global.gotomeeting.com/join/374912925

 Use your microphone and speakers (VoIP) - a headset is recommended. Or, call in using your telephone.

Dial +1 (872) 240-3212
Access Code: 374-912-925
Audio PIN: Shown after joining the meeting

Meeting ID: 374-912-925

Observers:

 

Apologies

Meeting Files

 

Meeting minutes

 

 

 

Objectives

  • Obtain consensus on agenda items

Discussion items

Item
Description
Owner
Notes
Action
1Call to order and role callJCA 

 

2Conflicts of interestJCA  
3Approval of minutes from WellingtonJCA 
  • Approve minutes from Wellington


   

Use of Arabic or Roman numerals in FSNs

Question from editors: "Anybody aware if there is guideline for using numbers vs. of Roman numerals? I can't find any related item in the current version of the ED guideline."

A search of PubMed for "phase II antibodies" yielded numerous results related to Coxiella burnettii serology assays. A similar search for "Phase 2 antibodies" yielded no equivalent representations for other assays.

Prior discussion related to Diabetes mellitus: Inconsistent use of Arabic/Roman numerals in Diabetes

 
 Clinical genomicsIGR

The purpose of this discussion is to inform the EAG of the current status of clinical genomic projects within IHTSDO and to gain insight from the EAG as to priorities and potential resources for input to the overall IHTSDO genomics strategy, including scope, alignment with external standards, sources of truth, level of granularity, etc.

 

 Drug Model updateTMOInformational only: Update on current decisions from the Modeling project group (subgroup of EAG) 
6Extension of Cauastive agent to include ProductJCA/TMO

Update needed: There are specific use cases that more appropriately require the use of concepts from the Product hierarchy. The current approach has been to create matching Substances to allow for sufficient modeling, but in many cases this does not make sense and creates duplicate meanings.

E.g. Adverse reaction to product; Allergy to food product, etc.

  • Develop editorial guidelines
  • Request Technical services to extend the range of this attribute
8ECE UpdateBGO

Update on ongoing issues with ECE

  • Model for complications and sequela incl. postoperative complications
  • Final approval on editorial guide updates for combined disorders
    • Result of combine disorder naming exercise
  • Updates to allergy models
    • Allergy to substance
    • Allergic disorder caused by substance
    • Pseudoallergy to substance
    • Intolerance to substance
    • SNOMED allergy content and ICD-11
  • Final agreement on the model for surgical complications/sequellae
  • Editorial guidance for combined disorders (BGO)
9Need to address semantics and placement of "Care plan for X"JCA

Care plans Care plans - what are they ontologically?

Initial discussion brief: https://jira.ihtsdotools.org/secure/attachment/18619/artf222780_Discussion_Plans.docx

 

  • Gain consensus on position within terminology
  • Develop fast track to resolve internal issue.
 Arteriography vs. ArteriogramJCA

Current editorial guidance for "Arteriography of X" concepts recommends the addition of "Arteriogram of X".

7.8.4 Magnetic resonance imaging - "...It was agreed that the use of near synonyms is acceptable for these procedures (i.e. angiogram/arteriogram)."

7.8.8 Fluoroscopy imaging -

Fluoroscopic arteriography
Descriptions:
FSN: Fluoroscopic arteriography of X (procedure)
PT: Arteriography of X
Synonym: Arteriogram of X
Synonym: Angiography of X
Synonym: Angiogram of X

An arteriogram is the output of the procedure and is more akin to a record artifact than a procedure. Question from the editorial team is whether this guidance is still acceptable due to a large number of requests in this area.?

 

  •  Get consensus on whether to maintain current guidance or revise to reflect the "information object" nature of "-gram"
10Aligning SNOMED CT with clinical use casesKCA/JCAHigh level discussion on whether SNOMED CT is appropriately organized to support the highly variable granularity of content the are influenced by current EHR applications (i.e. single code recording of pre-coordinated content) and newer initiatives that are focused on capturing more structured data (e.g. CIMI, FHIR) 
11Unilateral findings and proceduresJCA

Revisit of this issue following decision on laterality. From the discussion held in Uruguay:

  • The Unilateral concepts were confusing both from a clinical usage and terminological aspect.
  • Having these concepts located in the Situation with explicit context hierarchy while lateralized concepts are was not helpful, he said. User feedback showed confusion.
  • In the short term it was suggested that we remove them from the situation hierarchy, providing a clear message to users, and eventually getting rid of them.

In light of the approval of lateralized content into the International release, is there a compelling reason to keep these concepts (approx. 325).

14Organizational groupersJCA

The IHTSDO Editorial Panel would like guidance on the creation of a policy regarding the addition of fully defined "grouper" concepts that are not clinically useful, but are used primarily for navigation of the hierarchy. For example "Procedure on vena cava" without any specifics as to the nature of the procedure.

 
15Action item reviewEAG

Space Actions

 
16Meeting schedule 2017EAG