Finance wants the health system’s telecom bill smaller. Clinical engineering wants nothing touched. Both are right, and on a multi-site invoice they’re usually staring at the same circuit IDs with no way to tell which ones keep a nurse-call integration talking and which ones ring in an empty office.
Healthcare telecom expense management is the practice of inventorying, auditing, and controlling every voice, data, and wireless service a health system pays for across its hospitals, clinics, and administrative sites. It works when every circuit is tagged clinical or administrative before anyone disconnects, re-rates, or renegotiates it, and when vendor access is scoped as tightly as clinical access.
This guide lays out a method built on three parts: RadiusPoint’s line-item audit in ExpenseLogic instead of a sample, a four-tier checklist this guide calls Clinical-Circuit Guardrails, and a HIPAA-aware way to handle vendor access that doesn’t depend on a “HIPAA certification” (HHS doesn’t recognize one). It’s written for the people who own telecom spend across facilities: IT, telecom, and finance leaders at health systems and multi-site care operators.
Key Takeaways
- Tag before you touch. Every circuit gets a clinical or administrative tier, with named approvers, before any disconnect or rate change. No tag means no change.
- Zero usage isn’t zero purpose. Fire alarm and elevator emergency lines rarely place calls, so usage reports make them look dead.
- Audit every line item. Health-system billing errors hide in low-dollar charges spread across sites and billing accounts, which is exactly what sampling skips.
- HIPAA-aware means scoped, not certified. Keep patient data out of telecom records, decide on a business associate agreement from real data flows, and limit the letter of agency to records and disputes.
- Validation before disconnection has published proof. A RadiusPoint healthcare client cut telecom expenses 26% after every line was validated before it was disconnected.
The Short Version
Build a tagged, invoice-matched inventory first, then audit every line item and route every change through clinical-aware approvals, because a health system that cuts telecom spend from a usage report alone is trading savings for uptime risk.
What healthcare telecom expense management covers across hospitals, clinics, and admin sites
Healthcare telecom expense management covers every billed voice, data, and wireless service in a health system, from hospital WAN circuits to clinician phones. The scope is set by the bill, not the org chart. If a carrier invoices it or a customer service record lists it, it belongs in the inventory, no matter which department ordered it.
That definition matches the industry standard. The Enterprise Technology Management Association (ETMA) defines a TEM inventory as anything that appears on an invoice or customer service record (CSR) for a mobile or fixed line, circuit, or service. In a health system, that spans four kinds of sites with very different risk profiles.
Hospitals carry the heaviest and most sensitive services: MPLS or SD-WAN circuits that move EHR traffic and imaging files, internet and SIP trunks, paging and nurse-call integrations, and analog lines that still serve fire alarm panels, elevator emergency phones, and fax machines. Outpatient clinics and physician offices add broadband, POTS and fax lines, and UCaaS seats, often on their own billing account numbers (BANs). Administrative and billing centers bring contact-center trunks, toll-free numbers, and corporate voice. Mobility runs across all three: clinician smartphones, shared unit devices, tablets, hotspots, and SIM-enabled equipment.
If you want the general framework before the healthcare specifics, start with what telecom expense management covers. The rest of this guide focuses on what changes when the services on the bill keep patients safe.
Why do health-system telecom bills break at multi-site scale?
Health-system telecom bills break because ordering is decentralized, billing accounts multiply with each acquisition, and nobody owns a circuit’s clinical purpose. Each failure is ordinary on its own. Together they produce invoices that accounts payable can pay but can’t validate, and inventories that IT can’t trust enough to act on.
BANs multiply faster than anyone maps them. Every hospital, clinic, and acquired practice arrives with its own billing account numbers, and carriers don’t bill them the same way. In one RadiusPoint healthcare engagement, some vendors sent invoices showing only a total due, with no service description or phone number attached. You can’t dispute a charge you can’t identify.
Ordering happens at the edge. When each location buys its own lines and devices, global contracts and volume pricing never apply, and the inventory never learns what was bought. Location-level invoice approval adds a second problem: bills sit in local queues, late fees accrue, and occasionally a service gets suspended for nonpayment.
A circuit ID says nothing about clinical purpose. The same invoice line format describes a circuit carrying imaging transfers and one serving a closed billing office. Because nobody can tell them apart, teams either freeze everything (so waste persists) or cut from a spreadsheet (so the wrong line goes down).
Devices outlive their users. Clinician turnover, traveling staff, and shared unit phones leave lines active long after the person or the purpose is gone. Without a reconciliation against the HR roster, those lines bill indefinitely.
Copper retirement is forcing decisions on a deadline. In March 2026 the FCC adopted a Report and Order (FCC 26-19) that streamlined how carriers retire copper networks and discontinue legacy services. Carriers now have blanket authority to grandfather legacy copper voice services and a faster path to discontinue them, and the lines most affected in hospitals are the ones that look idle on a bill: fire alarm communicators and elevator emergency phones.
“The telecom industry can’t keep up with the ubiquitous challenges and doesn’t have the time to identify savings.”
Sharon Watkins, Founder and CEO, RadiusPoint
Clinical-Circuit Guardrails: tag every circuit before you cut, re-rate, or disconnect
Clinical-Circuit Guardrails is the checklist this guide proposes: every circuit gets a clinical or administrative tier, with named approvers, before any disconnect, rate change, or contract move. Untagged circuits are frozen until someone identifies them. The rule front-loads inventory work and removes the one failure a hospital can’t absorb: a cost cut that silences a clinical or life-safety service.
The tiers below are assigned during the inventory build, circuit by circuit and site by site. Each tier defines what evidence is required before a MACD (move, add, change, disconnect) request and who has to approve it.
| Tier | Typical services | Required before any change | Who approves |
|---|---|---|---|
| Tier 1: Life safety | Fire alarm communicator lines, elevator emergency phones, emergency call stations, E911 trunks | Site walk confirming the device; replacement path installed and tested before any disconnect | Facilities or life-safety lead, plus the telecom owner |
| Tier 2: Clinical critical | Circuits carrying EHR access, imaging transfers, nurse-call and patient-monitoring integrations, pharmacy and lab interfaces | Redundant path confirmed; change scheduled inside an approved maintenance window | Clinical engineering or the IT change board, plus the telecom owner |
| Tier 3: Clinical support | Clinician mobile lines, on-call paging, referral and order fax lines, patient scheduling trunks | Owner confirmed; test call or usage check; suspend before cancel where the carrier allows | Department manager, plus the telecom owner |
| Tier 4: Administrative | Corporate and billing office lines, admin wireless, lines at closed or sold sites | Inventory matched to the invoice and to current site status | Telecom owner under standard MACD approval |
Zero usage isn’t zero purpose. A fire alarm communicator line can go months without placing a call and still be required. Replacing a fire alarm or elevator emergency line is a facilities project, not a billing edit. A cleanup driven by usage reports will flag exactly these lines first.
RadiusPoint’s published work with an assisted living and nursing home operator shows why this kind of check matters. Every location had to keep copper lines for direct fire notification, so analysts verified each line through test calls and, where nobody answered, on-site visits before anything was deactivated. The lines that traced to nothing came off the invoices. The lines that traced to a fire panel stayed.
ExpenseLogic routes MACD tickets through client-defined approval workflows, so you can require the approvers you named before any Tier 1 or Tier 2 change moves.
How does RadiusPoint run healthcare TEM inside ExpenseLogic?
RadiusPoint runs healthcare TEM as a managed service in ExpenseLogic, where named analysts audit every invoice line against contract and inventory rather than sampling. Software plus people matters here because clinical tagging, carrier disputes, and approval routing all need judgment that a dashboard can’t supply on its own.
The monthly cycle runs in seven steps. Each one carries a check that only matters in healthcare.
| Step | What happens in ExpenseLogic | The healthcare check |
|---|---|---|
| 1. Collect | Invoices from every BAN are loaded each cycle, and daily missing-bill reporting flags any invoice that doesn’t arrive | A missed bill at a clinic becomes a late fee or a service interruption, not just an accounting gap |
| 2. Build the inventory | Carrier CSRs are pulled under a scoped letter of agency and matched to invoices, site by site | Give each circuit a clinical or administrative tier before anything changes |
| 3. Audit | Every line item is checked against contracted rates and the inventory of record | Services still billing after cancellation, duplicate features, and charges at closed sites are flagged |
| 4. Dispute | Disputes are filed with carriers and tracked through to credit | Evidence includes the circuit’s tier and the site’s status |
| 5. Change | MACD tickets move through client-defined approval workflows | Tier 1 and Tier 2 changes require the named facilities or clinical approver |
| 6. Allocate | Costs are coded to GL account, facility, and cost center, with accrual files and circuit split-billing | A WAN circuit shared by a hospital and its clinics lands on the right budgets |
| 7. Govern | Contract expiration and termination-fee alerts, plus closed-location billing exception reports | Divested or closed facilities stop billing, and renewals don’t roll over unnoticed |
Why a line-item audit beats sampling in healthcare. Sampling works when errors are large and concentrated. Health-system telecom errors are the opposite: feature charges and taxes still billing on lines canceled years ago, or circuits that kept billing after a disconnect order failed, spread across every BAN in the estate. The nursing home engagement found both. A sample of the largest invoices would have missed them, because the errors lived on the small ones.
Two more ExpenseLogic capabilities address the decentralized ordering problem directly. Employee ID validation against a monthly HR roster catches lines belonging to clinicians who’ve left. The Intelligent Queue ordering portal restricts requests to an approved equipment catalog, so a clinic manager can still order a device without creating an off-contract line. Because ExpenseLogic also runs Utility Expense Management (UEM), which covers electricity, gas, water, and waste invoices, facilities teams can review a clinic’s telecom and utility costs in one place.
You can see the full scope of RadiusPoint’s telecom expense management services, including bill payment and accrual support, on the service page.
What does a HIPAA-aware telecom expense management vendor do differently?
A HIPAA-aware TEM vendor keeps patient data out of telecom records, scopes its own access, and helps you decide whether a business associate agreement applies. That decision belongs to your privacy officer and counsel, not to a sales deck. The vendor’s job is to make the facts easy to see.
Start with the data flow, not the contract. Under HIPAA, a business associate is a person or organization that creates, receives, maintains, or transmits protected health information (PHI) on a covered entity’s behalf. Telecom invoices, CSRs, and circuit IDs usually don’t contain PHI. It drifts in through side doors: call detail records listing patient callback numbers, MACD tickets that name the patient in a room, or device records for patient-facing tablets. A health system can either keep PHI out by design, with ticket templates that have no patient fields, or sign a business associate agreement (BAA) that reflects what actually flows. Some health systems require a BAA from every vendor as policy, which settles the question.
Don’t borrow your carrier’s status. HHS treats transmission-only services, with no storage beyond what’s temporary and incidental to transmission, as conduits rather than business associates. A TEM provider that stores your records isn’t a conduit, so whatever applies to the carrier doesn’t automatically apply to the company auditing the carrier’s bills.
Ignore “HIPAA certified.” HHS states that it doesn’t endorse or recognize private organizations’ Security Rule “certifications,” and that such certifications don’t relieve anyone of their legal obligations. Ask for evidence instead. The questions below apply to every TEM vendor, RadiusPoint included.
| Ask the vendor | Why it matters in a health system | Evidence to request |
|---|---|---|
| Will any PHI enter your systems from our invoices, tickets, or device records? | Determines whether a BAA applies | A written data-flow description and the ticket template you’ll use |
| Who on your team can see our data, and how is access granted? | Least-privilege access limits exposure | Role and permission list; unique logins with no shared accounts |
| Can you show us a user-activity log? | You need to reconstruct who changed what, and when | A sample audit log export |
| What does your letter of agency authorize? | Ordering rights on clinical circuits bypass your change control | A letter of agency limited to records and disputes |
| How is access removed when people leave, on either side? | Stale access is a standing risk | Offboarding procedure and its timing |
| How do changes reach clinical circuits? | Uptime outranks savings | An approval workflow tied to circuit tiers |
The letter of agency deserves extra attention. A well-scoped letter of agency lets a TEM provider pull carrier records and file disputes without giving it standing authority to order or disconnect services, which keeps clinical changes inside your own approval chain.
Watch the pending Security Rule update. HHS proposed an overhaul of the HIPAA Security Rule in the Federal Register on January 6, 2025, including stronger verification of business associates’ safeguards and a technology asset inventory requirement. As of September 2026 it isn’t final; the 2026 Unified Agenda lists July 2027 as the target for final action. If it’s finalized as proposed, a TEM-grade circuit inventory gives your compliance team a head start on the asset inventory piece.
What two published healthcare cases show, and what they don’t promise
RadiusPoint’s published healthcare cases show a 26% telecom expense reduction and a 448% ROI, both from inventory and process fixes, not clinical cuts. They’re results from specific engagements, not a forecast for yours. What transfers is the method, and the method is visible in how each result was produced.
| Client | Starting problem | What RadiusPoint did | Published result |
|---|---|---|---|
| Assisted living and nursing home operator | No prior telecom inventory or audit; summary-only invoices; rising business line costs; mandated fire notification lines at every site | Audited and inventoried telecom, IT, and wireless services; verified each line by test call or site visit; protected fire notification lines; disputed charges for long-canceled services | 26% reduction in telecom expenses |
| Multi-site healthcare organization | Decentralized ordering, inaccurate inventory, and late fees from location-level invoice handling | Centralized invoice receipt and built a per-location service inventory in ExpenseLogic so the corporate telecom team could remove unneeded services | 448% ROI from AP and ordering automation |
The first engagement is documented in the case study healthcare telecom expenses down 26%, and it’s the clearest example of validating before disconnecting: nothing was disconnected until its purpose was known. The second is described in the healthcare TEM implementation case study, where the savings came from fixing how invoices and orders moved through the organization. Treat the 448% figure as one engagement’s published outcome, not a guarantee.
Outside validation points the same way. Amalgam Insights named RadiusPoint a Distinguished Vendor in its 2024 TEM Vendor SmartList, and ExpenseLogic holds a 4.8 out of 5 rating on Capterra from 31 reviews. RadiusPoint has operated since 1992 and remains independently owned.
Should a health system outsource TEM or keep it in-house?
Outsource healthcare TEM when your team can’t audit every invoice line and work disputes each cycle; keep it in-house when you have staffed, documented processes. Either way, the health system keeps the decisions. A provider takes on the repetitive work, not your accountability for clinical uptime.
The signals below are more reliable than spend thresholds, because a health system’s risk depends on how its services are documented, not just how much they cost.
| Signal | Points to in-house | Points to outsourced |
|---|---|---|
| Inventory accuracy | You can name the clinical purpose of each circuit today | Nobody can say which circuits are clinical |
| Billing footprint | A stable set of BANs and sites | BANs change with acquisitions, closures, and new clinics |
| Staffing | A dedicated analyst audits line items every cycle | Telecom work is squeezed into IT or AP roles |
| Disputes | Disputes are filed and tracked to credit monthly | Disputes are filed occasionally or not at all |
| Change control | Disconnects already route through clinical approvals | Disconnects happen from spreadsheets or email |
If most of your answers land in the right-hand column, read when you need TEM for the broader warning signs, and see how a managed program divides responsibility in our guide to outsourced TEM.
What to do before your next invoice cycle closes
Before your next cycle closes, pull every BAN, freeze untagged disconnects, and compare one month of invoices against what each site actually uses. Those three steps tell you whether you have a cleanup project or a running program. Every unaudited month repeats the same errors at the same rate.
- Build the BAN list from AP payment history, not from IT records. Payments show what you actually pay for, including accounts IT never knew existed.
- Put a “no tag, no touch” hold on disconnects for any circuit without a tier, effective immediately.
- Pick one hospital and one clinic and match their CSRs to their invoices line by line. The gap between the two is a preview of the whole estate.
- Review every vendor’s access, including what each letter of agency authorizes and who still holds a login.
- Decide who runs the cycle next month, using the in-house versus outsourced signals above.
If you’d rather have RadiusPoint run the first pass, ask us to audit one month of invoices for a hospital and a clinic, or request a demonstration of ExpenseLogic and see the inventory, audit, and approval workflow on your own sites.
Frequently asked questions
Can we cancel phone lines that show no usage on the bill?
Not until you know what’s on the other end. Fire alarm communicators, elevator emergency phones, and some fax lines can sit idle for months and still be required. Treat zero usage as a reason to investigate: trace the line to a device, confirm the owner, and check whether a replacement path exists. Lines that trace to nothing, or to a closed site, are the safe disconnects.
Is there such a thing as a HIPAA-certified TEM vendor?
Not in any official sense. HHS says it doesn’t endorse or recognize private organizations’ HIPAA Security Rule “certifications,” and those certifications don’t relieve anyone of legal obligations. Ask a TEM vendor for evidence instead: how it keeps PHI out of telecom data, a signed BAA if PHI will flow, its access controls, a sample activity log, and any independent audit reports it can share.
Does our telecom carrier need to sign a business associate agreement?
Usually not for pure transmission. HHS treats transmission-only services, with no storage beyond what’s temporary and incidental to transmission, as conduits rather than business associates. That changes when a provider stores or maintains PHI for you, as cloud services do. Confirm each vendor’s role with your privacy officer, and don’t assume a carrier’s conduit status extends to the TEM provider auditing its bills.
How does healthcare TEM handle acquisitions, divestitures, and closed clinics?
It treats site status as an audit input. When a health system acquires a practice, that practice’s BANs, contracts, and circuits enter the inventory and get tiered before anything changes. When a site closes or sells, closed-location billing exception reports flag charges that keep arriving, and Tier 1 lines are handed over or migrated deliberately rather than disconnected by default.
What should we hand a TEM provider in the first week?
Start with the most recent invoice for every billing account number, your carrier contracts and amendments, a site list showing open, closed, and sold status, and a letter of agency scoped to records and disputes. Add your approval matrix for clinical changes and an HR roster feed for wireless lines. Leave patient information out entirely, because a TEM program doesn’t need it.
References
- U.S. Department of Health and Human Services, Business Associates guidance
- U.S. Department of Health and Human Services, FAQ on the conduit exception for transmission services
- U.S. Department of Health and Human Services, FAQ 2003 on Security Rule “certification”
- Electronic Code of Federal Regulations, 45 CFR 164.312, Technical safeguards
- Federal Register, HIPAA Security Rule to Strengthen the Cybersecurity of Electronic Protected Health Information (proposed rule, January 6, 2025)
- Holland & Knight, HIPAA Security Rule Amendments Now Projected for July 2027 (July 2026)
- Federal Communications Commission, Report and Order, Accelerating Network Modernization, FCC 26-19 (March 2026)
- Enterprise Technology Management Association, IT and Telecom Inventory is Critical to TEM Success
- Capterra, ExpenseLogic reviews
- Amalgam Insights, 2024 Telecom Expense Management Vendor SmartList
- RadiusPoint, Healthcare Case Study: Telecom Expenses Down by 26% in Healthcare (linked above)
- RadiusPoint, Telecom Expense Management in Healthcare: Implementing Best Practices case study (linked above)
Latest updates
Published October 8, 2026.
This guide is general information about telecom expense management operations. It isn’t legal or compliance advice, and it doesn’t determine whether any vendor is a business associate under HIPAA; confirm that with your privacy officer and counsel. Case study results describe specific published engagements and don’t guarantee results for other organizations.