Atlas project production

CYBHI / Leader Services Billing Integration

Integrates student insurance billing information with Leader Services to support SPED billing workflows.

Internal-only entry. Do not publish externally without review.

Type: System
Lifecycle: Active
Last touched: 2026-03-24
Visibility: Internal

Purpose

Integrates student insurance billing information with Leader Services to support SPED billing workflows.

Current state

Integr8r reveals a concrete technical implementation path behind the broader CYBHI billing and service workflow. The enabled `CYBHI` job generates six structured files: Student, Roster, Provider, Location, Insurances, and Guardians. Those files are uploaded through the runner's secure transfer path to a vendor-managed destination labeled in config as `CYBHI CA STaR`. This strongly suggests the billing or compliance workflow is a coordinated roster-and-insurance exchange rather than a single loose export. The code does not by itself prove whether "Leader Services" and the CA STaR destination are the same downstream service or adjacent steps in the workflow, so that naming relationship should remain an explicit validation item. Current registry state: Production / Active / High. Student-services billing integration. Trigger / frequency: recurring secure export [validate exact scheduler and downstream ingest cadence]..

Next step

exact downstream service identity, hosting model, and audit expectations still need documentation. Yes - document whether the current Integr8r `CYBHI` export is the same operational path referred to in weekly-report notes as the Leader Services billing integration, or whether it is only one component of that broader workflow. The repo now clearly shows a structured multi-file production exchange.

Interfaces

Inputs

student insurance and program-related data in Aeries plus related guardian, provider, and location context.

Outputs

CYBHI or CA STaR downstream workflow and possibly related billing-service processing.

Reality to Action trace

Reality Ingestion

Contributes in this stage.

Canonical Storage

Not in scope.

Automation Engines

Not in scope.

Human Interfaces

Not in scope.

Operational Adoption

Not in scope.

Core workflow

TBD. Document the 5-10 steps that define the core workflow.

Data integrity and contracts

Source of truth rules

student insurance and program-related data in Aeries plus related guardian, provider, and location context. remain the authoritative upstream inputs for this workflow.
CYBHI or CA STaR downstream workflow and possibly related billing-service processing. should be treated as downstream copies, recipients, or operational consumers rather than the authoring system.

Safe handling

Protect credentials, generated files, logs, and any transient export artifacts.
Treat student identifiers, rosters, and related records as FERPA-restricted data.
Apply district retention and approval controls to billing, archive, or finance-adjacent data in scope.

Operational notes

Reliability posture

Integr8r runtime and file-generation evidence exist, but formal downstream audit controls are not yet documented here. Failure impact: billing delays, data mismatch, and manual reconciliation burden. Manual fallback: manual export or manual billing-data updates..

Observability

Integr8r runtime and file-generation evidence exist, but formal downstream audit controls are not yet documented here.
Failure impact: billing delays, data mismatch, and manual reconciliation burden..
Manual fallback: manual export or manual billing-data updates..

Security and privacy

secure vendor file transfer and district-admin controls. Classification: restricted student service and billing-support data. sensitive student-service data with reimbursement implications.

Dependencies

Upstream

authoritative source data, consent accuracy, secure transfer, and downstream workflow stability.

Downstream

CYBHI or CA STaR downstream workflow and possibly related billing-service processing.

Ownership

Owners

Technology Services with SPED or billing stakeholders, Josh Barton / Technology Services

Users

Technology Services with SPED or billing stakeholders, Special Education and billing stakeholders

CYBHI / Leader Services Billing Integration

Operational Notes

Method: multi-file CSV export plus secure vendor file transfer.
Implementation: Integr8r job key CYBHI with dedicated SQL files under CYBHI/SQL/.
Trigger / frequency: recurring secure export [validate exact scheduler and downstream ingest cadence].
Failure impact / fallback: billing delays, data mismatch, and manual reconciliation burden. Manual fallback: manual export or manual billing-data updates..
Related references: README.md, Config/Config.ps1, CYBHI/SQL/, Weekly Reports/Perpetual Weekly Reports.md, research/weekly-reports-presentation-enrichment-2024-2026.md.

Registry Alignment

Mapped registry entry: INT-025
Registry context: former INT-024 is now treated as component scope within this same billing integration.
Registry clarified: Integr8r reveals a concrete technical implementation path behind the broader CYBHI billing and service workflow.
Validation gaps: exact downstream service identity, hosting model, and audit expectations still need documentation.