Page tree

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

Compare with Current View Page History

« Previous Version 11 Next »

Date

04/04/2016

1800 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

Attendees

Apologies

Objectives

Discussion items

ItemDescriptionOwnerNotesAction
1call to order and role callJCA
  •  Need to make sure that the GTM link is the same on the main meeting page and the individual pages. - JCA
2Approval of minutes from 20160229JCAMinutes approved
  • Approve minutes
3Drug product Action Item follow upJCA
  • KCA talk - That has been noted and will schedule when the group is ready. Additional support needed.
  • Product roles - next release concepts will be active but relationships moved to a separate sub-hierarchy. Update documentation coming
  • Status updates on drugs in London.
  • UK uses a role based organization of drugs. Will not be part of product hierarchy but there will be navigational hierarchies for therapeutic roles. EME verifies it fits with their expectations.
  • New documents to be reviewed in :London
  • Much of the drug product content originated in Read V2. Plan is not to retire this content at this time. They would move into a minimally maintained module that could be used by members that need it. UK says that would work for them.
  • TMO to invite KCA to present the VA RxNorm project to the drug modeling group.
  • Paul Amos to speak to Jo Goulding and Emma Melhuish about the use of mappings to the drug concepts being considered in the drug strength project. 
  • TMO to revise the proposal document after getting input from Paul Amos about Read Codes v.2.
  • JCA said that TMO should collect input on the inactivation of concepts needing role from CMAG, then brief the MF. TMO should talk to IGR about how to do that.
  • JCA instructed TMO to write up an inquiry to the MF and Content AG stating what the plan was, outlining benefits and detriments, and requesting information on how it would impact users.
  • Check with Danish folks to determine the value of additional modeling of strength-related products -TMO
4Uses of slashes in FSNJCA

Review discussion on editorial guidelines for use of "/" in FSN.

Use+of+slashes+in+FSNs

  •  Write up final recommendation and submit to Editorial Guide for update - JCA
5Continuation of Laterality proposalJCA

Comments received from Content Managers Advisory Group

Laterality Proposal

Related issues: Bilateral and Unilateral concepts.

Growing UKTC view of choosing Option 2 (lateralized anatomy) vs, Options 4 (relationship group).

Use cases for lateralized body structures include specimen collection and substance administration. Will revist this in London.Impact of Option is greater than the impact of Option 2 from a MCRM perspective.

  • from IGR - Can we have an idea of the extent of changes that will be required on current content?
  • From IGR - What will it mean for project where there is usage of content that currently represent a lateralised concept?
  • Add quality assurance section
  • Clarify the advantages when moving to nested DL of selecting ""Laterality" in relationship group over creating Lateralized anatomy. - GRE, YGA
  • Document development of technical implementation and communication plan
6Content tracker reviewJCA

Content tracker dashboard

 

IHTSDO-858 - artf6279-definition of grouper, whitelisting of exceptions to MRCM rules in User Guide ACCEPTED  
IHTSDO-908 - artf221357-Extended (non-ASCII) UTF8 characters in terms ACCEPTED
IHTSDO-512 - artf6196-Moving between hierarchies without retirement: policy ACCEPTED
IHTSDO-803 - artf6195-Word order variants: policy OPEN
IHTSDO-707 - artf222830-Editorial policy issue - "AND" vs. "AND/OR" ACCEPTED 
IHTSDO-387 - artf6200-Editorial policy approval: criteria ACCEPTED
IHTSDO-608 - artf6253-Imperatives ACCEPTED
IHTSDO-541 - artf6312-Policy re unretiring (conceptstatus move from non-zero to zero) ACCEPTED 

 

  • Assign PAM to IHTSDO - 387
  • Assign BGO to IHTSDO - 541
7Use of URLs in definitionsJCA

Review of comments supplied by members.

Use of URLs in Text Definitions

Suggestion that is we use a reference in a definition in SNOMED CT, we should be able to point to that reference in the text description. For published papers, can use the standard bibliographic referencing procedure (many of these have a DOI). For items that are only published on the web, a DOI might be sufficient. An edge case is where there is not a gold standard definition that can be referenced.

Use of URLs in text definitions: Not allowed.

DOIs were viewed to be acceptable for use as pointers to sources of definitions.

  • Summarize final decision on use of URLs.
  • Determine if DOIs are acceptable in definitions
  • Write up summary and send to Editorial guide - JCA (How to find DOIs)
  • Find out what happens of a document with a DOI gets removed from access. - JCA
8Potential agenda topics for London meetingJCA

We are meeting for a full day in London. Need substantive topics to move forward.

BGO - provide an update oin the ECE activities.

  • Solicit additional agenda topics for London meeting
9May conference call date and time verificationJCA

JCA is traveling on May 23. Move call to May 30?

Agree to move to May 30 at 1800 UTC.

 
10Additional itemsEAGPAM Asked for how many nights they are supported.
  • Get clarification from CGI on support for AG members who stay over two days. - JCA

Meeting Files

No files shared here yet.

Meeting minutes

2016-02-29 Editorial AG Conference Call Minutes


 

Previous Meetings

TitleCreatorModified
No content found.

 

  • No labels