Prescribe inside your product,on rails that already exist
5,000+ verified prescribers already work on eNavvi. Bring them your CDS, AI agent, or scribe — on a rail where identity, signing, routing, and audit are already handled.
How it works
The legal frame, the engine underneath it, and the two ways your product connects.
The Terms
- Contract
- The prescriber signs with eNavvi directly, and integration happens at their request. You connect to the prescribing layer without becoming the prescribing entity yourself.
- Certification
- eNavvi is a complete, certified ePrescribing system. It runs standalone inside your product rather than becoming part of it — the certification stays ours.
- Neutrality
- Pharmacy search is prescriber- and patient-directed.
The Engine
Identity, signing, routing and audit run as one engine — the certified rails that turn a prescription into a compliant, routed, audited transaction. Every partner integrates the same core.
The regulatory layer
- 01
Identity
IAL2 prescriber proofing. DEA and multi-state licenses verified.
- 02
Signing
Certified EPCS with two-factor and biometric.
- 03
Routing
NCPDP SCRIPT v2023011 across the national network.
- 04
Audit
Every action provenance-logged, permanently.
Included with the engine
- Price Transparency
- Cash and discount prices, side by side, unranked.
- eNavvi Wallet (Close Beta)
- The patient's verified record, across every prescriber.
- Prior AuthorizationComing
- We help complete the PA at the point of prescribing.
Two Ways In
Both are enabled at the prescriber’s request, and both complete every prescription in eNavvi.
Embed
A secure iframe drop-in — the full eNavvi prescribing tool, running inside your app. Nothing to build, nothing to certify.
Explore moreAI Connector
Now pilotingBring an agent you already have and connect to our ePrescribe platform. Your agent proposes; a licensed prescriber reviews and signs.
Explore moreHealth Tech
eNavvi clinicians prescribe inside your product, and data is shared at their request.
A secure iframe drop-in — the full eNavvi prescribing tool. With the prescriber's consent, context flows from your system into eNavvi, so details your product already holds are not entered twice.
- 01
The prescriber consents
The prescriber authorises the connection. Patient and prescription context then passes from your system into eNavvi.
- 02
They prescribe in eNavvi
Signing happens inside the eNavvi iframe, on the prescriber's own credential and under their BAA with eNavvi.
- 03
eNavvi routes it
Across the national network on the certified rails, with every action logged.
- 04
The data comes back
With the prescriber's consent, prescription data is available to your product — in the chart your users already work in.
No double entry
Not a roadmap item — it works today. How far it reaches depends on what your side can send and receive.
A sandbox from the start
Every partner gets one to build against before anything touches a real patient.
The agent orchestrates.eNavvi executes.
Your product reaches a recommendation and stops. It can suggest a therapy, explain the reasoning, and hand the clinician a plan — but it cannot put a prescription in a pharmacy’s queue. That last step needs identity proofing, a certified signing environment, network conformance, and an audit trail. It takes 18+ months to build. eNavvi is that step, as an integration.
Attests to the review. Can modify, decline, or refer — signing is one outcome, not the default.
Bring Your Own Agent
Connect the AI agent you already have. Available to AI health companies and health platforms.
Built for Async Telemedicine
Prescriptions complete without a live visit — weight-care, chronic-condition and other async programs run end to end for established patients.
Integration questions
Anything not covered here, ask us directly —we'll route you to the right people the same business day.
How an agent connects
How an agent connects
Your backend connects to eNavvi over a secure server-to-server API, and your product embeds the eNavvi prescribing flow so an already-signed-in user lands in it without a second login. Patient and medication context can be passed in. Full integration documentation, a client spec and a sandbox with test prescribers and test pharmacies come with your key.
What a proposal must contain
What a proposal must contain
Patient identity and demographics, the medication as discrete fields — RxNorm or NDC, strength, form, sig, quantity, days supply, refills — an ICD-10 indication, and the requesting agent's identity and version. Free-text is not accepted in clinical fields. The agent's rationale travels with the proposal as a separate, non-transmitted field: the prescriber sees it, the pharmacy never does.
What comes back on decline
What comes back on decline
A decline returns a structured reason code plus an optional prescriber note, delivered by webhook. The declined proposal is terminal — it never transmits and cannot be resubmitted. Your agent may submit a revised proposal referencing the original; both remain in the audit trail as linked, separate records.
Controlled substances
Controlled substances
AI-originated proposals are limited to non-controlled medications during the pilot. Controlled-substance prescribing on eNavvi is EPCS-certified and available to prescribers directly; it is not in scope for agent-submitted proposals at this phase.
For manufacturers
Three ways to work with us
Price Transparency
Your direct-program price, listed beside every other source. Unranked, complete.
Patient Access
Your programs reach identity-verified patients, after the prescription is written.
Program Insights
Aggregate reporting on how your programs perform — no prescriber-level data.
Build it yourself
18+ months
- Identity-proofing program
- Controlled-substance certification
- Network certification
- Standards conformance
- Audit infrastructure
Prescribe on eNavvi
Days
- Identity proofing, handled
- EPCS certified
- Network certified
- NCPDP SCRIPT v2023011
- Immutable audit, built in
verified prescribers already on eNavvi — every one identity-proofed and license-checked.
