Date
25 October 2016
Location
Wellington, New Zealand
Attendees and Observers
See agenda page
JCA: Right now, you enter the FSN, and the tooling creates the matching description. authomatically assigns that as the preferred term for English and GB refsets unless there's a known GB spelling then it creates that. are there other tooling requirements if we keep this matching description? Or do we want it to require us to enter a different one if it's inappropriate for clinical use? That would require more work.
GRE describes how his system works, based on the Workbench translation.
JCA: so leave it as it is? Do we require tooling changes so we don't require it?
JCA: the way we currently have it leads to some unwieldy FSNs. Other burden on the editors is if there is no term, they have to come up with a clinically acceptable term.
GRE: we should consider an internal policy for the English edition.
YGA: from ed. policy perspective, if FSN is not clinically friendly, it should not be entered into a synonym. i agree about semantic clearness the FSN provides that. from search perspective the FSN includes all the key words there. Synonym keep clinically friendly, FSN keep semantic clarity. Automation is still necessary. we create a new concept, FSN, automatically create a preferred term FSN, if not clinically friendly, change it.
GRE: policy started because of request submission some years ago, we can stop it but some will say we want it, we requested it. it will be nice if you want to discontinue that to provide this kind of education to the MF. It is language dependent, let each language decide if need it or not. Submissions are usually significantly high number of non-compliance.
BGO: any thought given to user friendly names like Kaiser for preferred terms. JCA: issue is many contain abbreviations and truncations, many are broader than the FSN.
JCA: How do we determine what a clinically friendly term is? need guidelines on how to construct. I think development of ed guides on how to create clinically friendly term is as much as a challenge as other things we're discussing. BGO: I can share some of our guidelines so you can see what they look like.
TMO: if don't create a term that matches the FSN, user could search on the FSN. Do we know that they do that? GRE: most of the browsers we looked at searched for FSN too.
JCA: Matter of how find a concept in the first place vs. how is it represented in the system.
IMO rep: all of terms we create we map to SCT, only use the FSN because all the other terms are ambigious or otherwise problematic.