oracle insurance revenue management and billing ... nmon the awr (automated workload repository) ...

Download Oracle Insurance Revenue Management and Billing  ... NMON  The AWR (Automated Workload Repository)  Active Session History (ASH) statistics Figure 2: Oracle Revenue Management and Billing Batch Topology

Post on 08-May-2018

217 views

Category:

Documents

0 download

Embed Size (px)

TRANSCRIPT

  • Oracle Insurance Revenue Management and Billing V2.4.0.1.0 Performance and Scalability Test on Exalogic X3-2 and Exadata X3-2

    Healthcare Industry Benchmark

    O R A C L E W H I T E P A P E R | F E B R U A R Y 2 0 1 6

  • ORACLE INSURANCE REVENUE MANAGEMENT AND BILLING V2.4.0.1.0 PERFORMANCE & SCALABILITY TEST ON EXALOGIC X3-2 AND EXADATA X3-2

    Table of Contents

    Executive Summary 1

    Introduction 2

    Oracle Insurance Revenue Management and Billing Overview 2

    Test Scenarios 2

    Small Business Scenario 2

    Exchange Business Scenario 2

    Process Flow 3

    Methodology 4

    Topology and Configuration 4

    Batch Server Configuration 4

    Database Server Configuration 5

    Measuring Tools 5

    Small Business Benchmarking 6

    Batch Processing 6

    Results 7

    Exchange Business Benchmarking 11

    Batch Processing 11

    Results 12

    Conclusions 15

  • 1 | ORACLE INSURANCE REVENUE MANAGEMENT AND BILLING PERFORMANCE AND SCALABILITY TEST

    Executive Summary

    Objective

    This white paper describes the performance and scalability capabilities of Oracle Insurance Revenue Management

    and Billing Version 2.4 on Exadata X3-2 and Exalogic X3-2. This benchmarking exercise was undertaken to

    determine whether health payers using Oracle Insurance Revenue Management and Billing can generate large

    volumes of premium bills and billing transactions for two scenarios: small business billing and exchange business

    (individual policy) billing.

    Scope

    Three process flows pending bill generation, bill segment generation and bill completion were tested under the

    small business and exchange business scenarios. Under the small business scenario, each billing account was

    associated with multiple plans (contracts or products) and multiple members. Under the exchange business

    scenario, each billing account was associated with multiple plans, but only one subscriber.

    The performance and scalability tests were executed on the Oracle Database Machine, Exadata X3-2 (half rack)

    and Exalogic X3-2 (half rack).

    Findings

    Oracle Insurance Revenue Management and Billing can successfully generate the volumes of bills and billable

    charges for each scenario tested. The following is a snapshot of the billing test runs.

    Test Description TPS Comments

    Exchange Business -14 million bills created

    for 28 million billable charges

    1300 Half rack of Exadata and 13 nodes of Exalogic have been used

    Small Business 70 K bills created for 11

    million billable charges

    1900 Half rack of Exadata and 10 nodes of Exalogic have been used

    The application scales almost linearly (as anticipated), when additional hardware was added.

    The results of this benchmarking study illustrates that Oracle Insurance Revenue Management and Billing can

    process premium bills for 56 million individual policies almost three times the total number of individual

    policies in the US in a single day.

  • 2 | ORACLE INSURANCE REVENUE MANAGEMENT AND BILLING PERFORMANCE AND SCALABILITY TEST

    Introduction

    This white paper describes the performance and scalability capabilities of Oracle Insurance Revenue

    Management and Billing Version 2.4 on Exadata X3-2 and Exalogic X3-2. This benchmark was

    designed to demonstrate that healthcare payers can successfully generate large volumes of bills and

    billing transactions for two distinct premium billing scenarios: small business and exchange business.

    The test also illustrates that the results scaled as expected when additional hardware was added.

    Please note that the benchmark data in this white paper is intended for general information purposes

    and not as a substitute for implementation-specific sizing or benchmarks

    Oracle Insurance Revenue Management and Billing Overview

    Oracle Insurance Revenue Management and Billing (ORMB) is a rules-based system for billing, payment, and

    collections. Configurable business rules enable healthcare payers to change billing processes quickly and as often

    as needed. Oracle Insurance Revenue Management and Billing supports group billing, list bill processing and

    individual billing, and scales to support high-volume billing environments.

    Test Scenarios

    As part of the benchmarking exercise, the following health care scenarios were tested:

    Small Business Scenario

    Under the small business scenario, a billing account is associated with multiple plans (contracts or products) and

    multiple members (subscribers and dependents). In this scenario, 34 million billable charges were created and

    applied to 200,000 accounts as part of the data setup. The entity setup uses the following configuration:

    Contracts: each account has three contracts per subscriber

    Dependents: each subscriber has three dependents

    Subscribers: the number of subscribers varies from 10 to 100 per billing account

    Discounts: there is an additional segment for policy discounts on each billing account. A discount is calculated

    based on the number of active members for the related policy.

    Exchange Business Scenario

    Under the exchange business scenario, a billing account is associated with multiple plans, but only one subscriber.

    In this scenario, 140 million billable charges were created and applied to 70 million accounts as part of the data

    setup. The entity setup uses the following configuration:

    Contracts: each account has two contracts per subscriber

    Dependents: each subscriber has three dependents

  • 3 | ORACLE INSURANCE REVENUE MANAGEMENT AND BILLING PERFORMANCE AND SCALABILITY TEST

    Below is the representation of the basic insurance data/entity setup:

    Figure 1: Oracle Revenue Management and Billing Insurance Data Entity Relationships

    Process Flow

    The following Oracle Insurance Revenue Management and Billing process flows were tested as part of the small

    business and exchange business scenarios.

    Pending Bill Generation: generate bills in pending status for accounts that meet specific criteria, based on batch

    business date, bill cycle code and division.

    Bill Segment Generation: generate bill segments. Based on the batch business date, the system identifies the

    billable charges for which bill segments are to be generated. The process also freezes the generated bill

    segments.

    Bill Completion: generate post processing bill segments and marks the bills as complete. The setup includes

    posting financial entries during bill completion process.

  • 4 | ORACLE INSURANCE REVENUE MANAGEMENT AND BILLING PERFORMANCE AND SCALABILITY TEST

    Methodology

    The performance and scalability test described in this white paper comprised of system configuration for processing

    data, loading the recurring billable charges for small business and exchange business scenarios, and processing the

    billable charges to generate bills. For benchmarking purposes, data was built up to ensure none of the billable

    charges went into an error state to test the peak loads conditions. A total of 70 million accounts were populated, with

    two billable charges for exchange business; and 200,000 accounts were populated for small business with billable

    charges varying from 10 to 100. Please refer to the entity set up section for details on data setup and configuration.

    In this benchmarking exercise,

    34 million billable charges, equally distributed across 3 billing cycles, were processed for the small business

    scenario.

    140 million billable charges, equally distributed equally across 5 billing cycles, were processed for the exchange

    business scenario.

    Each billable charge was processed through a complex rate schedule, which has multiple rate components and SQ

    rules to calculate the premiums. Billing modules also invoked pricing crawl algorithm to derive discount rates for

    each account to calculate policy discounts for small business accounts.

    In Oracle Insurance Revenue Management and Billing, bills can be generated in two ways:

    Starting with the billing account and adding bill segments to the account. This is implemented in ORMB as

    single job.

    Generating a blank bill and adding the bill segments to the bill. This is implemented with three jobs pending

    bill generation, bill segment generation and bill completion as described in the Process Flow section of this white

    paper.

    In this benchmarking exercise, the three jobs process was executed to process the recurring billable charges and

    generate the bills. The bill segment generation job equally distributes the billable charges among the threads

    irrespective of how billable charges are distributed across accounts and thus improves overall performance and

    hardware utilization.

    Topology and Configuration

    This section describes the hardware topology of the systems used for the stress test, as well as the hardware and

    software combinations used.

    Batch Server Configuration

    Hardware specs (Compute Node):

    2 x Eight-Core Intel Xeon E5-2690 Processors (2.9 GHz)

    256GB Memory

    Oracle Enterprise Linux 6.5 - 64 bit Kernel Version 2.6.39-400.215.10.el6uek

    Software:

    Java 1.6.0_31

    Weblogic 10.3.6 (security update 10.3.6.0.8)

    OracleClient_11.2.0.1.0

    MicroFocusServer_WP7_Linux

    hibernate 4.1.0

Recommended

View more >