Application Certification Requirements

rtpbrequest s 201 customers shall ensure all messages are syntactically correct before transmission to surescripts pm 200 quantityunitofmeasure code qualifiers shall be correctly associated with medication descriptions note avoid using "unspecified" and “each”, if possible, for quantityunitofmeasure in the rtpbrrequest if "unspecified" or “each” is sent, the pbm may not be able to process correctly and the response may result in an error or unintended conversions rtpbresponse 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 pm 211 for all medications that were priced, the pbm response shall include the quantity (element), and dayssupply values in the appropriate pricingcoverage element general requirements 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 207 if an element does not have a value to be sent, the application shall not send any data if no data is sent, the receiving application shall not display a value equal to zero, nor infer any value for that field note placeholder values such as zero or n/a should not be sent s 208 codified values within a message shall not conflict with the related textual concept s 209 the customer shall implement and maintain a surescripts approved drug compendia that is updated at least monthly note approved drug compendia for real time prescription benefit include the following elsevier scholz databank first databank (fdb) oracle health multum wolters kluwer medi span merative (formerly ibm truven health analytics) or others as approved by surescripts s 210 customers shall support the scenarios in the message linkage section of this guide