100 likes | 181 Views
Query Construction across Multiple Terminologies. Dr Dai Evans PRIMIS. Process. V2, CTV3, EMIS drugs Avoid NHS browser ( V2 flaws) Use bespoke mapping tools integrated with browsers & query library management system Use Excel tables with additional metadata
E N D
Query Construction acrossMultiple Terminologies Dr Dai Evans PRIMIS
Process • V2, CTV3, EMIS drugs • Avoid NHS browser ( V2 flaws) • Use bespoke mapping tools integrated with browsers & query library management system • Use Excel tables with additional metadata • Biannual update processes with more frequent drug handling where important
Process Specification – QoF, Research, Audit.... V2* CTV3 EMIS drugs * Has to work as a minimum..
Problems CTV3 highlights terms missing from V2 specs. Missing maps Extinct terms in CTV3 Markedly different hierarchies – CTV3 not always better Contemplate differing contexts of terms.... i.e. Just “Diagnostic Terms” vs “all related terms” What do you do about Synonymous terms? MIQUEST brings in local codes
Wide range of requests H33% H33% (1780.) 173A 173c H47y0 H3120 H44%
Synonyms CTV3 V2
Diabetes Diabetes Q441 Q441 L1808 L1808
Specification Problems • Historic problem with Flu Reports v2 CTV3 • CVA/TIA A,B,C A,B,E,H • Chr.Neurol D,E,F C,D,F,G Disease
Code Compilation Tools • Accurate • Mapping embedded • Handle manipulation & display of complex hierarchies • Handle inclusion/exclusion across multiple parents • Bi-dimensional version control (new codes, hierarchy shifts, retirement; specification) • SPEED
SNOMED querying • Perceived huge breadth of codes • ?Retired codes • ?Post co-ordination • Data entry advice/templates/facilitation • Possible subset usage (1st pass/2nd pass) • Constrained roll-out & implementation • Extraction/Data entry can be pre-ordained in certain scenarios (e.g. QoF)