Consumer navigation platforms help patients search provider directories. Orita is the API infrastructure for platforms building that experience — applying deterministic eligibility rules, verifying real-time availability, and safely confirming bookings.
| Capability | Navigation platforms | Orita |
|---|---|---|
| Primary user | Patients searching for providers | Developers building provider-routing platforms |
| Eligibility rules | Directory filters (specialty, location) | Included: license, insurance, modality, region, age group — as hard API constraints |
| Insurance verification | Display-only filter | Hard constraint: excludes providers that do not accept the plan |
| License verification | Not typically enforced in real-time | Hard constraint: enforces region, expiry, and verification freshness |
| Availability check | Shown as "accepting new patients" | Real-time calendar verification + hold + atomic confirmation |
| Provider data model | Managed by vendor | Customer-owned external IDs; your database stays source of truth |
| Bulk provider sync | Vendor-managed import | Included: 500 providers, dry-run, upsert, external IDs |
| Explainability | Not available | Per-provider: why matched, failed, or had unknown data |
| AI agent integration | Not typically designed for it | REST, Node, Python, MCP — built for agent-native workflows |
| Idempotent confirmation | Not applicable | Included: prevents duplicate bookings |
| Multi-org isolation | Single-tenant | Included: scoped keys, isolated networks |
| Webhooks | Varies | Included: signed, stable IDs, retry, replay |
| Consumer UI | Included | Not provided — you build the UI on top of the API |
| Panel capacity | Not enforced | Included: exclude providers at capacity |
| Waitlist | Sometimes included | Included via API: POST /api/v2/waitlist |
When to use a navigation platform: You need a consumer-facing directory where patients self-select providers. The platform handles the UI and trust layer.
When to use Orita: You are building the routing logic behind a navigation experience, AI receptionist, or behavioral health platform — where the system must determine which providers are operationally eligible for a specific request, not just display a filtered list.
Important: Orita evaluates operational provider eligibility. The upstream application determines what service a patient needs. Orita does not diagnose, triage, or make clinical decisions.