Special Topics in Vendor- Specific Systems Unit 6 Vendor strategies for terminology, knowledge...

23
Special Topics in Vendor-Specific Systems Unit 6 Vendor strategies for terminology, knowledge management, and data exchange

Transcript of Special Topics in Vendor- Specific Systems Unit 6 Vendor strategies for terminology, knowledge...

Page 1: Special Topics in Vendor- Specific Systems Unit 6 Vendor strategies for terminology, knowledge management, and data exchange.

Special Topics in Vendor-Specific Systems

Unit 6Vendor strategies for terminology, knowledge management, and data

exchange

Page 2: Special Topics in Vendor- Specific Systems Unit 6 Vendor strategies for terminology, knowledge management, and data exchange.

Objective

• Evaluate EHR strategies for terminology management, knowledge management and data exchange

Component 14/Unit 6Health IT Workforce Curriculum

Version 1.0/Fall 20102

Page 3: Special Topics in Vendor- Specific Systems Unit 6 Vendor strategies for terminology, knowledge management, and data exchange.

After this completing this unit, you should be able to:

• Define interoperability

• Describe vendor strategies for terminology and knowledge management, and how these impact interoperability

• Describe processes and requirements for exchanging data with personal health records

Component 14/Unit 6Health IT Workforce Curriculum

Version 1.0/Fall 20103

Page 4: Special Topics in Vendor- Specific Systems Unit 6 Vendor strategies for terminology, knowledge management, and data exchange.

InteroperabilityIf I’m faxed a discharge summary which I can read, is that interoperable, since it’s human interpretable? If I’m sent an electronic note via email that notes “Allergy to MS”, is that interoperable? Of course MS could mean Morphine Sulfate, Magnesium Sulfate, or even Minestrone Soup. If I’m sent an electronic message which has an agreed upon format, a standard vocabulary, and a set of business rules which enable me to take action, is that interoperable? i.e. Your patient is allergic to medication NDC Code 123456789. Administration will cause a SEVERE reaction with HIGH CONFIDENCE. My e-Prescribing software could use this information to display a warning alerting me to the issue and could suggest an effective alternative medication.

» John D. Halamka MD, MS, Chair, Health Information Technology Standards Panel (HITSP)

Component 14/Unit 6Health IT Workforce Curriculum

Version 1.0/Fall 20104

Page 5: Special Topics in Vendor- Specific Systems Unit 6 Vendor strategies for terminology, knowledge management, and data exchange.

Three Types of Interoperability:

Component 14/Unit 6Health IT Workforce Curriculum

Version 1.0/Fall 20105

Page 6: Special Topics in Vendor- Specific Systems Unit 6 Vendor strategies for terminology, knowledge management, and data exchange.

Technical InteroperabilityIf I’m faxed a discharge summary which I can read, is that interoperable, since it’s human interpretable? If I’m sent an electronic note via email that notes “Allergy to MS”, is that interoperable? Of course MS could mean Morphine Sulfate, Magnesium Sulfate, or even Minestrone Soup. If I’m sent an electronic message which has an agreed upon format, a standard vocabulary, and a set of business rules which enable me to take action, is that interoperable? i.e. Your patient is allergic to medication NDC Code 123456789. Administration will cause a SEVERE reaction with HIGH CONFIDENCE. My e-Prescribing software could use this information to display a warning alerting me to the issue and could suggest an effective alternative medication.

» John D. Halamka MD, MS, Chair, Health Information Technology Standards Panel (HITSP)

Component 14/Unit 6Health IT Workforce Curriculum

Version 1.0/Fall 20106

Page 7: Special Topics in Vendor- Specific Systems Unit 6 Vendor strategies for terminology, knowledge management, and data exchange.

Technical Interoperability: Messaging Standards

Component 14/Unit 6Health IT Workforce Curriculum

Version 1.0/Fall 20107

MSH|^~\&|GHH LAB|ELAB-3|GHH OE|BLDG4|200202150930||ORU^R01|CNTRL-3456|P|2.4<cr> PID|||555-44-4444||EVERYWOMAN^EVE^E^^^^L|JONES|19620320|F|||153 FERNWOOD DR.^ ^STATESVILLE^OH^35292||(206)3345232|(206)752-121||||AC555444444||67-A4335^OH^20030520<cr> OBR|1|845439^GHH OE|1045813^GHH LAB|15545^GLUCOSE|||200202150730||||||||| 555-55-5555^PRIMARY^PATRICIA P^^^^MD^^|||||||||F||||||444-44-4444^HIPPOCRATES^HOWARD H^^^^MD<cr> OBX|1|SN|1554-5^GLUCOSE^POST 12H FST:MCNC:PT:SER/PLAS:QN||^182|mg/dl|70_105|H|||F<cr>

Page 8: Special Topics in Vendor- Specific Systems Unit 6 Vendor strategies for terminology, knowledge management, and data exchange.

Semantic Interoperability

Component 14/Unit 6Health IT Workforce Curriculum

Version 1.0/Fall 20108

MSH|^~\&|GHH LAB|ELAB-3|GHH OE|BLDG4|200202150930||ORU^R01|CNTRL-3456|P|2.4<cr> PID|||555-44-4444||EVERYWOMAN^EVE^E^^^^L|JONES|19620320|F|||153 FERNWOOD DR.^ ^STATESVILLE^OH^35292||(206)3345232|(206)752-121||||AC555444444||67-A4335^OH^20030520<cr> OBR|1|845439^GHH OE|1045813^GHH LAB|15545^GLUCOSE|||200202150730||||||||| 555-55-5555^PRIMARY^PATRICIA P^^^^MD^^|||||||||F||||||444-44-4444^HIPPOCRATES^HOWARD H^^^^MD<cr> OBX|1|SN|1554-5^GLUCOSE^POST 12H FST:MCNC:PT:SER/PLAS:QN||^182|mg/dl|70_105|H|||F<cr>

Page 9: Special Topics in Vendor- Specific Systems Unit 6 Vendor strategies for terminology, knowledge management, and data exchange.

Semantic Interoperability (cont.)

If I’m faxed a discharge summary which I can read, is that interoperable, since it’s human interpretable? If I’m sent an electronic note via email that notes “Allergy to MS”, is that interoperable? Of course MS could mean Morphine Sulfate, Magnesium Sulfate, or even Minestrone Soup. If I’m sent an electronic message which has an agreed upon format, a standard vocabulary, and a set of business rules which enable me to take action, is that interoperable? i.e. Your patient is allergic to medication NDC Code 123456789. Administration will cause a SEVERE reaction with HIGH CONFIDENCE. My e-Prescribing software could use this information to display a warning alerting me to the issue and could suggest an effective alternative medication.

» John D. Halamka MD, MS, Chair, Health Information Technology Standards Panel (HITSP)

Component 14/Unit 6Health IT Workforce Curriculum

Version 1.0/Fall 20109

Page 10: Special Topics in Vendor- Specific Systems Unit 6 Vendor strategies for terminology, knowledge management, and data exchange.

Semantic Interoperability: Terminology Standards

Component 14/Unit 6 10Health IT Workforce Curriculum

Version 1.0/Fall 2010

Page 11: Special Topics in Vendor- Specific Systems Unit 6 Vendor strategies for terminology, knowledge management, and data exchange.

ICD-9 Codes

Component 14/Unit 6Health IT Workforce Curriculum

Version 1.0/Fall 201011

Page 12: Special Topics in Vendor- Specific Systems Unit 6 Vendor strategies for terminology, knowledge management, and data exchange.

Transition to ICD-10

Component 14/Unit 6 12Health IT Workforce Curriculum

Version 1.0/Fall 2010

Page 13: Special Topics in Vendor- Specific Systems Unit 6 Vendor strategies for terminology, knowledge management, and data exchange.

LOINC

Component 14/Unit 6Health IT Workforce Curriculum

Version 1.0/Fall 201013

MSH|^~\&|GHH LAB|ELAB-3|GHH OE|BLDG4|200202150930||ORU^R01|CNTRL-3456|P|2.4<cr> PID|||555-44-4444||EVERYWOMAN^EVE^E^^^^L|JONES|19620320|F|||153 FERNWOOD DR.^ ^STATESVILLE^OH^35292||(206)3345232|(206)752-121||||AC555444444||67-A4335^OH^20030520<cr> OBR|1|845439^GHH OE|1045813^GHH LAB|15545^GLUCOSE|||200202150730||||||||| 555-55-5555^PRIMARY^PATRICIA P^^^^MD^^|||||||||F||||||444-44-4444^HIPPOCRATES^HOWARD H^^^^MD<cr> OBX|1|SN|1554-5^GLUCOSE^POST 12H FST:MCNC:PT:SER/PLAS:QN||^182|mg/dl|70_105|H|||F<cr>

Page 14: Special Topics in Vendor- Specific Systems Unit 6 Vendor strategies for terminology, knowledge management, and data exchange.

Process InteroperabilityIf I’m faxed a discharge summary which I can read, is that interoperable, since it’s human interpretable? If I’m sent an electronic note via email that notes “Allergy to MS”, is that interoperable? Of course MS could mean Morphine Sulfate, Magnesium Sulfate, or even Minestrone Soup. If I’m sent an electronic message which has an agreed upon format, a standard vocabulary, and a set of business rules which enable me to take action, is that interoperable? i.e. Your patient is allergic to medication NDC Code 123456789. Administration will cause a SEVERE reaction with HIGH CONFIDENCE. My e-Prescribing software could use this information to display a warning alerting me to the issue and could suggest an effective alternative medication.

» John D. Halamka MD, MS, Chair, Health Information Technology Standards Panel (HITSP)

Component 14/Unit 6Health IT Workforce Curriculum

Version 1.0/Fall 201014

Page 15: Special Topics in Vendor- Specific Systems Unit 6 Vendor strategies for terminology, knowledge management, and data exchange.

Process Interoperability (cont.)

Component 14/Unit 6 15Health IT Workforce Curriculum

Version 1.0/Fall 2010

Page 16: Special Topics in Vendor- Specific Systems Unit 6 Vendor strategies for terminology, knowledge management, and data exchange.

Example: Cerner

Component 14/Unit 6 16Health IT Workforce Curriculum

Version 1.0/Fall 2010

Page 17: Special Topics in Vendor- Specific Systems Unit 6 Vendor strategies for terminology, knowledge management, and data exchange.

Example: Eclipsys

Component 14/Unit 6 17Health IT Workforce Curriculum

Version 1.0/Fall 2010

Page 18: Special Topics in Vendor- Specific Systems Unit 6 Vendor strategies for terminology, knowledge management, and data exchange.

Example: eClinicalWorks

Component 14/Unit 6 18Health IT Workforce Curriculum

Version 1.0/Fall 2010

Page 19: Special Topics in Vendor- Specific Systems Unit 6 Vendor strategies for terminology, knowledge management, and data exchange.

Examples of Third-party Terminology Products

Component 14/Unit 6 19Health IT Workforce Curriculum

Version 1.0/Fall 2010

Page 20: Special Topics in Vendor- Specific Systems Unit 6 Vendor strategies for terminology, knowledge management, and data exchange.

Personal Health Records

Component 14/Unit 6 20Health IT Workforce Curriculum

Version 1.0/Fall 2010

Page 21: Special Topics in Vendor- Specific Systems Unit 6 Vendor strategies for terminology, knowledge management, and data exchange.

Accuracy of EHR->PHR Data

Component 14/Unit 6 21Health IT Workforce Curriculum

Version 1.0/Fall 2010

Page 22: Special Topics in Vendor- Specific Systems Unit 6 Vendor strategies for terminology, knowledge management, and data exchange.

Benefits of PHRs

Component 14/Unit 6 22Health IT Workforce Curriculum

Version 1.0/Fall 2010

Page 23: Special Topics in Vendor- Specific Systems Unit 6 Vendor strategies for terminology, knowledge management, and data exchange.

Barriers to Linking EHR and PHR Data

Component 14/Unit 6 23Health IT Workforce Curriculum

Version 1.0/Fall 2010