In short: Teleradiology per-study billing only works when provider and client agree what one study is. Counts drift because of compound scans, multiple procedures in one study, duplicate or split studies and inconsistent naming. Fix it with a written billable-study definition, a monthly reconciliation routine, standardised metadata and an audit trail for every adjustment.
Most teleradiology contracts are priced per study. It sounds simple: count the exams, multiply by the rate, send the invoice. In practice, teleradiology per-study billing is where small differences in how two organisations count exams turn into disputed invoices, delayed payments and strained client relationships.
The provider counts what arrived on its worklist and was reported. The client counts what it ordered, or what its RIS says was performed. The two numbers are rarely identical, and neither side is necessarily wrong. This article explains why the counts diverge, how to reconcile them, and the controls that keep them aligned.
A note on scope: this is generic operational guidance. It is not coding, legal or contractual advice. Billing codes, bundling rules and what may be charged separately vary by country, payer and contract, so always check local coding rules and your agreements before changing how you bill.
Why do exam counts drift in teleradiology per-study billing?
Counts drift because “one study” in the image archive does not always equal “one billable exam” in the client’s ordering system. Four patterns cause most of the gap.
| Cause | What happens | Typical effect on counts |
|---|---|---|
| Compound studies | One scan covers several ordered procedures (for example head, chest and abdomen in trauma) | Provider sees one study; client expects several reports and charges |
| Multiple procedures in one study | Several orders or accession numbers are attached to a single study | Systems disagree on whether to count one or many |
| Duplicate or split studies | Images are resent, or one exam arrives as two studies | Over-counting (duplicates) or double-charging (splits) |
| Naming variance | The same exam appears under different study descriptions | Exams are grouped or priced inconsistently |
Compound studies are well recognised. The IHE Presentation of Grouped Procedures profile was written for exactly this case: a patient with several orders where “it is better for the patient, and more efficient to perform a single scan covering all three procedures” [1]. IHE notes that its approach specifies “how reporting and billing can proceed properly for each of the three orders based on a subset of images” [1]. Not every site implements it, so in many networks the grouping has to be reconstructed.
DICOM allows for this complexity. The Request Attributes Sequence (0040,0275) in a series can carry one or more items from the imaging service request [2], so a single study may legitimately link to several requested procedures. Whether that counts as one billable unit or several is a contract decision, not a technical one.
Naming variance is the quieter cause. When the same exam arrives under many study descriptions, price-tier mapping and exam-type reports split one procedure into several apparent ones. The wider cost of inconsistent names is covered in why study descriptions are a mess across sites.
How do you define a billable study group?
For teleradiology per-study billing, define the billable unit in writing, in terms both sides can check against data, before you argue about any individual invoice. The definition should say what one billable study is, how compound and split cases are handled, and which data fields decide.
A practical definition usually covers:
- The counting key. For example, one billable study per accession number, or per requested procedure, or per Study Instance UID. Choose one and name the field.
- Compound acquisitions. Whether a single acquisition covering several ordered procedures is billed once, per procedure reported, or under an agreed combined tier.
- Duplicates. Resends with the same identifiers are not counted again; state which identifiers decide.
- Splits. Two studies that belong to one order are merged for billing; state who flags them.
- Addenda and re-reads. Whether addenda, second opinions and re-reads after a technical repeat are billable.
- Cancelled or incomplete exams. Whether studies received but not reported, or reported as non-diagnostic, are counted.
- Exam-type tiers. Which standardised exam names map to which price tier.
Agree the definition per client and keep it as a schedule to the contract. Reading volume interacts with service levels too, so align it with the definitions in your radiology turnaround time SLA.
How do you reconcile exam counts with a client?
In teleradiology per-study billing, reconcile monthly, at study level, using the same counting key on both sides. Comparing totals hides the cause; comparing lists of identifiers shows it.
- Extract both lists for the same period and time zone, with accession number, Study Instance UID, study date, study description and report status.
- Match on the agreed key. Pair records that match exactly.
- Classify the unmatched. Label each as a duplicate, split, compound, cancelled, late arrival or naming mismatch.
- Apply the contract rules to each category, rather than deciding case by case.
- Record every adjustment with the reason and who approved it.
- Share the reconciliation with the client before the invoice, not after a dispute.
Over a few cycles, the categories tell you where to intervene. If most mismatches are naming-related, standardising study descriptions will remove them at source. If most are splits, the fix lies in acquisition or transfer workflow at the client site.
Which controls stop counts drifting again?
Reconciliation catches errors; controls keep teleradiology per-study billing accurate in the first place. The most effective controls sit where studies enter your workflow.
- Standardised exam names at ingest, so every study maps to one agreed name and price tier.
- Duplicate detection on Study Instance UID and accession number before studies reach the worklist.
- Compound and split flags that let staff group or merge studies with a recorded reason.
- A single source of truth for counts, ideally derived from reported studies rather than received images.
- Change control for price-tier mapping, so new exam names cannot silently fall into the wrong tier.
For groups reading across many client sites, these controls belong in the shared operating model described in our guide to multi-site radiology operations.
How should you audit per-study billing?
Audit teleradiology per-study billing by sampling, by trend and by exception. A short monthly routine catches most issues early.
Sample a fixed number of studies per client each month and trace each one from receipt to report to invoice line. Track trends per client: a sudden change in studies per patient or in the share of compound exams is worth a question. Review every manual adjustment, because a growing adjustment log usually signals a broken upstream rule. Keep the original metadata alongside any corrected values, so you can always show what the client’s system sent and why you counted it as you did.
How does standardised study data support accurate billing?
Most teleradiology per-study billing disputes trace back to metadata: names that vary, studies that should be grouped, and duplicates that look new. Consistent study data shrinks that gap before reconciliation starts. evoTag organises and corrects DICOM tags such as study descriptions, giving them consistent, accurate names, working from the existing DICOM tags and study descriptions rather than analysing images. It supports reliable study grouping and accurate counts of distinct exams for billing, and passes normalised metadata to downstream billing and analytics systems. Your contract definitions and local coding rules still decide what is billable. For the technical side of mapping, see our guide to DICOM tag normalisation.
Related guides
Frequently asked questions
What is per-study billing in teleradiology?
Teleradiology per-study billing is a pricing model where the teleradiology provider charges a client a fee for each study read, often with different rates by exam type, urgency or time of day. It is simple to quote, but it depends on both sides agreeing what counts as one study, which is where most invoice disputes begin. For background, see what teleradiology is.
Should we count by accession number or by Study Instance UID?
Either can work if both sides use the same one. Accession numbers usually follow orders, so they suit clients who bill per procedure. Study Instance UIDs follow the images, so a compound scan may appear as one study. Choose the key that best matches how your contract prices work, write it down, and reconcile against it consistently.
How should compound studies be billed?
There is no universal answer. Some contracts bill each ordered procedure that is reported separately; others apply a combined rate. What matters is that the rule is written, applied consistently and reflected in local coding requirements. This article is not coding advice, so check your jurisdiction’s coding rules and payer requirements before you decide.
How often should we reconcile counts with clients?
Monthly reconciliation before invoicing suits most groups, with a lighter weekly check for new clients or after any system change at a client site. The aim is to catch mismatches while studies are fresh and records are easy to trace, rather than investigating a quarter’s worth of disputes at once.
Can standardising study descriptions alone fix billing disputes?
It removes one common cause, naming variance, and makes grouping and exam-type pricing more reliable. It does not by itself resolve contract ambiguity, duplicate transfers or split acquisitions. Combine standardised metadata with a written billable-study definition, duplicate checks and a regular reconciliation routine for the best results.
Want fewer “your count does not match ours” conversations? See how evoTag supports accurate counts of distinct exams.
Sources
- “Presentation of Grouped Procedures.” IHE International Wiki, date not stated. https://wiki.ihe.net/index.php/Presentation_of_Grouped_Procedures
- DICOM PS3.3 Information Object Definitions, Section C.7.3 “Series Modules” (General Series Module, Request Attributes Sequence (0040,0275)). NEMA, current edition. https://dicom.nema.org/medical/dicom/current/output/chtml/part03/sect_C.7.3.html
- “Presentation of Grouped Procedures (PGP).” SIIM OTPedia, Society for Imaging Informatics in Medicine, date not stated. https://siim.org/otpedia/presentation-of-grouped-procedures-pgp
