Difference between revisions of "Vendor Selection Criteria: Interoperability"
(→Content Standards) |
|||
| Line 16: | Line 16: | ||
=== Content Standards === | === Content Standards === | ||
* The content standards consist of [[Extensible Markup Language (XML)|XML]], [[HL7]], [[Clinical Document Architecture (CDA)|CDA]] and [[DICOM]].<ref name="Hoyt"/> | * The content standards consist of [[Extensible Markup Language (XML)|XML]], [[HL7]], [[Clinical Document Architecture (CDA)|CDA]] and [[DICOM]].<ref name="Hoyt"/> | ||
| − | There are mainly two types of contents in clinical data; 1. Structured Data, which is computationally tractable and used in Billing, Lab reports, problem lists and others and 2. Unstructured Data, which is usually physician dictations that is free text, this is not computationally tractable and requires Natural Language Processing. Data extractors likes cTAKES, METAMAP and MEDLEE are used to process free texts.<ref name="Hoyt"> < | + | There are mainly two types of contents in clinical data; 1. Structured Data, which is computationally tractable and used in Billing, Lab reports, problem lists and others and 2. Unstructured Data, which is usually physician dictations that is free text, this is not computationally tractable and requires Natural Language Processing. Data extractors likes cTAKES, METAMAP and MEDLEE are used to process free texts.<ref name="Hoyt"> <Hoyt, R. E. Y. A. (2014). Health Informatics: Practical Guide for Healthcare and Information Technology Professionals (Sixth Edition) eBook: Robert E. Hoyt, Ann Yoshihashi: Kindle Store. Retrieved September 14, 2015, from http://www.amazon.com/gp/product/B00LBOO3Y8?psc=1&redirect=true&ref_=oh_aui_d_detailpage_o00_></ref> |
=== Terminology Standards === | === Terminology Standards === | ||
Revision as of 06:27, 23 September 2015
Contents
Interoperability
When selecting a vendor for EHR implementation, interoperability or functionality should be considered. In a 2015 publication, "What makes an EHR "open" or interoperable?" there were five cases where interoperability should be considered when selecting an EHR. The following should be considered:
- Clinicians- essential to provide safe and effective care
- Researchers- critical to advance and understand disease processes
- Administrators - to reduce the dependence on one EHR vendor
- Software developers- to develop interface and software
- Patients- important to access personal health information
Widespread access to EHR information is important if the full potential of the electronic health care system is to be realized.[1]
The purpose of EHR is to provide access of patient information to the right people at the right time. Interoperability is the ability to exchange this information between different EHR systems and stakeholders. [2] There are standards considered by the Health IT. These standards are divided into 3 different categories: content, terminology and transport.[3]
Content Standards
There are mainly two types of contents in clinical data; 1. Structured Data, which is computationally tractable and used in Billing, Lab reports, problem lists and others and 2. Unstructured Data, which is usually physician dictations that is free text, this is not computationally tractable and requires Natural Language Processing. Data extractors likes cTAKES, METAMAP and MEDLEE are used to process free texts.[3]
Terminology Standards
Transport Standards
- The transport standards consist of ELINCS, IEEE 11073, NCPDP and ASC X12.[3]
References
- ↑ Sittig, D.F., Wright, A. (2015). What makes an EHR "open" or interoperable? Journal of the American Medical Informatics Association. http://jamia.oxfordjournals.org/cgi/doi/10.1093/jamia/ocv060
- ↑ http://www.healthit.gov/providers-professionals/faqs/what-ehr-interoperability-and-why-it-important
- ↑ 3.0 3.1 3.2 3.3 3.4 Hoyt, R. E., & Yoshihashi, A. K. (Eds.). (2014). Health Informatics: Practical Guide for Healthcare and Information Technology Professionals (6th edition)
