A healthcare claims processing platform needed to demonstrate a credible database exit plan ahead of a compliance audit deadline. O2PIM automated schema and procedure conversion, while OptiSol engineers closed out the CONNECT BY hierarchies and Oracle hints the accelerator flagged as needing judgment — clearing the audit milestone without a rewrite from scratch.
An upcoming compliance review required the claims platform's operator to show a credible, funded plan to reduce dependence on proprietary database licensing — with a hard date the organization could not negotiate away.
Claims adjudication and provider-network lookups relied heavily on Oracle CONNECT BY hierarchical queries, ROWNUM-based pagination, and optimizer hints tuned over years — constructs with no direct one-to-one equivalent in PostgreSQL.
Claims intake and adjudication services connected through the Oracle OCI driver with connection pooling tuned specifically to Oracle's session behavior, meaning any migration required re-pointing and re-tuning at the application layer, not just the database.
OptiSol used O2PIM to clear the bulk of the schema and procedure conversion automatically, then dedicated engineering time specifically to the CONNECT BY and hint-dependent logic O2PIM correctly flagged rather than guessed at.
O2PIM inventoried the claims schema end-to-end, isolating every CONNECT BY query, ROWNUM pattern, and optimizer hint into a dedicated gap report so the manual-effort scope was known before conversion began.
Schema DDL, data types, and the majority of PL/SQL packages behind claims intake and eligibility checks were converted automatically to PostgreSQL and PL/pgSQL, reaching 91% automation on this codebase.
Engineers rewrote CONNECT BY hierarchies as PostgreSQL recursive CTEs, replaced ROWNUM pagination patterns, and re-evaluated query plans where Oracle hints had no PostgreSQL equivalent — validating each rewrite against claims adjudication test cases.
Claims intake and adjudication services were re-pointed from the Oracle OCI driver to the PostgreSQL driver, with pgBouncer introduced and tuned to replace Oracle's native session pooling behavior under equivalent load.
A staged cutover moved claims traffic to PostgreSQL ahead of the audit date, followed by a 30-day support window using pg_stat_statements to catch query-plan regressions under full production volume.
"The hierarchical queries were the part everyone assumed would blow the timeline. Having O2PIM isolate exactly which ones needed a human meant we spent our time only where it mattered." — OptiSol Oracle Engineering Lead
Let's Talk
Tell us what you are running today and where you need expert support.
"*" indicates required fields
Global Presence
Five global locations. One connected engineering team.
North America
Chennai · Coimbatore
Client services
Regional operations
Client services
