Business Requirements Document Example Business Requirements Template Examples Disclaimer

Document Sample
Business Requirements Document Example Business Requirements Template Examples Disclaimer Powered By Docstoc
					                                 Business Requirements

                           Template Examples Disclaimer

Unless otherwise specifically stated, the information contained herein is
made available to the public by the Department of Human Services, Office
of Information Services, Project Management Office for use as an example
of template content information and may not reflect the realities of an actual
project. The intent of the template example is to assist an individual
creating a new document using the PMO standard template.

Neither the DHS, OIS, PMO nor any other agency or entities thereof,
assumes any legal liability or responsibility for the accuracy, completeness,
or usefulness of any information, product or process disclosed in these
examples.

Reference herein to any specific commercial product, process, service by
trade name, trademark, manufacturer, or otherwise, does not constitute or
imply its endorsement, recommendation, or favoring by the PMO or any
entities thereof.

The views and opinions of the originators expressed therein do not
necessarily state or reflect those of the DHS, OIS, PMO or any agency or
entities thereof.




Author: PMO                                               Page 1 of 7
D:\Docstoc\Working\pdf\b1625a55-e5aa-46b9-b8cb-9378d735503a.doc
Created on: 11/13/ 2010                            Last Modified on: 11/13/ 2010 4:04: 00 AM
                                 Business Requirements

             Oregon Department of Human Services
                 Office of Information Services
                            HCFA-372

             Business Requirements Documentation
                         Approval Date: September 12, 2002

                               Purpose of the Document
The business requirements define the owner’s view, sketching key aspects of the
problem and the requirements that will resolve the problem. It also examines the issues
and risks that have an impact on the system as a whole.




Author: PMO                                               Page 2 of 7
D:\Docstoc\Working\pdf\b1625a55-e5aa-46b9-b8cb-9378d735503a.doc
Created on: 11/13/ 2010                            Last Modified on: 11/13/ 2010 4:04: 00 AM
                                 Business Requirements


                              Document Change Activity
The following is a record of the changes that have occurred on this document from the
time of its original approval
#   Change Description                                                      Author       Date




Business Contacts
          Name                                   Title                          Phone
Don Fries                               Research Analyst                   503 945-6455
Sean McMullen                           Research Analyst 3                 503 945-9799




Author: PMO                                               Page 3 of 7
D:\Docstoc\Working\pdf\b1625a55-e5aa-46b9-b8cb-9378d735503a.doc
Created on: 11/13/ 2010                            Last Modified on: 11/13/ 2010 4:04: 00 AM
                                      Business Requirements

                                           Table of Contents

1 Business Requirements ............................................................................. 1
 1.1 Purpose of the System..............................................................................1
 1.2 Problem Definition ..................................................................................1
 1.3 Objectives ...............................................................................................1
 1.4 Mandatory Requirements of the System....................................................2
   1.4.1 Mandatory Requirement #1 ..................................................................2
   1.4.2 Mandatory Requirement #2 ..................................................................2
   1.4.3 More Mandatory Requirements as needed .............................................2
 1.5 Functional Requirements of the System ....................................................2
   1.5.1 Functional Requirements in General .....................................................2
   1.5.2 Functional Requirement #1...................................................................2
   1.5.3 Functional Requirement #2...................................................................3
   1.5.4 More Functional Requirements as needed .............................................3
 1.6 Constraints ..............................................................................................3
 1.7 Assumptions............................................................................................3
 1.8 Exclusions ...............................................................................................3
 1.9 Issues to be Resolved ...............................................................................3
2 Impact Statement ...................................................................................... 3
3 Risk Statement ........................................................................................... 3
4 Appendix ..................................................................................................... 3




Author: PMO                                               Page 4 of 7
D:\Docstoc\Working\pdf\b1625a55-e5aa-46b9-b8cb-9378d735503a.doc
Created on: 11/13/ 2010                            Last Modified on: 11/13/ 2010 4:04: 00 AM
                                 Business Requirements



1 BUSINESS REQUIREMENTS
1.1 PURPOSE OF THE SYSTEM
The Client Process Monitoring System (CPMS) supports client tracking and
financial reporting capabilities for SPD providers of DD services. Providers
offering DD services submit client enrollments and service costs to CPMS.
Financial accountability is accomplished by producing a monthly Provider
Financial Statement (PFS), PFS Year End, and HCFA reporting.



1.2 PROBLEM DEFINITION
To produce the annual reports for Home and Community-Based Services
Waivers for the model waivers approved by CMS. ODDS has organized its
service delivery into 4 waiver tracks, which are identified at the client level
by selected service elements. Each of the 4 waivers requires a separate
HCFA-372 report. The 4 waivers are described below, with the
representative service element and the reporting period.

The Regular ICF Waiver is represented by service element 640. The report
period for this run will be July 1, 2001 through June 30, 2002. The report is
due December 31, 2002.

The ICF Model Waiver (Behavior) is represented by service element 641.
The report period for this run will be April 1, 2001 through March 31, 2002.
The report is due September 30, 2002.

The Hospital Model Waiver is represented by service element 642. The
report period for this run will be April 1, 2001 through March 31, 2002. The
report is due September 30, 2002.

The Support Services Waiver is represented by service element 643. The
report period for this run will be July 1, 2001 through June 30, 2002. The
report is due December 31, 2002.




Author: PMO                                               Page 1 of 7
D:\Docstoc\Working\pdf\b1625a55-e5aa-46b9-b8cb-9378d735503a.doc
Created on: 11/13/ 2010                            Last Modified on: 11/13/ 2010 4:04: 00 AM
                                 Business Requirements

The reorganized HCFA-372 reports will need to identify the appropriate
waiver on the report. The report will also need to identify whether the
report is for the lag period.


1.3 OBJECTIVES
As a result of this project, the separate waivers will be reported as outlined
in the waiver approval documents.

1.4 M ANDATORY REQUIREMENTS OF THE SYSTEM
1.4.1   MANDATORY R EQUIREMENT #1
Modify the HCFA-372 reporting system to report the 4 ODDS waivers as
described above.

1.4.2   MANDATORY R EQUIREMENT #2


1.4.3   MORE M ANDATORY REQUIREMENTS AS NEEDED


1.5 FUNCTIONAL REQUIREMENTS OF THE SYSTEM
1.5.1   FUNCTIONAL REQUIREMENTS IN GENERAL
The method for determining the appropriate waiver report for a client will be
to determine the waiver tracking service element (640, 641, 642, or 643).
Once this service element is determined, any services received by the
client during the period of enrollment in the waiver tracking service element
will be reported on that version of the waiver report.
1.5.2   FUNCTIONAL REQUIREMENT #1
Utilize waiver tracking service element to create client eligible file for each
version of the waiver report.




Author: PMO                                               Page 2 of 7
D:\Docstoc\Working\pdf\b1625a55-e5aa-46b9-b8cb-9378d735503a.doc
Created on: 11/13/ 2010                            Last Modified on: 11/13/ 2010 4:04: 00 AM
                                 Business Requirements

1.5.3   FUNCTIONAL REQUIREMENT #2
CPMS services will be broken out into new component parts on each report, according
to appendix G of the waiver approval documents. This relates to the unbundling of
services for CMS reporting requirements. Specified MMIS services will also be
accumulated in the line item details for the appropriate waiver(s).

1.5.4   MORE FUNCTIONAL REQUIREMENTS AS NEEDED


1.6 CONSTRAINTS
CPMS programs and resources are not always available.

1.7 ASSUMPTIONS
ODDS will use the waiver tracking service elements to identify the
appropriate waiver for each eligible client. These are:
Service element 640 - ICF/MR Waiver
Service element 641 - ICF Model Waiver (Behavior)
Service element 642 - Hospital Model Waiver
Service element 643 - Support Services Waiver

1.8 EXCLUSIONS


1.9 ISSUES TO BE RESOLVED

2 IMPACT STATEMENT
If the necessary changes to the CPMS/HCFA reporting system are not
implemented, the state of Oregon will produce misleading reports for CMS.
3 RISK STATEMENT
If the necessary changes to the CPMS/HCFA reporting system are not
implemented, the state of Oregon will produce misleading reports for CMS.
The state of Oregon may lose Medicaid funding for DD services. The state
would probably be required to do the project anyway.
4 APPENDIX



Author: PMO                                               Page 3 of 7
D:\Docstoc\Working\pdf\b1625a55-e5aa-46b9-b8cb-9378d735503a.doc
Created on: 11/13/ 2010                            Last Modified on: 11/13/ 2010 4:04: 00 AM

				
DOCUMENT INFO
Description: Business Requirements Document Example document sample