Software Requirement Specifications V1.0



Similar documents
The Best Treatment For Your MedSpa

Information Technology Solutions. Managed IT Services

HP Windows 7 Onsite Upgrade Service

Software Requirements. Specification. Day Health Manager. for. Version 1.1. Prepared by 4yourhealth 2/10/2015

CENTER FOR EYE CARE STAFF JOB DESCRIPTIONS 12/2013

PRACTICE MANAGEMENT SOFTWARE SYSTEM (PMS) PHYSICIAN PRACTICE NEEDS ASSESSMENT

DDS Rescue DDS Rescue Leads and Sales Processing Manual. For Patterson Dental. January 2013

Large Scale Systems Design G52LSS

RIMS. Restaurant Inventory Management System. ISDS 3100 Spring Creighton Boggs Rachel Bradley Jackson Greenwood Jimmy Lambert

Software Requirements Specification for POS_Connect Page 1. Software Requirements Specification. for. POS_Connect. Version 1.0

Software Update Bulletin

High Level Design Distributed Network Traffic Controller

Attachment Y SaaS ITSM Demonstration and Scenarios

Software Requirement Specification for Web Based Integrated Development Environment. DEVCLOUD Web Based Integrated Development Environment.

Software Requirement Specification For Flea Market System

NETWRIX EVENT LOG MANAGER

ISO COMPLIANCE WITH OBSERVEIT

FaciliWorks 8i. Product Features. Features in blue are specific to FaciliWorks 8i Enterprise. Flexible Installation Options

Draft Information Technology Policy

Acronym Full Name Description. RoR Ruby on Rails Web application framework

Simple. Smart. Powerful.

Trend Micro Incorporated reserves the right to make changes to this document and to the products described herein without notice.

Performance with a single touch

APPENDIX 4 TO SCHEDULE 3.3

CCUMED Complete Behavioral Health EHR and Practice Management Solutions

Software Requirements Specification. Task Management System. for. Prepared by. Version 1.0. Group Name: Pink and Purple. Date:

Hostrings EMR Software

Software Requirements Specification VODKA. for. Version 1.1 Approved April 24, 2007

Software Installation and Creating a New Company

Hardware and Asset Management Program

NOAA HSPD-12 PIV-II Implementation October 23, Who is responsible for implementation of HSPD-12 PIV-II?

University of Illinois at Chicago Health Sciences Colleges Information Technology Group Security Policies Summary

Licensing Guide for Partners. Leveraging Data Center Providers and Software Services Resellers

TeamViewer 9 Manual ITbrain

Application Compatibility Best Practices for Remote Desktop Services

MET/TEAM Test Equipment Asset Management Software

10231B: Designing a Microsoft SharePoint 2010 Infrastructure

BUILDER 3.0 Installation Guide with Microsoft SQL Server 2005 Express Edition January 2008

How To Use Zh Openemr

Rise Broadband Networks, Inc. Privacy Policy and Customer California Privacy Rights. Effective date: January, 2016

CSG Windows Support Policy

BridgeConnex Statement of Work Managed Network Services (MNS) & Network Monitoring Services (NMS)

HP Service Manager. Software Version: 9.34 For the supported Windows and UNIX operating systems. Processes and Best Practices Guide

A Nemaris Company. Formal Privacy & Security Assessment For Surgimap version and higher

Requirements Specification Document for esim-mr 1.0

LogMeIn HIPAA Considerations

Æ Æ. PROVYS TVoffice. management reporting. evaluation. planning. integrated workflow and information sharing environment. asset procurement costs

Introduction. PCI DSS Overview

Everything you every wanted to know about how to licence your Windows Server with Client Access Licences (CALs)

MANAGED FILE TRANSFER: 10 STEPS TO HIPAA/HITECH COMPLIANCE

MakersInstitute Open edx Extension

HP LoadRunner: Essentials 11

Last Updated on 11/06/

HELP DESK SUPERVISOR

Security FAQs (Frequently Asked Questions) for Xerox Remote Print Services

A.Team Software (.DMS) Dynamic Meeting Scheduler Vision Document

Microsoft Dynamics AX 2012 Licensing Guide. August 2011 Customer Edition

Volume Licensing reference guide. Windows 8 and Windows RT

SECTION C SCHEDULE A: PROJECT BRIEF PART 1: SCOPE OF SERVICES

HP Service Manager. Software Version: 9.40 For the supported Windows and Linux operating systems. Processes and Best Practices Guide (Codeless Mode)


FedEx Billing Online User Guide

M O B I L E E A M E Q U I P M E N T M A I N T E N A N C E

Greenway Customer Support SUPPORT POLICIES. To deliver world class client experiences that delight each and every time we interact with our clients.

AdminToys Suite. Installation & Setup Guide

LEARNING SOLUTIONS website milner.com/learning phone

Dell UPS Local Node Manager USER'S GUIDE EXTENSION FOR MICROSOFT VIRTUAL ARCHITECTURES Dellups.com

Software Requirements Specification

Volume 2 Compliance Process

Billing and scheduling software checklist

StruxureWare Power Monitoring In-Place Upgrade Guide SQL Server Standard Edition Only

EMS Portal How to Apply to Become an EMS Education Coordinator

Vision Document Airline Reservation System

Unless otherwise stated, our SaaS Products and our Downloadable Products are treated the same for the purposes of this document.

Vision Examinations & Optical Hardware Coverage & Billing Guidelines

TIME KEEP LEGAL BILLING SOFTWARE REQUIREMENTS SPECIFICATION

Trend Micro Incorporated reserves the right to make changes to this document and to the products described herein without notice.

Sophos SafeGuard Disk Encryption for Mac and the Casper Suite

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

WellDyneRx Mail Service General Questions and Answers

Reform PDC Document Workflow Solution Streamline capture and distribution. intuitive. lexible. mobile

Draft Middleware Specification. Version X.X MM/DD/YYYY

Intrado Call Handling CPE. Standard Maintenance and Support Services ( MSS Terms )

Fundamentals of LoadRunner 9.0 (2 Days)

Privacy Policy. Introduction. Scope of Privacy Policy. 1. Definitions

Concur Travel & Expense

This policy shall be reviewed at least annually and updated as needed to reflect changes to business objectives or the risk environment.

Transcription:

V1.0

1. Introduction 1.1 Purpose... 1 1.2 Document Conventions... 1 1.3 Intended Audience and Reading Suggestions... 1 1.4 Project Scope... 1 1.5 References... 1 2. Overall 2.1 Product Perspective... 2 2.2 Product Features... 2 2.3 User Classes and Characteristics... 2 2.4 Operating Environment... 2 2.5 Design and Implementation Constraints... 3 2.6 User Documentation... 3 2.7 Assumptions... 3 2.8 Dependencies... 3 3. System Features 3.1 Management... 3 3.2 Appointment Management... 4 3.3 Inventory Management... 4 4. External Interface Requirements 4.1 User Interfaces... 4 4.2 Software Interfaces... 4 4.3 Communications Interfaces... 4 5. Other Nonfunctional Requirements 5.1 Performance Requirements... 5 5.2 Safety Requirements... 5 Appendix A: Use Cases... 6-1

1. Introduction 1.1 Purpose The purpose of this Software Requirement Specifications (SRS) document is to outline the functional and nonfunctional requirements of the proposed electronic medical record system for Ruston Eye and Laser Institute. The document will give an overall description of the proposed new system and a detailed description of the new system features. 1.2 Document Conventions Unless otherwise notated, all requirements listed in this document are of high-level importance to the design of the overall system 1.3 Intended Audience Dr. Jared M. Vincent the rest of this document contains requirements for the system proposed for Ruston Eye and Laser Institute. Read the document in the order presented to gain a clear understanding of system requirements. Approach the requirements as they pertain to your system usage, paying close attention to sections dealing with physician input. Rhonda White, Business Manager the rest of this document contains requirements for the system proposed for Ruston Eye and Laser Institute. Read the document in the order presented to gain a clear understanding of system requirements. Approach the requirements as they pertain to your system usage, paying close attention to the overall system and how its parts relate to the business operations of Ruston Eye and Laser Institute. 1.4 Project Scope The Insight system proposed for Ruston Eye and Laser Institute is an all-inclusive electronic medical record storage system with capabilities for patient management, inventory control, and automatic insurance verification. As a full-featured ophthalmology clinic and optical shop, the Insight system will allow Ruston Eye and Laser Institute to expand its patient-base while experiencing increases in efficiency and decreases in cost. The system will meet needs being met by the system currently in place as well as unmet needs identified in business operations and the development of these requirements. 1.5 References The Health Insurance Portability and Accountability Act of 1996 (HIPAA) Privacy and Security Rules 1

The Safety and Quality Improvement Act of 2005 (PSQIA) Safety Rule 2. Overall 2.1 Product Perspective The Insight system proposed for Ruston Eye and Laser Institute is a modern iteration of the system currently utilized. 2.2 Product Features Major features of the proposed Insight system include: FE-01 Electronic medical record creation and storage FE-02 Automated insurance coverage verification FE-03 Inventory control *refer to Appendix A for Use Cases pertaining to these features 2.3 User Classes and Characteristics Physician The physician is the primary user of the system. The physician has administrator privileges and can set privileges for other employees. This user class is can edit all aspects of the proposed system and is the only class that can input and edit a patient diagnosis and authorize prescriptions. Manager The manager is the secondary user of the system. Privileges are set by the physician. This user class can edit privileges for all employees except the physician. This user class can edit all aspects of the system except for privileges reserved for the physician user class. Employee This employee is the ternary user of the system. Privileges are set by the physician or the business manager. This user cannot edit their privileges or the privileges of other users of the same class. This user can only edit aspects of the system for which they have been granted permission by either the physician or the manager. 2.4 Operating Environment Hardware: HP Slimline Desktop Computers HP ProLiant Blade Server Operating System: Microsoft Windows XP or later 2

The system will be accessed remotely over the internet, allowing use of the system from any computer with a compatible internet browser. 2.5 Design and Implementation Constraints CO-01 CO-02 CO-03 CO-04 The designed system must be able to be accessed remotely over an internet connection. Storage and encryption must be compliant with HIPAA regulations. Permissions must be set for three types of users: physician, manager, and employee. All current medical records must be able to be entered into the system. 2.6 User Documentation A comprehensive User Manual will be included with delivery of the final system. 24/7 email technical support will be available through SDLC. 2.7 Assumptions AS-01 AS-02 AS-03 SDLC technical and project resources are available and have capability to define, develop, test, train, and deploy the project. Peripheral testing devices export in a graphical format that can be stored and viewed. Medical diagnosis and procedural codes cover the complete range of possible patient diagnosis and treatment. 2.8 Dependencies DE-01 DE-02 DE-03 DE-04 Wasp Inventory Control System must be purchased Updates from the Medicare system to medical diagnosis and procedural codes will be provided, allowing for system updates. Individual insurance companies allow for online verification of patient insurance coverage. HIPPA regulations will remain unchanged. Should a change occur, ample time is provided for system upgrades. 3. System Features 3.1 Management 3.1.1 The system will allow employees to add a new patient to the patient database. 3.1.2 The system will allow employees to add a new insurance company and coverage to the insurance database. 3

3.1.3 The system will allow employees to add a new physician to the physician database. 3.1.4 The system will allow employees to view the current patient schedule. 3.1.5 The system will allow employees to create new patient appointments. 3.1.6 The system will automatically verify patient insurance coverage with the respective insurance companies. 3.1.7 The system will allow employees to manage patient accounts. 3.2 Appointment Management 3.2.1 The system will allow employees to check patients in for an appointment. 3.2.2 The system will allow technicians to record patient medical history. 3.2.3 The system will store graphical data from tests performed during the patient appointment. 3.2.4 The system will allow physicians to input physician notes. 3.2.5 The system will allow physicians to select applicable diagnosis codes. 3.2.6 The system will allow physicians to select applicable procedural codes. 3.2.7 The system will record physician signatures. 3.2.8 The system will allow employees to schedule patient follow-up appointments. 3.2.9 The system will record patient payments in patient accounts. 3.3 Inventory Management 3.3.1 The system will allow employees to view the current frame and contact lens inventory. 3.3.2 The system will allow the optical shop manager to place orders for new frames and contact lenses. 3.3.3 The system will record the addition of new frames and contact lenses to inventory when they are received from the supplier. 3.3.4 The system will print coded labels to identify frame types. 3.3.5 The system will alert the optical shop manager when a re-order level for an item is reached. 3.3.6 The system will record patient payments in patient accounts. *refer to Appendix A for use cases pertaining to these features 4. External Interface Requirements 4.1 User Interfaces Website All employees of Ruston Eye and Laser Institute will interface with the Insight system through a web interface 4.2 Software Interfaces Wasp Inventory Control Software This is specialized software for creating and maintaining an inventory. This software allows for items to be entered and sold, barcoded labels to be printed, and reports to be generated. 4.3 Communications Interfaces 4

Email all employee communications with SDLC support will be made through email. Message the Insight system will allow employees to send inner-office messages that will display as pop-up windows within the system. Alerts The Insight system will allow employees to create alerts on patient accounts. These alerts will display as a pop-up window when a patient s account is accessed. 5. Other Nonfunctional Requirements 5.1 Performance Requirements 5.1.1 The system should support an inner-office staff of at least 5 employees and 1 medical doctor. 5.1.2 Links for s, Schedule, and Records should be able to be accessed from every page. 5.1.3 Page loading should be completed in no more than 5 seconds 5.2 Security Requirements 5.2.1 Only physicians and the business manager can access other employee accounts. 5.2.2 Only physicians and technicians can edit patient medical records. 5.2.3 Account permissions will be set by the business manager and are verified by employee username and password. 5

Scenario Name: Manage s ID Number: 1 Short : Manage new and existing patients, schedule appointments, and verify patient insurance coverages. Trigger: calls to schedule an appointment Type: External / Temporal Major Inputs: Source Major Outputs: Destination Insurance Information Referring Physician Available Appointments Eligibility Response Eligibility Status Appointment Data Store Insurance Company Data Store Scheduled Appointment /Appointment Data Store Insurance Company Major Steps Performed Information for Steps 1. Gather 2. Schedule Appointment Insurance Information Referring Physician Available Appointments Scheduled Appointment 3. Verify Insurance Coverage Eligibility Status Eligibility Response 6

Scenario Name: Verify Eligibility ID Number: 1.3 Short : Upon appointment scheduling, the system automatically verifies patient insurance coverage with the insurance company. Trigger: Appointment scheduled Type: External / Temporal Major Inputs: Source Major Outputs: Destination Insurance Information Store Insurance Policy Information Store Referring Physician Verification Date Eligibility Response Eligibility Status Data Store Insurance Company Data Insurance Coverage Data Physician Data Store Appointment Data Store Insurance Company Data Store Insurance Company Major Steps Performed Information for Steps 1. Create 2. Send Insurance Information Insurance Policy Information Referring Physician Verification Date 3. Update Eligibility Status Eligibility Response Eligibility Status 7

Scenario Name: Create ID Number: 1.3.1 Short : Upon appointment scheduling, the system automatically compiles an eligibility request to send to the insurance company. Trigger: Appointment scheduled Type: External / Temporal Major Inputs: Source Major Outputs: Destination Insurance Information Store Insurance Policy Information Store Referring Physician Verification Date Major Steps Performed Data Store Insurance Company Data Insurance Coverage Data Physician Data Store Appointment Data Store Gathered Information Process 2 Compiled Information Process 3 Data Store Information for Steps 1. Gather Entity Information Gathered Information 2. Compile Entity Information Insurance Information Insurance Policy Information Referring Physician Verification Date Compiled Information 3. Save Completed 8

Scenario Name: Complete Appointment ID Number: 2 Short : Upon patient check-in, the technicians and physicians complete the patient appointment. Trigger: checks in Type: External / Temporal Major Inputs: Source Major Outputs: Destination Medical History Physician Notes Diagnosis Codes Procedural Codes Available Appointments Payment Major Steps Performed Data Store Physician Diagnosis Code Data Store Procedural Code Data Store Appointment Data Store Test Results Process 3 Diagnosis Appointment Data Store Doctor s Orders Process 4 Follow-up Appointment Appointment Data Store Information for Steps 1. Record Medical History Medical History 2. Perform Tests Test Results 3. Diagnose Doctor s Orders 4. Check Out Diagnosis Codes Procedural Codes Diagnosis Available Appointments Payment Follow-up Appointment 9

Scenario Name: Manage Glasses and Contact Lens Inventory ID Number: 3 Short : Once a re-order level is reached, the optical shop manager is automatically notified by the system of a need to reorder. Trigger: order causes re-order level to be reached Type: External / Temporal Major Inputs: Source Major Outputs: Destination Selection Payment Inventory Levels Process 2 Shipment Process 4 Major Steps Performed 1. Sell to Customer 2. Issue Reorder Notification Glasses/Contacts Sale Information Inventory Data Store Reorder Notification Optical Shop Manager Order Supplier Invoice Optical Shop Manager Shipment Information Process 5 New Inventory Inventory Data Store Information for Steps Selection Payment Glasses/Contacts Sale Information Inventory Levels Reorder Notification 3. Order New Inventory Order Invoice 4. Receive New Shipment Shipment Shipment Information 5. Update Inventory New Inventory 10