Resupply
4 min
resupply overview resupply messages are sent from a ltpac setting or service to a pharmacy via the prescribing system as a request to replenish inventory this message can be used for on demand pharmacy or a cycle fill pharmacy depending on the need for inventory a status, error, or verify response is always sent after a resupply message is received resupply requirements a resupply message must follow the business rules within elements found in subsequent sections of this guide r 311 when sending a resupply message for a resident that resides within a facility care setting, the current facility data and patient location shall be populated resupply epcs requirements resupply is not a fillable message, only a request for supply or inventory if an original prescription is for a controlled substance and the pharmacy has only supplied a portion of the original quantity, the resupply can be used to request up to but not more than the total quantity approved in the newrx resupply best practices when requesting inventory from a ltpac pharmacy either the urgencyindicatorcode or the needednolaterthan element found within the medicationprescribed element may be populated these indicators will notify the pharmacy that inventory is critically low and cannot wait until the next routine delivery it is not necessary to populate both elements when requesting inventory that is not critical to patient safety or a potential lapse in treatment, the needednolaterthan element may be used to indicate a date and reason, whereas the urgencyindicatorcode is a flag only populated for a highly urgent situation occasionally resupply messages are sent as a standard practice of inventory management in a ltpac setting or service and an rxfill message of notdispensed – requested refill too soon is returned from the pharmacy the resupply has a followuprequest element that may be used to make a subsequent request these follow up requests should follow a minimum of 24 hours between requests or time periods defined in trading partner agreements message linkage would include a relatestomessageid that is the messageid from the last fillable messages, such as newrx non electronic messages may disrupt the workflow and a relatestomessageid may not be present, but should be populated when possible to assist both systems in linking messages