Process Overview

patient file load flow the customer generates and posts the patient file load (onto the sftp site) that identifies which patients they want to enroll for medication history for populations patients enrolled in medication history for populations (prescription notifications) are enrolled until the specified end monitoring date docid\ esie7tcj7byluhl1bpued customers can define the end monitoring date (which must be set for a future time period) on the initial load, which automatically stops notifications at that point if no value for end monitoring date is specified, then patient processing will continue until an end monitoring date is loaded please refer to the medication history for populations (prescription notifications) implementation guide for details on accessing the notification details patients enrolled for medication history for populations (panel) are enrolled for a one time medication history response please refer to either the medication history for populations (panel) implementation guides for details on accessing the response details depending if your organization utilizes xml or flat file panel output note if a patient does not grant access to their data, then the customer is responsible for excluding the patient from the patient file load surescripts validates the submitted file surescripts generates and posts onto the sftp site the patient response file for retrieval the response file notifies the customer that the patient file load was received and provides details into any errors that were encountered during the validation process the customer should review the patient response file to determine if a file and/or patient resubmission is required due to errors note only resubmit records that have errors review the panel response file and/or prescription notification api request response patient file load maintenance – prescription notifications after the initial file load, additions and changes to the list of enrolled patients is accomplished using the same file format and process each file is considered an update to the current list of enrolled patients it is not necessary to resend the entire list every time recipient and patient identity prescription notifications uses the following to identify a notification recipient and each patient that recipient has enrolled intended recipient of a notification sender id npi patient the recipient is monitoring assigning authority patient id notes \<font color="#000000">sender id is from the file header (hdr) record the rest of the fields are from the patient detail (pma) record \</font> \<font color="#000000">when a patient (assigning authority plus patient id) is enrolled by more than one recipient (sender id plus npi), it is necessary to send patient updates for each recipient’s enrolled record \</font> updating a previously enrolled patient to change data for a patient, submit the patient in a patient file using the updated information for the patient updates can be made to any data in the patient detail record (pma) other than npi, assigning authority, and patient id updates can include change of patient demographics (name fields, address fields, date of birth, gender) adding / removing notifications requested for this patient changes to the end monitoring date deleting a previously enrolled patient it is not possible to delete an enrolled patient; however, customers can stop receiving notifications for a patient this is accomplished by updating the end monitoring date docid\ esie7tcj7byluhl1bpued of the patient to a desired future date once the update is processed by surescripts and the date is reached, no notifications will be generated for the patient note all patients who are currently being monitored can be unenrolled from prescription notifications with a unr file load (panel does not apply to this feature) see detail information for unenrollment docid\ esie7tcj7byluhl1bpued enrolling or adding a new patient or notification recipient please consider the following when enrolling or adding a new patient or notification recipient new patients (assigning authority plus patient id) received in a patient file load will be validated and loaded new recipients (sender id, npi) with associated patient detail (pma) records will be validated and loaded a new recipient for a patient already monitored by a different recipient will be validated and loaded independently from the original recipient record surescripts considers the combination of sender id, npi, assigning authority, and patient id to be the unique keys to a record being monitored for notifications file validation surescripts will ensure that customers are in compliance with the message specifications outlined in this guide during integration testing and will continue to enforce once in production at a minimum, surescripts validations include the sender identification and authentication the recipient identification syntax of the message, including field lengths, required fields, data types, number of repeats and code values surescripts business rules and applicable requirements