BRD - NGL Claims Release 4
BRD - NGL Claims Release 4
BRD - NGL Claims Release 4
0
Business Requirements Document
Version: 1.0
DOCUMENT PURPOSE
The Business Requirement Document represents the customer’s requirement for a project. It does not
anticipate what the solution to these requirements may be – this is the purpose of the Functional
Requirements and Technical Design documents. The Business Requirements document ‘what’ needs to be
done, and the Functional Requirements and the Technical Design documents ‘how’ it will be done. The
other key function of the Business Requirements is to document the current state of affairs in terms of
business processes and existing systems.
All rights reserved. Information contained herein is for internal use and may only be used for business
purposes authorized by NGL.
Document Control
a. Document history
The following table records information regarding released versions of this document and briefly describes the
changes to them.
0.1
0.2
0.3
0.4
0.5
0.6
0.7
0.8
0.9
1.0
b. Document Reviewers/Approvers
List the individuals that must review or approve this document. An “X” indicates whether the individual is a
reviewer only or a reviewer and approver. (Choose One).
1 EXECUTIVE SUMMARY………………………………………………………………….…… 4
2 OVERVIEW…………………………………………………………….…………………………4
2.1 The Business Problem/Need……………………………………….………………………….4
2.2 The Business Goals and Benefits………………………………….…………………………..4
2.3 Critical Success Factors…………………………………………….…………………………5
2.4 Assumptions and Restrictions…………………………………………….…………………...5
3 CURRENT PROCESSES……………………………………………………….…………………5
3.1 Current Processes……………………………………………………………………………...6
3.2 Current Limitations……………………………………………………………………………6
4 DESCRIPTION OF REQUIREMENTS………………………………………………..….………7
4.1 Required Business Processes………………………………………………………….………7
4.2 Business Scope……………………………………………………….……………………..…7
4.2.1 Business Groups……………………………………………….………………….……7
4.2.2 Business Product / Business Transaction Types……………….….……………………7
4.2.3 Primary Business Users…………………………………………………………………7
4.2.4 External Impacts / Other Business Groups affected………………………………….…8
4.3 Specific Business Requirements……………………………………………………..……8
4.4 Performance Requirements…………………..…………………………………………..17
4.4.1 Volumes…………………..…………………………………………….…….………..17
4.4.2 Potential Growth…………………..………………………………….………………..17
4.4.3 Performance…………………..…………………………………………………..……17
4.4.4 Exception Handling…………………..………………………………………………..17
4.4.5 Usability…………………..………………………………………………..…………..17
4.4.6 System Availability…………………..……………………….………………………..17
4.4.7 Contingency and Disaster Recovery…………………….……………………………..17
4.4.8 Information Security…………………..………………………………………………..17
4.4.9 Help and Training…………………..…………………………………………………..17
4.5 Regulatory, Audit and Data Retention Requirements………………………………….…18
6 GLOSSARY OF TERMS………………………………………………………………..….………19
1. EXECUTIVE SUMMARY
Handling claims is a key business process—and a significant area of overhead—for any insurance organization.
Recent studies have shown that the processing cost of a claim that adjudicates on the first pass (60–70 percent
of claims) is pennies compared to dollars for a manually processed claim resulting from an exception or "pended"
from the core system (30–40 percent of claims).
When you consider that claims processing applications involve significant volumes and amounts of paper-based
documents, it is clear insurance payers could save significant sums by addressing the issues inherent in manual
claims processing.
2. OVERVIEW
2.1 The Business Problem/Need
The current Claims processing is processed manually and has the following Issues:
a) High errors and exceptions Manual data entry in line-of-business or accounting systems can increase
the number of "pended" claims and raise the time and cost of claims processing.
b) Inefficient workload distribution The inability to distribute work evenly across multiple claims processors,
adjudicators and managers makes it difficult to allocate staff efficiently.
c) Slow turnaround time Manually routing, processing, searching and retrieving physical documents increases
the turnaround time, which impacts customer service and can result in penalties for late claims in some cases.
d) High claims processing costs The supplies and labor associated with paper-based manual document routing,
shipping and storage raise overhead costs, which can lead to higher premiums and lower revenues.
e) Inconsistency Documents received at multiple input points may be routed or classified differently, resulting in
discrepancies and inefficiency.
f) High risk Paper documents are subject to loss or damage and expose organizations to legal and financial risks.
These challenges make claims processing an ideal candidate for automation through workflow, document
management and document delivery technologies. Such technologies accelerate claims processing from beginning
to end and reduce errors—resulting in faster close-out of claims, improved operational efficiency and lower costs.