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 display requirements pm 201 during the prescription writing process and prior to sending the newrx, the application shall display pm 202 the estimatedpatientfinancialresponsibility, quantity (element), and dayssupply at requested pharmacy (first \<pricingandcoverages> element) for all medications returned (including alternatives) pm 203 the estimatedpatientfinancialresponsibility, quantity (element), and dayssupply at other pharmacies (subsequent \<pricingandcoverages> elements) this concession is allowed an indicator that pricing at other pharmacies applies user action on this indicator presents estimatedpatientfinancialresponsibility, quantity (element), and dayssupply at other pharmacies in their entirety pm 204 coverage restrictions for all \<pricingandcoverages> elements for medication combinations returned (including alternatives) this concession is allowed an indicator that coverage restriction(s) apply to a specific combination user action on this indicator presents all coverage restrictions in their entirety note coverage restrictions may be communicated in various coded and text fields, beyond the \<coveragerestriction> element, within the \<pricingandcoverage> element (i e , \<coveragestatuscode>, \<coveragestatusmessage>) pm 205 all available appropriate alternatives displayed together if all alternatives cannot be shown together, this concession is allowed an indicator that alternative medications are available user interaction on this indicator presents all alternative medications together pm 206 user shall be made aware that the pricing/coverage data is a point in time calculation based upon data provided in the request and may vary once the prescription is filled at the dispensing pharmacy any returned alternative information is informational only and not intended to replace clinical decisions pm 207 alternatives shall be displayed in the order provided from the pbm pm 208 pricing information shall be displayed as returned in the rtpbresponse pm 209 the textual description of the codified value and not the coveragerestrictioncode itself, shall be displayed to the user pm 210 the textual description of the codified value and not the coveragestatuscode itself, shall be displayed to the user 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