Reading Perio Charts Through the API: Dentrix and Beyond
Six-point pocket depths, recession, bleeding, mobility — the periodontal chart is one of the richest clinical datasets in the practice, and one of the hardest to get out of the PMS. Here is what is in it, and how to work with it through an API.
What a perio chart actually contains
The periodontal chart is a full-mouth clinical survey of the tissues that hold teeth in place. It is measured tooth by tooth, and for each tooth the hygienist records up to six sites: mesial-buccal, buccal, distal-buccal on the cheek side, and mesial-lingual, lingual, distal-lingual on the tongue side. Thirty-two teeth times six sites is a lot of numbers, and each site can carry several measurements.
At each site the clinician records the probing depth (PD) — how many millimeters the probe slides into the pocket — and the gingival margin (GM), the position of the gum edge relative to the cementoenamel junction. Where the gum has pulled back, that is recession. Bleeding on probing (BOP) is a yes/no flag per site, and suppuration notes pus on probing. Per tooth there is mobility (graded 0–3), furcation involvement (I–III, where the roots split), plaque scores, and the position of the mucogingival junction.
The single most important number is one you rarely probe directly: clinical attachment level (CAL). CAL is, roughly, probing depth plus recession — the total distance from a fixed anatomical landmark down to the base of the pocket. Pocket depth alone can mislead you; gums swell and shrink. CAL measures the real, irreversible loss of the attachment apparatus. It is the metric that actually tracks disease progression over time, and it is why a chart taken today is worth so much more when you can compare it to one from a year ago.
Why it is so hard to get out of the PMS
Most clinical data in a practice management system is a row: one patient, one appointment, one procedure code, one fee. Perio data is not a row. It is a matrix — tooth by site by measurement type by exam date — and that nesting is exactly what makes it hard to extract.
Every PMS stores it idiosyncratically. Some keep a flat table keyed by tooth number and site index. Some encode the whole exam as a packed binary blob. Some split probing depths from recession into separate measurement streams that only make sense when you rejoin them. And almost none of them expose a clean, documented way to read the exam back out. The vendor reporting tools will print you a chart on paper; they will not hand you the structured data behind it.
So a product team that wants perio data faces the worst kind of integration: deeply nested, stored differently in every system, and rarely surfaced by any official interface. Getting it once, for one PMS, is a project. Getting it consistently across Dentrix, Eaglesoft, Open Dental, and the rest is the kind of thing that quietly kills a roadmap.
The Dentrix case, specifically
Dentrix is a good concrete example because its perio module is widely used and its measurement model is well defined. Dentrix’s default perio script captures a set of measurement types including Probing Depths, Gingival Margin, Clinical Attachment Level, and Mucogingival Junction. Each is recorded per tooth and per site, which is how you reconstruct the six-point picture for a full exam.
CRMBridge supports perio for Dentrix in both directions. You can read an existing perio exam out as structured data, and you can perform perio writeback — writing a full perio exam back into the patient’s chart so it appears natively in the Dentrix perio module, exactly where the hygienist and dentist expect to find it. That matters for any product that captures perio measurements on its own device: the reading has to land in the real chart, not a parallel database. The endpoint details live in the docs at /documentation#create-perio-chart.
What perio data unlocks
When perio comes out as clean, structured, dated data, it stops being a paper artifact and starts being a feature. A few of the products it enables:
Perio AI and risk scoring.
Full-mouth PD, CAL, and BOP are exactly the inputs a periodontal risk model wants. Feed them in and you can stage and grade disease, flag patients trending toward active periodontitis, and surface the ones who need attention before the next recall.
Treatment acceptance.
Case presentation for scaling and root planing lands better with the numbers on screen. Showing a patient the sites with 5–6mm pockets and bleeding — their own chart — turns an abstract SRP recommendation into a picture they accept.
Recall and reactivation.
Perio patients are on a maintenance interval, and the ones who lapse are the ones who relapse. Structured exam dates let you find everyone overdue for perio maintenance and pull them back before the attachment loss compounds.
Longitudinal tracking.
Because CAL is the disease-progression metric, charting CAL per site across successive exams shows whether therapy is holding or the pockets are deepening. That trend line is the clinical story, and it only exists if you kept the exam dates.
Hygiene productivity.
Perio drives a large share of hygiene revenue. Knowing which patients have unaddressed perio findings, and which are due for maintenance, is a direct line to a fuller hygiene schedule and better-utilized chairs.
A note on modeling the data
When you pull perio out, resist the urge to flatten it immediately into one wide row per patient. The natural shape is a list of measurements, where each measurement is { tooth, site, type, value, examDate }. Keep that granularity. A wide, one-row-per-exam table is convenient for a single report and hostile to everything else — you lose the ability to query by site, to trend a single tooth, or to add a measurement type later without a schema migration.
Above all, keep the exam date on every measurement. Perio is only valuable longitudinally; a chart without a date is a snapshot you cannot compare. The date is what turns a pile of millimeters into a trend.
{
"tooth": 4,
"site": "distal-buccal",
"probingDepth": 6,
"recession": 2,
"cal": 8,
"bop": true
}One record like this per site, per exam. Collect them into an exam, stamp the exam with its date, and you have something you can score, present, trend, and act on — instead of a printout in a drawer.
Where clinical AI and hygiene revenue meet
Perio is a rare place in dentistry where the clinical frontier and the revenue frontier sit on top of each other. It is the data periodontal AI needs to stage disease, and it is the data the practice needs to keep hygiene chairs full and patients in maintenance. Both stories run through the same matrix of numbers.
The barrier has always been getting that matrix out — and back in — reliably, across the systems real practices actually run. Solve that with one API, and you unlock a class of products that were previously impossible to build: perio-driven risk scoring, case presentation, recall, and longitudinal tracking that work the same whether the practice is on Dentrix or anything else.
Build on the richest data in the operatory.
CRMBridge lets you read and write full periodontal exams — probing depths, recession, CAL, bleeding, and more — across connected practice management systems through one API. No per-PMS reverse engineering, no parallel database.