This page contains a Flash digital edition of a book.
CPOEs should put physicians fi rst

Virtually every hospital that PatientKeeper works with says its biggest concern regarding meaningful use is physician adoption of CPOE and, perhaps even more so, physician documentation. These two have been the “third rail” applications of healthcare IT. It has been 40 years since the fi rst CPOE system was installed and we’re at less than 10 percent adoption. Adoption of electronic physician documentation in the inpatient setting is even lower. Given that the vast majority of this adoption has been at academic medical centers with residents, it is no wonder that community hospitals are concerned about whether traditional approaches will work for them.

What’s needed is an approach to CPOE that

puts physicians fi rst and creates an automated environment for physicians that saves them time and helps them do their job. After all, isn’t that what technology has done for the rest of the world? If the iPad was hard to use and didn’t help anyone do anything better or faster, do you think Apple would have sold 15 million of them? CPOE has been, by far, the most diffi cult challenge

Paul Brient, CEO, PatientKeeper

PatientKeeper has undertaken because there are so many ways to make it wrong for physicians. It is still early, but we’re making some great strides.

Using NLP technologies to achieve meaningful use

Cheryl Servais, MPH, RHIA, VP of compliance and privacy offi cer, Precyse Solutions

Many Stage 1 requirements can be addressed through the use of advanced natural language processing (NLP) technologies available today. While problem list creation is just one of many Stage 1 criteria, it need not be a major obstacle to early Stage 1 qualifi cation. By implementing a sophisticated NLP framework capability as an adjunct to the EMR/EHR system,

c o p a

j i

providers can create active problem lists based on either SNOMED-CT concepts or ICD-9-CM concepts or both. The inputted data sources can range from structured transcribed documents to OCR scanned data. Once the NLP engine is programmed to search the data to identify the patient’s various diagnoses and conditions, it will electronically return data to the target EMR/EHR application for view by caregivers in a process requiring no additional physician, nursing or clerical time. Furthermore, through the NLP engine, the data for the problem list can become an automatic byproduct of the transcription system.

Integration vendor can help achieve meaningful use When it comes to meaningful-use certifi cation, hospitals

are fi nding that they need to look beyond their core EHR systems when tackling public health objectives. Doylestown Hospital of Doylestown, Pa., needed a meaningful-use-certifi ed interface capable of functioning with the Pennsylvania Department of Health for their immunization data requirements. Summit Healthcare was chosen to work with Doylestown Hospital to accomplish this. In order to ensure that its interface received the

government’s meaningful-use stamp of approval, Doylestown and Summit Healthcare went through the Drummond Group’s ONC-ATCB program. The Drummond Group employed its sophisticated software- testing services to determine that the immunization registry interface met the meaningful-use standards

required by the Secretary of Health and Human Services. As a result, Doylestown Hospital became eligible to receive federal stimulus dollars as stipulated under the American Recovery and Reinvestment Act (ARRA). The certification shows how an integration vendor can help hospitals take part in the electronic revolution that is reverberating across the healthcare industry. Healthcare providers are able to leverage technology to not only make signifi cant improvements to their HIT systems, but also achieve meaningful use and qualify for incentive funds.

Ellen Bellini, product marketing manager,

Summit Healthcare HEALTH MANAGEMENT TECHNOLOGY May 2011 13

Page 1  |  Page 2  |  Page 3  |  Page 4  |  Page 5  |  Page 6  |  Page 7  |  Page 8  |  Page 9  |  Page 10  |  Page 11  |  Page 12  |  Page 13  |  Page 14  |  Page 15  |  Page 16  |  Page 17  |  Page 18  |  Page 19  |  Page 20  |  Page 21  |  Page 22  |  Page 23  |  Page 24  |  Page 25  |  Page 26  |  Page 27  |  Page 28  |  Page 29  |  Page 30  |  Page 31  |  Page 32  |  Page 33  |  Page 34  |  Page 35  |  Page 36