Business Analyst Healthcare Interview Questionc 416s65

1) How did you make sure that the requirements you gathered from the s are exactly what they are looking for? After every requirement gathering session, I developed meeting minutes that was a preliminary draft of the requirements gathered. These minutes were sent to the business s that were involved for review and to check for any disconnects and additional information. After the approval from all concerned parties was received the final document was produced and put into a formal template format for sign-off from the business s. 2) At the end of the project, was there any case when the might have come up and said this is not what I desired from the system? (In other words, they expected more from the system.) How did you handle that? Did you enhance the requirements and re-released the product? I was in such situation during my most recent project. The s expected a functionality which was not considered as part of the first release and they thought that the requirement existed in the functional requirements document. I pulled up the requirement specification document, the meeting minutes and showed them that the functionality had never been requested for. Since this was not an immediate requirement, the business s agreed to wait for the next release of the application to incorporate the functionality. 3) Have you worked on any Rational tools? I have normally worked on RUP methodology and Rational tools are based on the same. I am quite well versed with Rational Rose for making use case diagrams, use case documents, realizations etc. I have used Requisite pro for managing and documenting the requirements. 4) How far were you involved in the testing phase? These would be specific to your resume based on what project is being talked about. Example: During the testing phase I was responsible for: Developing Test Cases and Test Plans. Recording the observations of the s and reporting them back to my manager. Discussing any changes and updates with the and if need arises handling the Change Request procedures and tracking. 5) How do you decide which features to include in what releases? Everyone wants there features to be release in the 1st iteration. We normally decide on the features of the 1st release or any releases ahead on the basis of:  Business priority  What feature goes 1st based on the scope document.  Review with the business managers what they require in the 1st release and get their approval.  Business complexity/Risk 6) What is your main strength or what do you think that you have accomplished in your last project with which you are most proud of? I think my strength is my ability to be detail oriented. There are always times when there are disconnects or constant changes in the project and if information and documents are not well organized, it might lead to a disaster and failure. I am also quite detailed oriented which helps me to list the use cases and requirements properly and comprehensively so that there is minimum element of doubt.

7) What were the risks involved in the project? How did you come with the solutions for those risks? There were several risks involved in the project: Securities Regulations: During this project there were a lot of regulations involved which needed to be considered while developing the site. For example: who should be given what kind of access to the system, what path will the document How do you deal with difficult

stakeholders? Stakeholders sometimes could be difficult to deal with but we could overcome this situation by: Patiently listening to them and being polite.  Make them understand the situation from a prospective they understand. Show a commitment to working with them. Make them realize how their interests will be realized when they are more open and collaborative. Engage them and make them realize that their contribution is valued. What is the Importance of a Flow Chart? The flow charts gives a clear graphical representation of an implemented process, This makes the system simple to understand for all persons involved in the project. Explain briefly the use case Model? The use case model requires a use case diagram, It describes the business environment, It`s primary goal is to show the series of events and actions with in any given process that will be performed by an actor What is UML Modeling? UML means unified Modeling Lanugae,Its is industry standard language for constructing,visulazing and documenting the different componenets within the system. Name the skills which Business Analyst should have? Good Listener , Quick & continuous learner, Analytical skills, problem solving approach, thinking beyond the box, tech savvy (can keep updating what are the latest technologies released in market and how those are important). Team or people management, solid communication, documenting skills (written English), team player, devising new solutions, market research etc (if know some more you can add What do you think about challenges faced by Business Analyst? Change management is the biggest challenge because this happens in real time as well. After requirements stage when development is started client will come-up some changes or enhancements. Cross departmental or cross team management – like conflict management between teams. Also individuals. This requires soft skills and smartness. Communication problems – In real time this can happen. You might be good in speaking and understanding the English language. BUT sometimes it happens like Different people across the globe speak different style of English. In USA itself Mexico people speak English differently. Romans speak different English. So at initial level to understand the accent can be a challenge but after some time you will become perfect What is your understanding on – Risk and Issue?

Risk is something which can be forecasted and can be handled by formulating mitigation plans. Risk which happened is called Issue. There will be contingency management or issue management to solve issue. Basically we will be not solving the issue but will try making Damage control and take it as learning for other projects. What would you do if you haven't received all the required signoffs on phase documentation submitted for approval? Highlight risk management process - how to flag these? Resolution - of such scenarios, by working alongside PM

Explain how you organize or prioritize your workload Make a list. Work out what order to do things in by thinking about which tasks are urgent and how important each task is. If not sure what`s urgent and what isn`t, or how important different tasks What is HIPPA? 270-271 is for eligibility inquiry 276-277 is for claim status response 820 payment 811 billing 275 pt information, medication pt has already taken 278 health care service/before the service is provided is the service eligible for this pat or not Medical Billing Process 1. Patient goes to the hospital 2. Services are provided,(Sign and Symptoms will be checked by dictor and according to that the procedure and services are done, and the procedure and service will be converted to a code)HC 3. After discharge the Charge Entry will happened 4. This is when the actual Billing process Starts 5. A. Data Entry(all patient information is entered in the system, The doctors information The NPIThe DX ,The Procedure codes b..Charge Entry, The cash poster will post the charges in the system c .claims will go through and claim swill be gong to interfaces to getn the claims paid 837 and 835 electronic claims After claims are submitted Rejections And approvals come, it keeps on going like a circle, claims will get denied for Not medically Necessary or DX code is not a Valid DX or Valid HC code ETC