Every claim a practice submits is a statement that a specific service was provided for a specific reason. The clinical note is the evidence. When the note and the codes line up, claims go through and audits are uneventful. When they don’t, the result is rejections, repayments or worse. A short billing and coding summary per encounter is a simple way to keep the two connected.
What is a billing and coding summary?
A billing and coding summary is a one-page record for a single encounter that lists the service provided, the diagnoses and the codes chosen for each, and where in the clinical note the supporting documentation can be found. It usually includes a short documentation checklist and space for queries back to the clinician.
It is not a replacement for the clinical note. It is a bridge between the note and the claim, and it makes review faster for billing staff, the clinician and any auditor.
Why it matters
- Fewer rejections. Claims that match the documentation are less likely to bounce back.
- Audit readiness. When a payer asks why a service was billed, the supporting text is already identified.
- Clear handoffs. Clinicians and billing staff often work at different times. A summary keeps questions and answers in one place.
- Learning. Patterns in queries show where documentation habits could improve.
Documentation that supports coding
Coding is only as good as the note behind it. Clinicians can make billing far smoother with a few habits:
- State each problem addressed in the assessment, with its status, rather than leaving it implied in the history.
- Be specific. “Type 2 diabetes with chronic kidney disease” codes differently from “diabetes.” Write the most specific diagnosis you can support.
- Record times for any service that depends on them.
- Document procedures fully: site, side, technique and consent where required.
- Note referrals and requisitions when a payer requires them for the service billed.
Billing staff should never have to guess. When documentation and codes are built together from the start, queries become rare.
How to write each section
Encounter details
Record the date, clinician, setting, payer and, where it affects billing, whether the patient is new or established. Small details such as setting or modality can change which code applies.
Service provided
Describe the service in the terms used in the note: a follow-up visit, a consultation, a counseling session, a procedure. If the service is billed by time, record start and end times or total time exactly as documented.
Diagnoses
List each diagnosis as written in the note, the code chosen and the coding system used. Mark which one is primary. If the note says “likely” or “query,” follow your payer’s rules for coding uncertain diagnoses.
Procedures and services
For each billed item, record the code, any modifiers or premiums, units and where the supporting documentation is. That last column is the core of the summary: it makes the link between note and claim explicit.
Documentation check and queries
Run through the checklist before submission. If something is missing, write a specific query to the clinician (“Time not documented for counseling; please add if known”) and hold the claim until it is answered.
Claim status
Note who prepared the summary and when the claim was submitted or held.
Free billing and coding template
Copy the template below into your practice management system or Notatio template library. Bracketed text explains each field.
Summary template
Billing and Coding Summary
Encounter details
Date of service: [Date]
Clinician: [Name, role and billing number if used]
Location and setting: [Office, hospital, telehealth, home visit, long-term care]
Payer: [Public plan, insurer or self-pay]
Patient type: [New or established, if relevant to the payer]
Service provided
Service description: [Type of visit or service as documented, for example follow-up assessment, consultation, counseling session, procedure]
Time: [Start and end time or total time, if the service is time-based. Omit if not time-based]
Modality: [In person, video or telephone]
Diagnoses
| Diagnosis as documented | Code | Coding system | Primary? |
|---|---|---|---|
| [Diagnosis from the note] | [Code] | [ICD-10-CM, ICD-10-CA, provincial diagnostic code list or other] | [Yes or No] |
Procedures and services
| Service or procedure | Code | Modifiers or premiums | Units | Supporting documentation |
|---|---|---|---|---|
| [Service] | [Fee or procedure code per schedule] | [If applicable] | [ ] | [Where in the note it is documented] |
Documentation check
- Chief complaint and reason for visit documented
- Assessment supports each diagnosis code
- Time documented for time-based services
- Procedure details documented, including site and consent where required
- Referral or requisition on file where the payer requires one
- Note signed by the clinician
Queries
[Questions for the clinician about missing or unclear documentation. Write “None” if no queries]
Claim status
Prepared by: [Name and date]
Amount claimed: [Total fee claimed for the encounter, and any amount billed to the patient or a third party. Omit if not tracked]
Submitted: [Date, or “Held pending query”]
Billing and coding summary example
Here is the template completed for a fictional follow-up visit. Diagnosis codes are shown in ICD-10 for illustration; the service code is left generic because fee codes differ between payers.
Encounter details
Date of service: Weekday clinic session
Clinician: Family physician
Location and setting: Office
Payer: Public health plan
Patient type: Established
Service provided
Service description: Follow-up assessment of type 2 diabetes and hypertension, with medication review
Time: Not time-based
Modality: In person
Diagnoses
| Diagnosis as documented | Code | Coding system | Primary? |
|---|---|---|---|
| Type 2 diabetes without complications | E11.9 | ICD-10 | Yes |
| Essential hypertension | I10 | ICD-10 | No |
Procedures and services
| Service or procedure | Code | Modifiers or premiums | Units | Supporting documentation |
|---|---|---|---|---|
| Follow-up assessment | Per payer fee schedule | None | 1 | Note: history, exam, assessment and plan for both problems |
Documentation check
- Chief complaint and reason for visit documented
- Assessment supports each diagnosis code
- Time documented for time-based services (not applicable)
- Note signed by the clinician
Queries
None.
Claim status
Prepared by: Billing coordinator, same day
Submitted: Same day
Fictional patient. Illustrative only, not clinical advice.
Common mistakes to avoid
- Coding from memory. Codes should come from the note, not from what the clinician said in the hallway.
- Missing time. Time-based services without documented time are one of the most common audit findings.
- Diagnosis codes without support. Each code needs a matching assessment in the note.
- Copy-forward diagnoses. Conditions not addressed today generally shouldn’t be coded as if they were.
- Not querying. Guessing to avoid a delay creates a bigger problem later.
Coding systems at a glance
| What is coded | Common examples | Notes |
|---|---|---|
| Diagnoses | ICD-10-CM (US), ICD-10-CA (Canadian hospital data), provincial diagnostic code lists | Use the system your payer requires |
| Physician services | CPT (US), provincial fee schedules (Canada) | Rules and codes vary by payer |
| Supplies and other services | HCPCS (US) | Payer-specific |
How Notatio helps with billing documentation
Notatio is an ambient AI scribe. It records the visit and drafts the note in the clinician’s chosen template, so the documentation that supports a claim is written while the visit is fresh. In Canada, Notatio also suggests billing codes from the documentation. The clinician or billing team reviews every suggested code before anything is submitted.