Many ways to bring H2H into your workflow
Whether you're an independent prescriber or an EHR platform serving thousands, H2H fits the way you already work — from a direct login to a fully agentic integration.
Four core models, one certified platform
Every model runs on the same Surescripts-certified backend with full EPCS support — they differ mainly in who owns the interface and how much you build.
| Model | Integration effort | Who owns the UX | Who authenticates | EPCS & controlled substances | Typical time to live |
|---|---|---|---|---|---|
| Stand-Alone | None | H2H | H2H login | Full EPCS support | Same day |
| Embedded (EMR/EHR/MAR) | Low | H2H, in context | Your system (SSO) | Full EPCS support | Days |
| Web API (SOAP & REST) | Medium–High | You | Your system | Full EPCS support | Weeks |
| Agent-to-Agent (MCP) | Low–Medium | Your agent | Your system | Full EPCS support | Days–weeks |
Scroll horizontally to see all columns on smaller screens.
Stand-Alone Access
For prescribers who aren’t associated with an EMR, EHR, or MAR system. Log in directly to H2H DigitalRx at the point of care with a unique user ID and password, and send prescriptions straight to the pharmacy.
View setup docs →Embedded EMR / EHR / MAR Access
H2H DigitalRx opens from a “prescribe” link or button inside your existing EMR, EHR, or MAR system. Logging into that system uniquely identifies the user and care location — authentication happens behind the scenes, with no separate H2H login.
View embed docs →Web API (SOAP & REST)
Connect to H2H DigitalRx services through our web API — available in both SOAP and REST, with webhooks for asynchronous events like ePA status changes. Often the fastest way to bring e-prescribing into your own application without a separate login screen.
View API reference →Agent-to-Agent (MCP Server)
H2H DigitalRx exposes a Model Context Protocol (MCP) server, so the AI agents already running inside your EHR, EMR, or health-tech platform can invoke e-prescribing as a set of tools — write a new Rx, run RTPB and formulary checks, initiate ePA, query the PDMP, or sign an EPCS order — through native tool calls. Your agent orchestrates the clinical conversation; H2H handles the regulated prescribing actions and returns structured results, keeping the human prescriber in the loop for final confirmation.
View MCP tool schema →Fine-tune the Embedded and API models
These aren’t separate models — they’re variations on Embedded access and the Web API, ordered from the lightest to the heaviest integration lift.
Iframe — full application
The entire H2H DigitalRx application loads in an iframe inside your product, themed to match. Minimal engineering on your side.
End-to-end API ownership
Build your own UX entirely on top of H2H’s SOAP & REST APIs and webhooks — total control of the experience, at the cost of more development effort.
AI capabilities like Transcribe to Prescribe and PrescribeAgent aren’t separate integrations — they’re available across every model above, through the API and the MCP server.
Which model fits you?
Not sure which model fits?
Our integration team can map your existing system in a single call.