Re: Interface

[Richard Tomancikl <Richard_Tomancik@TIGINSURANCE.COM>]

I just completed (last week) an interface to CIGNA for dental and medical.
I can feel your pain!

(Our platform is: PeopleSoft 7.0x HRMS / Oracle 7.3.4.1/ Sun 3000 Server
with Solaris / NT Workstation)

I assume that you are running your interface from the Snapshot tables
(ps_ben_per/plan_data), that are loaded on an as-needed basis by
ben100.sqr.

As delivered, ben100.sqr does not select terminated employees to load into
the snapshot tables.  We had to remove the 'where' clause where only active
employees are selected.  Then add 'empl_status' to the snap-shot tables and
update programs. Then use logic to check empl_status and coverage_elect and
determine whether to use termination_dt from ps_employment or the
coverage_begin_dt (not 'end_dt', it is never populated) for the benefit
cancellation date.

The tricky thing here is these programs (and most benefit interfaces) are
designed to be a 'full-file format' meaning that we send to CIGNA everyone
that is eligible every time, and they figure out the changes by comparing
what we send from month to month.  Most folks default the benefit
cancellation date to the end of the month that the employee drops off the
file.

In the course of completing this interface it became obvious that the
classic full file format is much easier, instead of figuring about who
terminated and when (since they may terminate either employment or benefits
or both, but not always in the right order).  It was also real fun to
program for sending cancellation records for dependents that drop off.
That's like asking for 'everyone who is not here, please raise your hand'.

But as is with software, 'With enough time and money, anything is
possible', and it is done and working.

Any other questions let me know.  RT