Page tree

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

Compare with Current View Page History

« Previous Version 4 Next »

Date

08/22/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

Apologies

Objectives

  • Obtain consensus on agende items

Discussion items

ItemDescriptionOwnerNotesAction
1Call to order and role callJCA

 

 

2Approval of 20160627 minutesJCA 
  • Approve minutes from 06/27/2016

3Editorial guidance on numeric ranges in FSN 

Are numeric ranges separated by dash, em-dash, or "to", or "from"?

e.g. |128131000119102|History of low birth weight status, 2-2.5kg (situation).
Is there supposed to be a space between the number and the unit (e.g. 2mg or 2 mg)?

Existing content does not use a space, but use of a space has been standard editorial policy.

Should we use a reference such as AMA or Chicago Manual of Style (and there are probably others) to provide guidance?

 
5Requirement for description matching FSN in MRCMJCA

Summary of previous discussion: (see 2016-01-22 Editorial AG Conference Call)

  • Current FSN naming conventions result in "non-user-friendly" descriptions. Creation of another description without the semantic tag adds no value
  • Many existing FSNs would be ambiguous without the addition of the semantic tag.
  • Users often do not request "preferred terms" so rely on editors to provide appropriate descriptions.
  • Historically, many FSNs were glorified preferred terms
  • This is an issue that only affects English versions as translation provide terms of use in their languages
  • Challenge to editors is when to create a different preferred term if the FSN term is not user-friendly.
  • This has an impact on acceptance of word order variants as preferred terms.

Assumptions:

  • Semantic tags provide value in disambiguating concepts in different hierarchies with the same description (e.g Swab (physical object) vs. Swab (specimen))
  • Current FSN naming conventions do not always provide user friendly descriptions, so duplication of these descriptions adds no value.
  • Consensus on options: 1) require matching description (SCA give error) or 2) matching description optional (SCA gives warning)
  • Bruce Goldberg To take this naming issue back to the ECE for discussion and recommendation.
6Action item reviewEAG

Space Actions

 
7Potential agenda topics for Wellington meetingJCA

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

 

  • Solicit additional agenda topics for Face-to-face meeting
8September conference call date and time verificationJCA

JCA is traveling Sept 10-23. Meeting scheduled for Sept 26

 

 
9Additional itemsEAG  

Meeting Files

 

Meeting minutes

2016-06-27 Editorial AG Meeting Minutes

 

 

  • No labels