Google Health Discontinuing

Just a reminder to anyone that has their information on Google Health that they had announced that they will be discontinuing their service from January 1st, 2012.

To read more about this, I have shared the link here on this post.

https://accounts.google.com/ServiceLogin?service=health&nui=1&continue=https://health.google.com/health/p/&followup=https://health.google.com/health/p/&rm=hide

Advertisements

Testing Strategies during an EHR Implementation

You will certainly be ‘tested’ during Unit and Integration Testing time during an EHR implementation.

The keys to a successful Testing Cycle is of course great test scripts based on functional requirements that the users have shared with you at the beginning of the project and following them. Having teams that have at least some experience with the software and it’s workflow is ideal and have an understanding of what should happen on each and every screen, such as going through a Progress Note.

Try and understand what has gone wrong from previous experiences; whether it is of known bugs (you may have to work on this and try and get it out of the vendor as I am sure they won’t want to admit that there are any “bugs” at all) or some user forced errors. It is not a great distinction to be the first to find out about an bug in the system. Identifying dates for fixes as well as workaround if issues are discovered is an effective plan for action on any identified workflow issues. Additionally, always assume that the software will not perform the way you think it will and perform a stress test to try and simulate a “day in the life” environment as much as possible. Having 2 to 3 trial runs would be ideal. If you have a major code change, a strong suggestion would be to do “regression testing”, which checks to see if previously known bugs return after a patch is put in place and possibly interferes with previously written code. Summing it all up really is that the 3 most important words in prior to an EHR/EMR implementation Go Live are “Test, test, test!”

5010 statement shared across HIMSS Chapters today

ICD-10 Stakeholders Members,  P.O. Boxes No Longer Permitted in Billing Provider Address in 5010 Transactions Jan. 1

Do you use a P.O. Box or lock box address as you billing provider address to receive payments?  If you submit claims electronically, you will be required use only a street address or physical location as the billing provider address.  Continuing to report a P.O. Box in the billing provider address field will cause your claims to reject. Under the Health Insurance Portability and Accountability Act (HIPAA), all physicians and other health care providers that submit claims electronically are required to transition to the Version 5010 transactions by Jan. 1. 

One of many data reporting changes in the Version 5010 transactions is the requirement to report only a street address or physical location as the billing provider address. Practices that wish to continue having payments sent to a P.O. Box or lock box will report this address in the “pay-to” address field.   You may need to work with your practice management system vendor, billing service, or clearinghouse to have this address change made for your claims.  Talk to them today to find out if a change is needed and when it will be done.  This work needs to be done prior to Jan. 1 to prevent claims rejections and interruptions in your cash flow. Visit www.ama-assn.org/go/5010 or www.cms.gov/Versions5010andD0 for more information on data reporting changes in the Version 5010 transactions and to prepare your practice for the Jan. 1 deadline.

Mobile Device Strategy for EHR

“Let’s have a Device Fair!” or “Let’s get a few devices together and let the physicians make an educated choice.” Typical conversations during an EHR implementation or upgrade or migration.

I think quite frankly that physicians these days want to have “an app for it” if they are at all IT savvy and want that app to be on an Apple iPad. Unless the public starts to migrate away from Apple as the legion of fans of the late, great Steve Jobs possibly move their allegiences, I think Apple’s iPad will rule the roost for at least a few more years. Blackberry has lasted for about close to a decade and is only waning now (except for die-hard “keyboard vs. touch screen” fans).

(Note to self: Remember the function of the right click…iPads can’t right click yet…remember that when your physician wants to use it to complete their patient progress notes).

What is good strategy that has been used across healthcare organizations to purchase, develop policy, adopt and monitor compliance? I know that HIMSS had a great webinar on November 16th, 2011 on this.

Everybody at a hospital (especially Physicians) love their mobile devices as they have become the preferred in the healthcare domain. These have their pros and cons as anything, such as security for instance. When a physician receives an image sent by a patient of their tumor on their mobile device (via text), what should be done? Is this a breach of HIPAA? I have heard arguements for both sides (not that I necessarily believe the arguements for that). If the physician’s device is lost and data is breached, this can affect many individuals at once. I think that the focus should be on your overall device and computer usage policies and compliance to those policies that will be the clincher and how you can maintain those policies effectively, especially when the devices go offsite. Satisfying evolving regulatory policies, education on proper usage and risk mitigation will drive the day.

CHCIO Certification

Yesterday, one of the CIO’s that I have the honor of knowing mentioned to me that she had taken and passed the CHCIO (Certified Healthcare CIO) certification. I congratulated her and felt it was great achievement. The CHCIO certification is granted by  the College of Healthcare Information Management Executives.

http://www.cio-chime.org/

I believe that this will set apart healthcare CIO’s from other industry CIO counterparts to deal with the unique challenges that healthcare has in today’s environment.

The stress of an EHR implementation

We’ve all known that projects can be stressful at times and that patient safety and lives are affected when something goes wrong. Read these 14 tips that might help you manage your life more effectively. I know that “Time Management” is the most difficult aspect of life to manage. Maybe bending the fabric of time (watch Nova episode during week of November 7th, 2011) will give you some relief. if you can’t bend time, then check out the link below and just maybe, dealing with all those irritating issues during your EMR project (vendors, developers, physicians, project managers, testing, testing and oh and more testing) may be less of an irritant that you thought.

 http://www.datacenter-edge.com/content/fourteen-tips-managing-work-related-stress?slide=1

Big Bang EHR Implementation vs Phased Approach

I sat in on a great webinar from HIMSS the other day that covered an EHR implementation by a hospital system and it’s consulting partners Massachusetts. They had 18 physician pratices that covered areas from Primary Care to Neurosurgery and they went from a paper to a paperless EHR solution.  They spoke about how they went in for the Big Bang approach in their implementation and were then in their 9 day after go live. So far so good from what I heard. I wonder if that will continue.

Another great organization here in Columbus, Ohio recently did the same with their EHR implementation. I’m waiting to hear about that, hopefully during next year’s CSO HIMSS conference (if I can convince them to speak about it). Yes, the big bang approach can work folks!

If there is the big bang EMR approach, it forces everyone, physicians, clinical staff, administration and IT to get on the same page and fast, otherwise there could be the ability to continue with the old system and that would develop into political brinksmanship. Nobody wants that. There’s no political wrangling in healthcare!

While this approach can get the “rigors” of implementation over and done with, (pull off that bandaid at one go) the compressed timeframe may have long term repurcussions in terms of support. An example of this could be a more phased approach towards physician clinical/progress note development. Physicians may not always have the ability to document all of their information at a few sittings to develop a somewhat comprehensive note and that will lead to high frustration with the system. A phased project approach can reduce that frustration and EHR adoption rates could be higher.