DoctorGraph
A profile graph richer than any CRM column
A canonical doctor profile: specialty, sub-specialty, institution, licence, language, preferred channel, topics of interest and full attendance history — shared by the agent, the planner and every reporting dashboard.
- 1 Source of truth for every doctor signal
- Graph Topics of interest as weights, not tags
- Audit Every enrichment carries a source record
DoctorGraph is the source of truth that every other service reads. It holds the facts about a doctor that matter for outreach — specialty, sub-specialty, institution, licence number, preferred language, preferred channel, topics of interest, past webinar attendance, past declines — and serves them in milliseconds to the agent, the cadence planner and every reporting dashboard.
The graph is purpose-built rather than a repurposed CRM column-list. Topics of interest, for example, are stored as a weighted graph — an oncologist who consistently registers for immunotherapy webinars gets a higher weight on that sub-track than on general oncology. Institution is stored with hierarchy (hospital → department → unit), so peer-signal strings can say "twelve other cardiologists from the same hospital" without a single string-match hack.
Enrichment is an explicit pipeline. DoctorGraph accepts a thin import (list of doctors with names, licence numbers, basic contact details) and fills the rest from vetted sources: the medical registry, hospital directories, past campaign outcomes. Every enriched field carries a source tag, so auditors always see how a datum got there.
Graph is not CRM. DoctorGraph does not hold deals, quotes, invoices or any sales-pipeline noise — AIM CRM holds those. Keeping the two separate keeps the doctor profile clean and re-usable: the same graph feeds MedReach outreach, post-webinar analytics and sponsor reporting without having to untangle it from a marketing stack.
Everything DoctorGraph handles for you
-
Purpose-built schema
Specialty, sub-specialty, institution hierarchy, topics of interest as a weighted graph — not CRM columns.
-
Source-tagged enrichment
Every field has a source record; auditors see how each datum was populated.
-
Millisecond reads
The agent and the planner read the graph inside the decision window of a single turn.
-
Hospital hierarchy
Hospital → department → unit, so peer-signal strings compute exactly without string matching.
-
Clean separation from CRM
Deals and invoices live in AIM CRM; DoctorGraph stays focused on the profile.
The profile layer under every campaign
DoctorGraph feeds the agent, the specialty matcher, the peer-signal engine and the cadence planner. It receives identity and account context from AIM CRM and AuthGate.
- SpecialtyMatch reads specialty and topic-of-interest weights to decide eligibility.
- PeerSignal computes peer groups (hospital, department, specialty) from the graph.
- CadenceConductor reads channel preference and language per doctor.
- AIM CRM supplies the account and contact shell that wraps the profile.
Wire DoctorGraph into your product today
Book a consultation with our founders and we'll walk you through the whole microservice stack — not just this one — live on your domain.