HOMER System Requirements Documentation
This site is the reverse-engineered requirements documentation for HOMER, a PowerBuilder-based third-party administration (TPA) system for self-funded health benefit plans operated for "SFPI". It was produced by extracting and analyzing the complete application source from its 53 PowerBuilder libraries (3,284 objects, including 546 screens and 2,110 DataWindows) and reconstructing the Oracle data model from the SQL embedded in them.
Its purpose is to serve as the requirements baseline for migrating HOMER to a new platform. The requirements are written technology-agnostically: they describe what the system does, not how it should be rebuilt.
How to read this site
- Overview — what HOMER is, the business it supports, and a domain glossary.
- Architecture (As-Is) — the current technical shape: PowerBuilder client, Oracle backend, PFC framework, configuration, integrations.
- Data Model — the reconstructed database schema by subject area, with inferred relationships and a module↔table CRUD matrix.
- Modules — the core of the site: functional requirements per business domain (claims, enrollment, billing, COBRA, funding, utilization management, …). Each documents the screens, business rules, workflows, and data of one domain, with source references for traceability.
- Cross-Cutting Concerns — security, navigation, EDI/integrations, reports, and batch processing that span modules.
- Migration Considerations — what must carry over, data-migration notes, and the open-questions register for SME review.
- Appendix — the complete object inventory, screen→DataWindow→table traceability matrix, and the Coverage Audit proving what is covered and listing what is missing.
Everything here derives from static analysis of the application binaries (source was
recovered from the PBLs — see _re/ next to the site). Statements are traceable to
source objects, cited like claims/w_claim_editor. Facts that could not be
confirmed from source are flagged as open questions rather than guessed.