Planning this workflow?

The [E-Prescribe Decision Guide](/content/docs/decision-guides/e-prescribe/index.html) walks through requirements questions and FHIR modeling decisions for e-prescribing — use it alongside these docs.

Representing medications in FHIR supports many common scenarios and can be used in concert with [Bots](/content/docs/bots/index.html) to enable complex medication-related workflows. A common first step is constructing a [MedicationRequest](/content/docs/api/fhir/resources/medicationrequest/index.html) FHIR resource. Adherence to the spec, referring to other relevant FHIR resources, and tagging the resource with RxNorm or CPT codes can be useful here to aid in integration, analytics and billing.

Appropriate use of FHIR resources can be used to represent prescriptions, prescription requests, medication dispense events, prior authorizations and allergies. To get started, we recommend reading the [MedicationRequest](/content/docs/api/fhir/resources/medicationrequest/index.html) and [Medication](/content/docs/api/fhir/resources/medication/index.html) resource pages.

`MedicationRequest` resources tagged with the appropriate medication code (e.g. RxNorm) can be linked to [subscriptions](/content/docs/subscriptions/index.html) and [bots](/content/docs/bots/index.html) to automatically send a prescription to an eRx provider.