Automated Medical Patient Evaluation System - Phase 2 Design Report

Transcription

1 Automated Medical Patient Evaluation System - Phase 2 Design Report Team Number Dec02-01 Date Submitted 4/23/2002 Client Dr. David Carlyle Family Practice East McFarland Clinic Ames, IA Faculty Advisors R. Patterson III J. Lamont Team Members Janna Hora Logan Kahler Yuk-Chiu Luk Hui-Juan Sim

2 Table of Contents List of Figures...ii List of Tables...iii List of Tables...iii 1 Abstract Introduction General Background Technical Problems Operating Environment Intended Users and Uses Assumptions and Limitations Design Requirements Design Objectives Functional Requirements Create New Templates Design Constraints System Constraint User Interface Constraint Measurable Milestones Repair Bugs in Original Software Add Additional Features To Original Software Add Additional Templates Add Additional Users Develop Template Creation and Editing Software End Product Description Technical Approach and Design Introduction Template Generation Software Graphical User Interface Function Descriptions Output Description Testing Description Template Generator Interface Tests Risk and Risk Management Financial Budget Personal Effort Budget Project Schedule Project Team Information Summary References...30 i

3 List of Figures Figure 1: Flow Chart...9 Figure 2: Templates Screen...10 Figure 3: Section Screen...11 Figure 4: Questions Screen...12 Figure 5: Question Screen...13 Figure 6: Answers Screen...14 Figure 7: Copy Template Screen...15 Figure 8: Copy Section Screen...16 Figure 9: Copy Question Screen...17 Figure 10: Semester One Gantt Chart...27 Figure 11: Semester Two Gantt Chart...28 ii

4 List of Tables Table 1: Template Generator Interface Tests...23 Table 2: Financial Budget...26 Table 3: Personal Effort...26 iii

5 1 Abstract Currently, the doctors at McFarland Clinic record patient examination data by hand which is then voice recorded. The doctor s recordings are typed by an outside expensive source and placed into the patient s file several days later. The client, a doctor, would like to reduce the time, effort, and cost needed to produce a patient visit record. The previous team developed software to provide a way to automate the process of the doctor recording the patient s data, illness, symptoms, and treatment, and then print a record of the patient s visit soon after the examination. In this phase of the project, the client doctor will test the software, and the team will make revisions and improvements. Additional software will be developed to allow medical staff to modify or add additional diagnoses templates easily, expanding the system to accommodate additional doctors and medical specialty areas. 1

6 2 Introduction 2.1 General Background The Automated Medical Evaluation System Phase 2 involves improving upon the software already developed to record daily patient visits. The software developed by the previous team is designed to be used by a doctor while examining patients to quickly record patient s answers to common questions associated with a particular illness that is selected and the doctor s assessment and treatment plan. The current software developed by the previous team implements the basic features requested by Dr. Carlyle using the S.O.A.P. (subjective, objective, assessment, plan) format. The software requires the user to login with a username and password. Once authorized the software prompts the user for information about the patient. After general patient information is entered the user is presented with a choice of illnesses to select. Based on which illness is selected the software will display a form containing the appropriate questions and fields for the selected illness. Once the examination is complete and the form has been filled out the user can review the report and then print it to a printer. In addition to the existing software, a software tool will be developed to aid in the creation and modification of templates. This project s goal is to further test the existing software produced by the previous group along with improving it by making changes to the existing code and adding new features suggested by the previous team and the client. 2.2 Technical Problems The Automated Medical Evaluation System shall continue to be developed for the Microsoft Windows platform using the Microsoft Visual Basic development system. Any new assisting applications will also be developed in Microsoft Visual Basic for consistency. The Automated Medical Evaluation System will require that the Microsoft Windows-based computer, that it is run on, have a Windows compatible printer installed that is either connected locally or through a network connection in order to print the forms. 2

7 The Microsoft Windows-based computer that the Automated Medical Evaluation System is run on may require a network connection if it is decided that the login and template information is to be stored on a central server. This will also be required if the printer is available on a separate computer also on the network. The Automated Medical Evaluation System is required to work with a variety of different input devices, which includes a touch screen monitor, a standard keyboard and a standard computer mouse. 2.3 Operating Environment Security is also a concern since the computer on which the Automated Medical Evaluation System and the template creation and modification software that is used may be unattended and available to a patient while in an evaluation room waiting for a doctor. 2.4 Intended Users and Uses The Automated Medical Evaluation System will be used primarily by doctors while in an evaluation room examining a patient. Along with doctors, a secondary user might be a nurse that would need to use the software to add and maintain templates and initial data entry such as a patient s name and date of birth. The first user of the software will be Dr. Carlyle at the McFarland clinic, however, other doctors at the clinic will eventually use the software as it is refined and more templates are developed. 3

8 2.5 Assumptions and Limitations Assumptions for this project are as follows: 1. The previous team s code is complete as far as their final report states. 2. Dr. Carlyle has had a chance to look over the existing software and has developed ideas for improvements and changes to be made. 3. Computer hardware, such as networking and printers, is already in place at the clinic. 4. Computer software, such as a Microsoft Windows, is already in place at the clinic. 5. Dr. Carlyle will provide any medical related information that may be needed. Limitations for this project are as follows: 1. Dr. Carlyle s schedule limits the availability of meeting times and increases the amount of time that it will take to schedule meetings. 2. Some members of the team may not be experienced with the Microsoft Visual Basic development system and other technologies and techniques used by the previous team. 3. Questions of motivation behind certain design choices of previous team may be difficult to ascertain due to the limited availability of previous team members. 4. Specifics of the clinic s hardware and software setup are unknown at this time. 4

9 3 Design Requirements 3.1 Design Objectives An automated medical software package will be developed that will allow users to enter the information gathered during an examination. This will include the ability to add information about physical examinations and create and store new illness templates. 3.2 Functional Requirements Support Testing by Dr. Carlyle Dr. Carlyle will need to perform tests upon the newly developed software to ensure that it is meeting his requirements. This will need to be done on a regular basis so correct software can be developed Create New Templates Creation of new illness and physical examination templates will be done through graphical user interfaces, that will be developed, that will allow the user to enter information regarding specific illnesses or a physical examination. 3.3 Design Constraints System Constraint Software must run on a Microsoft Windows system with a 10 or a 17 monitor. It must also be capable of utilizing touch screen technology User Interface Constraint Graphical user interfaces must be user friendly and easily used by users with minimal computer skills. 5

10 3.4 Measurable Milestones Repair Bugs in Original Software Repairs to original software will include any code changes to fix any problems found by Dr. Carlyle as needed. These may include, but are not limited to, repairs to existing installation software, and repairs to existing printing format. Successful completion of bug repairs to the original software will result in software that operates correctly and to Dr. Carlyle s satisfaction Add Additional Features To Original Software New features, requested by Dr. Carlyle, will be added to original software. This may include, but is not limited to, changes in the existing templates. Successful addition of new features to the existing software will result in improved software that meets the needs of Dr. Carlyle, as specified Add Additional Templates New templates will be created upon receiving specifications from Dr. Carlyle. This may include, but is not limited to, creation of physical and illness templates. Successful creation of additional templates will require that templates fully function with the existing software Add Additional Users New users will be added as needed Develop Template Creation and Editing Software Software to create and edit illness templates will be developed so that the clinic staff may create their own illness templates at their own convenience. Successful development of the template creation software will include a program that is easily usable by anyone with limited technical background. 6

11 4 End Product Description Phase two of the Automated Medical Patient Evaluation System project will take the software one step further to include more capabilities. New external software will be developed that is able to create, copy, edit, store, and delete an illness template. If a user chooses to create a new template they will be able to chose from a list of previous template questions or create a new template question. The user will also be able to edit and delete questions from the template that they are working on. If the user chooses to create a new question they will be guided through a series of steps necessary for question creation. All questions will need to have a label and input type. Some questions may require multiple answers. Once the template has been created it can be stored and will appear in the list of current templates. If the user chooses to copy a template they will be required to rename the copied template. Physical examination templates will also be developed. The user should also be able to input data for multiple illnesses for a single patient and be able to do template folding, which is the ability to hide unnecessary template information as needed. In addition to that, the user interface will be upgraded to become user-friendlier, and user will get to choose to print to a printer other than the default selection. 7

12 5 Technical Approach and Design 5.1 Introduction In the following sections the technical approach and design of the template generating software are discussed in detail. The template generating software shall have two main functions, creating and modifying templates to be used within the Automated Medical Patient Evaluation System, which will be described in detail. The testing requirements associated with the template generating software also will be discussed. This shall include a list of subcomponents that will require testing to ensure the correct functionality of the end product. Certain risks are associated with design, these risks will also be discussed in detail. 5.2 Template Generation Software The template generation software shall be used by the clinic staff to create and modify medical evaluation templates compatible with the Automated Medical Patient Evaluation System. The software shall facilitate creation and modification of templates with minimal technical knowledge. 5.3 Graphical User Interface The graphical user interface is a key component to the success of the template Generation Software. Designed correctly, the graphical user interface should provide a natural organization and flow to direct the user through the proper order of steps to create a medical evaluation template. The flow of the graphical user interface for the template Generation Software takes the user from the most general information and moves toward specific information. Specifically, the user follows the steps specified in the flow chart 8

13 Figure 1: Flow Chart 9

14 Templates Screen The Templates Screen (Figure 2) is the first screen the user encounters. This screen contains the following objects:? The existing template list contains all the medical evaluation templates that are available for modification and copying.? The create button allows the user to create a new empty template.? The copy existing button allows the user to copy an existing medical evaluation template that is selected from the existing templates list. The copied medical evaluation template is not allowed to have the same name as any other existing template, including the template from which it was copied. When copying a medical evaluation template the user will be prompted to provide a new name.? The modify button allows the user to open an existing medical evaluation template, selected in the existing template list, to be modified.? The remove button allows the user to remove an existing medical evaluation template selected in the existing template list.? The exit button allows the use to exit the template generation software. Figure 2: Templates Screen 10

15 Sections Screen Once a medical evaluation template has been selected for modification, or a new medical evaluation template has been created, the section screen (Figure 3) is displayed. This screen contains the following objects:? The existing sections list displays a list of sections that have been defined within the current template.? The create button allows the user to create a new empty section.? The copy existing button allows the user to copy an existing section from either the current medical evaluation template or from any other existing medical evaluation template.? The modify button allows the user to open a section, selected in the existing sections list, to add, remove and modify questions within that section.? The remove button allows the user to remove the section, selected from the existing sections list, from the medical evaluation template.? The exit button allows the user to return to the templates screen. Figure 3: Section Screen 11

16 Questions Screen Once a section has been selected for modification the questions screen (Figure 4) is displayed. This screen has the following objects.? The existing questions list displays a list of questions that have been defined within the current section.? The create button allows the user to create a new question.? The copy existing button allows the user to copy an existing question from either the current medical evaluation template or from any other existing medical evaluation template.? The modify button allows the user to edit the properties of the selected question in the existing questions list.? The remove button allows the user to remove the question, selected from the existing questions list, from the section.? The exit button allows the user to return to the sections screen. Figure 4: Questions Screen 12

17 Question Screen Once a question is created or selected for modification the question screen (Figure 5) is displayed. The question screen has the following objects:? The question title field allows the user to enter the title for the question that is displayed in the Automated Patient Medical Evaluation System.? The question types options allow the user to select the type of question with the aid of a visual corresponding to each question type.? The answers button allows the user to specify the answers for multiplechoice questions if selected.? The save button allows the user to save the changes she or he have made to the question.? The exit button allows the user to return to the questions screen. Figure 5: Question Screen 13

18 Answers Screen If a question is a multiple-choice type, the possible answers must be defined. If the answers button is clicked, while creating a multiple-choice question, the answers screen (Figure 6) is displayed. This screen contains the following objects:? The existing answers list displays a list of questions that have been defined within the current question.? The create button allows the user to create a new answer.? The copy existing button allows the user to copy an existing answer from either the current medical evaluation template or from any other existing medical evaluation template.? The modify button allows the user to edit the properties of the selected answer in the existing answers list.? The remove button allows the user to remove the answer, selected from the existing answers list, from the section.? The exit button allows the user to return to the question screen. Figure 6: Answers Screen 14

19 Copy Template Screen When a template is copied from an existing medical evaluation template, the copy template screen (Figure 7) is displayed. This screen has the following objects:? The name field allows the user to enter a new name for the copy medical evaluation template.? The copy button performs the copy using the new name specified in the name field. If a name is not specified an error message shall be displayed.? The cancel button allows the user to abort the copy and return to the templates screen. Figure 7: Copy Template Screen 15

20 Copy Section Screen When a section is copied from an existing section the copy section screen (Figure 8) is displayed. This screen has the following objects:? The existing sections list displays all possible sections to be copied. This includes both sections from the current medical evaluation template and sections from all other available medical evaluation templates.? The copy button performs the copy action.? The cancel button allows the user to abort the copy and return to the sections screen. Figure 8: Copy Section Screen 16

21 Copy Question Screen When a question is copied from an existing question, the copy question screen (Figure 9) is displayed. This screen has the following objects:? The existing questions list displays all possible questions to be copied. This includes both questions from the current medical evaluation template and questions from all other available medical evaluation templates.? The copy button performs the copy action.? The cancel button allows the user to abort the copy and return to the questions screen. Figure 9: Copy Question Screen 17

22 5.4 Function Descriptions To accomplish the tasks that the template generation software must be capable of performing, a set of functions must be defined that perform these tasks. Read medical evaluation template from disk Public Function ReadTemplate(strName As String) As Boolean This function will take the name of an existing template as a string parameter and load the template information into memory. If this function is unable to load the medical evaluation template from the disk, the function will return a Boolean false. If the medical evaluation template is loaded successfully, the function will return a Boolean true. Write medical evaluation template to disk Public Function WriteTemplate(strName As String) As Boolean This function will take the name of a template, as a string parameter, that need not already exist and will write the template information from memory to the disk. If the write operation is for any reason unsuccessful, the function will return a Boolean false. If successful, the function will return a Boolean true. Copy medical evaluation template to disk Public Function CopyTemplate(strSouce As String, strdestination As String) As Boolean In order to copy an existing template to a separate file, this function will take two string parameters. These parameters will specify the source and the destination template names. If the source does not exist, and thus the copy process fails, the function will return a Boolean false. If the copy process is successful the function will return a Boolean true. 18

23 Remove medical evaluation template from disk Public Function RemoveTemplate(strName As String) As Boolean This function will take the name of a template, as a string parameter, that is to be removed. If the template specified by the parameter does not exist, the removal process will fail and the function will return a Boolean false. If the removal process is successful the function will return a Boolean true. Read section information from current template Public Function ReadSection(strName As String) As Section This function will take the name of a section, as a string parameter, that exists in the current template loaded in memory and return a section structure containing the section s information. Write section information to current template Public Function WriteSection(Source As Section, Optional strparentsection As String) As Boolean This function will take a section structure as a parameter and adds the information to the current template loaded in memory under the parent section if specified. If the parent section is not specified, the section is added at the top level. If the function is unsuccessful, the function will return a Boolean false. If the function is successful it, will return a Boolean true. Copy section information from template Public Function CopySection(strSourceTemplate As String, strsourcesection As String, strparentsection As String) As Boolean This function will take both the name of the source template and the name of the source section, within that template, as string parameters. The section, with sub-sections and questions contained within, specified by the source will be copied to the current template loaded in memory under the parent section if specified as a parameter. If no parent section is specified, the section will be added at the top level. If the source template or source section does not exist, the function will return a Boolean false. If the copy process is successful, a Boolean true will be returned. 19

24 Remove section from template Public Function RemoveSection(strName As String) As Boolean This function will take the name of the section to be removed as a string parameter. If the section does not exist, the function will return a Boolean false. If the section removal process is successful, then the function will return a Boolean true. Read question properties to current section Public Function ReadQuestion(strSection As String, strquestion As String) As Question This function will take the name of a question and the section in which it resides as string parameters and return a question structure containing the information associated with the question. Write question properties to current section Public Function WriteQuestion(strSection As String, Source As Question) As Boolean This function will take a question structure, containing the question information to be written, and a string parameter specifying the section the question belongs in and adds the question to the current template loaded in memory. If the function is for any reason unsuccessful, the function will return a Boolean false. If the function successfully writes the question, a Boolean true is returned. Copy question information from template Public Function CopyQuestion(strSourceTemplate As String, strsourcesection As String, strsourcequestion As String, strdestinationsection As String) As Boolean This function takes four string parameters specifying the source template, source section, and source question and destination section. The question specified will be copied to the destination section within the current template 20

25 loaded in memory. If the function is unsuccessful, it will return a Boolean false otherwise, it will return a Boolean true. Remove question from current section Public Function RemoveQuestion(strSection As String, strquestion As String) As Boolean This function takes two string parameters that specify the question and the section in which it is contained. If successful, the function will remove the specified question and return a Boolean true. If unsuccessful, the function will return a Boolean false. Get list of sections in current template Public Function GetTemplateSections() As String() This function will return a list of the top level sections contained in the current template loaded in memory. Get list of sub-sections in section Public Function GetSubSections(strSection As String) As String() This function will return a list of sub-sections contained within the section specified by the string parameter. The section specified must exist within the current template loaded in memory. Get list of questions in section Public Function GetQuestions(strSection As String) As String() This function will return a list of sub-sections contained within the section specified by the string parameter. The section specified must exist within the current template loaded in memory. 21

26 5.5 Output Description Phase two of the Automated Medical Patient Evaluation System project will include the creation of new software called the template generator. The output of the template generator will be a new template. The new template will be an XML file formatted according to the previous team s example. Each template will have a name and will include the subjective, objective, and treatment plan parts of the SOAP analysis. 5.6 Testing Description In order to ensure that software functionality meets the expectations of Dr. Carlyle. The software has to be completed ahead of time to allow adequate time for Dr. Carlyle to test the software. Fully functional testing will be needed to make sure the template generator functions properly. The template generator allows user to create, copy, modify or remove an existing template. The template generator will make changes on the existing template by changing the contents of the different sections Template Generator Interface Tests Tester: Date: Time: The purpose of these tests is to make sure the template generator is able to display all the existing templates. They also determine if all the functions of template generator are working as expected. 22

27 Table 1: Template Generator Interface Tests Test Expected Results Actual Results Template Generation Interface Open the template All the existing templates generation program. are displayed. Click on the Create By clicking on the Create button. button, the program jumps to a new interface that list all the existing Select one of the existing templates, and press the Copy Existing button. Select one of the existing templates, and press the modify button. Select one of the existing templates from the list, and click the Remove button. Click on the Exit button. Sections Interface Click on the Create button. Click on the Copy Existing button. Click on the Modify button. Select one of the sections, and click the Remove button. Click on the Exit button. sections in the Sinusitis. The program jumps to another interface that ask the user the give the name of the new template. The program jumps to another interface that list all the existing sections in the template, which the user selected. The template that selected by the user is removed from the existing template list. The program exits. The program jumps to the Question for Section Subjective Screen. Jumps to the Copy Section Screen. The program jumps to the Question for Section Subjective Screen. The section selected is removed from the section list. Exit from the Section interface and back to the Template Generation Screen. Questions for Section Subjective Interface Click on the Create Jumps to the Question button. Screen. 23

28 Click on the Copy Existing button. Select one of the questions, and click the Modify button. Select one of the questions, and click the Remove button. Click on the Exit button. Question Interface Enter an name in the Question Title section. Select question type by select one of the three question types: Multiple Choice, Fill in The Blank and Check Box. Click on the Answer button. Click on the Save button. Click on the Exit button. Copy Template Interface Given an name different to the template and click Copy button. Click on the Cancel button. Copy Section Interface Select any sections from the list and click Copy button. Click on the Cancel button. Jumps to the Copy Question Screen. Jumps to the Question Screen and the name of the question that selected by the user is displayed on the Question Title section. The question that selected by the user is removed. Exit from the Question interface and back to the Sections screen. The name displays as entered. The question should be the same as selected. Jump to the Answer screen. The question is saved. The interface is exited and back to the Questions for Section Subjective screen. The new template is copied. The action is cancel and exit to the Template Generation Screen. The section is copied and back to the Section Interface. The action is cancel and exit to the Section Interface. 24

29 Copy Question Interface Select any questions from the list and click Copy button. Click on the Cancel button. Answers for Question Interface Click on the Create button. Click on the Copy Existing button. Select one of the answers, and click on the Modify button. Select one of the answers, and click the Remove button. Click on the Exit button. The question is copied and back to the Question Interface The action is cancel and exit to the Question Interface. The user can typed in an new answer and an new answer is created. Jump to the Copy Answer Interface. Jump to the Modify Answer Interface. The answer is removed. The interface is exited and back to the Question Interface. 5.7 Risk and Risk Management Because Dr. Carlyle is very busy, the group was only able to meet with him once during the planning of the design. To avoid the risk of Dr. Carlyle not being satisfied with the end product the group had planned ahead and had clear, unambiguous questions for Dr. Carlyle ready before the meeting. Another risk that the team faced was when the program developed by previous team could not be installed into Dr. Carlyle s computer. It was feared that the difficulty with installation might have been an unsolvable problem. However, after some inspections and tests were done by a couple of the group members, it was found that the installation file was the problem. After continued testing they were able to create a working installation CD. A risk associated with continued work with the templates as designed by the previous team is a lack of familiarity with XML. The impact of this may be reduced if group members familiarize themselves with XML before coding. 25

30 6 Financial Budget Table 2: Financial Budget Item Estimated Cost Actual Cost Poster $50 $30 Copying & Binding $30 $10 CDs $15 $0 Total $95 $40 The financial budget can be broken down into three major sections poster, copying & binding, and CDs. Materials and the cost of production was taken into consideration for the overall cost of the poster. An estimated number of pages and cost for binding was taken into consideration for copying and binding. To determine the overall cost of CDs, prototypes and test CDs were taken into consideration. 7 Personal Effort Budget Table 3: Personal Effort Personnel Logan Kahler Meeting Time Individual Work Estimated Effort (hours per semester) Janna Hora Yuk-Chiu Luk Hui-Juan Sim Total estimated effort Actual Effort (hours per semester) The total number of hours per semester per person was calculated by taken the number of meetings scheduled throughout the semester, which is estimated to be two hours per week for sixteen weeks, along with the individual tasks that need to be accomplished outside of each meeting, which is estimated to be three hours. Logan Kahler was selected as the team captain and Janna Hora was selected as the communication coordinator. Therefore, the estimated effort for 26

31 Logan and Janna is somewhat higher than Yuk-Chiu s and Hui-Juan s estimated effort due to the extra responsibilities that are associated with those titles. 8 Project Schedule To determine the overall project schedule the required tasks that need to be accomplished were taken into consideration. Then an estimated number of hours were calculated for each task. Tasks include, but are not limited to, writing documents, developing new template creation and modification software, expanding on original software, repairs to original software, and testing the software. Jan Feb Mar Apr Task Project Plan Preparing Unbound Revising Project Posting Project Poster Designing Poster Printing Poster Design Report Preparing Unbound Revising Design Posting Design Expected = Actual = Figure 10: Semester One Gantt Chart 27

32 Task Presentation Preparing Presentation Aug Sept Oct Nov Dec Revision of Existing Software Repairs Testing Repairs Addition of New Features Testing New Features Designing New Templates Testing Templates Creation of New Software Coding Creation Routines Testing Creation Routines Coding Modification Routines Testing Modification Routines Final Report Preparing Unbounded Report Revising Final Report Posting Report to Web Regional Industrial Panel Presentation Preparing Presentation Figure 11: Semester Two Gantt Chart 28

33 9 Project Team Information Team Members: Janna Hora 4733 Toronto St #101 Ames, IA (515) CpE Yuk-Chiu Luk 133 University VLG Apt A Ames, IA (515) dluk@iastate.edu CpE Logan Kahler 4335 Maricopa Dr. #2 Ames, IA (515) logan@iastate.edu CpE Hui-Juan Sim 218 North Hyland Ave Apt. #302 Ames, IA (515) vkijenn@iastate.edu CpE Client: Dr. David Carlyle Family Practice East McFarland Clinic Ames, IA Faculty Advisors: Dr. John Wm. Lamont Iowa State University Department of Electrical and Computer Engineering 324 Town Engineering Ames, IA (515) FAX: (515) jwlamont@iastate.edu Prof. Ralph E. Patterson, III Iowa State University Department of Electrical and Computer Engineering 326 Town Engineering Ames, IA (515) FAX: (515) repiii@iastate.edu 29

34 10 Summary Updating patient medical records at the local McFarland Clinic is currently a costly, time-consuming process. The current software developed by the previous team implements the basic features needed in an automated medical evaluation system. The team shall improve upon the previous team s efforts by expanding on the current software to save doctors time and money. The team will repair the original software, add new features to original software, add new templates, and create new software tool to create and modify templates. 11 References Automated Medical Software Final Report, Dec01-03 Team Senior Design Website Current Projects, 30