Skip to main content
MedWrite can be embedded inside an Electronic Health Record (EHR) system so clinicians can use it within their existing workflow.

​
Architecture

The integration uses a URL-based embedding pattern. The EHR opens MedWrite by loading specific URLs in an embedded frame and passes patient context and authentication as parameters. 
EHR Application
  |
  |-- Embedded Frame
        |
        |-- MedWrite Frontend
              |
              |-- Authenticated via token passed from EHR
              |-- Patient context passed via URL parameters

​
How it works

  1. The clinician logs into their EHR as normal.
  2. The EHR backend obtains a MedWrite bearer token via the login API on behalf of the user.
  3. The EHR renders an embedded frame pointing to the MedWrite frontend, passing the token and patient identifiers as URL parameters.
  4. MedWrite authenticates the session and shows the relevant patient view.
The embedded frame runs in its own browsing context, isolated from the host EHR. The MedWrite server is configured to allow framing only from authorised EHR domains. Tokens in the embedded context use the same expiry and security rules as direct API access. This pattern works with major EHR platforms including Epic Hyperspace and other web-based clinical systems.
The exact frontend URL, parameter format, and domain whitelisting are configured during onboarding. Contact the medWrite team for integration support.

​
Next steps

API Authentication

API key and bearer token.

Get Approved Outputs

Retrieve approved letters.