Epic’s Dental Bet Is Becoming a Healthcare Infrastructure Story

Dentistry has spent decades arguing that oral health belongs inside healthcare. PDS Health and Epic are testing a more consequential proposition: what happens when dentistry actually operates on healthcare infrastructure? The answer is beginning to move beyond philosophy. Epic says more than 2,300 dental clinics now use its platform, while PDS Health Technologies is taking a dental-optimized Epic environment that was built for a national dental organization and offering it to universities, health systems, DSOs and private practices. That makes the PDS-Epic relationship less a dental software story than an infrastructure story about whether oral health data can become part of the longitudinal health record. ¹²

The distinction matters. Medical-dental integration is often discussed as a clinical aspiration: physicians should pay more attention to oral health; dentists should recognize systemic risk; benefits should become more coordinated. But integration cannot scale on aspiration alone. It needs a common data layer, workflows that clinicians will actually use, identity matching, medication and allergy visibility, referral pathways, billing logic, imaging access, patient communication and governance. PDS has spent years building those capabilities around Epic. It is now trying to turn that internal operating system into external infrastructure. ²³

That is the story Oral Signal is watching. The strategic question is not whether Epic is a better dental practice-management system than every incumbent. It is whether a medical-grade, interoperable health record changes what dentistry can become when oral data no longer lives in a separate software universe. ¹

PDS Health's Epic journey predates the current wave of medical-dental integration enthusiasm. In 2022, then-Pacific Dental Services announced that it had completed deployment of Epic across all of its supported dental practices. PDS described itself as the first dental support organization of its scale to do so. The implementation centered on Epic's dental module, Wisdom, but the strategic value was broader: dental professionals could view medical history, medications, laboratory information and other clinical data in the same record used elsewhere in healthcare. Patients could also see dental and medical information through MyChart. ³

The implementation solved a structural problem that is easy to underestimate. Traditional dental software was designed around the dental encounter: scheduling, treatment plans, imaging, insurance estimates, claims and collections. Medical EHRs were designed around a different clinical and reimbursement environment. When those systems remain separate, integration usually depends on interfaces, document exchange, phone calls, patient recollection or one-off referral workflows. A shared record changes the default. The dentist does not have to request a separate medical history every time a relevant decision arises; the medical context can already be present. ⁹¹⁰

PDS did not stop at internal deployment. PDS Health Technologies now describes a business that provides a dental performance platform built on Epic, along with revenue cycle management, practice operations support, consulting and staffing. The company says the platform serves more than 1,100 connected practices across more than 24 states and has served more than 13 million patients. Those figures are company-reported, but they establish the scale of the environment PDS is attempting to commercialize. ²

This is an important evolution in the business model. A DSO normally creates technology advantages for its own supported practices. PDS is doing something different: packaging part of its operating infrastructure for outside institutions. Through Epic Community Connect, PDS Health Technologies can extend its configured Epic environment to other organizations rather than requiring each dental institution to build an Epic dental instance from scratch. ²⁴

The product, in other words, is not merely software access. It is accumulated implementation knowledge: dental workflows, configurations, reporting, revenue-cycle alignment and operating processes developed at national scale. That is potentially more defensible than simply reselling an EHR license because the difficult part of enterprise software is often not the underlying code. It is making the software work in a specific clinical environment. ¹

The strongest evidence that this model is extending beyond PDS's own network is coming from academic dentistry. In November 2025, PDS Health Technologies announced a partnership with the University of Michigan School of Dentistry to implement its Epic electronic health record platform through Community Connect. PDS said its instance had served more than 13 million unique patients and processed more than half of all dental visits in Epic globally. Again, those utilization figures come from PDS, but the customer decision itself is significant: a major dental school chose an externally operated dental Epic model for its next-generation clinical infrastructure. ⁴

The pattern continued. PDS's 2025 year-end report cited academic relationships with Michigan, the University of the Pacific Arthur A. Dugoni School of Dentistry and Roseman University. In March 2026, PDS announced that University of the Pacific would deploy Epic across medical, dental and surgical centers. In June 2026, ADA Forsyth Institute selected PDS Health Technologies to implement the Epic platform at Forsyth Faculty Associates. The sequence suggests that Community Connect may provide a practical path for dental schools and oral-health institutions that want medical-grade interoperability without independently reproducing PDS's years of configuration work. ⁵⁶

Academic adoption matters for another reason: training. If dental students learn inside a shared health record, medical-dental integration becomes less of a post-graduate behavior change and more of a default workflow. Roseman explicitly framed its Epic implementation as a way to expose students to integrated, patient-centered care. That could have a compounding effect. Software shapes what information clinicians see, what actions are easy, what referrals are visible and what constitutes a complete patient history. ⁷

There is still a long distance between several academic implementations and an industry standard. Dental schools have complex requirements, and Epic remains a large-enterprise platform. But the direction is strategically important. Infrastructure choices made by teaching institutions influence workforce expectations, research datasets and the operating models graduates encounter later. ¹

The strongest near-term argument for shared records may not be a dramatic claim that dental treatment prevents heart attacks or lowers total medical cost. It may be something much more concrete: dentists making safer decisions because they can see more complete medication, allergy and medical information. ¹

In January 2026, Epic reported that dentists using its shared medical records helped patients avoid more than 260,000 potential drug interactions during 2025. Epic explained that when a dentist places an order, the system can alert the clinician to potential interactions with existing prescriptions or allergies in the patient's record. The number is notable because it describes a direct workflow consequence of integration rather than an epidemiologic association between oral and systemic disease. ¹

“With access to the comprehensive health record, they can act on that role with more information.” — Seth Howard, Epic ¹

The metric still requires careful interpretation. An alert for a potential drug interaction is not the same thing as a documented adverse event prevented. The public Epic material does not provide, in that announcement, a peer-reviewed evaluation of alert severity, override rates, counterfactual harm or clinical outcomes. Oral Signal therefore would not describe 260,000 alerts as 260,000 proven injuries prevented. But it is evidence of a real mechanism: shared information can change what a dentist sees at the moment of prescribing. ¹

That mechanism is particularly relevant as patients age and medication lists become more complex. Dental prescribing does not happen in isolation from anticoagulants, diabetes therapies, immunosuppressants, cardiovascular drugs, allergies or medications that affect salivary function and oral health. A connected record can make those relationships visible without relying entirely on a patient to reproduce a current medication list from memory. ¹

Epic also points to another population-health opportunity. It cites an estimate that roughly 9% of Americans — more than 28 million people — saw a dentist in the prior year but not a medical doctor. If a dental visit is the only healthcare encounter for a meaningful subset of the population, the dental chair can become a screening and navigation node for hypertension, diabetes risk and other conditions, provided there is a reliable way to document findings and route patients into medical care. ¹

A shared EHR by itself does not create integrated care. It creates the possibility of integrated care. PDS's broader strategy is interesting because the organization is layering screening, co-located care and diagnostics on top of the record. ¹

PDS reported more than 7.5 million patient visits across more than 1,000 practices in 2025 and said it continued opening primary-care practices connected to dental locations. It also reported expanded use of chairside HbA1c and aMMP-8 screening and said shared dental and medical records supported the exchange of hundreds of millions of patient records. These are PDS-reported operational metrics rather than independent outcome studies, but they show the intended architecture: screening produces a signal, the shared record preserves the signal, and an integrated care network can potentially act on it. ⁵

In May 2026, CareQuest Innovation Partners and PDS Health announced results from a six-month effort to scale blood-pressure screening and consultation in dental offices. The initiative is another example of dentistry functioning as an entry point into broader preventive care. The important infrastructure question is what happens after an elevated reading: whether it is documented in a place other clinicians can see, whether a referral closes, and whether the patient receives appropriate follow-up. ⁸

PDS is also connecting imaging to the same environment. In December 2025, it announced a strategic investment in SOTA Cloud and a planned rollout across more than 1,000 dental practices. PDS said the cloud imaging platform would integrate into its Epic-based environment and contribute imaging data to the patient's health record. If executed well, that moves another traditionally siloed dental data type closer to the longitudinal record. ⁹

The strategic pattern is increasingly clear: Epic is the record layer; screening and diagnostics generate new signals; imaging contributes clinical context; connected dental and primary-care sites create an intervention path; and PDS Health Technologies packages the infrastructure for outside organizations. ¹

Oral-systemic health has an evidence problem and a translation problem. The evidence problem is that associations are often communicated more strongly than the underlying science supports. The translation problem is that even when an association is credible, healthcare organizations still need a workflow that turns information into action. ¹

The PDS-Epic story is valuable because it sits primarily on the translation side. It does not require us to claim that periodontal treatment prevents cardiovascular events. A dentist seeing an anticoagulant in the medical record is useful regardless of whether a disputed causal pathway is eventually proven. A blood-pressure reading that reaches the broader care team is useful because it can trigger follow-up. A medical clinician seeing relevant dental history can improve context even if oral data is only one small part of the patient's risk profile. ¹

This is the more durable version of the 'oral health is healthcare' thesis. Oral health does not need to be the hidden cause of every chronic disease to deserve a place in healthcare infrastructure. It needs to contain information that can improve decisions, coordination, safety or access. ¹

Epic's strategic position in this market comes from something dental software companies cannot easily reproduce: its footprint across the medical delivery system. A dental EHR can have excellent dental workflows and still leave oral data isolated if the rest of healthcare cannot readily consume it. Epic's value proposition is that the dental record can sit inside an ecosystem already used by hospitals, health systems and physicians. ¹

That does not automatically make Epic the right solution for every dental practice. Cost, implementation complexity, workflow fit, revenue-cycle requirements and organizational scale matter. Many independent practices will reasonably prefer purpose-built dental platforms. The question is different for large DSOs, academic institutions and health systems that view interoperability as a strategic capability rather than a convenience. ¹

Epic says more than 2,300 dental clinics are now using its platform. That is still a fraction of U.S. dentistry, but it is enough to create a meaningful installed base. If dental adoption continues through Community Connect and health-system relationships, Epic could become one of the bridges through which oral data enters mainstream clinical infrastructure. ¹

The competitive implication is subtle. Dentistry may not need to build a completely separate interoperability ecosystem and then persuade medicine to connect to it. One path is for dentistry to join infrastructure medicine already uses. PDS's bet is that it can make that path operationally viable for dental organizations. ¹

PDS Health Technologies creates a second story beyond clinical integration: the emergence of a healthcare technology and services business inside a large dental support organization. The unit offers Epic implementation and configuration, revenue cycle management, consulting, staffing and operational support. That bundle looks less like a traditional DSO service center and more like an enterprise healthcare-services platform. ²

The addressable market is broader than PDS's own supported practices. Dental schools need clinical systems. Health systems with dental programs need interoperability. DSOs need scalable workflows and revenue-cycle infrastructure. Private practices affiliated with larger health ecosystems may want access to shared records. PDS Health Technologies explicitly lists all four groups as target industries. ²

There is an important flywheel if the model works. More external organizations on the PDS-configured Epic environment can create more implementation knowledge, more standardized workflows and potentially richer opportunities for benchmarking and research. Academic partners can create training and research relationships. A larger network can make integration with diagnostics, imaging and other tools more attractive. None of those benefits is guaranteed, but the platform logic is visible. ⁹¹⁰

It also changes how PDS should be analyzed. The company is still fundamentally an integrated healthcare support organization with a very large dental footprint. But its technology arm increasingly deserves to be evaluated as a standalone strategic asset: a distribution channel for dental Epic, a services organization and a possible infrastructure layer for institutions trying to connect oral and medical care. ¹

The story is compelling precisely because it should not be overstated. Most of the scale and performance metrics available publicly come from PDS Health or Epic. The 260,000 potential drug-interaction figure is meaningful but is not equivalent to 260,000 independently adjudicated adverse events prevented. Claims about earlier detection, better outcomes and lower costs require controlled evaluation rather than assumption. ¹⁵

We also do not yet have enough public evidence to conclude that a shared dental-medical EHR produces lower total cost of care at scale. That would require patient-level outcome studies, matched comparison populations, careful adjustment for selection effects and transparent definitions of utilization and savings. The same applies to claims that dental screening materially changes long-term chronic-disease outcomes. ¹

There are operational questions too. How much does implementation cost? How long does it take? How well do dental revenue-cycle workflows perform relative to incumbent systems? How portable is PDS's configuration to organizations with different payer mixes and clinical models? How much customization is required? How are dental images surfaced to medical users without creating information overload? How consistently do referrals close? ¹

Those are not reasons to dismiss the model. They are the questions that determine whether integration becomes infrastructure rather than a showcase project. ⁹¹⁰

The next phase should be judged by adoption and outcomes. First, does PDS Health Technologies continue adding institutions outside its own network? The Michigan, Pacific, Roseman and ADA Forsyth relationships create an early cohort worth following. Second, does Epic's dental-clinic footprint continue expanding beyond 2,300 sites? Third, do PDS and its partners publish stronger outcome evidence around medication safety, screening, referral completion and chronic-disease management? ¹⁴⁶

Fourth, watch the payer layer. Shared records become more economically powerful if benefit design and reimbursement reward coordination. PDS says it works with payers, Medicare Advantage plans and employer groups around integrated preventive care. If dental-generated screening or periodontal interventions become connected to medical quality programs, risk contracts or benefit design, the EHR becomes more than a clinical record; it becomes part of the economic infrastructure of integration. ¹⁰

Fifth, watch data rights and research. A large longitudinal dataset containing dental and medical information could be unusually valuable for studying which oral signals add predictive value, which interventions change outcomes and which populations benefit. Academic partnerships make that possibility more interesting. The opportunity will require rigorous governance, privacy protections and transparent research methods. ¹

Healthcare has historically treated dentistry as adjacent to medicine: a separate benefit, separate software category, separate provider network and often a separate clinical record. PDS and Epic are attacking one of the deepest layers of that separation — the information architecture. ¹

That does not mean Epic will become the operating system for all of dentistry. It does not mean every oral-systemic hypothesis will prove clinically useful. And it does not mean interoperability alone fixes fragmented benefits, incentives or care delivery. ¹

But infrastructure changes what is possible. When the dentist can see the medical record, when a physician can see relevant oral information, when screening results can travel with the patient, when medications are reconciled against one chart, and when academic institutions train clinicians inside that environment, oral health becomes harder to treat as an isolated category. ¹

The most important part of the PDS-Epic story may be that dentistry is not building another silo. It is building a door into healthcare's existing one. ¹

For Oral Signal, that is the signal: the mouth-body connection is beginning to acquire an operating system. ¹