I’ve made the transition to health IT relatively recently. In May that I started doing some contract work as tech writer for a health IT vendor, then looked around for health IT related gigs – if there was a business analyst or tech writer posted in the DC/Baltimore area on Craigslist or Monster, you can bet that my resume was in there somewhere. It took me a good two months of searching to land my current job (and after two months of email after email saying “sorry, your resume didn’t make the cut”, I got three job offers in the same week – true story.) This is what I’ve learned along the way:
1) Having health-care related credentials helps: It can be anything – a degree, college coursework, actual paying jobs or volunteer positions you’ve held. In my case, I had a B.S. in pharmacy with a minor in IT, and a masters in Communication, so it seemed as if a health IT tech writer gig would be perfect for me. I believe that adding the “My undergrad major was pharmacy” in my cover letters was the phrase that opened doors for me.
2) Volunteer: I have mixed feelings about this piece of advice. It’s a well known secret that employers want certifications in vendor-specific products in the candidates they shortlist, which makes it something of an impossibility for regular IT folks looking to transfer to health IT.
On the HIMSS blog, there was a really interesting discussion from some time ago on healthcare employers not getting enough trained health IT people. The comment section was really enlightening – a commenter said “I’d like to share a little known secret: many hospital employees, IT included, are hired as a result of volunteer activities at the very same hospital that he or she volunteered at.”
Someone else commented that “An open secret in the NPO world is that they get many person hours donated with the unstated goal of being hired but no person ever actually receives employment. Especially in towns with many colleges and universities, some NPOs glean many free person hours from students and depend on the myth that all NPOs hire this way.”
So in effect: you might get a paid health IT gig after volunteering at a hospital or similar setting, but such NPOs are also the most liable to take advantage of you by dangling the job carrot before you. Also volunteering when you’re a newbie to the workforce might make sense, but I’d really love to see how that might help a mid-career IT person with a few years of experience under her belt, and with mouths to feed at home. I’m not discounting it entirely, but I’d do my research (how many volunteers were actually hired, and so on).
3) Hone up on healthcare concepts skills: HIMSS has a great repository Health IT Body of Knowledge. Read some blogs, follow the #EMR #EHR twitter feeds, or check out the thought leaders on Quora. Figure out which aspect of health IT interests you – is it the mobile apps sector, or EMR product development?
4) Learn from the greats: I really lucked out that I got some great health IT mentors this year who worked with me into turning the raw ingredients of my healthcare knowledge into something semi-cooked. And this is true of any area where you’re a learner – the more you show your enthusiasm for something, the more people are willing to teach you what they know. If there’s someone in your office or friends circle who is a walking encyclopedia of anything health IT, talk to them, and ask for their advice. If you don’t know any such person, make online relationships by commenting on blogs or following conversations on twitter. Read what the greats read, engage them in conversations. Knowledge osmosis will take care of the rest.