> For the complete documentation index, see [llms.txt](https://docs.mdintegrations.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mdintegrations.com/partner/key-concepts/pharmacy-fulfillment/partner-owned-transmission.md).

# Partner-Owned Transmission

Use partner-owned transmission when your pharmacy has neither a native Surescripts connection nor an existing MDI integration. In this model, MDI prepares the clinical prescription data as a downloadable PDF, and your team takes it from there, sending it on to the pharmacy through whatever channel that pharmacy accepts.

### Set up the workflow

{% stepper %}
{% step %}

#### Enable the Service Offering

Ask your MDI Partner Success Manager to designate the relevant Offering as a Service Offering.
{% endstep %}

{% step %}

#### Create the Encounter

Pass the Service Offering's `offering_id` when you create an Encounter or Voucher, exactly as you would with any other [Offerings](/partner/key-concepts/offerings.md).
{% endstep %}

{% step %}

#### Configure webhooks

Register a webhook endpoint in the Partner Portal, then listen for `offering_submitted` — it signals that the Encounter has been approved and the clinical data is ready for you to retrieve.
{% endstep %}

{% step %}

#### Retrieve prescription data

Use the webhook payload itself, or retrieve the Encounter's Offerings through the API:

* The webhook provides `case_id`.
* `product.description` contains prescription metadata.
* `product.additional_note` contains patient directions.
  {% endstep %}

{% step %}

#### Retrieve the Service PDF

Request the Service PDF using `case_id`, and download it right away — the pre-signed URL you get back expires.
{% endstep %}

{% step %}

#### Transmit to the pharmacy

Route the clinical asset to the pharmacy through whichever channel it supports — API, fax, email, or a manual operations workflow.
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
MDI does not transmit Service Offerings to a pharmacy. Your transmission workflow must handle every handoff after clinical approval.
{% endhint %}

### Compare with order-driven fulfillment

It helps to contrast this with order-driven fulfillment. There, MDI still sends the e-prescription to the pharmacy on your behalf, and your team's only job is submitting a separate commercial order on top of it.

With partner-owned transmission, MDI never contacts the pharmacy at all — your team owns both prescription transmission and order handling from end to end.

See [Example: Mapping to LifeFile](/partner/key-concepts/pharmacy-fulfillment/partner-owned-transmission/example-mapping-to-lifefile.md) for a concrete, field-by-field mapping example.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.mdintegrations.com/partner/key-concepts/pharmacy-fulfillment/partner-owned-transmission.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.