servicios terminológicos

26
Terminology Service Jussara Rötzsch Based on: Ian McNicoll Christopher Chute

Upload: pablo-pazos

Post on 07-Dec-2014

2.892 views

Category:

Health & Medicine


0 download

DESCRIPTION

Servicios Terminológicos para el (re)uso efectivo de la Información Clínica - Dra. Jussara Macedo

TRANSCRIPT

Page 1: Servicios Terminológicos

Terminology Service

Jussara Rötzsch

Based on: Ian McNicoll

Christopher Chute

Page 2: Servicios Terminológicos

What do we need?

Information Models

An EHR that is• Independent of implementation technology• Independent of clinical system developer• Enables access to multiple clinical applications• Designed for longevity and re-use

Content Specifications

Terminology

Query

Messaging

Page 3: Servicios Terminológicos

March, 2009 3© 2002‐2009, Health Level 

Seven, Inc.

The Problem

• Terminology systems vary considerably in both content  and structure.

– NDF‐RT– RxNorm– SNOMED‐CT– ICD‐9 and ICD‐10– CPT– etc

• Requirements of terminology vary widely• Implementation decisions of terminology vary widely• Storage formats may differ (relational database, XML, 

...)

Page 4: Servicios Terminológicos

Real world use of SNOMED CT

• Clinicians– Need to be able to find the term that they need easily

– Need to use SNOMED terms correctly – good subsets  are safe

– Transparent to the end user• Applications

– Need to be able to deploy SNOMED and use it reliably  in their apps

– Need to be able to query reliably

1.4

Page 5: Servicios Terminológicos

March, 2009 5© 2002‐2009, Health Level 

Seven, Inc.

Common Terminology Services (CTS)

• Purpose is to specify a common Application  Programming Interface (API) to access 

terminological content

• Client software doesn’t have to know about  specific terminology data structures and/or  how to access them

• Server software can plug and play with many  clients

Page 6: Servicios Terminológicos

March, 2009 6© 2002‐2009, Health Level 

Seven, Inc.

Common Terminology Services API

• Allows Client Software to be developed  Independently from Service Server Software

• Allows Terminology Plug‐and‐Play

• Allows Client Plug‐and‐Play• Defines a “Functional Contract”

Page 7: Servicios Terminológicos

March, 2009 7© 2002‐2009, Health Level 

Seven, Inc.

CTS API

Application

Service

Interface

Data

CTS

. . .

Page 8: Servicios Terminológicos

March, 2009 8© 2002‐2009, Health Level 

Seven, Inc.

CTS API

CTS

MS AccessTables

Application

Service

Interface

Data

HL7VocabBrowser

HL7 Terminology

Server

Find codes having “*myelitis”

Select * from VOC_concept_designationWHERE text like ‘%myelitis’

Page 9: Servicios Terminológicos

March, 2009 9© 2002‐2009, Health Level 

Seven, Inc.

CTS API –

Different Client, Same Service

IHC

Picklist

Tool

MS AccessTables

Application

Service

Interface

Data

HL7 Terminology

Server

Find codes having “*icillin”

Select * from VOC_concept_designationWHERE text like ‘%icillin’

CTS

Page 10: Servicios Terminológicos

March, 2009 10© 2002‐2009, Health Level 

Seven, Inc.

CTS API –

Different Server, Same Client

IHC

Picklist

Tool

SNOMEDCT

OracleTables

Application

Service

Interface

Data

APELONDTS

Find codes having “*icillin”

Select * from conc_reprWHERE text like ‘%icillin’

AND ...

CTS

Page 11: Servicios Terminológicos

March, 2009 11© 2002‐2009, Health Level 

Seven, Inc.

CTS API –

Distributed Services

IHC

Picklist

Tool

Internet Service

Application

Service

Interface

Data

Find codes having “*icillin”

<msg><soap....><filter=“*icillin”...</msg>

CTS

WebPortal

Page 12: Servicios Terminológicos

March, 2009 12© 2002‐2009, Health Level 

Seven, Inc.

Common Terminology Services

Message Processing ApplicationMessage Processing Application

VocabularyVocabularyVocabulary

Message Processing Application

Message API

Vocabulary API

Page 13: Servicios Terminológicos

OpenEHR (Ocean)Terminology Server

MultipleLanguages &

subsets

Maintenance

Use cases

Page 14: Servicios Terminológicos

Terminology Server

SNOMED-CT UKextensionEnglish

Ocean TerminologyServer

• Stores named queries• Caches complex queries• Caches saved between

sessions

Page 15: Servicios Terminológicos

Process

User determines which part(s) of SNOMED‐CT  hierarchy is of interest (including which 

subsets)Can choose to:

– Include a node– Exclude a node (pass through)– Exclude a node and all the children of a node 

(exclude)– Include the node for navigation only– Hoist the children to be peers of the parent

Page 16: Servicios Terminológicos

Blood groups – raw views

Page 17: Servicios Terminológicos

Blood Groups simple list (all terms)

• Choose all relevant blood groups• Hoist all nodes to be peer with parents

This gives a flat list of terms

Page 18: Servicios Terminológicos

ABO Blood Groups 3‐layer tree

• The hierarchy of ABO blood groups

Navigate

Select

Page 19: Servicios Terminológicos

Terminology Query language• <?xml version="1.0" encoding="utf‐8" ?>• <ots:query • xmlns:ots="urn:xmlns:oceaninformatics.biz:schema:OTSQuerySchemav2"• name="BloodTypev2"• language="en‐us"  • terminology="Snomed"  • cacheMode="Permanent">• <childNodes>• <concept conceptId="112143006"• operation="Navigate">• <childNodes>• <relatedConcept operation="Navigate"• relationship="116680003">• <childNodes>• <relatedConcept operation="Select"• relationship="116680003">• </relatedConcept>• </childNodes>• </relatedConcept>• </childNodes>• </concept>• </childNodes>• </ots:query>

Start at ABO blood group

Iterate down the IS_A relationship

Make all nodes with an IS_A relationshipselectable

Set root to Navigate

Page 20: Servicios Terminológicos

ABO Blood Groups 3‐layer tree restructured

Placeholder

Navigate

Select

Placeholder

Page 21: Servicios Terminológicos

ABO Blood Groups 3‐layer tree restructured  code

• <?xml version="1.0" encoding="utf‐8" ?>• <ots:query • xmlns:ots="urn:xmlns:oceaninformatics.biz:schema:OTSQuerySchemav2"• name="BloodTypev2"• language="en‐us"  • terminology="Snomed"  • cacheMode="Permanent">• <childNodes>• <placeHolder text="Blood Types">• <childNodes>• <concept conceptId="112143006"• operation="Passthrough">• <childNodes>• <relatedConcept operation="Navigate"• relationship="116680003">• <childNodes>• <placeHolder text="Rh subtypes">• <childNodes>• <relatedConcept operation="Select"• relationship="116680003">• <constraints>• <lexicalConstraints>• <lexicalConstraint matchRule="MustMatch">• <searchString>*Rh*</searchString>• </lexicalConstraint>• </lexicalConstraints>• </constraints>• </relatedConcept>

Placeholder

Navigate

Placeholder

Select

Page 22: Servicios Terminológicos

OTS Features• Terminology support

– Support for multiple terminology• linking concepts by relationships (hierarchies)• property based

– Support for terminologies in their native structures– Access to terminologies in any database technology

• Queries– Queries may be pre‐defined and made available to all users– Queries based on queries– Provide a high‐level mechanism for identifying concepts relevant 

to local requirements

Page 23: Servicios Terminológicos

OTS Features• Query language

– XML based– terminology‐independent– allows selection or navigation around relevant concepts depending on the 

situation.

– powerful expressive capabilities across trees, multiple links and iterative structures

• Visual interface– hierarchical navigation– rapid text searches– visual specification of queries

• Computer Interfaces– Global Web Service interface accessible to all– Class library available for local .NET usage

Page 24: Servicios Terminológicos
Page 25: Servicios Terminológicos
Page 26: Servicios Terminológicos

Q&A

[email protected]