Query Health Concept-to-Codes
(C2C) SWG
Meeting #8
January 31, 2012
1
Today’s Agenda
Topic
Review Timeline
Time Allotted
2:30 – 2:35
Presentation by Subject Matter Experts
2
Floyd Isenberg - NQF
2:35 - 3:15
Kevin Puscas – S&I
3:15 – 4:00
Proposed Timeline
Meeting times extended from 2:30-4:00pm
TODAY
Meeting 2 –
Meeting 3 –
Meeting 4 –
Meeting 5 –
Meeting 6 –
Meeting 7 –
Meeting 8 –
Meeting 9 –
Meeting 10 –
Dec 13
Dec 20
Jan 03
Jan 10
Jan 17
Jan 24
Jan 31
Feb 7
Feb 14
Presentation
•I2b2 (Cont.)
•Intermountain
Health
•DOQS (Data
Warehousing /
Mapping)
Presentation
•DOQS (Data
Warehousing
/ Mapping)
Cont.
•PopMedNet
•NLM
Presentation
•Ibeza
•CDISC SHARE
Presentation
•RELMA
(LOINC)
•3M
•NY
Presbyterian
Hospital
Vocab Team
Presentation
•AHIMA
•LexEVS and
CTS2
•Jacob Reider
- ONC
Presentation
•NQF – Value
Sets
•S&I
Repository
Tasks
•IHE SVS
•Kaiser
(Convergent
Medical
Terminology)
Tasks
•Review of
presentations
and selection
of proposed
approach
•Overview of
Constrains
and Criteria
•Consensus
process to
follow
Presentation
•hQuery
•i2b2
•Begin
Overview of
Next steps
Coordinate offline activities to summarize approaches and develop draft deliverable from presentations
3
The S&I Repository
Kevin Puscas
The S&I Framework Web
Platform
S&I Framework
Front Page
S&I
Framework
Repository
S&I
Framework
Pilots
S&I
Framework
Wiki
The S&I Repository (SIR)
Artifact
Manager
Category
Manager
Information
Browser
SIR Architecture
S&I Repository (SIR)
–
–
–
–
Managed Repository for S&I artifacts (docs, models, links, …)
Facilitates artifact lifecycle (publishing, versioning, …)
Create and manage contextual relationships between artifacts
Provides the ability to create, apply and manage taxonomies of
categories for additional meta-data tagging.
– Contextual Searching based on both artifact meta-data as well
as content
– Shopping cart model allows user to select artifacts to be
downloaded as a structured zip package.
– Managed Links provides integration with external web
information sources
Types of Information
Documents
– Searchable information contained in specific “physical” artifacts
– Examples: PDF, MS Word, Presentations, Spreadsheets, XML, Text)
– In some cases can be transformed to other forms as part of publishing
process
Multi-Media
– Image files, Audio, Video
– Examples: JPEG, TIFF, MP3, MOV
– Meta-data tagging important to provide context to artifacts
Links (static and dynamic)
– URL to information contained in other web sites/systems
– Examples: HITSP PDF files, UMLS Value Sets, IHE wiki pages
Models
– Process Models, Data Models, ….
S&I Browser
Artifact Manager
Category Manager
Vocabulary Value Set Support
• Business needs defined by HITSC in April 2010*
– Support the S&I Initiative teams in the definition and governance
of value sets.
– Provide value sets in a computable format to assist in
incorporating those value sets into Meaningful Use compliant
solutions.
• NLM’s UMLS system was identified by ONC to be the source of
vocabularies in support of S&I Framework activities
• 2 Key Requirements for Value Sets.
– What information is needed in a value set.
– What information would be needed for the definition of a value
set.
*http://healthit.hhs.gov/portal/server.pt/gateway/PTARGS_0_11673_911677_0_0_18/5Ferguson_VocabularyTF.ppt
NLM UMLS Integration
Valueset Definition.xml
Retrieve Valueset
ValuesetResults.xml
S&I User
Value Set SME
Valueset
Definitions
Values et Definitions specify a subset of
a Vocabulary Source (ex SNOMET-CT,
LOINC, HL7,…). The value set definition
includes:
• Vocabulary Source Identifier
• Source version
• List of Codes
SOAP Interface
S&I Repository
UMLS
Vocabulary Sources
Value Sets in S&I Repository
•
•
•
•
S&I Repository only manages value set definitions. Value sets
themselves are not in the repository.
Definitions require
– Vocabulary Source
– List of Concept Codes
– Description of Value Set
– S&I Value Set Identifier (SI-VS-xxxx)*
– S&I Value Set OID (2.16.840.1.113883.3.1275.1.1.1.xxxxxx)*
Content of value sets based on value set element metadata defined in
HITSP C80 Section 2.3
– Concept Code, Concept Name, Code System Name)
Value Sets are returned in XML format based on schema defined in the
IHE Sharing Value Set Profile
* Assigned to the value set definition by the S&I Repository.
Current Constraints
• Only supports enumerated value set definitions. Intensional value
set definitions are not yet supported
• Currently 14 of the 160 UMLS vocabularies are used for creating
definitions covering SNOMED-CT, LOINC, ICD9/10, RxNorm, CPT,
MEDCIN, and HL7v2/v3. More can easily be added as needed
• A UMLS account is required to author value set definitions or
retrieve published value sets.
• Limited to current UMLS metathesarus version.
Tentative Roadmap
• Fuller implementation of SVS profile
• Working with UMLS to support intensional value set definitions
• Providing access to vocabularies not available in UMLS as
requested (ex ISO 3166-1 country codes)
• Alternative definition authoring mechanisms (ex csv)