Query Construction

across

Multiple TerminologiesDr Dai Evans PRIMIS

• 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

V2*

CTV3

EMIS drugs

Specification – QoF, Research, Audit....

* Has to work as a minimum..

CTV3 highlights terms missing from V2 specs.

Missing mapsExtinct terms in CTV3Markedly 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

H33% H33%

H44%

H47y0

173c173A

H3120

(1780.)

CTV3

V2

Synonyms

Q441L1808

Q441

L1808

• 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

• 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

• 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)