never been through a panel interview before so was just curious if there was something more that she didn't get the first time, or if there was anything else i needed to prepare for aside from all the interview info i've already gone through for the 1st interview?
meeting with a panel for a job in the informatics field is standard procedure because you'll be working with different teams and they want to make sure that you will not only fit in with those teams, but fit in the culture of those teams. in your case, it sounds like they want you to meet the 'rest of the team,' which is standard procedure. i personally have even gone through 4-5 interview panels for one job, mainly because it was a larger hospital and the position required a lot of interaction with different departments.
when you interview for a normal nursing job, they are just looking to see if you have the skills and maybe the experience, but they never say, lets bring you back so you can interview with the rest of the floor because if that was the case, hospitals i guess would never hire anyone. :d very different in informatics, and in the it world.
i'm thinking i should maybe prepare to answer more nursing related questions relating to computer charting since i will be meeting with other rn's and doctor?? any clue??
panel interviews are very dynamic because every person in the panel is looking for something different. for me, these interviews are different because i have experience so they always ask me questions related to past projects; when we have interviewed entry level candidates, questions were always different because it depended on the experience of that candidate, but like i said before, questions were geared to see if the person was trainable, personable, and able to handle priorities.
but the questions came out differently....you won't get a question like, 'so tell us, how do you handle priorities', but more like, 'you come to the office today, and you have something that is due, by 10 am, and you just need an hour or so to finish it, but you get a call from doctor xyz and he says he needs help right away charting orders---what do you do?' and there are tons of variations to that question, as you can imagine.
maybe they can ask you a general question like, 'what is your experience with electronic charting,' and if you have any experience other than just charting, then you can bring that in; and by that i mean, if you have had experience training other nurses on how to use the emr, or maybe you were asked to give input on how to improve an emr, or maybe you helped testing a new feature of the emr, etc.
bottom line, is very difficult to guess the questions in a panel, but for the most part they are looking for specific things in candidates, and that all varies by hospital, job position, and interviewing panels. one thing to note as a future tip though is, whenever you have a first interview, once they tell you that you're having a panel interview, you can always ask, 'what specific job qualifications is the panel looking for?' i know i have had jobs that were mainly to configure an application or train staff, so hiring managers will tell you, 'we are looking for this and that,' so you know that when the panel interview comes along there will be questions to address those requirements.
oh, and also one other question. are there any other questions besides work environment and level of support from superior that i can ask to help me determine if i will be supported in this role?
i typically ask, what type of training do you offer, and if a problem comes up that is not supported by the existing documentation, what other resources do i have to solve the problem? or, what type of access do i have to the vendor of this emr for problems that i won't be able to solve?
and finally....if you feel good about the position, just go for it. you do have to train yourself to not take things personally. you will learn to answer many questions with, "that's a really good question, let me get back to you on that once i find out more." believe me, you can not know it all in this business.
and yes, staff not being compliant or insulting you or the product is always a problem, and is a matter of getting along with people and like i said before, learning to not take things personally; i have dealt with supposedly 'nasty' doctors who actually come out looking for me to help them because they say, 'that guy knows his stuff, can you send him over?' and believe me, many times i don't know some of the questions they have, but is about acting professional, putting on a 'smart' and confident appearance, and not taking it personally.
finally working at a smaller hospital is a lot better because is a good way to get your foot in the door without being overwhelmed too much; i have implemented projects at smaller hospitals and implementations are not as complex, but they follow the same structure than implementing at a larger hospital, and therefore, this is a good opportunity for you to get ready for the major leagues later on. :d