Start
Name the source event: enrollment task, visit export, missing field, external response, or deposit.
An operating guide for independent practices
Can you accept insurance without hiring a biller?
Possibly, but “no hire” cannot mean “no owner.” A small practice can use software, a service, or a narrow mix of both only when every insurance queue has a named person, a clear stop, proof of what happened, and backup when that person is away.
The ownership contract
Define five facts for every queue.
A tool can sort, check, prepare, and route work. It cannot sign a contract, approve a diagnosis, make a financial decision, or become accountable when the queue stalls.
Decide
Name one role that can act now. “The front desk” or “the vendor” is too broad.
Bound
State when automation or routine work must pause for clinical, financial, or access authority.
Prove
Keep the source, version, action, actor, time, and external response that support the state.
Cover
Set queue limits, absence cover, and an escalation path before work accumulates.
The work inventory
Map the whole operating loop.
Preparing a claim is one part of the job. A no-hire plan fails when it covers the first file but leaves setup, exceptions, or close without an owner.
| Queue | Work that appears | Authority the practice keeps | Proof to require |
|---|---|---|---|
| Readiness | Practice, provider, location, access, route, fee, and policy setup | Contracts, representations, access grants, and launch choice | Configured scope, effective dates, owner, and unresolved gaps |
| Visit intake | Patient, coverage, provider, service, diagnosis, unit, and charge fields | Source correction and privacy rules | Source record, import result, duplicate check, and missing-field list |
| Claim review | Configured edits, documentation checks, charge review, and exceptions | Clinical facts, coding judgment, and charge approval | Exact version, office approval, provider approval when required, and rule results |
| Release | Superbill, portal work, or electronic claim path | Release choice and route authority | Released artifact and a truthful prepared, dry-run, or submitted state |
| External result | Transport response, acknowledgment, reject, denial, or status gap | Correction, appeal, retry, and patient communication choices | Raw response, mapped state, next action, and responsible owner |
| Financial close | Remittance, deposit, patient balance, adjustment, and ledger work | Financial policy and books | Matched evidence, approved adjustment, unresolved variance, and close date |
Choose the staffing model
No hire is a scope choice, not a goal by itself.
Use the model that covers the real queue at a cost and risk the practice can carry.
A no-hire test may fit when
The first lane is small and controlled.
- One location and one configured insurance lane
- A clean export from the practice system
- Named office and clinical approvers with weekly capacity
- A visit cap, queue limit, and end date
- A defined owner for work outside the software's scope
Add a biller or service when
The work needs daily judgment or broad cover.
- Many payers, providers, locations, or service types enter at once
- Enrollment, access, or contract work is not settled
- The practice cannot cover corrections and external follow-up
- Patient balances and financial close lack an owner
- The queue exceeds the pilot cap or stays unresolved
Practical readiness drill
Run the week before you run the lane.
A short tabletop test will show where responsibility is missing before real patient work reaches the queue.
60-minute queue test
Walk five sample visits through the map.
- Include one clean visit, one missing field, one clinical question, one duplicate, and one route question.
- Name the owner and backup at each stop.
- Write the exact evidence that moves the work to the next state.
- Time each person and record what only they can decide.
- Stop if any queue has no owner, limit, or proof.
Weekly capacity test
Price attention, not just software.
- Set the maximum visits and unresolved items the practice can carry.
- Reserve time for office and provider review.
- Set response times for routine and urgent exceptions.
- Decide what pauses new intake when the queue crosses its limit.
- Compare that labor with a service or part-time hire.
No-PHI drill: Use invented or fully de-identified sample visits. Do not place patient names, dates of birth, addresses, member IDs, charts, images, or other PHI in a planning worksheet, calculator, email, or first-fit review.
What the current pilot can prove
Test whether the queue fits the team you have.
Claims Native can test one configured lane from a practice-system export to a reviewed superbill or clearly labeled electronic dry run.
It can measure
The work inside the pilot boundary.
- Required source fields and import failures
- Configured rule stops and exception volume
- Office and provider approval time
- Artifact accuracy against the approved version
- Weekly queue size and unresolved work
It cannot prove
The full no-hire operation.
- Payer access, enrollment, or contract terms
- Payer acceptance, adjudication, or appeal results
- Reimbursement, payment, posting, or patient collection
- Queue load outside the configured lane
- That the practice will never need a biller or service
The pilot can show whether a no-hire model is plausible at a defined volume. It makes no financial or staffing guarantee. Review the scope and proof plan for the 90-day pilot. The framework reflects Ian Harman's work across payer products, provider networks, EDI, claims, and payment operations. Read the control-state model and the TPN Match operating case. This guide is not legal, coding, billing, contracting, staffing, or reimbursement advice.
Common questions
Keep the owner in the answer.
A no-hire plan can reduce fixed payroll. It does not remove accountable work.
Can a small practice accept insurance without hiring a biller?
Possibly. A practice can avoid a new hire only when every insurance queue has a named owner, a trigger, a stop rule, evidence of completion, and backup coverage. Software can move work but cannot hold the practice's clinical or financial authority.
What work still belongs to the practice?
The practice must retain authority over clinical facts, charges, release decisions, access, contracts, patient communication, and financial records, even when software or a service does routine work.
What can the current Claims Native pilot prove?
The pilot can measure source-data quality, review time, exception volume, approval flow, and artifact accuracy for one configured lane. It cannot guarantee payer access, reimbursement, payment, posting, or a no-hire result at wider scale.
Size the first lane
See whether the opportunity justifies the operating test.
Start with practice-level counts and planning ranges. Then compare the likely queue with the team you already have.
Planning estimate only. No payer, revenue, reimbursement, payment, or staffing guarantee. Do not enter or send names, dates of birth, member IDs, charts, or other PHI.