Integration Models

Many ways to bring H2H Digital Rx into your workflow

Whether you're an independent prescriber or an EHR platform serving thousands, H2H Digital Rx fits the way you already work - from a direct login to a fully agentic integration.

Compare at a glance

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 Digital Rx
H2H Digital Rx login
Full EPCS support
Same day
Embedded (EMR/EHR/MAR)
Low
H2H Digital Rx, 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.

SA

Stand-Alone Access

Best for: Independent practices without an existing EMR

For prescribers who aren’t associated with an EMR, EHR, or MAR system. Log in directly to H2H Digital Rx at the point of care with a unique user ID and password, and send prescriptions straight to the pharmacy.

View setup docs →
Prescriber logs in directly
H2H DigitalRx workflow
Sent via Surescripts to pharmacy
Step four
EMR

Embedded EMR / EHR / MAR Access

Best for: Practices and platforms with an established EMR/EHR

H2H Digital Rx 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 Digital Rx login.

View embed docs →
User logs into EMR/EHR/MAR
“Prescribe” link opens H2H DigitalRx
Sent via Surescripts to pharmacy
Step four
API

Web API (SOAP & REST)

Best for: EHR/EMR vendors and health-tech platforms building their own UI

Connect to H2H Digital Rx 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 →
Your application calls the H2H API
Functionality embedded in your UI
Webhooks push status back to you
Sent via Surescripts to pharmacy
MCP

Agent-to-Agent (MCP Server)

Best for: Platforms building agentic AI experiences that need e-prescribing as a callable capability

H2H Digital Rx 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 Digital Rx handles the regulated prescribing actions and returns structured results, keeping the human prescriber in the loop for final confirmation.

View MCP tool schema →
Your agent calls an H2H MCP tool
H2H executes the prescribing action
Structured result returned to your agent
Prescriber confirms — sent via Surescripts
Delivery variants

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.

Low effort

Iframe - full application

A lighter form of Embedded access

The entire H2H Digital Rx application loads in an iframe inside your product, themed to match. Minimal engineering on your side.

High effort

End-to-end API ownership

Full ownership on the Web API

Build your own UX entirely on top of H2H Digital Rx’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.

Find your fit

Which model fits you?

No existing EMR - you prescribe at the point of care

→ Stand-Alone Access

You already run an EMR/EHR/MAR and want prescribing in context

→ Embedded Access

You’re building your own prescribing interface

→ Web API (SOAP & REST)

You’re building an agentic AI flow that needs to prescribe

→ Agent-to-Agent (MCP)

Not sure which model fits?

Our integration team can map your existing system in a single call.