The numbers tell you what's there. The pattern tells you what it means.
Gum disease isn't caused by one bacterium crossing one threshold. It emerges from how bacteria combine. That's exactly what a list of detection levels can't show you - and what OraPath is built to.
A list of levels asks every clinician to reconstruct the same biology, by hand.
Most saliva reports hand you a column of bacteria and a column of numbers, then leave the interpretation to you. The trouble is that the clinically important information lives in the relationships between bacteria - and those relationships don't show up in a list.
So the same report gets read three different ways by three different team members. The hygienist sees the tallest bar. The dentist scans for familiar names. Nobody is wrong, exactly - but nobody is seeing the whole community.
Reading raw levels well takes training, time, and consistency that a busy operatory rarely has on every patient, every visit.
Nothing here is "high." Easy to call this low-concern. The biology says otherwise.
Same-looking numbers. Very different risk.
Four illustrative specimens. Toggle between them. Each time, see what the raw bars suggest - then what the pattern actually is.
Specimen A
Raw detection levelsSpecimens A-D are illustrative examples built to demonstrate OraPath's pattern-first interpretation - not real patient results. Results are interpreted by a qualified provider alongside clinical findings and patient history.
The patterns OraPath detects.
Each card is a representative profile in the same Detection-Level format your report uses — scroll across to see how each named pattern reads at the chair.
Pattern-first, level-informed - and you can still check the math.
Patterns evaluated in priority order
Every specimen is matched against defined bacterial patterns - from low burden through synergistic and severe multi-pathogen profiles - and the dominant combination drives the Periodontal Risk Score, not a single threshold.
Levels still differentiate within a pattern
Detection levels aren't discarded - they sharpen the read. Isolated Aa at a high level, for example, is treated more seriously than at a low level, because its leukotoxin activity warrants it even without co-pathogens.
Prioritized clinical focus areas
The report surfaces the few highest-priority next steps for that specific specimen - care urgency, targeted interventions, retest timing - so your team acts on conclusions, not on a spreadsheet.
Transparent and documented
Underlying detection levels are still reported, so you can verify every call. The logic is version-controlled and mapped to the published literature behind it.
Stop interpreting lists. Start reading patterns.
Bring OraPath into your practice and give your whole team a result they can read the same way, every time.