E-Prescribing Message Flows
4 min
e prescribing message flows overview the surescripts e prescribing service enables new prescription transmissions from a prescriber to the patient's pharmacy of choice the graphic below depicts allowable message flows between surescripts network participants prescribers and pharmacies must have the appropriate service levels enabled to send or receive messages see the directory implementation guide docid\ wewxqy1rx7 g9qxaspwyx for more information r 318 customers shall support the mandatory messages detailed in the message flow section of this guide per customer (long term and post acute care (ltpac) and non ltpac) settings and services e prescribing messages for non ltpac required newrx; rxrenewalrequest/rxrenewalresponse; rxchangerequest/rxchangeresponse; cancelrx/cancelrxresponse e prescribing messages for ltpac required newrx; cancelrx/cancelrxresponse; rxfill; rxfillindicatorchange (pharmacies); census; resupply surescripts e prescribing message flow diagram notes messages marked with one asterisk ( ) are fillable messages a fillable message is a message from the prescriber or prescribing system to the pharmacy that results in an initial prescription being filled, a change approval, or a refill approval other messages may support fillable messages or workflows messages marked with two asterisks ( ) only apply to ltpac message workflow the following steps depict the basic workflow of a prescriber or pharmacy initiated message sender initiates a message for a patient via the sender’s vendor system and transmits to surescripts surescripts validates the message if there is an issue with the message, surescripts returns an error back to the sender’s vendor system and the process ends if no error in validation occurs, surescripts routes the message to the appropriate receiver’s vendor system the receiving system then validates the message and responds with a synchronous status message (code of either 000 or 010) or an error to surescripts surescripts sends the synchronous response to the sender’s vendor system if either the status message (code 010) or error is returned, then the process ends if the synchronous message is a status (code 000) message, then the receiver’s vendor system follows up with an asynchronous (free standing) verify message (code 010) or error if a free standing asynchronous message is received, the sender’s vendor system needs to synchronously acknowledge with a status (code 010) message when surescripts receives either the verify or error, the message is validated and forwarded to the sender’s vendor system note for additional information, see acknowledgement message table docid\ xgplk6zd1l7x8nxymqrlr section