Electronic Data Solutions. E-Prescription System Software Requirement Specifications. Version 1.0

Transcription

1 E-Prescription System Software Requirement Specifications Version 1.0

2 Contents 1. Purpose Scope Definitions and abbreviations Overview Overall Description Use-Case Model Survey User Characteristics Requirement specifications External interface specifications Functional Requirements User Registration Delete User Profile Search Pharmacy Order Processing Detailed non-functional requirements... 14

3 1. Purpose This document describes the requirement specifications for an Electronic Prescription System and is for use by software development teams. The intended audiences of this document include development, testing, validation and quality assurance teams Scope The system to be developed is the Electronic Prescription System (EPS). EPS will allow the users to utilize a digital medium to execute prescription transactions. The transactions include prescription submission, record keeping and verification as well as drug dispensing. The primary users of EPS are pharmacists and individual prescription holders. The system will simplify existing prescription management and delivery operations Definitions and abbreviations DAK Document Access Key EPS Electronic Prescription System NDC National Drug Center User Portal User Interface Pharmacy Portal Pharmacy Interface OCR Optical Character Recognition 1.3. Overview This document covers: Overall description of EPS Requirements and

4 Specifications 2. Overall Description EPS is a complete order prescription suite for both individual and pharmacy users. EPS will provide prescription ordering, processing and managing functions using an Internet connection. An EPS individual user must have an internet connection and must have installed the EPS application to use the EPS service. The pharmacy user will require more in depth installation configuration and support. General System Design

5 EPS System Pharmacy Portal User User Portal Pharmacy EPS Database Stakeholders 2.1 Actors EPS has two active actors: Individual User and Pharmacy User, one secondary actor: EPS Database and one supporting actor: Stakeholders. Individual user and pharmacy access EPS using an Internet. Stakeholders have access to the entire system. Communication between the pharmacy and individual user is via EPS. EPS has two separate portals for each user type: the User Portal and the Pharmacy Portal.

6 The EPS database is the data vehicle that is accessed and updated constantly during transactions. 2.2 Use-Case Model Survey This section outlines use cases for each actor Use Case: User Registration Brief Description: User creates new account in EPS. 1. User starts an EPS application via browser or mobile device 2. User selects create new account 3. User creates user name and password 4. User fills out form information: personal and insurance 5. User selects notification preference Use Case: Delete User Profile Brief Description: Deleting user profile in existing system Initial Step-By-Step: 1. User starts an EPS application via browser or mobile device 2. User logins to the system 3. User selects account option- Delete Profile Use Case: Search Pharmacy Brief Description: User searches for the nearest pharmacy with a better price option. Initial Step-By-Step: 1. User starts an EPS application via browser or mobile device 2. User logins to the system

7 3. User scans and uploads a prescription image 4. User enters his/her zip code and selects option to find a pharmacy 5. User selects Search Pharmacy The following diagram highlights use cases for an individual user: User Create User Profile Search Pharmacy Delete User Profile Use Case: Order Processing Brief Description: User initiates new prescription order. User confirms order placement. Initial Step-By-Step: 1. User starts an EPS application via browser or mobile device 2. User logins to the system 3. User selects Add/Refill prescription from order history 4. User scans and uploads a prescription image 5. User enters his/her zip code and selects option Find 6. User selects preferred pharmacy 7. User reviews order summary 8. EPS initiates initiating order processing 9. EPS verifies user information with EPS database

8 10. EPS sends order notification to the pharmacy 11. Pharmacy picks up notification and prepares a prescription 12. EPS initiates order confirmation and time available for a pick up 13. User receives notification by preferred means of communication The following diagram highlights use case for user-pharmacy interaction via EPS: Pharmacy EPS Pharmacy Order EPS Order Processing 2.3 User Characteristics Individual users must be capable of using either an Internet browser or mobile application to access the internet. Users must be able to use search engines to reach EPS main page via computer or download the application to their smartphone or tablet. Users must be knowledgeable about using scanning technology. Pharmacies must integrate EPS with their network in order to establish a connection to the EPS database. Pharmacies must provide staff training. Stakeholders must provide continuous updates and technical support if any issues arise.

9 2.4 Nonfunctional requirements EPS will be a three-tier system: a server, a database and a user/pharmacy application. All system components will be scalable in order to achieve maximum performance. The EPS server will support high-speed data connection to the database. Databases replication and distribution will address security and back-up requirements. EPS will be use a sophisticated OCR system for image recognition. Personal data will be securely encrypted when sent via internet, wireless or WI FI network Requirement specifications 3.1. External interface specifications None 3.2. Functional Requirements User Registration Use Case Name: User Registration Priority Essential Trigger Menu selection Precondition The user must be connected to the Internet and on the EPS Entries page. Basic Path 1. The User clicks on add a new account. 2. The EPS Server returns a form. 3. The user fills in the form and clicks submit. 4. The EPS Server checks to see if any required field is empty or invalid. 5. If any required field is empty the EPS Server will send a message and return the user to the new entry form page. 6. If the validation is successful the EPS Server will create a new

10 account in the EPS Database, send to user and return the user to the EPS Home Page. 7. The user may select Cancel. 8. If the user selects Cancel, the form is cleared and the user is returned to the EPS Home page. No information will be saved. Alternate Path N/A Post condition A record is created in the EPS Database. Exception Path 1. If the connection is terminated before the form is submitted, the fields are cleared and the EPS server is returned to the wait state. 2. If the connection is terminated after the form is submitted, but before the user is returned to the EPS Home Page, the record is created in the EPS Database. The is sent to user s . Other Reference: SRS Delete User Profile Use Case Name: Delete User Profile Priority Essential Trigger Menu selection Precondition The user must be connected to the Internet and on the EPS Entry Page. Basic Path 1. The user search for the user profile. 2. The user click on the profile and click on delete user profile. 3. The EPS server will pop up the deletion confirmation question

11 (Y/N). 4. If user selects Y, the EPS server will delete user profile and show the successful deletion message. 5. If the user select N, EPS server will return user to Search profile page. If the password matches go to 8. Alternate Path N/A Post condition The user was deleted from EPS. Exception Path 1. If the connection is terminated before the answer (Y/N) is received, the EPS Server is user to Search Profile page and the EPS server returned to the wait state. 2. If the connection is terminated after the answer is received, but before the user is returned to the EPS Search profile page, the record in the EPS Database is deleted and the EPS Server is returned to the wait state Other Reference: SRS Search Pharmacy Use Case Name: Search Pharmacy Priority Essential Trigger Menu selection Precondition The user is connected to the Internet and on the EPS Home Page. Basic Path 1. The user clicks on Search Pharmacy. 2. The EPS Server returns a form so user can upload prescription

12 image file and enter a zip code. 3. The user selects the prescription image file and enter zip code then click on Find. 4. The EPS Server checks to see if the image is empty or not. 5. If the image file is empty or zip code the EPS Server returns a message and the upload form. 6. If the image and zip code are not empty the EPS Server uploads the image to EPS server. 7. The EPS server will show a list of pharmacy nearby the entered zip code. Alternate Path N/A Post condition The user will get a list of nearby pharmacy. Exception Path 1. If the connection is terminated before the information is received, the EPS Server is returned to the wait state. Other Reference: SRS Order Processing Use Case Name: Order Processing Priority Essential Trigger Menu selection Precondition The user is connected to the Internet and on the EPS Home Page. Basic Path 1. The user clicks on Add/Refill Prescription. 2. The EPS Server returns a form so user can upload prescription image file and enter a zip code.

13 3. The user selects the prescription image file and enter zip code then click on Find. 4. The EPS Server checks to see if the image is empty or not. 5. If the image file is empty or zip code the EPS Server returns a message and the upload form. 6. If the image and zip code are not empty the EPS Server uploads the image to EPS server. 7. The EPS server will show a list of pharmacy nearby the entered zip code. 8. User selects the pharmacy and click select. 9. EPS server will show the order summary. 10. User click on submit. EPS server will initiate the order process after verifying user information against EPS database. 11. EPS send order to chosen pharmacy. 12. After receiving order confirmation from pharmacy. EPS server will send notification to user via with date and time available provided by the pharmacy. 13. After user picked the prescription, pharmacy system will send the acknowledgement to EPS. EPS server will close the order. Alternate Path N/A Post condition The user will get notification when the prescription is available for pick up. Exception Path 2. If the connection is terminated before the information is received, the EPS Server is returned to the wait state. Other Reference: SRS 2.2.4

14 3.3. Detailed non-functional requirements Attribute Name Attribute Type Attribute Size LastName* String 30 FirstName* String 30 MaidenName* String 30 Address1* String 50 Address2 String 50 City* String 30 State* String 2 Zip* Int 6 INSNUMBER* String 30 SSN* String 11 DOB* Date 15 CMedicine Text 200 PhoneNumber* String 12 Address* String 20 ConfAns Boolean 1 Password*# String 10 Fields marked with an * are required fields. Hardware Operation System Internet Connection EPS Server Window 2008 Server, Oracle 11G database Existing connection

15 Code Standard The web pages will be coded in html and JavaScript Performance The forms will in Java Server Pages. The connection to the EPS Database will with JDBC. Each page of the web site will be fully documented The EPS will be up 99.99% of time