Messages Overview

medication history load message flow the surescripts medication history load for pharmacies service assists pharmacies by hosting medication history data using the pharmacy extract file the file is sent by the pharmacy in a batch file process on a daily basis and loaded into a repository at surescripts surescripts validates the submitted file and generates and posts a validation response file in the sftp folder for customer retrieval this response notifies the customer that the medication history file was received and processed the response file also provides details of any errors (represented in mandatory fields) or correction requests (in conditional fields) that were encountered during the validation process these are shown as dtl errors/correction requests within the sftp file retrieved by the pharmacy customer the pharmacy user should plan to resend the corrected records with errors (1st priority) and correction requests (2nd priority) in a subsequent file an error represents a mandatory field that does not meet the validation rules outlined in this guide and therefore will not be passed to the surescripts repository a correction request is representative of a set of data within a conditional field that does not meet the validation rules outlined in this guide and will be passed into the surescripts repository with the field left blank for example, an error occurred due to invalid zip code format (mandatory field), resulting in that record being excluded from the surescripts repository if the correction request occurred in patient primary phone number field (conditional), the record will pass into the surescripts repository with the patient primary phone number left blank (for multiple correction requests in conditional fields, all fields will be left blank and passed into surescripts repository) for a record that has an error and a correction request because the mandatory field must meet validation it will not be passed into surescripts repository if a correction request record is corrected and sent via a subsequent pef file, the record will be updated in the surescripts repository to include the corrected data within the previous correction request field it is highly recommended to ensure you are only resubmitting the records with errors and correction requests please do not correct the errors/correction requests and resubmit the full file (i e if you submit a request with 100 records and 25 errors were returned, the correction file should only contain 25 revised records) surescripts retrieves and aggregates available dispensed fill data surescripts locates patients using the master patient index (mpi) for patients found the medication history request is routed to the appropriate pbm/payer for processing this data will contain any claim on file for medications where the pharmacy benefit may be used and may be reversed if the medication is returned to stock the medication history request also calls on our dispensed medication fill database, which is updated regularly by pharmacies connected to surescripts this data will contain records for dispensed medications and includes both cash and coupon pay for processing record reversals (voids), reference record reversals and updates docid\ wniorh6j4evyqcbom6s0e all records are subject to validation prior to reversal; therefore validation errors will prevent a reversal from occurring surescripts will never over write or replace existing data from data suppliers if a patient does not grant access to their data, the pharmacy is responsible for excluding the patient’s data from the file sent to surescripts surescripts uses an overall file trailer for each file, which provides detailed summary information inside