Release notes
13 October 2026
The day charging gained a chokepoint. The authority to bill a line moved from checks scattered across several paths to one boundary every line has to pass.
Written for: Evaluators tracking what the platform does today · Existing customers · Anyone reviewing what changed and when
One boundary for every billable line
Newer: 14 October 2026 · Older: 12 October 2026
Charging
- Every billable line now passes one authorization boundary before it can become a charge. The checks existed on several paths before, which meant a line arriving by a path that lacked them could be written without being authorized.
3cc0f77c - That boundary is now the single place the authority to bill is decided, so the answer to whether a line may be charged no longer depends on which screen asked.
3cc0f77c
Protected information
- Eligibility check results are classified as protected health information, and the classification is derived from the database schema rather than maintained by hand - so a field added to that response cannot quietly fall outside it.
a60aecda - The authorization bar on a patient's record is read from the same alert engine that raises the alerts, instead of being computed separately for display and drifting from it.
a60aecda - A simulated-eligibility action could be reached in a state it did not expect; gated.
a60aecda
Verification
- 9,771 tests passed and none failed.
a60aecda - Both releases were installed as blue/green swaps with zero seconds of interruption.
3cc0f77c