Provider Vendor and PBM/Payer Requirements

pa 212 payer and submitter systems shall be able to send and receive pdf attachments at a minimum pa 213 participant applications shall not allow users/systems to respond multiple times to a message the application has already sent the only exceptions are the inprocess paresponse followed by an approved/denied paresponse message; and parequest/paresponses when additional information is requested pa 220 customers shall support the scenarios detailed in the message flow section of this guide s 200 customers shall be able to receive syntactically valid maximum and minimum populated messages optional data elements (and values therein) shall not cause message failure s 201 customers shall ensure all messages are syntactically correct before transmission to surescripts s 205 the sender shall ensure the combination of the from and messageid elements, for all messages including error, is unique for at least 18 months surescripts recommends an unformatted globally unique identifier (guid) s 206 system shall support user entry and display of up to three digits to the right of the decimal place, without the system rounding or truncating the decimal point is represented by a period and shall be used as follows only when there are significant digits to the right of the decimal when there is a digit before and after the decimal point not with whole numbers for example, consider the following possible values correct format examples incorrect format examples 2 5 27 0 15 3 00 21 14 s 209 the customer shall implement and maintain a surescripts approved drug compendia that is updated at least monthly