MMM Admin SRS - 12092015

Revision: 1.
2 Medflow Medication Manager - Admin Page: 1 of 22

Date: 10/15/2015 Software Requirements Specification Status: DRAFT
Medflow Medication Manager

Software Requirements Specification
Medflow, Inc., 6739-A Fairview Rd., Charlotte, NC 28210 Confidential

Revision: 1.2 Medflow Medication Manager - Admin Page: 2 of 22
Table of Contents
1. INTRODUCTION.................................................................................................................................4
1.1 PURPOSE..................................................................................................................................................4
1.2 SCOPE......................................................................................................................................................4
1.2.1 Scope Inclusion.............................................................................................................................4
1.2.2 Scope Exclusion............................................................................................................................4
1.2.3 Impact on other systems................................................................................................................4
1.3 DEFINITIONS, ACRONYMS, AND ABBREVIATIONS...................................................................................5
1.4 REFERENCES............................................................................................................................................5
1.5 OVERVIEW...............................................................................................................................................5
2. OVERALL DESCRIPTION................................................................................................................6
2.1 PRODUCT PERSPECTIVE...........................................................................................................................6
2.2 PRODUCT FUNCTIONS..............................................................................................................................6
2.3 USER CHARACTERISTICS.........................................................................................................................6
2.3.1 Permissions...................................................................................................................................6
2.3.2 Preferences....................................................................................................................................6
2.3.3 Logging.........................................................................................................................................6
2.4 CONSTRAINTS..........................................................................................................................................7
2.5 ASSUMPTIONS AND DEPENDENCIES.........................................................................................................7
3. FUNCTIONAL REQUIREMENTS....................................................................................................8
3.1 ACCESS AND CREATING THE MMM ADMIN APPLICATION......................................................................8
3.1.1 Access within EHR application.....................................................................................................8
3.1.2 Access to Prescribers Details........................................................................................................8
3.1.2.1 Prescribers Details..................................................................................................................................8
3.1.2.2 Managing Prescribers.............................................................................................................................9
3.2 PRACTICE REGISTRATION........................................................................................................................9
3.2.1 Practice Registration....................................................................................................................9
3.2.1.1 Adding a Practice in Practice Registration............................................................................................10
3.3 AUDIT LOG............................................................................................................................................10
3.3.1 Access to Audit Log.....................................................................................................................10
3.3.2 Functional requirements for Audit Log.......................................................................................10
3.4 MANAGE CONFIGURATIONS..................................................................................................................10
3.4.1 Physician Medication Choices....................................................................................................10
3.4.2 Configurations for Pick List........................................................................................................12
3.4.3 Setting up Patient Instructions....................................................................................................15
3.5 E-PRESCRIBING LOG..............................................................................................................................15
3.5.1 Access to the E-prescribing log shall appear.............................................................................15
4. NON FUNCTIONAL REQUIREMENTS........................................................................................16
4.1 PERFORMANCE AND LOAD REQUIREMENTS..........................................................................................16
4.2 COMPATIBILITY REQUIREMENTS...........................................................................................................16
4.3 CERTIFICATION REQUIREMENTS............................................................................................................16
4.4 SUPPORTABILITY REQUIREMENTS.........................................................................................................16
4.5 USABILITY REQUIREMENTS...................................................................................................................17
4.6 USER MANUALS AND ONLINE HELP.....................................................................................................17
5. EXTERNAL INTERFACE REQUIREMENTS..............................................................................17
6. SECURITY AND AUTHENTICATION REQUIREMENTS........................................................17
7. PROJECT SUCCESS CRITERIA....................................................................................................17
8. IMPACTED FUNCTIONALITIES..................................................................................................17

8.1.1 Dependent Functionalities..........................................................................................................17

8.1.2 Bidirectional Functionalities......................................................................................................18
9. USER INTERFACE REQUIREMENTS..........................................................................................18
9.1 PHYSICIAN MEDICATION CHOICES........................................................................................................18
9.2 CONFIGURATIONS FOR PICK LIST..........................................................................................................18
9.2.1 Mock up for Medication Configuration......................................................................................18
9.2.2 Mock up for Section Pick List.....................................................................................................19
9.2.3 Specialty Code Key (reference section 3.2.1).............................................................................19
9.2.4 Directory Specialty......................................................................................................................19
9.2.5 Service Level...............................................................................................................................19
9.2.6 Use Case......................................................................................................................................19
10. FUTURE REQUIREMENTS............................................................................................................20
11. REVISION HISTORY.......................................................................................................................21

1. Introduction
1.1 Purpose
The purpose of this document is to outline the requirements for the Medflow Medication
Manager Administration. This Administration application shall allow users to manage
users, configurations and manage E-prescribing logs. Each
Broad Goals:
 Manage Practice Registration
 Manage configurations
o Medication Favorites List
o Medication Picklist
o Patient Instructions
 Managing E-Prescribing Logs
 Access to Audit Logs
1.2 Scope
1.2.1 Scope Inclusion

Provide a list of features/functionality and issues in the current system, which will
be addressed in this project. It may include a context diagram or a block diagram
to illustrate the scope of the system.
1.2.2 Scope Exclusion

List the features/functionality and issues that will not be addressed in this project.
All those features, which can cause confusion related to what is included in the
scope and what is out of the scope needs to be considered while doing the
requirements. Hence, if there are any specific features, which appear to be part
of the scope, but the client has explicitly requested that they be excluded from
the project, then those should be listed here to provide better clarity on the scope
of the work.
1.2.3 Impact on other systems

Discuss the impact of this project on other systems, and how other systems will
affect this project.
The SRS will address the following:

• Functionality
• User Interface
1.3 Definitions, Acronyms, and Abbreviations

CPOE-Computerized Provider Order Entry

eRx- Electronic prescribing
Generic Prescription-a drug defined as a product that is comparable to a drug
brand with similar dosage form, strength, quality, performance use and intended
use.
MMM-Medflow Medication Manager
CMS-Centers of Medicare & Medicaid Services
API-Application Program Interface- s a set of routines, protocols, and tools for
building software applications. An API expresses a software component in terms
of its operations, inputs, outputs, and underlying types. An API defines
functionalities that are independent of their respective implementations, which
allows definitions and implementations to vary without compromising the
interface.
Definitions, Acronyms, Details
and Abbreviations
MMM Medflow Medication Manager
Prescriber User that is allowed by state laws and regulations
to prescribe a medication
EHR Electronic Health Record
1.4 References
Medflow Medication Manager API Version 1.0 05/17/2015
Medflow Medication Admin SRS Version 3 09/16/2015
Formulary Widget (94) Version 1 06/12/2015
Drug to Drug/Allergy/Disease Widget (96) Version 1 05/21/2015
E-prescribing Log (98) Version 4 09/14/2015
CMS.gov-Meaningful Use
E-Prescribing- https://www.cms.gov/Regulations-and-
Guidance/Legislation/EHRIncentivePrograms/downloads/Stage2_EPCore_2_ePre
scribing.pdf
Computerized Provider Order Entry- https://www.cms.gov/Regulations-and-
Guidance/Legislation/EHRIncentivePrograms/downloads/Stage2_EPCore_1_CP
OE_MedicationOrders.pdf
CMS.gov (https://www.cms.gov/Medicare/Quality-Initiatives-Patient-
Assessment-Instruments/PQRS/MeasuresCodes.html)
API
SRS
1.5 Overview
 Section 2 provides a summary description of the requirements including
background information on the product and intended workflow.

 Section 3 contains the functional requirements. These specify the "business logic"
for the software. Individual requirements are marked in each section with a
number that includes the section number, followed by a dash, followed by a
requirement number, e.g. "3.1.1 - 1".
 Section 4 contains the user interface requirements. These specify the "look and
feel" of the software.
 Section 5 contains the document revision history.

2. Overall Description
2.1 Product Perspective
2.2 Product Functions
2.3 User Characteristics
1.1.1 Permissions
Permissions and users roles will be determined by individual EHR applications. This
information shall be sent to the Medflow Medication Manager through API
1.1.2 Preferences
Category Preference Description / Action

Medication Sample Medication If action is set to Y for a clinic, the lot
Lot Number number field is required when a sample is
required added to medication list
Medication Discontinue If option is set to Y for clinic, a box shall
Medication appear when discontinuing medication to add
statement required reason for discontinuation
Drug to
Drug/Allery/Disease
1.1.3 Logging
The application will log all instances that saves any changes. We will include the name
of user, the change saved. This will include adding, editing, removing, deleting any item
within application. The date and time the change occurred.
The system shall provide a section that allows users to view all logging. The Log section
shall allow the user to filter by date and user.
Type Action Description

2.4 Constraints
# Constraint Impact
NA
2.5 Assumptions and Dependencies

Assumptions
# Assumptions Impact
Dependencies
# Dependencies Impact

3. Functional Requirements
3.1 Access and Creating the MMM admin application

The user shall have access to the MMM admin screen from within application and a
separate web link for access outside of application
3.1.1 Access within EHR application

A. User shall select an icon that labeled MMM Admin
3.1.2 Access to Prescribers Details

A. MMM Admin Main Menu Bar
3.1.2.1 Prescribers Details

A. MMM admin will only display providers that have been integrated with EHR
B. The system shall provide the following fields to be displayed about the physician.
These fields are read only. (Subject for discussion)
a. First Name
b. Middle Name
c. Last Name
d. Clinic Name
e. NPI Number
f. SPI Number

g. DEA number
h. State License field with associated state selection drop down
i. Address Line 1, Line 2, City, State and Zip Code
j. Email address
k. Phone Number
l. Fax Number
3.1.2.2 Managing Prescribers

A. Adding a prescriber will come from MMM API. This information will flow from
the EHR. The following fields are required to be received from API
B. User enters at a minimum the following fields
a. Prescriber Name
b. SPI
c. NPI number
d. DEA number
e. State License/State
f. Username to be linked from EHR
C. MMM Admin will not allow configurations of prescriber to be modified. Any
Editing of the prescriber details shall be in done in EHR and the same shall be
received by the application through API.
D. Changing prescriber status to inactive shall be handled by EHR. MMM admin
must have ability to disable users through MMM API
3.2 Practice Registration
A. The MMM shall allow the user to register the practice and edit practice details
3.2.1 Practice Registration

A. Practice Name
B. Practice Facility Name
C. Practice Facility Key (Index)
D. Practice Type

E. Address
F. Phone number
G. Fax Number
H. Account Number
3.2.1.1 Adding a Practice in Practice Registration

A. User enters Practice details. All fields are required
B. User selects Add
C. Information populates save data fields
3.3 Audit Log

A. The Audit Log shall capture details of user actions.
B. The log shall provide Date/Time, User identification, Patient Identification and
Action Taken for all actions within MMM Admin. The actions should include
additions, deletions, changes, queries and printing. The exact action performed
shall populate the log.
Example: John Smith, MD added medication- Pred Forte 1% QID OU,
09/16/2015 at 5:45AM.
3.3.1 Access to Audit Log

A. MMM Admin Main Menu Bar
3.3.2 Functional requirements for Audit Log

B. The user shall have the ability to view logs by the following:
a. Prescriber
b. Date Range
c. Action
d. User
3.4 Manage Configurations
3.4.1 Physician Medication Choices

User shall have the ability to create favorites list of systemic medications selection and
ocular medications selection.
A. Accessing the Physician Medication Choices
a. Access MMM Admin application

b. Select Physician Medication Choices
B. Upon accessing Physician Medication Choices, the users shall see the
following:
a. List of physician names with a sort feature
b. List of Medication Types
i. Ocular
ii. Systemic
c. A second list of physician names with sort feature
d. Copy button
C. Functionality of the Physician Medication Choices
a. User selects physician name from list
i. List shall present all active physicians within the MMM
admin screen
b. User selects medication type
i. A medication search field shall appear
ii. List of saved medications for selected physician by
medication type shall appear
c. User searches for medication
i. Searches from master medication database
ii. Search shall be conducted by intellisense
d. User selects medication
e. User selects Plus sign to add medication to selected medication
type list
i. The application shall not allow duplicates
1. If user attempts to add a medication that already
exist on list the following validation shall appear
a. “Medication already included in list”
ii. The application shall allow user to remove an entry from
the user lists
1. A standard red (x) shall be used to remove an item
from the physician list
a. This standard (x) shall appear next to each
line item
2. User selects red (x) to remove
3. The application shall remove selected medication
from physician list
4. A validation shall appear stating “Medication
removed from list”
D. Functionality of adding favorite instructions by medication
a. This configuration is available for ocular medications only
b. User shall select an ocular medication from physician medication
list.
c. The following columns shall appear:
i. Dosage
ii. Form Type

iii. Frequency
iv. Route
d. The medication list associated with selected medication shall
appear
e. The columns selections shall show based on configurations
described in Section 3.3.2
f. User shall select a dosage, form type, frequency and route
g. User selects Add
i. The instruction shall populate the Medication Instruction
list that is attached to selected medication
ii. Validation shall appear “Medication Instruction save
successfully”
iii. User shall have the ability to add several instructions to
each selected medication.
h. User shall have the ability to remove medication instruction from
selected medication instruction list.
i. User selects Medication
ii. User selects Medication from ocular medication
iii. Medication Instruction list for selected medication shall
appear
iv. User selects the (X) remove button
1. Medication removed from list
v. Validation appears “ Medication Instruction removed”
E. User shall have the ability to view the favorites medication list within
MMM user interface
F. User shall have the ability to view the medication instructions by
medication with MMM user interface once medication is selected from
favorites list.
G. User shall have the ability to copy physician medication choices from one
physician to the next physician
a. User selects physician
i. All saved configuration shall populate
b. User shall select a physician from second drop down
i. User shall have the ability to select all physicians
c. User selects Copy
i. The list shall copy and a validation shall appear “ Copied
successfully”
3.4.2 Configurations for Pick List

User shall have the ability to configure the picklist by medication type. This is a clinic
wide list. The picklist will change based on medication selected. If a medication is
selected from master search or medication favorites list, the columns (Dosage, Form
Type, Frequency and Route) shall change based on configurations described below. This
configuration is different from creating favorite instruction list by medication.

The user shall also have the ability to create a picklist by physician for Pharmacist Notes
and Additional Instructions.
A. Access to the Configuration-Pick List

a. Access MMM Admin application
b. Select Configuration
B. Upon accessing Configuration-Pick List
a. Two Sections
i. Medication Instructions
ii. Pick List
b. Three radial dials within Medication Instructions section
i. Topical
ii. Ointment
iii. Oral
c. Four columns with a fields with additional field to allow adding items to
list in Medication Instruction Section
i. Dosage
ii. Form Type
iii. Frequency
iv. Route
d. Save button with Medication Instruction Section
e. Section two shall include the following
i. Physician Drop Down
ii. Master Table Name Drop Down
iii. Column that allow user to select or multi select items
iv. Description Column
v. Remove Column
vi. Description field
vii. Actions Buttons
1. Save
2. Clear
3. Print
4. Export
5. Copy with associated Physician Pick list
C. Functionality of the Configuration-Pick List
a. Medication Configuration
i. User accesses Medication Instruction configuration widget
ii. The application shall auto load the topical instructions
iii. Select a medication type
1. User shall select ointment or oral radial dial to see the
associated list.
iv. The previous configured list for selected medication type shall
load.
v. User shall enter items for Dosage, Form Type, Frequency or
Route.
vi. Select the associated (+) button to add to list

1. User shall add items one at a time

a. Changing the order of the dosage, form type, frequency or route list by
medication type
a. The application shall auto sort list by alphabetical or numeric
order
b. The user shall have the ability to change the order of the list by
selecting, drag and drop in the preferred order for all list.
i. User selects the medication type
ii. The lists (dosage, form type, frequency and route) for
selected medication type shall appear
iii. User selects a line item and drag/drop in preferred order
b. Removing a medication instruction
a. Select Medication Type
i. Application shall load saved medication instructions
b. User shall have the ability to select (x) to remove an items
c. User removes an item ,validation shall appear stating
“Removed successfully”
c. Pick List Configuration
a. Select Physician Drop Down
b. Select Master Table Name
i. Additional Instructions
ii. Pharmacist Notes
c. User free types value
d. Selects Save
i. The value shall appear as a picklist item
ii. Validation shall appear stating “ Saved successfully”
e. Removing an item from picklist
i. Select physician
ii. Select Master Table Name
iii. Select Red (x) next to item user wishes to remove
iv. Validation appears” Removed successfully”
f. Editing a description
i. Select Physician
ii. Select Master Table Name
iii. Select description by highlighting line item
1. Value shall populate the Description field
iv. User edits within Description field
v. User selects Save button
vi. Validation appears ”Updated successfully”
g. Printing or exporting the pick list
i. User selects physician
ii. User selects Master Table Name
iii. User selects items to print or edit by selecting the check
box
1. User shall have the ability to select all
iv. User selects Print

1. Items selected shall be prompted to Print

v. Users selects Export
1. Items selected shall be presented in csv format
h. Copy Picklist to another physician
i. User selects physician
ii. User selects Master Table Name
iii. User select items by select check box
iv. User selects physician(s) for second physician drop
down
v. User selects Copy
1. Application shall make sure physicians selected
have the selected items added to the list.
a. Application shall not allow duplicates
3.4.3 Setting up Patient Instructions

MMM allows the user to create patient instructions list. The purpose of the patient
instruction list to provide the patient with a list of instructions patient understand. The
instructions will not include medical acronyms. The purpose of this configuration page is
to add acronyms and place the English verbiage. The system will later support Spanish
and other languages.
3.5 E-prescribing Log

Reference the E-Prescription Log Requirements document.
3.5.1 Access to the E-prescribing log shall appear.

A. Access the MMM admin application
B. Select E-prescribing Log from menu bar
4. Non Functional Requirements

4.1 Performance and Load Requirements

Include all performance requirements known at this point. Include a reference to
the design document if performance requirements are further clarified in the
design. Include all UI performance (time to paint screens), response times, and
average processing times.
Example:
Current User Load

Expected Growth
Number of Concurrent Users
Transaction Size (files sizes,
etc.)
Maximum Average
Transaction Time Acceptable
4.2 Compatibility Requirements

Include all compatibility requirements for hardware, software and operating
systems.
Example:
HTML Versions to be Supported

Browser Versions to be Supported
Database Versions to be Supported
Communication Protocol
Platform Version to be Supported
Any Other External Systems or Standards
4.3 Certification Requirements

Include all certification requirements, if any.
4.4 Supportability Requirements

This section indicates any requirements that will enhance the supportability or
maintainability of the system being built.
4.5 Usability Requirements

Describe any special user interface or usability testing requirements, for

example, browser compatibility, use of specific widget sets, portability
requirements of the user interface, etc.
4.6 User Manuals and Online Help

Describe any manuals or help requirements,
5. External Interface Requirements

Include any interface requirements that allow external systems to communicate
with this application or allow this application to communicate with external
systems.
This section defines the interfaces that must be supported by the application. It
should contain adequate information, protocols, ports and logical addresses,
etc., so that the software can be developed and verified against the interface
requirements.
6. Security and Authentication Requirements

Describe any special requirements to protect data stored in the system, e.g.
database security, encryption, etc
7. Project Success Criteria

List the items and measurements necessary to prove the success of the project,
in terms of the benefits listed earlier. For example, if decreased transaction time
is listed as a benefit, give the current time to perform the transaction and the
expected time reduction.
Possible success criteria can include, but are not limited to:
 Decreased transaction time

 Improved training efficiency
 Decreased incidence of user reported problems
8. Impacted Functionalities
8.1.1 Dependent Functionalities
SRS Dependent Functionalities Impact

Ref
8.1.2 Bidirectional Functionalities
SRS Bidirectional Impact

Ref Functionalities
9. User Interface Requirements
9.1 Physician Medication Choices
9.2 Configurations for Pick List
9.2.1 Mock up for Medication Configuration

9.2.2 Mock up for Section Pick List
9.2.3 Specialty Code Key (reference section 3.2.1)
9.2.4 Directory Specialty

A. Doctor
B. In Store Clinic (?)
C. Medication Reconciliation
D. NP (Nurse Practitioner)
E. PA (Physician Assistant)
F. Resident
9.2.5 Service Level

A. Disabled
B. New
C. Change
D. Cancel
E. Census
F. Controlled Substance
9.2.6 Use Case

1. Att Alert
2. RTBC
3. ADVSAVE
4. PNLIMMUN
5. Basic Save

10. Future Requirements
As part of the project all those requirements, which may have been identified to
be implemented in the future phases of the project, can be detailed here. This
section should document all those known requirements that may impact the
current functionality (being considered for the existing project) or non-functional
requirements of the system. The objective here is to document all those features
or non-functional requirements, which may be considered in the subsequent
phases or in the future and will provide direction to improve the functionality of
the system, but due to various reasons cannot be considered within the current
scope of the project.

11. Revision History
Revision Author Date Description

1.0 Quentella 08/17/2015 Initial Document
Middleton
1.1 Quentella 09/16/2015 Added
Middleton Prescribers
Details, User
Registration,
and Audit
Log
1.2 Vimal 10/15/2015 Updated additional sections to make it more comprehensive (example NFR)

MMM Admin SRS - 12092015

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

MMM Admin SRS - 12092015

Uploaded by

Copyright:

Available Formats

Revision: 1.

2 Medflow Medication Manager - Admin Page: 1 of 22

Medflow Medication Manager

Medflow, Inc., 6739-A Fairview Rd., Charlotte, NC 28210 Confidential

Medflow, Inc., 6739-A Fairview Rd., Charlotte, NC 28210 Confidential

8.1.1 Dependent Functionalities..........................................................................................................17

Medflow, Inc., 6739-A Fairview Rd., Charlotte, NC 28210 Confidential

1.2.1 Scope Inclusion

1.2.2 Scope Exclusion

1.2.3 Impact on other systems

The SRS will address the following:

1.3 Definitions, Acronyms, and Abbreviations

Medflow, Inc., 6739-A Fairview Rd., Charlotte, NC 28210 Confidential

CPOE-Computerized Provider Order Entry

Medflow, Inc., 6739-A Fairview Rd., Charlotte, NC 28210 Confidential

 Section 5 contains the document revision history.

Medflow, Inc., 6739-A Fairview Rd., Charlotte, NC 28210 Confidential

2.1 Product Perspective

2.2 Product Functions

2.3 User Characteristics

Category Preference Description / Action

Type Action Description

Medflow, Inc., 6739-A Fairview Rd., Charlotte, NC 28210 Confidential

2.5 Assumptions and Dependencies

Medflow, Inc., 6739-A Fairview Rd., Charlotte, NC 28210 Confidential

3.1 Access and Creating the MMM admin application

3.1.1 Access within EHR application

3.1.2 Access to Prescribers Details

3.1.2.1 Prescribers Details

Medflow, Inc., 6739-A Fairview Rd., Charlotte, NC 28210 Confidential

3.1.2.2 Managing Prescribers

3.2 Practice Registration

3.2.1 Practice Registration

Medflow, Inc., 6739-A Fairview Rd., Charlotte, NC 28210 Confidential

3.2.1.1 Adding a Practice in Practice Registration

3.3 Audit Log

3.3.1 Access to Audit Log

3.3.2 Functional requirements for Audit Log

3.4 Manage Configurations

3.4.1 Physician Medication Choices

a. Access MMM Admin application

Medflow, Inc., 6739-A Fairview Rd., Charlotte, NC 28210 Confidential

3.4.2 Configurations for Pick List

Medflow, Inc., 6739-A Fairview Rd., Charlotte, NC 28210 Confidential

A. Access to the Configuration-Pick List

Medflow, Inc., 6739-A Fairview Rd., Charlotte, NC 28210 Confidential

1. User shall add items one at a time

Medflow, Inc., 6739-A Fairview Rd., Charlotte, NC 28210 Confidential

1. Items selected shall be prompted to Print

3.4.3 Setting up Patient Instructions

3.5 E-prescribing Log

3.5.1 Access to the E-prescribing log shall appear.

4. Non Functional Requirements

Medflow, Inc., 6739-A Fairview Rd., Charlotte, NC 28210 Confidential

4.1 Performance and Load Requirements

Current User Load

4.2 Compatibility Requirements

HTML Versions to be Supported

4.3 Certification Requirements

4.4 Supportability Requirements

4.5 Usability Requirements

Medflow, Inc., 6739-A Fairview Rd., Charlotte, NC 28210 Confidential

Describe any special user interface or usability testing requirements, for

4.6 User Manuals and Online Help