A care team can complete meaningful work for a patient and still leave billing with unanswered questions. A billing-ready CCM or RPM workflow assembles the supporting records, checks the requirements for the specific service and payer, resolves documentation exceptions, and hands a traceable record to billing. Billing-ready means prepared for claim review. It does not mean guaranteed reimbursement or automatic approval to submit a claim.
At 1bios, our approach starts with a practical idea: You already have the patients. We bring the operation. At the billing handoff, that means defining who documents the work, who investigates gaps, and who receives the completed record. Each team should be able to understand what happened without piecing it together from disconnected notes.
The workflow begins when care is delivered and documented, rather than when someone prepares a monthly report. Each activity needs enough context to identify the patient, the work performed, the person who performed it, and the relevant date or service period. Where time affects billing, the record also needs support for the qualifying time attributed to that service.
A practical handoff follows this sequence:
These steps are recommended operational practices, not a separate CMS certification process. They help teams apply the relevant billing requirements consistently. The billing reviewer still needs to determine whether the documentation supports the proposed claim.
For the broader work of establishing a program, the 1bios CCM launch guide covers patient eligibility, care planning, staffing, and implementation. This article starts at a narrower point: turning delivered care into a reviewable record. A program can have those foundations in place and still need a better handoff.
Use a service-specific checklist tied to the payer, practice setting, and date of service. The Medicare requirements discussed here should not be assumed to apply unchanged to every Medicaid program, Medicare Advantage plan, or commercial payer. Assign someone to maintain the checklist and identify when updated instructions take effect.
Practice setting matters as well. For example, CMS’s current RHC and FQHC billing updates identify changes to care-coordination reporting, including the termination of G0511. A Rural Health Clinic or Federally Qualified Health Center should use its applicable instructions rather than copy an office-practice billing template.
Store the source and effective date alongside each internal check. When guidance changes, identify which service periods and records are affected. A proposed policy should not silently become a current billing rule in the workflow.
CCM review needs to establish more than a monthly time total. The reviewer should connect the recorded activities with the patient’s care-management needs and the proposed service. A useful starting point is the CMS CCM guidance on consent, care plans, service elements, and code-specific requirements.
For Medicare CCM, check:
The reviewer should be able to locate the supporting information without relying on a generic “CCM completed” status. As an operational practice, link activity entries to the relevant note or care-plan record rather than copying the same narrative into multiple places. If a required element cannot be established, identify the gap before releasing the service for billing review.
RPM documentation needs to distinguish device-related services from treatment-management work. A shipment record does not establish that setup occurred, and a transmission report does not establish that a patient conversation took place. Review the components separately, using the CMS requirements for medically necessary monitoring, consent, connected devices, and data transmission.
For an RPM handoff, assemble:
Do not apply one reading-day minimum or one time threshold to every RPM service. The 2026 Medicare Physician Fee Schedule final rule addresses additional RPM codes for shorter data-collection and treatment-management periods. The reviewer needs the current requirements for the proposed code, including communication requirements, rather than a single “RPM complete” flag.
The person who delivers care is usually best positioned to explain the activity, but that person should not have to resolve every billing question alone. Clinical, operational, and billing questions need different owners. The following table should make those responsibilities visible without suggesting that one role can approve every part of a claim.
For the actual transfer, include the patient identifier, billing practitioner, service being reviewed, relevant dates, and links to supporting records. Include qualifying-time and transmission summaries where applicable, along with the disposition of any exceptions. Name the person who completed the preparation and the billing contact responsible for accepting or returning the record.
A handoff report should function as an index to the evidence. It should not replace the underlying clinical notes, device records, or other documentation. Agree on how billing acknowledges receipt so “sent” does not become the last known status.
Medicare permits CCM and RPM to be billed concurrently when the applicable requirements are met, but the same time and effort cannot be counted twice. CMS also identifies restrictions on combinations of services, including RPM with remote therapeutic monitoring. The remote monitoring guidance should inform the overlap check alongside the instructions for the other services involved.
Record the work at the activity level before aggregating totals. If a contact includes both monitoring-related management and broader care coordination, the record should describe the distinct work and support any allocation of qualifying time. Do not copy the entire contact duration into both programs.
The reviewer should also check who performed the work and which service period applies. CMS’s CCM guidance distinguishes clinical-staff services from services personally performed by the billing practitioner, with different time requirements and reporting restrictions. A large combined total cannot substitute for checking the correct category.
Make potentially overlapping services visible to billing, including services reported elsewhere in the practice when that information is available. Have the reviewer apply current concurrent-billing instructions and payer edits to the actual combination. Do not treat a software label separating two programs as proof that the underlying work is distinct.
An exception should describe a specific unresolved question. “Documentation issue” is too vague to tell the next person whether to locate a missing attachment, clarify an activity, or investigate a duplicate entry. Record the affected service, the issue, its owner, and the next action.
A practical exception process is to:
Locating an existing note is different from adding a late entry. CMS’s medical-record correction guidance requires amendments, corrections, and delayed entries to be identifiable, dated, and attributable while preserving the original content. Follow the applicable recordkeeping rules and practice policy rather than overwriting the record or backdating a change.
Do not invent activities, add estimated minutes merely to reach a threshold, or document a communication that never occurred. If the evidence does not support the proposed service, keep that service out of the submission queue unless and until the issue is appropriately resolved. A billing hold should not interrupt clinically necessary patient follow-up.
A practice prepares an RPM treatment-management record for billing review. The activity summary includes qualifying-time entries and identifies a completed patient conversation, but the communication note is missing from the handoff. The reviewer flags the missing support and holds the proposed treatment-management service.
The exception goes to the team member who documented the contact. That person locates the original dated note in the clinical record and confirms that it belongs to the correct patient and service month. The handoff is updated to include the note, and the reviewer checks its content and the other applicable requirements before changing the status to ready for billing review.
If the investigation instead shows that the contact was only an unanswered outreach attempt, the team does not relabel it as a completed conversation. The proposed service remains held or is marked unsupported after the applicable review. Other components are assessed on their own evidence and requirements rather than being automatically approved or rejected with it.
A clear division of work lets each team answer the questions it is equipped to resolve. The practice supplies clinical direction and decisions, the documenting team supplies accurate evidence of its work, and billing evaluates the proposed claim. An outside partner’s involvement should make those assignments explicit.
The practice identifies the responsible practitioner and directs clinical care. Its clinicians resolve questions about medical necessity, care decisions, and clinical content that require their judgment. Practice leadership also assigns responsibility for oversight and makes sure records remain accessible.
A partner should document the work it actually performs and supply the supporting information specified in the agreement. Its scope should identify who investigates missing records, corrects its documentation appropriately, and responds to billing questions. Ask what is delivered, where it is available, and how an unresolved exception is communicated.
The billing team reviews the assembled evidence against the applicable coding, payer, setting, and claim requirements. It decides whether the proposed service can proceed through the practice’s claim-submission process or needs further review. Claim submission, payment posting, and denial follow-up should each have an assigned owner.
In the standard 1bios CCM model, the practice’s billing team submits claims and collects reimbursement while 1bios supports documentation and billing workflows. RPM responsibilities should be confirmed separately in the relevant agreement. Denial management should also be explicitly assigned rather than assumed to be part of documentation support.
For more on structuring the relationship, see the guidance on outsourced CCM and insourcing versus outsourcing an RPM monitoring team. Those choices affect who performs the work and where its records originate. The billing handoff still needs a defined owner in either model.
Measure the quality and movement of records rather than only the number of services released. A fast handoff is not useful if billing repeatedly returns it for missing evidence. Establish your own baseline before choosing improvement targets.
Use these measures to identify a process that needs attention. Repeated missing attachments may call for a better transfer process, while repeated coding returns may call for an updated review checklist. A denial reason should prompt investigation rather than an automatic conclusion that the care team’s documentation was at fault.
Choose a small set of recent records and trace each one from delivered care to billing’s decision. Look for places where staff had to search for evidence, repeat a request, or guess who owned a question. Use those findings to define the handoff and exception process your team actually needs.
For a practice working with 1bios, that discussion should establish the documentation deliverables, the division of review responsibilities, and the route for unresolved questions. Confirm CCM and RPM scope separately, including any billing or denial-related services. The goal is a record that billing can evaluate and a clear path for questions that remain.
Billing-readiness questions often arise when teams use the same label for different review stages. Agree on what each status means and who can change it. These distinctions help keep documentation preparation separate from claim approval.
No, billing-ready means the supporting documentation has been assembled and checked for billing review. The billing team still evaluates the proposed claim against applicable requirements. A completed handoff does not guarantee payment.
A shared workflow can cover ownership, record access, exceptions, and handoff status. The service-specific checks need separate branches for CCM, RPM components, and the proposed codes. One monthly total or completion flag cannot establish every requirement.
A missing document may already exist and simply need to be linked to the record. If a correction or delayed entry is appropriate, it must truthfully reflect work performed and follow applicable recordkeeping requirements. Adding a note cannot create a service or time that did not occur.
Identify the specific service and requirement affected by the issue. Billing should determine whether other proposed services remain independently supported and whether any dependencies or reporting restrictions apply. Do not automatically release the entire record or reject every component.
Not necessarily, because documentation preparation and denial follow-up are different responsibilities. The agreement should state who reviews payer responses, investigates causes, and handles any correction or appeal. Confirm the scope separately for CCM and RPM.