Shared infrastructure / Context
Practice Graph™ is the shared context layer underneath HeyJarvis. It models the approved facts and relationships the three growth systems need to operate: services, locations, insurance information, appointment types, providers, capacity signals, scheduling constraints, approved answers, and practice rules. Visibility, Concierge, and Recovery can therefore reason from the same version of how the practice actually works.
01
A Visibility system should not promote a service the practice cannot support. A Concierge should not offer an appointment type that does not fit the location. A Recovery system should not re-engage a lead without knowing current rules and capacity.
Practice Graph™ exists so those systems can operate from the same approved context.
02
Examples include services, locations, accepted insurance information, appointment types, scheduling constraints, provider context, capacity signals, FAQs, escalation rules, and other operational information the practice authorizes.
03
Practice Graph™ is not the clinical record and should not invent coverage or treatment decisions. Any use of patient or protected health information requires explicit scoping, appropriate permissions, and compliant handling.
Frequently asked questions
Dental Discover™, Patient Runtime™, and Demand Recovery™ can all use Practice Graph™ as shared approved practice context.
No. It is a context layer for the growth system, not the clinical or scheduling system of record.
The useful information is relational: which location offers which service, which appointment type is appropriate, which rules apply, what capacity exists, and how those facts relate. A graph model is meant to preserve those relationships rather than store isolated snippets.
Patient growth, measured
Start with one location, a defined baseline, and an agreed outcome.
Discuss a pilot