What Epic’s Push Into Dental Could Mean for Healthcare

PDS Health has spent years making dental-medical integration a central operating thesis. The organization describes itself as the first large U.S. dental group to implement Epic across its supported practices, creating a shared record that combines oral and medical histories. PDS argues that shared access lets providers coordinate care, identify systemic risk earlier and support a more complete picture of the patient. Those are company claims, but the infrastructure behind them is concrete. ⁵

The significance is not simply that dentists at PDS can see medical records. A large dental organization had to redesign workflows, train clinicians, integrate imaging and dental-specific processes, connect revenue-cycle operations and make a medical-grade EHR function inside hundreds of dental settings. That implementation experience has itself become a product.

PDS Health Technologies is now extending dental-optimized Epic infrastructure, operational services and revenue-cycle expertise to outside organizations. PDS describes the business as serving dental schools, health systems, DSOs and private practices seeking stronger clinical and operational performance. That is a notable evolution: a dental operator is commercializing the systems it built to integrate oral health with the rest of healthcare. ⁷

The external deployments are no longer hypothetical. In March 2026, PDS Health Technologies announced a partnership with University of the Pacific to implement its dental-optimized Epic instance across the Arthur A. Dugoni School of Dentistry, the Pacific HealthCare Collaborative and a future ambulatory surgical center. PDS called it a first-of-its-kind academic deployment spanning dental, medical and surgical settings. ⁶

Epic’s public FHIR documentation is strategically important because it shows dental data represented as standard healthcare resources. Dental findings can be returned through Condition resources. Periodontal readings — including probing depth, gingival margin and clinical attachment level — can be returned through Observation resources. That makes oral data less exotic from an interoperability perspective. ³⁴

This does not mean every EHR can instantly understand every dental workflow. Dental charting is unusually granular, imaging-heavy and tooth-specific. But the existence of public interfaces means software developers and health systems can increasingly treat dental information as something that can participate in healthcare exchange rather than something locked inside a proprietary dental silo.

Epic says Care Everywhere facilitates more than 30 million patient-record exchanges daily, with around half involving organizations using a different interoperable EHR. It also exposes more than 1,000 APIs and interface specifications. Dentistry entering this environment inherits a level of connectivity that a dental-only software vendor would struggle to recreate independently. ²

That network effect may be more consequential than the dental software itself. When oral health data sits inside a platform already used for medication lists, diagnoses, labs, referrals, care gaps and patient communication, the number of potential cross-domain workflows increases dramatically.

Epic has highlighted medication safety as one of the clearest benefits of integrated records in dentistry. Dentists treating people taking anticoagulants, immunosuppressants, cancer therapies or multiple chronic-disease medications can make decisions with a more complete medication and medical history. Epic also points to the ability of dentists to identify high blood pressure and route patients toward medical follow-up. ¹

These use cases are strategically useful because they require very little oral-systemic speculation. No one needs to prove that periodontal treatment prevents myocardial infarction for a shared medication list to be valuable. Integration can create value through safer treatment and better coordination even while larger causal questions remain unresolved.

Epic cited an estimate that more than 28 million Americans had seen a dentist in the prior year but not a medical doctor. For those patients, the dental office may be the only routine healthcare setting they enter. Shared records create the possibility that screening in dentistry becomes visible to medicine and that referrals can be integrated into the same patient story. ¹

The operational challenge is closing the loop. A screening without a completed referral is only a data point. A shared record without defined responsibility can become another source of alerts. The organizations that make integration work will need to design workflows that specify who sees the signal, who contacts the patient and how completion is measured.

Traditional dental software has generally been optimized for scheduling, charting, insurance billing, imaging and practice management. That remains essential. But if more dental organizations operate inside comprehensive health records, software buyers may begin valuing medical interoperability, enterprise security, shared patient identity and population-health capabilities more heavily.

This does not mean Epic will displace every dental PMS. Many practices will continue to prefer specialized, lower-cost dental systems. The more plausible shift is segmentation: health systems, academic institutions, integrated groups and large DSOs with medical ambitions may increasingly view a comprehensive record differently from independent practices whose operational needs remain primarily dental.

Academic deployments matter because they shape clinician expectations. A dental student trained in an environment where medical history, oral findings and interdisciplinary care live in the same record may view separation as an artifact rather than a default. University deployments can also create research datasets that link oral and systemic outcomes more effectively than disconnected records do.

The University of the Pacific announcement is particularly notable because the planned implementation crosses dental, medical and ambulatory surgical settings. That creates an educational environment in which integration is part of the underlying infrastructure rather than an elective rotation or referral protocol. ⁶

Health plans have long had an intellectual interest in the connection between oral and systemic health. Their practical problem is that medical and dental data often arrive through different systems. Shared records will not solve benefit fragmentation, but they can create better clinical data for evaluating interventions, identifying risk and measuring whether dental care changes broader utilization.

If oral-health data becomes easier to access in structured form, payers and integrated delivery systems can test narrower questions. Does periodontal status add predictive signal for uncontrolled diabetes? Do dental screenings identify hypertension earlier? Does integrated referral improve completion? Does medication reconciliation reduce avoidable adverse events? Those are measurable healthcare questions rather than category slogans.

Oral-systemic science is limited in part by fragmented datasets. Many studies rely on claims, surveys or small clinical cohorts because longitudinal dental and medical records are difficult to connect. A comprehensive record can support more robust analyses of temporal relationships, interventions and outcomes — provided researchers remain disciplined about confounding and causal inference.

This could be one of Epic’s least discussed contributions to oral health. The company is not merely helping dentists see medical records; it may be helping create data environments where oral findings can be studied alongside labs, diagnoses, medications and utilization at scale.

Epic is expensive, complex and designed for enterprise healthcare. Dental organizations must adapt workflows that are different from medicine. Revenue-cycle logic, insurance estimation, imaging, tooth-level charting and appointment patterns do not map perfectly onto medical operations. PDS Health Technologies exists in part because dental optimization requires specialized implementation expertise. ⁷

There is also a risk that the technology becomes the story while outcomes remain unmeasured. Shared records should eventually be evaluated against concrete endpoints: medication reconciliation, referral completion, screening follow-up, clinician burden, patient experience and health outcomes. Infrastructure is necessary, but infrastructure alone is not proof of integration.

Watch the next set of adopters. If more dental schools, integrated health systems and large DSOs choose comprehensive EHR models, that would suggest the PDS approach is becoming replicable. Watch payers for benefit programs that explicitly use shared dental-medical data. Watch Epic’s dental API surface for deeper support. And watch whether external developers begin building applications that use oral data through the same FHIR ecosystem as medical data.

Another signal would be competitive response. If dental software vendors accelerate FHIR support, medical integrations and shared-record capabilities, Epic may reshape the market even without becoming the dominant dental platform. A credible enterprise alternative changes buyer expectations.

Epic’s push into dental is not primarily a dental-software story. It is an infrastructure story. More than 2,300 dental clinics are now part of an Epic community that can operate with a shared medical record, and public APIs already expose dental findings and periodontal observations in healthcare-standard formats. ¹³⁴

PDS Health is the most visible proof point because it has moved from internal adoption to external commercialization through PDS Health Technologies. If that model continues spreading into dental schools, health systems and large provider groups, the long-term effect may be straightforward but profound: oral health data will increasingly stop living in a separate universe and start behaving like the rest of healthcare data.