Logging Procedure Bundles

Save a named procedure bundle with confirmed wRVUs, then reuse it by choosing the date and quantity.

Log a bundle

Choose Bundles in the Dashboard logger for related procedures performed together, such as bronchoscopy with endoscopy. To create one, select the codes, enter a Bundle name and one Total wRVUs per bundle, then Save bundle. Saved bundles appear directly in the logger. Select one, choose Service date and Quantity (bundles), then Log bundle. You do not need to open the editor to reuse it. Saving a shortcut does not log work. Never enter patient identifiers; your employer or coding team determines reporting eligibility.

Enable bundles at your first save

Build and review a bundle before enabling it for your account. At the first save, the app checks this device for ordinary saves still waiting to sync or needing review. Finish those saves first. The short Enable bundles step explains that older versions on your other devices will need updating. The app cannot verify devices that are offline. Enabling keeps your draft and refreshes its calculation; review the result and choose Log bundle. Existing entries are unchanged.

Component quantities and Quantity (bundles)

Component quantity belongs to the saved combination. Quantity (bundles) repeats the complete combination and starts at 1; enter 1 to 100 whole bundles on a supported server. A × 2 plus B × 1, logged with bundle quantity 3, records A × 6 and B × 3. Credit for one complete bundle is multiplied by 3; a custom total applies to that complete bundle, not separately to every component. A save accepts the complete quantity or none. History shows one expandable named bundle row with the logged quantity. If one saved session is later edited or removed, History shows the remaining sessions individually so it does not misstate the original group. Older records keep their original credit and appear as individual bundles.

Set one bundle total

Enter the total work RVUs you want recorded for one complete bundle. Save bundle keeps the codes, name and that value together. The app does not automatically adjust bundle totals or offer a credit-method selector. Your total includes any adjustments you intend, including modifier 22; it is not increased again. Blank or incomplete text cannot be saved as a value. An explicit 0 is allowed. Saving this value does not establish coding eligibility or insurer payment.

Review and log the bundle

The online preview shows credited wRVUs per complete bundle, bundle quantity and aggregate credit. Check the job, service date, procedures and chosen total, then choose Log bundle or Log N bundles. The saved total is multiplied by the bundle count once. A whole-bundle amount is not divided among procedure codes and does not supply total RVUs. Older unresolved logs remain excluded from credited totals until explicitly edited.

Bundle totals and compensation

The value you enter determines the work RVUs recorded for each complete bundle. Your job’s dated compensation settings convert that work into estimated earnings. Entering a bundle value does not change your pay rate or establish billing approval. Confirm reportable codes and the appropriate value with your employer or coding team.

Logged bundles and unresolved totals

Bundle logged or N bundles logged confirms the accepted patients, procedures and work credit. Multiple-patient saving accepts all selected cases or none. Each patient's credit appears once in History, totals, targets and work-based earnings. Individual codes can contribute procedure counts without receiving a share of that work credit; code reports show Unallocated case credit separately. Total RVUs are incomplete for ranges containing these cases because no total RVU value was supplied. Older unresolved cases stay excluded until their credit is resolved. Peer comparisons are unavailable when user-entered bundle totals cannot be compared fairly with the published-code cohort.

Save and reuse a bundle

Select codes, enter Bundle name and Total wRVUs per bundle, then Save bundle. The saved item appears in the same logger and a blank composer is ready for another. Select a saved item directly, choose date and Quantity (bundles), then Log bundle. Edit saved bundle uses the same codes, name and one value. Saving a changed shortcut affects future uses and leaves prior logged work unchanged. Changing the job or procedures clears the total so you enter it again; date, bundle count and name preserve it. Older shortcuts without a total ask for one value once. Existing logs keep their saved values. Bundle history contains logged-work management and recovery; occasional backup controls are in Settings > Data. Removing a shortcut does not delete logged work. This direct inline flow is the website/PWA flow; native presentation may differ by installed version.

Unfinished bundles and save recovery

Bundle calculations and saves require a connection. Fresh fields stay in memory while the logger stays open; navigating away, closing or restarting may clear them. New bundles do not read or create unsent draft copies. Older unsent copies remain optional under Bundle history. Actual Log bundle attempts keep their original request and receipt before sending. The website and app quietly check those original operation IDs in the background; confirmed results need no manual clearing. Checking a receipt never resubmits it. Multiple-patient saves require confirmation of the whole original group. A conflict, reset or still-unconfirmed result asks for attention without creating replacement work. Ordinary logs retain their automatic offline queue. Retry preview checks the bundle without submitting work.

Bundle backups

Older bundle JSON backups are in Settings → Data. Choose Download bundle backup to keep a copy, or Review bundle backup to inspect an existing file. Review the job, date, procedures and total before saving restored work. Some older files require you to re-enter the bundle total. Ordinary procedure CSV imports do not restore grouped bundle credit. Keep your original files.

Existing History and earlier totals

Older entries and saved cases keep their original values and methods. Matching dates or a Batch list never establish case membership. Correct known historical work deliberately and review the whole case; enabling procedure bundles does not regroup or reprice existing History.

Back to the wRVU Tracker Help Center