# Glossary

Terms for moving a prescription that are easy to mix up. Use them exactly as defined here in code, APIs, and tickets.

## Redirect (or Forwarding)

Moving an **unfilled** prescription. The legal document stays the original electronic prescription (eRx) sent by the
prescriber. Assignment, reassignment, and routing are all kinds of redirect.

## Transfer

Reserved for the traditional pharmacy-to-pharmacy move of a **filled** prescription. The legal document is the
pharmacist-verified (PV'd) copy produced by the original dispensing pharmacy's system, not the prescriber's original
eRx. Don't use "transfer" for a redirect.

## Assignment

The first step for a new, untouched prescription: placing it into a specific virtual pharmacy's (tenant's) queue in
SwiftyRx, where it waits for the patient's order. When a new prescription arrives from Surescripts, SwiftyRx asks the
Sailor system which tenant it belongs to. For example, if Sailor identifies a CenterWell prescription, it is assigned to
the CenterWell tenant.

## Reassignment

Moving an unfilled prescription from one tenant to another before an order is placed. For example, a prescription
assigned to CenterWell is reassigned to the HealthDyne tenant if the patient adds insurance that CenterWell can't
process before checking out.

## Routing

Sending the unfilled prescription out of its SwiftyRx tenant, through the API, into the dispensing pharmacy's
management software (such as ePost) so it can be filled.

## PV0

A SwiftyRx term for the initial prescription review done before the prescription reaches the dispensing pharmacy. It is
not a legal replacement for PV1. See [PV0](general_overview.rst) in the general overview.