01
Confirm the source is ready
Begin with the approved encounter and charge population. Confirm service completion, documentation status, qualified coding, patient and subscriber linkage, provider and location setup, and any required authorization or referral evidence in the secured systems.
Do not copy patient information into an external preparation list. Use the billing system’s work identifier and exception states so the source record remains authoritative.
- 1Reconcile eligible encounters to charge dispositions.
- 2Resolve documentation and coding questions through qualified roles.
- 3Confirm provider, location, enrollment, and payer configuration.
02
Assemble claim and line information
Create the claim from controlled registration, subscriber, provider, encounter, diagnosis, service, and charge sources. Verify which information belongs at claim level and which belongs on each service line.
Apply situational information only when its condition is true and supported. A default value that clears an edit but does not describe the claim is not a valid correction.
03
Run layered validation
Apply current structural, program, payer, organizational, and duplicate checks. Record the ruleset version and route each exception according to its actual owner—billing, coding, documentation, enrollment, authorization, compliance, configuration, or another qualified process.
Treat warnings and overrides as controlled decisions. Define who may approve them, what evidence is required, and how the rationale remains attached to the submitted claim version.
- 1Validate required fields and relationships.
- 2Compare against submission and correction history.
- 3Resolve or formally hold every exception before release.
04
Release and transmit the controlled batch
Assign the approved claim to a batch with stable claim, line, and charge totals. Record the releasing role, timestamp, destination, channel, generated artifact, and transmission identifier.
Keep prepared, released, generated, and transmitted as separate states. Successful file creation does not prove the file left the organization or reached the intended receiver.
05
Match acknowledgments and close the batch
Collect each expected transport, transaction, file, and claim response. Match it to the exact submission and assign rejections or missing responses before filing risk grows.
Close the batch only when the released and transmitted populations reconcile and every included claim has a known accepted, rejected, or actively owned exception state. Adjudication and payment occur later.
- 1Match each response to batch and claim identifiers.
- 2Route file-level and claim-level failures separately.
- 3Preserve submission and response evidence.
- 4Reconcile all released claims to known states.
