Laboratory Technologist looking to move into IT field, really would love some help and guidance.
Hey everyone, I’ve worked 5 years as a medical technologist and I am looking to move into a health IT area. I originally wanted to do engineering but it would likely to be too hard with my life situation. So I am now looking at Health Informatics, or Information Systems, or even data analytics? I definitely want to make more money but my transition is mainly because I have been on computers my entire life, I dabbled in HTML/CSS since I was 11 or 12, and I’ve tried learning Python and programming languages on multiple occasions but have yet to do so.
I want to make a good decision and do something that would be interesting and fun and also have a much higher salary cap. I want to do an online masters, my employer will reimburse about 5,000 a year. I’ve also considered getting IT certifications and looking for jobs without even getting a degree right now if that’s even possible.
Would really appreciate insight as to what you are doing or what you do and what the jobs are like. What my options are, etc.
Thanks for any help
Posted Jun 17, 2019, 3:33 PM UTC
It’s tough because there is no blueprint. I was a tech for 10 years and just grabbed IT related projects and signaled to management that I wanted to get into LIS. I eventually did LIS part time at my hospital and used that experience to find full time LIS at other hospitals.
Get involved in the software aspects of the job and volunteer for projects.
If you are going into straight HIT rather than LIS then I have no advice.
As for what the work is like, I personally love it, a lot of examining what data crossed what interface when, test building, location building, modifying reports, etc. As for the pay, it’s typically higher in LIS than HIS...about 20k more than I made as a tech.
Being on call sucks, make sure wherever you land that it’s a shared responsibility. Don’t be one of those sad people that are permanently on call.
Can confirm, it is very saddening to be permanently on "non-critical call" for critical systems.