inspire 2014 using eforms and iscripts with business applications

eForms and iScripts to Sync Info with Business Applications

Mary GrowneySenior Business Systems Analyst

Physicians Insurance A Mutual Company

[email protected]

Juli DrakeSenior Business Systems Analyst


[email protected]

#inspire14

Who is Physicians Insurance? ?

Physicians Insurance provides insurance coverage to more than 7,000 physician and other health care provider members in WA, ID, OR, and WY, as well as provides risk management consulting, continued medical education, and claims administration services.

#inspire14

Business Applications and Perceptive Content

► Our primary business application is OASIS

► We also use Microsoft Dynamics SL for AP and Claims Payments

► We have integrated Perceptive Content with these applications

Delphi Technology, Inc. OASIS

Client InformationCase FilesPoliciesClaims Payments

Vendor InformationAccounts PayablesClaims Payments

What are iScripts and eForms?

► iScripts are just javascript

► iScripts can be used to: Populate data from a database on eForms, document keys, and custom

properties

Populate data on eForms from document keys and custom properties in Perceptive Content

Validate data against a database or projects in Perceptive Content

Update information from your business application

► All you need is an ODBC connection to query your database from an iScript

► Perceptive Software offers iScripts and eForm Development Training

There Are Many Pros to Using eForms & iScripts

► Underwriting: New Business Application eForm – all in one place!

Ability to consolidate forms because of flexibility of sections based on selections

Frequency Severity Form automatically pulls in Claims information from OASIS to the form – “It was like a miracle!” – Kara, Underwriting Manager

Brings over information that’s really important that you do not want to be wrong

Hassle factor is lower

Better auditing controls of who entered data, reviewed it and approved it

AP Before eForms & iScripts

► Departments and Finance had to do entry multiple times on paper and in the systems

► Several different processes for General AP, Claims Payments, and Stop Loss Payments

► Controller used to have to flip through all cut checks and compare it against paper back up – time consuming

► Finance used to have to walk over to a file cabinet to look up existing invoices

AP After eForms & iScripts

► Cut time by departments doing entry once

► Can modify same eForm and process to use for General AP, Claims Payments, and Stop Loss Payments

► Controller able to review cut Check Numbers against invoices in 1 screen

► “I don’t have to walk to the file cabinet. I just kick back and click.” – Steve, Assistant Controller

Pros to Using eForms & iScripts – Accounts Payable

AP Before eForms & iScripts

► Claims looked up the vendors and claim numbers in OASIS first, then filled out the paperwork

► Auditors did not like that we did not have controls to validate payments for duplicates and approval authority limit checks

► Paperwork could get lost, unsure where it is in the process, filed late, or filed incorrectly

► Entering payments into Dynamics and OASIS was not user friendly

AP After eForms & iScripts

► Now Claims has a vendor lookup and claims lookup on the eForm that bring back the data from our OASIS database

► Moved us to best practices our auditors recommended with built in controls, with validations and approval authority limit checks

► Now we can’t lose the paperwork and know where it always is in the process

► Using the eForm is more user friendly than our systems

Pros to Using eForms & iScripts – Accounts Payable

Claims Before eForms & iScripts► We would have to print new labels for our

paper Case File jackets and manually move Closed Case files to our Closed Case file room or ship them to our Branch Office

► Claims File Coordinator used to have to manually move Case files among Claims Reps desks and on our network drive

Claims After eForms & iScripts

► Automatically update information on our Case files, including Case Status, Case Names, Claim Reps assigned, Claim Types, and Branch Offices


Claims Before eForms & iScripts

► Our Claims File Coordinator would print Face Sheets and bring the paper Case files to each Claims Rep’s desk every morning

Claims After eForms & iScripts

► Automatically bring in Face Sheets from our business application to the Case files in Perceptive Content


Why use iScripts and eForms?

► Example 1: Sync Info with Business Application

► Example 2: Eliminate Need to Re-Key

► Example 3: Automatically Bring in Content from Business Applications

Example 1: Sync Info with Your Business Application

► Claim Reps change the Case Name, re-assign a Claim Rep and/or Branch Office, or updates the Case Status (Open, Closed, Re-open) in OASIS


► How do we do this? Using Custom Properties on documents and projects


► An iScript can automatically update this information on the Case File Project in Perceptive Content and move the Case Files to the new Claim Reps Workflow Queue using custom properties

Example 2A: Eliminate Need to Re-Key Info

► Underwriting Frequency Severity eForm Uses an iScript to automatically pull Claim information from OASIS to the form


► How do we do this? Uses an iScript with a SQL query to automatically pull Claim information from

OASIS to the form


► Use of the AP Invoice eForm Departments can enter invoice data on the eForm and route it to the Finance

AP Clerk for processing

The AP Clerk no longer needs to re-key invoice data to enter it in the business application


► Previous Paper Process with eForm and iScripts:


► New Process with AP eForm & iScripts:


► We batch multiple AP eForms in ImageNow to create a CSV file we import into OASIS

► In a future phase, we plan to automatically populate the OASIS Batch Entry tables from the eForms using iScripts

Example 2B: Eliminate Need to Re-Key Info

► Underwriting RAW eForm When Underwriters bring in a new

application, they use an application plan to link the document to the business application with the appropriate Document Keys, Policy No, Policyholder, and etc.

This information automatically populates on the eForm using an iScript from OASIS

Example 3A: Bring Content In From Business App

► We automatically bring in OASIS ODS Forms for Underwriting to the Policy File using iScripts

Example 3B: Bring Content In From Business App

► Claims Reps select to “print” Face Sheets for Cases in OASIS

► These Face Sheets are a report that has the summary of each Claim


► We use INMAC to bring Claim Face Sheets into Perceptive Content

► When Claim Reps open up their Case File they can see the summary of the Claim and where it’s at so they can take action


► How do we bring the Claims Face Sheets in? Data warehouse runs and picks up Face Sheets to be printed for Claims

Export Crystal reports to a shared file location with a naming convention

Use a Task to run a Python script regularly to import the Face Sheets to ImageNow and run through INMAC conversion

Questions & Comments

► How might you apply iScripts and eForms in your business?

Questions?

Mary GrowneySenior Business Systems Analyst


[email protected]

Juli DrakeSenior Business Systems Analyst


[email protected]

#inspire14

inspire 2014 using eforms and iscripts with business applications

Documents