Find out everything about the vision, mission, and the people who shape CompuGroup Medical worldwide. Investors will also find helpful information, documents, and other publications.
Running an anatomic pathology lab inside a physician practice means wearing a lot of hats. The pathologist is focused on diagnostic accuracy. The lab director is managing workflow, staffing, and compliance.
Somewhere in the background is the relationship with the LIS (laboratory information system) vendor. The billing vendor. The platform handling remote monitoring.
Most practices haven't gotten this far. It's not because the opportunity isn't there, but because adding another vendor feels like more complexity piled onto an already full plate. That instinct makes sense on the surface, but it gets expensive over time.
Practices that have consolidated their LIS, revenue cycle management, and remote patient monitoring under a single enterprise vendor aren't simply streamlining their vendor list. They're closing revenue gaps they didn't know existed, eliminating the interface maintenance that quietly consumes IT resources, and positioning themselves to offer services their current setup doesn't support.
Start with the basics. Surgical pathology, GYN cytology, molecular reflex testing, and prostate workup each carry distinct documentation requirements and workflow logic. A system that handles surgical cases cleanly but forces manual workarounds on GYN cytology creates daily friction that compounds across hundreds of cases a month. It doesn’t show up as a line item. It shows up as staff fatigue and turnaround time that’s always a little longer than it should be.
Compliance adds another layer of complexity. The College of American Pathologists Laboratory Accreditation Program sets standards built from the input of more than 500 pathologists, updated annually, and enforced through peer inspection. Audit trails, QC workflows, and documentation practices have to hold up when an inspector walks in. An LIS that treats compliance as an afterthought creates exposure that tends to surface at the worst possible moment.
Beyond compliance, a modern, cloud-based anatomic pathology LIS should deliver the following without requiring add-on purchases or workarounds:
The more consequential question is whether the vendor designed its system for anatomic pathology specifically, or adapted a clinical lab platform and called it close enough. The difference becomes obvious the moment a demo gets specific about prostate diagram reporting or gross macro depth.
When labs come to us after years of struggling with a disconnected billing setup, the problem is almost never the coders. It's the broken data connectivity. Once the clinical and billing workflows are running from the same foundation, those headaches disappear.
Pathology billing is difficult. It is structurally demanding in ways that create real financial exposure for labs that aren't paying close attention.
Anatomic pathology CPT® codes run from 88000 through 88399. Clinical pathology occupies an entirely separate range.
Technical and professional components frequently require separate billing. A single case can involve multiple specimens at different complexity levels, each requiring accurate ICD-10 coding to establish medical necessity. Omit a modifier, miss a CLIA certification number, or let a medical necessity code slip through unchecked, and the claim fails.
The Clinical Laboratory Improvement Amendments, administered by CMS, set the regulatory baseline that every billing operation navigates daily.
When the LIS and the RCM platform belong to different vendors, the handoff between them is where claims quietly deteriorate. Data fields may not map cleanly between systems built independently. One vendor pushes an update. The interface breaks. Nobody catches it until the denial rate climbs two weeks later and someone starts pulling reports at 10 o'clock on a Tuesday night.
An RCM service operating in genuine coordination with a purpose-built, AP LIS removes that handoff risk. The data driving a claim comes from the same ecosystem as the clinical workflow. CO-16 rejections tied to missing documentation don't originate from a translation error between platforms that were never designed to talk to each other.
Not every AP lab is a standalone reference facility. Many operate inside gastroenterology practices, urology groups, dermatology centers, and multispecialty organizations. These settings have something a pure reference lab doesn't: an established Medicare patient population, active physician billing infrastructure, and chronic disease management already woven into daily clinical operations.
A GI practice managing a patient with long-term IBD already has the physician relationship, the documentation history, and the billing enrollment that support additional reimbursable services. The same is true of a urology group monitoring patients following oncologic treatment, or a dermatology practice managing patients on systemic biologics. The clinical work is largely happening, but the billing for it often isn't.
Medicare's remote physiologic monitoring codes are active and reimbursable today. For a practice already managing chronic conditions in a Medicare population, this is revenue attached to clinical activity that is already occurring—and recent CMS updates have made more patients eligible than ever.
Effective January 1, 2026, CMS finalized two new CPT codes that lower the thresholds for participation, meaning patients who previously fell outside billing requirements can now be included in an RPM program. The full current code set breaks down as follows:
The addition of 99445 and 99470 is meaningful for practice-affiliated labs. The previous 16-day data threshold excluded patients who monitored inconsistently but still benefited from clinical oversight. The new 2-day minimum brings those patients into the billable window. CMS has also confirmed that 99445 and 99454 reimburse at the same rate, so practices aren't penalized for serving patients with shorter monitoring periods.
CMS requirements for the existing codes remain in place: an established patient relationship with the billing provider, documented clinical staff time for review and response, and data collection meeting the applicable threshold for the code being billed. Gastroenterology, urology, and dermatology practices meeting those criteria don't need to reinvent their care model to add RPM. They need a platform that connects monitoring workflow cleanly to the billing infrastructure already in place, without introducing yet another vendor relationship to manage.
For a practice running an AP lab and billing through an integrated RCM service, adding remote patient monitoring through the same vendor is an extension of an existing relationship. The support line is the same. The contract is the same. The implementation doesn't start from zero.
Practices performing both clinical laboratory testing and anatomic pathology work often find themselves maintaining two LIS platforms, or one platform attempting to serve both disciplines without being genuinely built for either.
Interfaces between a clinical LIS and an AP LIS are expensive to build and sometimes unreliable. Separate vendors operate on separate release schedules and don't coordinate updates with each other. When those systems fall out of sync, the consequence isn't just an IT ticket. Inconsistent data surfaces at sign-out. Reconciliation work lands on the lab director. Claims get held.
At CompuGroup Medical, we've seen this pattern get resolved when labs make the decision to bring their clinical and AP operations under a single vendor.
One such lab had been juggling a clinical LIS, a billing service, and an AP workflow handled by a third platform that created persistent friction at every billing handoff. Moving to a model where CGM LABDAQ, CGM AP EASY, and ARIA RCM Services operated as a coordinated portfolio changed the accountability structure entirely. When something needed attention, there was one conversation to have rather than three.
That kind of consolidation does something a well-maintained interface never quite manages: it puts a single vendor on the hook for the outcome, not just the component.
Vendors claiming all-in-one LIS and RCM solutions are easy to find. Vendors that can demonstrate genuine depth across pathology lab management software, RCM, and RPM in a pathology-specific context are one of a kind. A few questions cut through the noise quickly.
On the LIS side, ask to see GYN cytology and prostate reporting workflows demonstrated in a live environment, not described in a slide deck—these are the specialty-specific capabilities that separate a purpose-built AP system from a clinical lab platform that's been stretched to cover anatomic pathology. Ask about gross macro support, including whether the system handles variable tokens that adapt to specimen-specific data rather than requiring separate macros for every scenario. Ask how the vendor approaches synoptic reporting and what their development roadmap looks like in that area.
Someone showing a platform with shallow roots in anatomic pathology will either skip these questions or answer them vaguely.
On the RCM side, KLAS Research is the standard for independent healthcare IT evaluation. Best in KLAS recognition in an RCM category reflects the documented experience of actual customers. Ask the vendor specifically how they handle the denial categories most common in AP billing—CO-4, CO-16, CO-97, and CO-167 each have distinct causes and resolution paths, and a billing partner with real pathology experience can describe them without hesitation.
On the RPM side, the question is straightforward: does the monitoring workflow connect directly to the existing billing infrastructure, or does it require a separate platform and a separate implementation? If the answer involves a third-party referral, that's worth knowing before the contract conversation starts.
Switching an LIS is not a minor project, and the right vendor should welcome challenging questions.
Pin down the implementation timeline and ask specifically what parallel processing looks like during transition. Data migration from a legacy system should be the vendor's responsibility. Interface rebuilds to existing EHR and billing connections should be scoped and priced in the contract before signing. Change orders discovered six weeks into go-live are a sign that the scoping conversation didn't go deep enough.
Ask for reference clients in a comparable setting—a practice-affiliated AP lab of similar size and specialty mix, live on the platform for at least two years. Call them directly. Ask about the implementation experience, not just the day-to-day performance. Those are genuinely different conversations and they tend to produce different answers.
Ask about the vendor's scale and long-term product investment. A platform serving a lab's LIS, RCM, and RPM needs is a multi-year infrastructure commitment. A vendor with more than 8,700 employees across 19 countries carries a different risk profile than a smaller platform, regardless of how polished the demo looks.
The labs that will be in the strongest position five years from now aren't necessarily the ones making the biggest equipment investments today. They're the ones that looked honestly at their operational infrastructure, identified where fragmentation was costing them, and made a deliberate decision to address it.
For a practice-affiliated AP lab running clinical testing alongside anatomic pathology, billing into Medicare, and positioned to offer remote patient monitoring to a chronic disease population, the consolidation opportunity is concrete.
The vendor capable of supporting all three—with the product depth, third-party recognition, and a track record to back it up—is worth finding before the next interface breaks at 10 o'clock on a Tuesday night.
An anatomic pathology LIS is laboratory information system software built specifically for AP workflow—surgical pathology, GYN cytology, cytopathology, prostate reporting, and related disciplines.
A clinical LIS handles high-volume quantitative testing such as chemistry, hematology, and microbiology. Some vendors offer a single platform attempting to serve both, but purpose-built systems typically offer deeper workflow support, more relevant compliance tools, and better reporting flexibility.
If your lab does both, the evaluation question isn't which type of LIS to choose—it's whether one vendor can deliver genuine depth in both.
Prioritize HIPAA-compliant infrastructure on an enterprise-grade hosting platform, HL7 and API connectivity to your EHR and billing systems, and specialty-specific workflow support for surgical pathology, prostate reporting, and cytology. Cloud deployment should reduce your IT burden, not transfer it.
Ask specifically whether updates are managed by the vendor and how interface maintenance is handled when either platform releases a new version. A vendor that can’t answer that question clearly is telling you something.
Pathology billing involves dual coding structures, technical and professional component splits, and CPT® complexity levels that don’t exist in most other specialties.
Anatomic pathology codes alone span CPT 88000 through 88399, and each case can involve multiple specimens requiring separate coding and medical necessity documentation.
A billing partner with genuine pathology RCM services experience will have specific workflows for the denial categories most common in AP billing and coders who understand laboratory-specific payer policies without needing to look them up.
Yes, provided the practice meets CMS requirements—and as of January 1, 2026, those requirements are more accessible than they used to be. Two new CPT® codes finalized in the 2026 Physician Fee Schedule lowered the minimum thresholds for both data collection and clinical staff time, bringing more patients into the billable window than the original code set allowed.
The billing provider must have an established patient relationship, and documented clinical staff time must be applied to reviewing and responding to patient-generated data. On the data collection side, practices can now bill under CPT 99445 for patients who generate as few as 2 days of monitoring data in a 30-day period, rather than the previous 16-day minimum. For clinical time, the new CPT 99470 covers 10 to 19 minutes of monitoring management per month, lowering the floor from the 20-minute threshold required under 99457.
Gastroenterology, urology, and dermatology practices with in-house AP labs frequently have the patient population and chronic condition profile to support RPM billing across the full code set—99453, 99445, 99454, 99470, 99457, and 99458. Many are already doing the clinical work. The billing infrastructure, and a platform that connects it cleanly to an existing RCM service, is the missing piece.
Interface instability and data inconsistency are the two that show up most often in practice. When two platforms operate on independent release schedules, an update from one vendor can break the connection to the other. When data fields don't map cleanly between systems, incomplete information reaches the billing platform, reconciliation work falls to the lab director, and claim accuracy suffers.
A single vendor providing both a clinical LIS and an AP LIS eliminates the interface maintenance burden and creates unambiguous accountability when something goes wrong.
The terms are frequently used interchangeably, but laboratory information system software typically refers to the core clinical and diagnostic workflow platform—specimen tracking, result entry, reporting, and compliance tools. Lab management software sometimes describes a broader set of operational and administrative functions including scheduling, inventory, and financial reporting.
For anatomic pathology labs, the LIS is the operational foundation. The most important evaluation criteria are AP-specific workflow depth, billing integration, and compliance support—in that order.
It depends on lab size, case volume, and the complexity of existing interfaces. A smaller, practice-affiliated AP lab can go live in 60 to 90 days with a straightforward implementation.
Larger environments with multiple EHR interfaces, high case volume, or both clinical and AP disciplines to migrate typically need longer parallel processing periods.
Data migration, interface rebuilds, and staff training are the three variables that most commonly extend timelines. Get all three scoped and priced before signing anything.
