Values hide in notes.
Cost shares live in free-text notes, so which value belongs to which benefit becomes interpretation, inherited year after year.
QS Axiom
QUANTUM GEARS · QS AXIOM PREVIEW
Coming Q1 2027 / Built on QS Platform 10
One benefit truth.
Every CMS document.
Consistent by construction.
QS Axiom manages the full life cycle of Medicare Advantage member documents, from benefit design to the EOC, ANOC and Summary of Benefits, from one curated Plan Benefit Package.
The PBP is the benefit commitment a plan files with CMS. QS Axiom makes it the single source every team works from: curated, extended with the business rules the PBP can’t express, and reconciled against every filing.
From the team behind QS Contracts and QS Benefits, in production in regulated healthcare since mid-2023.
ONE CURATED PBPCMS
QSAxiom
Design
Product team’s view
Filing
Regulator’s view
Documents
EOC · ANOC · SB
Every value traced to a PBP field or an owned business rule
PBP extracts
Every filing dropBusiness rules
Owned interpretationsYear over year
Changes as data
Every filing dropBusiness rules
Owned interpretationsYear over year
Changes as data
Update once. Every view follows.
THREE VIEWS.
ONE TRUTH.
ONE TRUTH.
Consistent by construction
One dataset behind every workbook, filing and document
Traceable
Every value answers “where did this come from?”
ANOC-ready
Year-over-year change captured as data, not red font
01
THE PROBLEM
Three sources of truth.
Three versions of every benefit.
The benefit design workbook, the PBP filed in HPMS and the member documents all describe the same benefits, each differently. The workbook is typed by hand, the PBP keeps key values in free-text notes, and the documents inherit whatever gaps are left. Reconciling them is manual work, repeated every cycle.
Entry errors survive.
A hand-typed value disagrees with the filing and ships anyway, because nothing checks the workbook against the PBP.
Sources disagree.
Three sources can say three different things about one benefit, and nothing stops all three from going out.
Rules have no home.
Member-facing facts the PBP can’t express are carried in people’s heads and hand-built side sheets.
THE RESULT
Gaps flow straight into document development.
Complex benefits like dental, hearing and vision take revision after revision to finalize.
02
HOW IT WORKS
Three sources become three views.
Generated from one dataset.
QS Axiom replaces three hand-maintained sources with one curated dataset. Each team keeps the view it works in today, and every view is generated from the same truth.
THE PRODUCT TEAM’S VIEW
The workbook you know.
Generated, not typed.
The familiar benefit design layout, produced from the dataset. Next year’s design changes are captured right here, and the same workbook still goes out by email.
Zero retraining.THE REGULATOR’S VIEW
The PBP, exactly
as filed.
Codes, type IDs, groups and notes from every HPMS extract, captured version by version and reconciled against what the product team intended.
Every filing drop verified.THE MEMBER’S VIEW
Documents in CMS
model language.
EOCs, ANOCs and Summaries of Benefits rendered as members will see them, with every variable mapped back to its PBP data or business rule.
Proofed against the source.THE BUSINESS RULES REGISTER
Every value knows its source.
Every interpretation has an owner.
Decisions the PBP can’t express, like tiered hearing aid pricing or a deductible waived at the PCP, are captured once, owned by a named person and applied everywhere. Update a value once and every view follows.
PBP extracts from every filing drop
QS AxiomCurated PBP dataset + business rules register
03
THE ANNUAL CYCLE
Nothing retyped.
Everything reconciled.
The product team makes the decisions; QS Axiom carries them forward into the filing and the documents, verifying at every update. Revision rounds feed back into design, and next year starts again from verified truth.
- 01
Start from verified truth.
Generate the baseline from the prior year’s final PBP, so design begins from what was actually filed.
- 02
Record design changes.
The product team captures changes as deltas, in the language they work in today.
- 03
Validate the proposed state.
Baseline plus deltas, checked against the PBP schema and reviewed by the product team.
- 04
Enter it in HPMS.
Entered as today. QS Axiom is designed to support API-based submission as CMS makes that path available.
- 05
Reconcile every drop.
Each extract is compared with the proposed state automatically, so entry errors surface immediately, not at document QA.
- 06
Track every version.
Every filing and revision is captured, with each change recorded as typed data, revision to revision and year over year.
- 07
Generate the documents.
The EOC and SB read the verified dataset; the ANOC reads the design deltas directly.
What stays: your product team designs the benefits, owns every ruling and approves every change.
What disappears: the hand-authored workbook, silent entry errors and unreliable ANOC change lists.
04
BEYOND DOCUMENTS
A curated PBP.
Ready for every CMS workflow.
Because the PBP is the plan’s benefit commitment to CMS, a curated and extended version of it is useful far beyond member documents. QS Axiom keeps that dataset current so other teams and solutions can build on it.
Answers that cite their source.
Ask in plain language, such as “Which benefits changed in the latest revision?”, and get an answer that points to the PBP field or business rule behind it.
One truth for member service.
The same verified benefits can inform member service and benefits knowledge, so what representatives say matches what the documents say.
Change and compliance review.
Year-over-year and revision-to-revision changes are typed data, so review teams see exactly what changed, when and on whose ruling.
BUILT ON QS PLATFORM 10
Runs on the same sovereign, governed foundation.
Deploy it inside your boundary, on infrastructure you choose.
THE DETAILS
Questions,
answered.
What QS Axiom does, how it fits your cycle and when it arrives.
Talk to our healthcare teamWhat is QS Axiom?
QS Axiom is a Quantum Gears solution for managing the full life cycle of CMS member documents, including Evidences of Coverage, Annual Notices of Change and Summaries of Benefits, from one curated Plan Benefit Package dataset.
Who is it for?
Medicare Advantage plans whose product, filing and document teams reconcile benefit design, the PBP and member materials by hand each year.
Does it replace our benefit design workbook?
Your team keeps the workbook layout it knows. QS Axiom generates it from the dataset instead of having people maintain it by hand, and it can still be exported and shared as it is today.
Does QS Axiom submit to HPMS?
Not at launch. HPMS entry continues as today, and QS Axiom reconciles every extract against the intended design. It’s designed to support API-based submission as CMS makes that path available.
Who owns interpretations the PBP can’t express?
Your team does. Each business rule is captured once in the register, assigned an owner and applied consistently across every view.
Does it require QS Platform 10?
Yes. QS Axiom runs on QS Platform 10, so it inherits the platform’s deployment options, security and governance.
When is it available?
QS Axiom is planned for Q1 2027. Plans can join the early access program now.
QS AXIOM · COMING Q1 2027
Start next cycle
from one verified truth.
Join the early access program to shape QS Axiom around your plan’s benefit design, filing and document cycle.