BOCA Prime is a proposed model for organizing dental coverage differently. It brings together advances in software, AI, privacy-preserving technologies, digital identity, cryptography, and programmable systems as parts of one coordinated system—using each where it can perform a necessary function more effectively.
Prime is being designed to reduce administrative overhead, make important rules clearer, automate more routine coordination, strengthen accountability, and create a stronger path for available resources to reach care.
It starts from the responsibilities any coverage system still has to perform—participation, eligibility, benefits, verification, financial responsibility, reserves, payment, and oversight—and asks how those responsibilities can be coordinated more efficiently, transparently, and adaptably.
01 / WHAT PRIME IS TRYING TO IMPROVE
Coverage should work harder for the people relying on it.
BOCA Prime focuses on several related pressures that affect how much practical value dental coverage can deliver to patients and practices.
Coverage value can erode over time
Dental care costs, wages, and practice expenses change. When benefit structures and annual limits fail to keep pace, the same nominal benefit can purchase less care over time.
Prime explores a model in which care costs, contributions, utilization, reserves, financial risk, and system performance can inform how coverage evolves rather than allowing its practical value to stagnate simply because the underlying benefit structure remains unchanged.
Important answers can arrive too late
Patients make treatment decisions at a specific moment. They want to understand what their coverage will support, what they may owe, and whether they can proceed with care.
Today, reaching those answers can involve benefit verification, manual interpretation, preauthorization, estimates, follow-up, and repeated handoffs—steps that consume staff time and can delay a patient’s ability to move forward with treatment.
Prime is being designed to establish more of that information earlier and more reliably, while it can still inform the decision.
Administration consumes real practice capacity
Dental practices spend staff time verifying benefits, interpreting plan rules, submitting and resubmitting information, responding to requests, following payments, reconciling estimates, and explaining administrative uncertainty to patients.
Some of that work serves a necessary purpose.
Prime asks how much of it can be reduced, automated, or handled more consistently by the system itself without weakening clinical judgment, appropriate review, or accountability.
Every coverage system has finite resources
Resources used to administer coverage are resources that cannot also support benefits, reserves, provider payment, technology, oversight, or care.
Greater efficiency does not eliminate those competing responsibilities. It can create more room to meet them.
The larger objective is to make better use of the resources people already contribute for the purposes the coverage system is meant to serve.
02 / THE DESIGN PREMISE
Coverage has necessary jobs. The way those jobs are performed can be redesigned.
A functioning coverage system has real responsibilities. It has to know who is participating, determine which rules apply, establish what support is available, verify required information, protect shared resources, maintain financial integrity, coordinate payment, and provide a way to handle uncertainty and exceptions.
Those responsibilities remain necessary even when the system around them changes.
Prime begins by separating each responsibility from the process currently used to perform it. It then asks how advancing technical capabilities can support clearer rules, more reliable information, greater automation and verification, and stronger financial controls—and where human judgment, review, or other safeguards still need to remain.
Rather than treating any one technology as the answer, Prime explores how those capabilities can work together around the actual responsibilities of coverage.
The design question is simple: if each necessary function were being organized deliberately today, how should it work?
NECESSARY FUNCTIONS OF COVERAGE
Participation & Eligibility
Who is participating, and which rules apply?
Benefits & Financial Support
What support is available under those rules?
Verification & Integrity
What information must be established and trusted?
Resources & Reserves
How are finite resources protected and obligations supported?
Payment & Execution
Once an obligation is established, what happens next?
Review & Oversight
What requires additional judgment, intervention, or accountability?
PRIME'S DESIGN QUESTION
How can each responsibility be performed more clearly, efficiently, reliably, and accountably?
03 / THE INTENDED COVERAGE EXPERIENCE
Coverage should be understandable while it can still inform the decision.
Imagine a patient sitting with their dentist after an examination, discussing recommended treatment.
This is the moment when coverage information is most useful. The patient is trying to understand what care is being recommended, what it will cost, what support their coverage may provide, and what responsibility will remain with them before deciding how to proceed.
The questions are practical:
What treatment is being recommended?
What does it cost?
Will my coverage apply?
What will it contribute?
What responsibility will remain with me?
Today, reaching a dependable answer can require verification, interpretation, preauthorization, estimates, follow-up, and repeated communication. That work takes time, and uncertainty can remain while a patient is trying to make a treatment decision.
Prime is being designed around a different experience.
Once the practice submits the recommended treatment and the information required under Prime’s rules, the system is intended to resolve more routine coverage questions quickly and communicate the result directly to both the patient and the practice.
The patient should be able to understand what Prime is expected to contribute and what responsibility may remain while that information can still help determine what happens next.
If a case requires additional review, the system should make that clear as well rather than leaving the patient or practice to reconstruct the status through repeated follow-up.
The responsibilities remain distinct:
The dentist recommends the care they believe is clinically appropriate.
The practice establishes its fee.
BOCA Prime applies its established rules and determines the financial support available.
The patient sees the expected Prime contribution and any remaining responsibility, then decides whether to proceed.
The intended result is a clearer relationship among clinical judgment, coverage, and patient choice—one in which financial information can be established and communicated more efficiently, so it is more useful when someone is deciding what to do.
THE DECISION, WITH EACH ROLE CLEAR
DENTIST / PRACTICE
Recommends appropriate care
Establishes the practice fee
BOCA PRIME
Applies established coverage rules
Determines available financial support
PATIENT
Sees expected Prime contribution
Sees remaining responsibility
Decides whether to proceed
Clinical judgment · Coverage support · Patient choice
04 / THE OPERATING ARCHITECTURE
Use automation for routine coordination. Preserve judgment where judgment is required.
For Prime to provide a meaningful coverage determination earlier in the treatment process, the system has to do more than calculate a benefit. It has to establish enough reliable information to know who is participating, what is being requested, whether the required evidence supports it, which rules apply, and what financial support those rules provide.
Today, a pre-treatment estimate or authorization may help a patient and practice understand what coverage is expected to provide, but it does not always guarantee the final payment. Once treatment is completed and the claim is submitted, coverage can still be interpreted or adjudicated differently.
Prime is intended to make the earlier determination more dependable. If Prime tells the patient and practice what it will contribute, and the treatment and relevant conditions do not change, the system should pay what it already determined rather than reopening the coverage question through another administrative process.
The opportunity is to automate much more of that routine work when the required information can be established with sufficient confidence. Cases involving incomplete or conflicting information, unusual circumstances, exceptions, appeals, or other uncertainty should move to additional review rather than being forced through an automated pathway.
Making that possible requires four complementary functions working together.
Prime Core
What do the coverage and financial rules require?
Prime Core coordinates the coverage, participation, and financial logic of the system. It applies the rules governing eligibility, benefits, limits, available resources, contribution levels, and other conditions that determine what financial support Prime provides.
To make that determination reliably, Prime Core depends on trustworthy information about who is participating and whether the requirements for coverage have been satisfied.
Rootprint™
Who is participating, and what relevant context can be trusted?
Rootprint is Cadmus Labs’ framework for identity, continuity, permissions, and trusted participation history.
Within Prime, Rootprint’s role is to help establish the relevant patient and provider relationships, confirm participation and permissions, and keep useful facts and history available in a form that remains verifiable over time. Where another part of the system only needs to verify that a requirement has been satisfied, Rootprint is intended to make that possible without unnecessarily exposing the sensitive information behind it.
It is also intended to give the individual greater control over what information is shared, with whom, and for what purpose—without requiring every interaction to begin again from zero.
DentAI
Does the submitted evidence satisfy the coverage requirements?
DentAI is the proposed verification and intelligence layer supporting evidence evaluation and system integrity.
It would evaluate submitted clinical information against defined coverage requirements, identify missing or inconsistent evidence, recognize unusual patterns and potential fraud, waste, or abuse, and help distinguish routine cases from those requiring additional scrutiny.
DentAI would support coverage verification and system integrity. Diagnosis and treatment recommendations remain the responsibility of the dentist.
Human Review
What cannot be resolved reliably by the system?
Not every case belongs in an automated process.
Incomplete or conflicting evidence, unusual circumstances, exceptions, appeals, suspected misuse, ambiguous rules, or other uncertainty may require human judgment.
Those cases should move into an accountable review process capable of investigating the issue, requesting additional information when necessary, reaching a determination, and correcting errors.
Automation only works responsibly when the system also recognizes where automation should stop.
PRIME IN MOTION
1 / CARE RECOMMENDEDDental practice
Treatment recommendation Practice-established fee
2 / REQUIRED INFORMATION SUBMITTED
Recommended treatment Required clinical evidence Relevant participation information
Coverage rules · financial rules · available support
4 / CAN THE CASE BE RESOLVED RELIABLY?
ROUTINE PATH
Prime contribution established Remaining patient responsibility established Determination communicated to patient + practice
REVIEW PATH
Additional information and/or human review Determination reached Result communicated to patient + practice
5 / PATIENT DECISION
Patient decides whether to proceed.
6 / CARE + PAYMENT
If the treatment and relevant conditions remain consistent with the determination:
Approved care → Prime payment → benefits and relevant history updated
05 / THE COVERAGE & FINANCIAL MODEL
Make support predictable while keeping the model financially sustainable.
A workable coverage model has to distribute finite resources across several legitimate responsibilities at the same time.
Patients need financial support that is meaningful enough to matter and clear enough to understand when treatment decisions are being made. Practices need a workable relationship between what they charge and what coverage contributes. And the system itself has to meet its coverage obligations, maintain appropriate reserves, account for changing utilization and costs, and support the infrastructure required to operate.
Prime’s current financial design explores a set of rules intended to make those relationships clearer: how support changes as eligible care accumulates during the coverage year, what amount Prime uses when calculating that support, and where its financial obligations are bounded.
The structure can be defined before every numerical parameter is settled. Prime already has working approaches for many of those parameters, but exact rates, thresholds, limits, contributions, and reserve requirements require further economic and actuarial validation.
How Prime applies support over the coverage year
Traditional dental plans often cover different percentages depending on the type of procedure being performed.
Prime’s leading model takes a different approach. The percentage Prime contributes would depend more on how much eligible dental care the participant has already used during that coverage year.
Prime would cover a higher percentage of the first portion of eligible dental costs during the coverage year, leaving a smaller share to the patient.
Once the participant has used that first portion, Prime would cover a lower percentage of the next portion, and the patient’s share would increase.
If spending continues, later portions would receive progressively less Prime support and a greater share would remain with the patient, up to the plan’s coverage-year limit.
This design makes coverage easier to understand and predict. Before treatment, the patient and practice should be able to see what Prime is expected to contribute, what responsibility remains with the patient, and how much support remains available for the rest of the coverage year.
Prime already has working assumptions for the percentages, thresholds, limits, and contribution levels. Those exact numbers require further economic and actuarial validation before becoming final plan terms.
FIRST PORTION OF ELIGIBLE COSTS
Prime contributes the highest percentage.
Patient responsibility is lowest.
NEXT PORTION OF ELIGIBLE COSTS
Prime contributes a lower percentage.
Patient responsibility increases.
LATER PORTIONS OF ELIGIBLE COSTS
Prime contributes progressively lower percentages.
Patient responsibility increases further, up to the coverage-year limit.
How treatment fees enter the model
Prime does not set a mandatory fee schedule for participating practices. The practice submits the fee it actually charges for the recommended treatment.
That keeps the treatment price separate from the coverage decision and allows fees to reflect real differences among practices and local markets.
But Prime also needs a limit on its own financial exposure.
For each covered procedure, Prime would use regional pricing information to establish a maximum amount that can be used when calculating its contribution.
If the practice fee is at or below that regional limit, Prime would apply the participant’s current support percentage to the actual fee.
If the practice fee is above the regional limit, Prime would calculate its contribution using the regional limit instead.
The practice may still charge its submitted fee. The patient would be able to see the practice fee, Prime’s expected contribution, and the remaining responsibility before deciding whether to proceed.
The regional limit is one of several mechanisms intended to keep pricing and system exposure in balance. Additional safeguards—including market transparency, verified patient feedback, system monitoring, and other forms of oversight—are explored in Prime Economics & Safeguards.
PRACTICE SUBMITS ITS FEE
IS THE FEE WITHIN PRIME’S REGIONAL LIMIT?
YES
Prime applies the current support percentage to the actual practice fee.
ABOVE THE LIMIT
Prime applies the current support percentage to the regional limit.
PATIENT + PRACTICE SEE
Practice fee · Prime contribution · Remaining patient responsibility
Prime still has to work within finite resources
The resources available to Prime have more than one job. The system has to support care, maintain appropriate reserves, and fund the infrastructure and oversight required to operate.
COVERAGE
What Prime contributes toward eligible care.
RESERVES
Resources held to support future obligations and changes in utilization.
OPERATIONS
The infrastructure, compliance, security, administration, and human review required to keep the system functioning.
Those responsibilities have to be balanced together. More generous coverage affects the resources available for reserves. Higher utilization changes what the system may need to support. Operating costs matter as well.
Efficiency can create more room inside that equation. It cannot eliminate the equation.
Prime may also use outside capital and future treasury strategies to strengthen reserves and support growth. Those mechanisms are part of the broader economic architecture discussed in greater detail in Prime Economics & Safeguards.
The model should be able to evolve with real-world evidence
Prime’s financial parameters should not remain fixed if actual experience shows that they need to change.
Over time, factors such as care costs, utilization, participant contributions, reserve performance, regional pricing, and overall system performance may justify adjustments to support percentages, limits, regional thresholds, reserve targets, or other financial rules.
Those changes would still have to preserve the financial health of the system. More generous support, for example, has to be considered alongside contributions, utilization, reserves, and other obligations.
Prime already has working approaches for these parameters, but the exact rates, thresholds, limits, contributions, and reserve requirements require further economic and actuarial validation before becoming final plan terms.
Making Prime work requires more than coverage rules.
Prime is focused on coverage: establishing what support is available, applying the rules consistently, and coordinating that support with patients and practices.
But making that system work creates other requirements.
Participants and permissions have to remain trustworthy. Clinical evidence has to be evaluated. Money has to move. Patients may still face affordability gaps after coverage is applied. Important system rules may need to change over time.
Those requirements are what give rise to the broader architecture around Prime. Each component addresses a problem the coverage model cannot solve on its own. Together, they create capabilities for identity, verification, affordability, financial coordination, and system stewardship that can support Prime, become useful across the wider BOCA ecosystem, and—if they prove themselves there—potentially have applications beyond BOCA as well.
That broader architecture—and its future potential—takes shape through several connected systems:
A persistent connection between a real person and their digital participation.
Rootprint is Cadmus Labs’ framework for carrying identity, permissions, and trusted history forward over time—so trust does not have to be rebuilt from scratch at every interaction.
Inside BOCA, that continuity could support verified patient feedback, provider reputation, governance, future financing, and other functions where knowing who participated and preserving that history matters.
Rootprint gives digital identity a memory—allowing trust, reputation, and accountability to build over time instead of disappearing between interactions.
Verification, pattern recognition, and system intelligence.
Within Prime, DentAI is intended to help evaluate submitted evidence, identify missing or inconsistent information, and recognize activity that may require additional review.
As the system develops, that same ability to understand patterns across larger amounts of information could also support fraud, waste, and abuse detection, provider and utilization analysis, system monitoring, and other forms of dental intelligence.
Diagnosis and treatment recommendations remain the responsibility of the dentist.
Contributions have to be collected. Providers have to be paid. Reserves and treasury resources have to be managed. Financial activity has to remain secure, accountable, and compatible with the legal and regulatory structure in which Prime operates.
Prime needs financial infrastructure that can work across today’s established payment systems while remaining ready for increasingly programmable forms of money, settlement, and asset ownership.
That could eventually include stablecoin settlement, tokenized assets, programmable payments, automated treasury functions, and other financial rails as those systems mature and become appropriate for use.
The aim is a financial layer that can support reliable payment and reserve management today while creating a path toward faster settlement, greater transparency, programmable execution, and participation in a financial system where more real-world value may move through digital and tokenized infrastructure.
Those capabilities also support a larger principle behind BOCA: Cadmus should earn its place by helping create and coordinate value, with increasingly transparent rules and a meaningful role for the people the system exists to serve.
Coverage can reduce cost. It cannot always make care affordable.
Even meaningful coverage may leave a patient with a remaining balance they cannot comfortably manage.
Rootline is the proposed financing layer for that gap.
Because Prime already establishes identity, provider relationships, treatment context, coverage activity, and financial history, Rootline could evaluate a financing request with far more context than a single application or credit score provides. Traditional underwriting could still be used where appropriate, but it would no longer have to be the only source of information.
Rootline could turn the history already built inside BOCA into useful underwriting context—creating the possibility of more informed, efficient financing tied to real care, real providers, and persistent identity.
How important rules change—and who has authority to change them.
A system intended to operate over many years cannot assume that every rule chosen at the beginning will remain appropriate forever.
Costs change. Utilization changes. Technology changes. Regulation changes. Evidence may show that an assumption was wrong or that a rule is being exploited.
Governance is the part of the architecture concerned with how those decisions are made, what authority different participants have, what limits apply, and how important changes can become more transparent and accountable over time.
Early operation would remain primarily under Cadmus, which would be responsible for running the system and meeting its legal and operational obligations. If Prime earns the evidence and maturity to support broader governance, certain system-level decisions could gradually include verified patients and participating dental practices under clearly defined rules for who can participate, what decisions they can influence, and what authority remains with Cadmus or other responsible parties.
As software systems become more capable, patients, practices, and the system itself may increasingly use software to perform routine actions on their behalf.
That creates a different kind of question:
What is an agent allowed to do, who authorized it, what information may it access, and who remains accountable for its actions?
Cadmus is exploring how identity, permissions, rules, and verifiable authorization could allow authorized agents to participate in parts of the system—helping schedule appointments, submit routine information, make authorized payments, or follow up on coverage status—without giving them unrestricted authority.
This remains a longer-horizon capability, but the underlying requirement is already important: automation should act within permissions that can be established, limited, and verified.
Technology follows purpose
Prime does not begin by asking where AI, blockchain, cryptography, decentralization, or these specialized systems just outlined can be inserted.
It begins with what the system needs to accomplish.
Some functions may be best handled with conventional software. AI may be useful where large amounts of evidence or behavior need to be evaluated. Cryptography may help where something needs to be verified without unnecessarily exposing the information behind it. Programmable infrastructure may help where established rules can move more directly toward execution. Distributed systems may become useful where independent verification, shared records, or shared control provide a real advantage.
And some responsibilities will continue to belong with people and institutions because judgment, accountability, law, or regulation require them.
Prime is therefore expected to be a hybrid architecture—using each approach where it provides a useful property rather than treating any one technology as the answer.
BOCA Direct can give Cadmus operating experience, real-world evidence, and relationships with participating practices before Prime is introduced.
That can make Prime better informed. It cannot validate the coverage model itself.
A membership platform cannot establish whether Prime’s pooled economics will work, whether reserves will be adequate, how a coverage population will behave, what regulatory structure will be required, or whether the proposed architecture will perform as intended.
Direct can inform Prime. Direct cannot prove Prime.
The questions that remain are the ones Prime itself must answer through legal, actuarial, economic, technical, and real-world validation.
08 / THE BURDEN OF PROOF
What has to be demonstrated before Prime earns implementation?
Prime should advance only where the evidence supports it.
The proposed architecture creates hypotheses about coverage, economics, technology, participation, and governance. Before those ideas become an operating system—or before an operating system expands—they have to survive scrutiny in the areas that determine whether Prime can work responsibly in the real world.
Legal & Regulatory
Can Prime operate within a lawful and workable regulatory structure in each market where it is introduced?
Actuarial
Can contributions, utilization, benefits, reserves, limits, and risk remain financially sustainable under realistic conditions?
Economic
Can the model create enough value for patients, practices, and the system to justify its costs and obligations?
Market & Participation
Will patients and dental practices actually choose to participate—and remain engaged once the model is operating?
Clinical
Can coverage rules, verification, review, and safeguards support legitimate care without improperly replacing professional clinical judgment?
Technical
Can the architecture perform its required functions reliably, including identity, verification, rules, payments, exceptions, and human review?
Privacy & Security
Can sensitive information remain appropriately protected while the system still establishes and verifies the facts it needs?
Governance
Can important decisions, authority, rule changes, and participant influence be structured with clear responsibility and meaningful safeguards?
Operational & Real-World
Does the system continue to work when it encounters actual practices, patients, exceptions, edge cases, changing conditions, and sustained use?
These are not boxes to check once.
Evidence may support one part of the model while challenging another. The purpose of validation is to determine what deserves to move forward, what needs to change, and what should be abandoned.
A compelling idea earns investigation. Evidence earns implementation.
The ambition is intentional. So is the burden of proof.