Presentation is loading. Please wait.

Presentation is loading. Please wait.

Wednesday, November 4 th 2015 Transitional Vocabulary Task Force Christopher Chute, Co-Chair Floyd Eisenberg, Co-Chair.

Similar presentations


Presentation on theme: "Wednesday, November 4 th 2015 Transitional Vocabulary Task Force Christopher Chute, Co-Chair Floyd Eisenberg, Co-Chair."— Presentation transcript:

1 Wednesday, November 4 th 2015 Transitional Vocabulary Task Force Christopher Chute, Co-Chair Floyd Eisenberg, Co-Chair

2 Transitional Vocabulary Task Force Membership MemberOrganization Co-Chairs Christopher ChuteChief Health Information Research Officer, Johns Hopkins Medicine Floyd EisenbergiParsimony, LLC Members Marjorie RallinsAmerican Medical Association Gay DolinIMO – Intelligent Medical Objects Rob McClureMD Partners, Inc. Joseph JentzschKaiser Permanente Federal Ex Officio Nancy J. OrvisDepartment of Defense Debbie KrauseCenters for Medicare & Medicaid ONC Staff Julia SkapikONC Staff Lead 1

3 Task Force Charge Charge: Should transitional vocabularies be eliminated as alternatives in reporting to federal quality measure programs using EHR-captured clinical data elements? If so, which ones and by when? Secondary Questions: What is the impact of retaining the transitional vocabularies on the reliability and validity of measure results? What are the potential costs and implementation impacts on vendors and providers? How does that compare to the current situation with vocabulary alternatives? Assumptions: EHR vendors and providers have a pressing need to know what approach will be taken in regards to transitional vocabularies as soon as possible to plan and program accordingly. Measure developers have an even more pressing need for this decision, as changes to the current approach could change measure workflows and will change large volumes of value sets, although removal could result in simplified measure development costs and testing efforts. vocabulary experts agree that there are benefits to using a single code system but that there are costs to this approach including at least initially increased effort of mapping. 2

4 Task Force Discussion Questions 1.Should there be more than one vocabulary assigned to a data element at any one time? If so, we want to recommend that any potential areas where two vocabularies exits be adjusted so only one is needed (e.g., QDM diagnosis/condition) 2.Are the vocabularies listed in slide #4 reasonable? If they are, are there mappings that still exist. Just because they are listed in NLM this doesn't mean they have been tested to do what we're expecting them to be used for and how would we know that? Ask NLM for mappings across transitional vocabularies. 3.Are there actually multiple methods of collection and are we going to identify the burden for change to make a recommendation? There is lots of mapping happening because most things are not captured in any of the codes systems at the interface level. Most people are capturing in their native system then mapping to share. 4.Once we come to some kind of conclusion and can enumerate costs and benefits we then have to address the related issues of barriers, validity, and cost. Office of the National Coordinator for Health Information Technology 3

5 Transitional Vocabularies ConceptPreferred terminologyTransitional Vocabulary Condition/Diagnosis/ProblemSNOMED CT ICD-9-CM, ICD-10-CM Encounter (any patient-provider interaction, e.g., telephone call, e-mail regardless of reimbursement status, status—includes traditional face-to-face encounters) SNOMED CTCPT, HCPCS, ICD-9-CM Procedures, ICD-10-PCS Diagnostic study test namesLOINCHCPCS InterventionSNOMED CTCPT, HCPCS, ICD-9-CM Procedures, ICD-10-PCS ProcedureSNOMED CTCPT, HCPCS, ICD-9-CM Procedures, ICD-10-PCS CommunicationSNOMED CTCPT, HCPCS Office of the National Coordinator for Health Information Technology 4

6 MeetingsTask Wednesday, October 14 th 10:30-12:00pm EST - Kick Off Meeting Membership introductions Review charge and work plan Identify action steps  Wednesday, November 4 th 11:00-12:30pm EST Task Force Discussion Friday, November 20 th 9:30-11:00am EST Task Force Discussion Wednesday, December 2 nd 11:00-12:30pm EST Task Force Discussion Develop Preliminary Task Force Recommendations Wednesday, December 10 HITSC Meeting Present Draft Recommendations to HITSC Wednesday, December 16 th 11:00-12:30pm EST Refine Recommendations, if needed Wednesday, January 20 – HITSC Meeting Present Final Recommendations to HITSC, if needed Transitional Vocabulary Task Force Meeting Dates/Workplan 5


Download ppt "Wednesday, November 4 th 2015 Transitional Vocabulary Task Force Christopher Chute, Co-Chair Floyd Eisenberg, Co-Chair."

Similar presentations


Ads by Google