Porting Queries UKTC Data Migration Workbench UKTC Analytics Workshop February 7 th 2013.
9
Porting Queries UKTC Data Migration Workbench UKTC Analytics Workshop February 7 th 2013
-
Upload
roderick-wilcox -
Category
Documents
-
view
216 -
download
0
Transcript of Porting Queries UKTC Data Migration Workbench UKTC Analytics Workshop February 7 th 2013.
Porting QueriesUKTC Data Migration WorkbenchUKTC Analytics WorkshopFebruary 7th 2013
Terminology Interoperability5-Byte READ2
Clinical Terms Version 3
SNOMED CT
RctSctMap
RctCtv3Map
Ctv3SctMap
SctRctMap
!
SctCtv3Map
!
Ctv3RctMap
!
OPCS 4.6 ICD10
What is the DM Workbench ?Reference implementation
load the Data Migration subpack contents(and all 3 terminologies and 2 classifications too)
Full Working Prototype author queries in one terminology translate to another terminologyfake/import SNOMED instance data
analyse, repair, xmap, query, report..tokenised search with word equivalents
Under the hood…Software ‘stack’
GUI for most functionsCommand Line Interface with scriptingTerminology services APIZero install
MS Access under OGL (WinXP/Win7 Access
2003,2007,2010,2013)
Data LoadOne-button import of TRUD data (WHO data for
ICD10)
Common information modelRange of query and instance data formats
UKTC Data Migration Workbench
DEMO
Known limitations
SNOMED Query TableImpact of terminology updateNo mapping for DrugsPostcoordinated ICD and OPCS expressionsPostcoordinated SNOMED CT
Flowing data from secondary care?5-Byte READ2
Clinical Terms Version 3
SNOMED CT
SctRctMap
!
SctCtv3Map
!
Ctv3RctMap
!
ICD10, OPCS
! !
27,564 SNOMED-coded eye surgeries16.5% only ‘lossy’ backmap to READ2 (1.6% to CTV3)
Top 21, accounting for 69% of all data with a lossy backmap
417,210 SNOMED-coded A&E attendances34.9% only ‘lossy’ backmap to READ2 (8.1% to CTV3)
Top 20, accounting for 36% of all data with a lossy backmap
