Need help really bad super desperate, partner dropped course today due to issues with the school and he was doing the UML-State Diagram for our project then showing me how to create one.

Need a State Model for the project I'm doing for my Software System Requirements Class.

Information Listed below. Please Help if you can, and Thank you for your tinme a condersation.

/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////

You have been asked to develop an Alternative Medicine Office Management System (AMOMS) for an actual alternative medicine office. The objective of the AMOMS project is to develop an application that will run on the offices intranet and will assist the employees of the medical group with management of all processes related to patients. You may assume this is a group with several types of medical practitioners including: physicians, chiropractors, physical therapists, massage therapists, and an acupuncturist; that all patient records are currently paper records with only basic patient information; that the client wants this system to help them move to digitized patient records; that those digitized records will be stored and maintained in a patient database ordered by a unique patient number; and that there are several different types of users. Although AMOMS is primarily an end-user system, there are administrative responsibilities that need to be taken care of by Office Management Personnel as well as other technical issues that need to be performed by the system administrator.

The types of users of AMOMS are: medical practitioners (as listed above), receptionists, patient account management personnel, office management, and system administration. The basic requirements for AMOMS can be summarized as follows:

Patient information needs to be maintained and updated every time communication occurs between any of the medical office personnel and the patient.

All personnel should be able to access only the portion of the patient information related to his/her function. (For example, account management personnel can only access the patients account balance and payment history, not things such as his/her current prescriptions.)

Receptionists use the system to register new patients (for data entry purposes); set, change and cancel appointments; and do the following things when a patient arrives at the office: check-in patients upon arrival, validate current insurance information, determine the amount due (copay) and process patient payments, file insurance claims - which will be emailed by the system, and generate callback lists for scheduling maintenance appointments as well as appointment reminders.

Each type of practitioner has associated appointment lengths, and some types have multiple length options.

There needs to be an appointment schedule that includes appointments for each practitioner and accommodates various hours of operation from Monday through Saturday.

Practitioners use the system to take notes during the office visit, enter diagnostic information, view patient history including previous prescription information and notes from prior visits, make referrals both internal to the office as well as external, write prescriptions, and create excuse notes.

When the practitioner writes a prescription, a printed version of the prescription form must be printed and given to the patient.

The client needs several different types of reports from various versions of receipts, and different lists of patients to be emailed, to more traditional financial reports.

The system also needs to keep track of aggregated management information to generate associated financial reports. These reports consist of Weekly Patient Reports identifying the number of patients seen by each practitioner that week, as well as Weekly Revenue Reports that identify the total amount of revenue each practitioner billed that week. These reports will only be accessible to the AMOMS management personnel.

The office currently has a billing system, so AMOMS billing must be able to interact with billing software: ASPEL

This medical office is in Mexico, and therefore is subject to following various Health department laws that will affect the system.

The user interface will be graphic and run in a browser. Users will log into AMOMS via individual accounts, created by the Management Personnel. Accounts will be password- protected. Users will be able to change the passwords in their accounts. Note: each user type will only be able to see that part of the system that is related to his/her role(s); e.g., a practitioner may log in as his/her specialization, e.g., a chiropractor, or physical therapist, or he/she may also be part of the Management Personnel, and be able to login in that role and generate reports.

There will be various secondary services:

1.Mail services will provide SMTP/MIME email tailored for AMOMS services.

2.User statistics will provide the system administrator with information about the performance and use of AMOMS.

When users access AMOMS they will be asked to select a language (English or Spanish) before login and then will be presented with all the services available to them (and only those available to them). The system administrator will have an account which will access all services available to users.

User input to AMOMS will be via the graphical interface. AMOMS output will be via the interface, printed reports and email. The email output will include insurance claims from the system, referrals, and various types of patient emails.