Since many readers may have considered such a move, I was interested to read an interview with a woman who had transitioned from an Epic-based staff position at hospital to a consulting gig. Here are some of the steps she took, which offer food for thought for those who might want to follow in her footsteps.
Prior to going into Epic consulting, Pam (no last name given) had worked full time as a Clindoc/Stork analyst, specializing in Reporting Workbench and Radar dashboards. The hospital where she worked with deploying Epic for the first time as their EMR solution, a three-year project spanning 14 hospitals in her health system. Prior to that, Pam had worked in both IT and in the ICU as an RN.
Before she agreed to take the consulting position, which requires her to travel to the northeast once a week, Pam weighed the effect all the required travel would have on her spouse and family, as well as her elderly parents and in-laws.
She also bore her financial situation in mind. While she knew she could earn more as an Epic consultant than she could as a staff member, she also wouldn’t have access to company benefits such as retirement plans, health insurance, and paid sick days and vacation time. (Now that she’s consulting, Pam works with a financial analyst to create a personal retirement plan.)
To market herself as a consultant, Pam began by updating a resume to reflect the most current experience, including, obviously, her Epic experience. She researched Epic consulting firms in sent her resume to those that seemed appropriate. She also pulled together her personal and professional references, getting their permission to be contacted by firms interested in learning more about her. Then she worked with recruiters and consulting firms to capture her desired position.
One cautionary note from her story: Despite her experience level, as well as her having obtained in additional Epic proficiency and badge, she didn’t get a job immediately. In fact, it took her seven months to find an opportunity that fit her skills, a period she calls “long and difficult.” But she tells the interviewer that all the effort was worth it.
A few comments from the peanut gallery: While Pam has done well, the ending of the story — that she ended up waiting nearly a year to get her Epic job — came as a surprise to me. Yes, we are not in the absolute heyday of Epic consulting, as we were a few years ago, I would’ve assumed that an experienced professional with both clinical and IT background would’ve been snapped up much more quickly.
After all, while most hospitals may have made their big initial EMR outlay, maintaining those bad boys is an ongoing issue, and last I heard few have the resources to do so without outside help. Not only that, I doubt Epic has begun to hand out certifications like fortune cookies.
So why would there be a glut of Epic consultants, if there is in fact one? All I can think is that 1) the prevalence of Epic installations has led to more trained people being available, and 2) that hospitals have figured out how to maintain their Epic systems without as much outside help as they once had.
Either way, there may be a warning in this otherwise upbeat story. If you are thinking about hanging out your shingle as a Epic consultant, you may want to check out demand before you do. You may also want to spend some time searching through the Epic and other Healthcare IT jobs on Healthcare IT Central.