Categories
Uncategorized

SEC290 Introduction to Programming with Python : Prescription Management

Question

Object Oriented Design (Uml)

Specification

Online Prescription Management System

You are required to design an object-oriented software for Online Prescription Management System (OPMS) which allows healthcare professionals like doctors, (GPs), nurses etc. to send prescriptions electronically to a pharmacy of the patient’s choice. This makes the whole process of prescribing more efficient and convenient for both patients and staff.

Access to the OPMS is controlled through the use of the health services Smartcard which has an embedded smart chip along with user’s name, photograph and unique ID printed on it. The Smartcard provides individual users different levels of access depending on their role.

Healthcare professionals who are the prescribers, log onto the system using their Smartcard and passcode, choose medication or medical appliance for the patient, add prescribing endorsements where required, and apply digital signature to authorize the online prescription. Online prescription is transmitted to the OPMS. Prescriptiontoken is printed where required. Authorized person hands prescription token to patientwhere necessary.

Tokens are paper copies of online prescriptions. They act as a hard copy of the details contained within the online prescription. There are two types of tokens – ‘prescription tokens’ and ‘dispensing tokens’. Paper copies of online prescriptions are no longer needed but should still be available by request, whenever necessary.

A dispenser is any organization that dispenses prescriptions to patients, such as a community pharmacy, a dispensing appliance contractor or a dispensing GP practice. With OPMS, only prescriptions sent to a patient’s nominated dispensing contractor can be signed and sent electronically.

Dispenser retrieves online prescriptions from the OPMS. It could be done in three ways either by automatic download (e.g. overnight), by manually entering the prescription ID printed on the token, or by scanning a barcode on a prescription token.Dispensing token is printed if required. Prescription items are issued to the patient or patient’s representative.

Dispenser should record the status of each of the prescription items as one of the ‘dispensed’, ‘not dispensed’, ‘owing’ or ‘partial’. In order to complete the dispensing process the whole prescription has to be completed, meaning that all prescribed items must be marked as either ‘dispensed’ or ‘not dispensed’. Some clinical systems will automatically record the status of dispensed items.

If dispensing process is complete, dispenser should send dispense notification to the OPMS. The message informs the OPMS which medication has/has not been supplied to the patient. A schedule will be issued for pharmacists to follow as to when to submit the electronic reimbursement endorsement message. The electronic reimbursement endorsement message can only be sent once the dispense notification message has been sent for the electronic prescription.

To support the reimbursement claim process, the OPMS will allow dispensers to electronically submit reimbursement endorsement messages to the reimbursement agency for the dispensed electronic prescriptions so that the reimbursement agency can make a payment. The messages are sent according to the reimbursement agency scheduling.

This assignment has been selected because it concerns a system for which the requirements are widely understood and do not require expert knowledge. If you are concerned about the appropriateness of any elaboration explain your reasons for the decisions made.

Assessment

This coursework contributes 30% of the total mark for Software and Systems module. Assessment is based on a report containing the relevant UML diagrams produced to design this system. Clearly the report must fully address all relevant issues. The assignment is open-ended but it is important that all diagrams of the design process are considered to a reasonable level of detail.

The figures, tables and pages should be numbered. Captions should be beneath figures and above tables. The report should not exceed 12 pages. Marks distribution will be as follows:

a) Introduction, which includes the discussion and interpretation of the specification, which should identify any issues that require clarification(5%)

b) Use-Case Diagram, Survey description and CRC cards. (30%)

c) Detailed class diagram with all attributes, methods, their visibilities, arguments, return types and relationships to define architecture. (20%)

d) Detailed interaction diagrams, both collaboration and sequence diagram. (20%)

e) Detailed state chart diagram to show events, actions and qualifiers. (10%)

f) Discussion of non-functional requirements. (5%)

g) Produce pseudocode for major functions. (10%)

Resources available

This assignment involves the development of designs on paper. It should be possible to draw good quality design diagrams using Word or other word processing package, adopting the correct notation. There is no need to use any Object-Oriented Design Tools. This is because learning curve associated with object-oriented design tools is normally steep. Many design consultants use graphical design programs and notobject-oriented design tools to document designs.