Life of a Consultant Clinical Analyst In the Nursing Informatics Department

*articles contain affiliate links*

Life of a Consultant Clinical Analyst In the Nursing Informatics Department

Life of a Consultant Clinical Analyst In the Nursing Informatics Department

In this post, guest blogger Chris will exam the typical workday and responsibilities of a Clinical Analyst Consultant (also known as an informatics nurse).

Life of a Consultant Clinical Analyst

Use this table of contents to jump to any section.

I am a registered nurse who worked in the clinical setting for about 10 years. I decided to quit bedside nursing and now work as a clinical analyst consultant. I maintain a blog for entry level candidates seeking to enter the nursing informatics field.

A snapshot of 3 days in my role as a Consultant Clinical Analyst in the nursing informatics department:

One of the projects I was involved in included implementing a surgical solution in a small size hospital with 12 OR beds. This hospital is part of a network of 3 other hospitals, which I’ll call A, B and C. The goal was to move all paper documentation (pre-op, intra-op, post-op) to electronic documentation, implement a new scheduling system, tracking board, and electronic picklist.

Last week we met with the OR department and we did a demo of how the application works, did a walkthrough of the facility, and this week’s goal is to start the design analysis and possibly do some data collection. At the same time, I assist the other 3 hospitals with any issues that might occur.

Day 1 in the Life of an Informatics Nurse

08:00

-Arrive at the office, open up emails and get caught up with emails from last week.

-I see two emails marked as urgent. Hospital A is requesting an emergency fix/change to one of their post-op forms. It appears the form is not working properly and their analyst needs help troubleshooting problem.

-The other email marked urgent is hospital B wanting to make some design changes to their forms and they want to see if there will be any downstream impact by their request.

-I quickly type the troubleshooting steps to the analyst at Hospital A and inform him that, if the steps don’t work, to email me back and let me know so that we can set up a time to review the issue

-I let Hospital B know that I’ll take a look at their design changes later on during the day.

09:00

-We have a meeting scheduled with the intra-op, pre-op and post-op nurses to review current paper workflow they use to document cases. There doesn’t seem to be a consensus as to what the proper workflow should be and it seems that the representative sent by the intra-op department that is not well versed in the intra-op workflow. There is a request to meet again with the proper people to make the right decisions. Not a good start for the week nor this project.

-Will discuss the incident with a project manager.

10:00

-Meeting with the scheduling department to give a 2nd demo on how the scheduling application works and to answer issues they could raise. The scheduling group believes that the application is too slow and that it doesn’t allow them to track the techs who run equipment. We addressed the slow issue by actually scheduling patients using shortcuts that were not detailed in the previous demo and staff was pleased. Yet, we have to come up with a solution to the tech scheduling tracking issue.

11:00

-Back to my desk and check/reply to emails.

-An analyst from hospital A has replied. My steps didn’t fix the issue. He wants to know if there is any chance I can log on to their system today. They have opened a ticket with the vendor already, but most likely the vendor will only get back to them within a couple of days. As I have time later in the afternoon, we set up a meeting at 4 pm.

12:00

-Lunchtime

13:00

-Back from lunch. There are strings of emails from the OR group. They seem to be having conflicts scheduling the meeting. The only available date is at the end of the week, which will put the project timeline in jeopardy. Meeting needs to take place asap.

-I write emails to the project manager and site manager to let them know of the situation. In the meantime, my other analyst colleague is trying to get a hold of the OR director to address the scheduling conflict directly with her.

14:00

-Head out to meet with the OR manager, but she has an impromptu meeting with a couple of surgeons.

-We decide to hit the cafeteria, get a cappuccino and come back to meet the OR manager.

14:30

-We meet with the OR manager. We discuss the timeline and talk about the OR meeting. As the right pre-op personnel didn’t attend, we found ourselves in the impossibility to map the current workflow. OR manager emphasizes that staff is short, whereas we emphasize the project timeline. After going back and forth, we decide that if pre-op doesn’t show up, then intra-op will make decisions for them, and they will fix any issues later. There is a real risk though that they won’t be happy with the documentation, hence the importance to send the right pre-op staff to the meeting. OR manager understands the situation and agrees to schedule a meeting for Wednesday morning with the proper staff.

15:30

-Back to my desk, inform hospital B that I won’t be able to look at their design until next day.

-Make sure the presentation is ready for the supply chain meeting the next day.

16:00

-Call analyst from Hospital A to assist in troubleshooting the problem. I log on remotely to the system and we go through the basic setup of the form, which looks fine. Then I notice that one of the rules appears to have the wrong logic. I ask to have the rules emailed to me for more analysis.

-Once I get the email with the rules I start analyzing. I reconfigure the rule in the test domain, but after about 30 min of troubleshooting, I’m still getting the error. I decide to go home and give it a try the next day.

Day 2 in Informatics Nursing

Tuesday:

07:00

-Meet up with the supply chain team. Fortunately, their senior member worked at a different hospital with a similar implementation and she understands the process of the data we need, but we just need to review the workflow to make sure it will actually work. What a relief! We also find out that we can only get the current supplies out of their database in a text file, but some of them will repeat, some others are indistinguishable from facility A to B, and a lot of them are no longer used. No problem, I can transfer the text file to the Access database, remove duplicates, and then try to analyze data to come up with the proper equipment.

08:30

-Back at the desk. Check emails again. A lot of meetings seem to be piling up for next week and not sure if I need to attend all.

09:00

-Attend project management meeting to discuss timelines and risks to project. So far we are on track, except for the minor delay with the OR team, but that should be ok, as long as we meet with them again during the week.

10:00

-Back to desk, check emails, pull up a query from last evening. I go through the logic of the rules again and I realize that I put the wrong operator in one of the statements. Shameful! I test the query again and it works. I page the analyst from hospital A to notify them of the results. He will test it again and then implement.

11:00

-I have time to review Hospital’s B design change. I discuss it also with another analyst and we don’t really see downstream effects. But we do notice that it doesn’t follow the standard methodology agreed by all hospitals in the network. The hospital insists that they have a different population of patients. We make our recommendations by email to hospital B.

12:30

-Quick lunch at the cafeteria

13:00

-Meet with hospital’s B new systems analyst to train her on how to configure and maintain the tracking board.

14:30

-Supply chain sent me the first text file of supplies/equipment. I import it into Excel and some of the columns don’t line up. I spend some time fixing that, then create a small access database file to find out duplicates in the file. Then I inspect the resulting data. The same equipment shows up with different naming convention. I email the resulting file to supply chain manager and tell her to look at the highlighted values and inform me of the pattern so that I can further analyze the file.

16:00

-I try to catch up with more emails, but I’m also tired and head home.

Day 3 as a Clinical Informaticist

Wednesday

08:45

-Arrive at the office, check emails…

09:00

-Attend weekly staff meeting

10:00

Attend OR meeting. Pre-op sent the right person this time. There are concerns about the workflow of printing out documentation and vital signs. This topic threatens to overtake the meeting. We bring meeting back to getting workflow documented and then we will deal with the printing issue. What we need is to get the current workflow documented on paper so that we can optimize it when moving to the electronic record.

11:45

-Back at the desk.

-Hospital C is requesting help with one of their upload files. System crashes any time upload is attempted. The file had been used before, so it can’t be a problem with the file. I figure it must be the data in the file. I start combing through the data and after 30 minutes I determine an empty space was causing the problem. I test file in the test environment and it works. Send fix to hospital C.

12:30

-Lunch

13:30

-Back at my desk. There’s an email from Supply Chain Manager. She has decoded the highlighted data and now I can work on cleaning out the file with the current supplies. There is also another large text file with more supplies that I will have to clean up in Access.

14:00

-I start writing the OR minutes from earlier today. I also get together with the other analyst and we go over the current OR workflow, which looks fairly straightforward. As we had collected the current paper documentation forms, we start analyzing them. We discover some minor redundant documentation and we make a note to clarify the issue in the next meeting. We can actually start building the basic forms in the test domain, but we get word that test domain will be down for maintenance at 16:00

16:00

-I continue to break down supply chain files in MS Access.

Note – Informatics nurses go by many names and titles such as clinical informatics specialist, informatics nurse, health informatics nurse, and so on. When trying to find out if this just is right for you, be sure to read the job description as the workload and responsibilities of positions vary.

See also:

 

Clinical Analyst TshirtClinical Analyst TshirtClinical Analyst TshirtInformatics and Nursing: Opportunities and ChallengesInformatics and Nursing: Opportunities and ChallengesInformatics and Nursing: Opportunities and ChallengesHealth Informatics: An Interprofessional ApproachHealth Informatics: An Interprofessional ApproachHealth Informatics: An Interprofessional ApproachMens Informatics Is My Sport T-Shirt Informatics Gift Tee 2XL NavyMens Informatics Is My Sport T-Shirt Informatics Gift Tee 2XL NavyMens Informatics Is My Sport T-Shirt Informatics Gift Tee 2XL NavyThe Nerdy Nurse's Guide To TechnologyThe Nerdy Nurse’s Guide To TechnologyThe Nerdy Nurse's Guide To Technology

8 thoughts on “Life of a Consultant Clinical Analyst In the Nursing Informatics Department”

  1. I too am a nurse. I “fell” into Nursing Informatics quite by accident on my way to pursuing other more traditional nursing options.
    I’m often asked by other nurses, new and more seasoned, how to get into informatics. What I have to gently tell them is I don’t know they can “get into” the field, since everyone I know who is active in this field came upon it by accident or were lucky enough to be invited to join in an implementation which offered to teach them the software.
    I was happy to come across your blog because I am finding that other informatics with a nursing background are few and hard to find, and it’s actually kind of nice to know there are more of us out here, somewhere..(~_^)

    1. Nurses in IT are rising in numbers.

      There are 4 nurses where I work.

      I find that many informatics nurses are sort of corralled into their role. However, there are many organizations that are willing to take nurses with enough drive and passion and train them to do it outright. I’m living proof of that. I am so thankful for the wonderful opportunity I was given and the great work I get to do every day.

  2. Hello Chris, 

    I just passed my RN license exam and I am good with computers. I know the basic things but I really really want to get into Nurse Informatics Field. Can you please guide me? What should I know to be entry level clinical analyst, what can I learn in the shortest time span? 

    1. Hi Chris,

      Most positions want 3-5 years of clinical experience minimum. I honestly probably wouldn’t even try before that. I had 3, and even then it was very difficult. You also should have worked as a super user, if possible. A strong understanding of software and how to repair technical issues is also recommended.
      There are masters degree programs that you can go too, but it’s not required to get a job.
      Start at the hospital you are employed at. You will have the best chances getting your foot in the door there.

Leave a Comment

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

shares
Scroll to Top