Scenario:Admitting a patient for both an inpatient and an outpatient stay
You are a member of the Informatics Team of Valley Medical Center. In this role you have been asked to be a member of a project team that will develop a replacement for the current Patient Admission module for their internally developed EMR. The changes that are required by the Affordable Care Act and the HITECH Act, which includes the Meaningful Use requirements would be more easily met by a total re-write of this function instead of just modifying it.
Analysis Phase – Patient Admission Module
You are to hold a fictional meeting with representatives of the Registration and Admission Departments of Valley Medical Center in order to discuss theirworkflowsand determine their need for data. Since these meetings are imaginary, responses to the following questions can be typical of those that you would obtain from real analysis meetings. You will not be graded on the reasonableness of the solution and not its completeness that would be possible if these meetings were actually held.
In this meeting determine the following.
How do the two departments interact in both inpatient and outpatient admissions? Are the functions of registration and admission entirely separate or are some aspects shared? How does the patient move through the two processes? What data is needed to register a patient? Of this data, what are needed at the time of registration and what data can be supplied at some later time? Are both inpatients and outpatients registered in the same way? What data is needed to admit a patient as an inpatient? Of this data, what are needed at the time of registration and what data can be supplied at some later time? What data is needed to admit a patient as an outpatient? Of this data, what are needed at the time of registration and what data can be supplied at some later time?
Once done as a means to document this analysis meeting, provide a written summary of the responses that you obtained for the questions noted above (2-3 pages). You can also include any other questions that from your experience may help to produce a better Patient Admission Module.
Design Phase – Patient Admission Module
After the successful meeting with members of the Registration and Admitting Departments you are now starting on the design of the new Patient Admission Module. You learn that the module will be written in Microsoft Visual Basic 2012 with Visual Studio 2012 Express Edition. This application development tool is based upon forms and menus with program logic associated with them.
As you review your summary from the meeting you start making some design decisions by answering some questions.
1.Will the registration and admissionworkflowsbe separate, necessitating their own forms?
2.For each of the registration and admissionworkflows, does the amount of required data necessitate multiple forms for data entry?
3.How will the forms “flow?” In what order will then be displayed to the user?
a.This can easily be shown by a “screen flow” or flowchart of the order of the business functions to be performed
4.What types of calculations or edits have to be done on the input data?
5.You can also include any other questions that from your experience may help to produce a better Patient Admission Module.
Once you have answered the above, provide a written summary of your decisions (2-3 pages).
Design Phase – User Interface Design - Patient Admission Module
With the requirements analysis and design completed, we now focus on the User Interface for the Patient Admissions Module. The components of the user interface flow directly from the design that was completed in Week 4.
1.Select two of the forms that are required in your version of the Patient Admission Module
2.Depict what the two forms will look like to implement the desired functionality. This can be done by any means that is convenient. This includes, Word,PowerPoint,Visio, hand-drawn-and-scanned, or hand-draw picture with cell phone..
3.Once you have implemented the above, provide a written summary (2-3 pages) of your design decisions.