1. (Worth 50% of the homework grade) Create a use case diagram for the medication prescribing and administration system described below:

A doctor enters a prescription order and submits it to the hospital pharmacy. A pharmacy technician reviews each prescription and sends it to one of the following pharmacy stations: Lab Station, if the prescription must be formulated (made) on-site; Shelving Station, if the prescription is for an off-the-shelf drug; or, Secure Station, if the prescription is for narcotics. At each station, a pharmacist reviews the order, checks the patient's electronic health record (EHR) to determine the appropriateness of the prescription, and fills the order if the dosage is at a safe level and it will not negatively interact with the other medications or allergies indicated in the patient's EHR.

If the pharmacist does not fill the order, she contacts the prescribing doctor to discuss the situation. In this case, the order may ultimately be filled, or the doctor may enter another prescription depending on the outcome of the discussion.

Once the prescription is filled, the pharmacist generates a barcode and label that identifies the patient's name, the drug type and dosage, an expiration date, and any special instructions. The pharmacist puts the barcode and label on the drug container, and sends the container to the appropriate nurse station. The pharmacist then sends the patient's admission number, the drug type and amount dispensed, and the cost of the prescription to the Billing department. The Billing department will use its own systems to code the visit and file claims with payers (e.g., insurance companies). 

A nurse scans the barcode on the patient's wrist band, scans the barcode on the medication, confirms the patient, medication, dose, and time, administers the medication, and documents the administration of the medication and patient vital signs.

Notes:
Use the diagramming notation described in chapters 2 and 10 of our text (if you send the response in an editable format, i can easily translate notations). we are using kendall systems analysis and design 9th edition

How many use cases should you have? In general, the fewer the better. The average number of use cases on this problem will probably be in the range of five to nine. Each use case should be focused on a discrete goal of one or more actors. You can omit system-oriented interactions like "Login to system."