Retrievability Sample Clauses

Retrievability. Pharmacy agrees to maintain, in a retrievable manner, the Electronic Third-Party Signature Claim Log for a period of not less than 6 years from the date the prescription was dispensed. Subject to a request from Medco Health, either in writing, during an on-site claims review, by telephone, or as otherwise required by Medco Health, Pharmacy agrees to retrieve, display, print, electronically transmit, and/or provide copies of Electronic Third- Party Signature Claim Logs to Medco Health. The information displayed, transmitted, or printed must be in a format that includes at least the Data Elements as outlined earlier in this section, including the unique signature of the Eligible Person or Authorized Representative, in an image format, obtained by Pharmacy at the time of dispensing. Pharmacy is not entitled to payment for any prescription claim for which the Pharmacy is unable to produce an Electronic Third-Party Signature Claim Log or for any claim in which the Electronic Third-Party Signature Log is not maintained in the required format as outlined above. Pharmacy certifies that the prescriptions referred to in the Electronic Third-Party Signature Claim Logs were lawfully dispensed to the person whose signature appears in the electronic record and the prescriptions comply with the conditions and applicable instructions of the third party program identified. Pharmacy also certifies that the information covering each transaction, is, to the best of Pharmacy’s knowledge, correct and that all documentation is available for audit.
Sample 1
AutoNDA by SimpleDocs
Retrievability. The information that an originator’s bank must retain under paragraphs (e)(1)(i) and (e)(2) of this section shall be retrievable by the originator’s bank by reference to the name of the originator. If the origi- nator is an established customer of the originator’s bank and has an account used for funds transfers, then the infor- mation also shall be retrievable by ac- count number. The information that a beneficiary’s bank must retain under paragraphs (e)(1)(iii) and (e)(3) of this section shall be retrievable by the beneficiary’s bank by reference to the name of the beneficiary. If the bene- ficiary is an established customer of the beneficiary’s bank and has an ac- count used for funds transfers, then the information also shall be retrievable by account number. This information need not be retained in any particular manner, so long as the bank is able to retrieve the information required by this paragraph, either by accessing funds transfer records directly or through reference to some other record maintained by the bank.
Sample 1
Retrievability. The information that a transmittor’s financial institu- tion must retain under paragraphs (f)(1)(i) and (f)(2) of this section shall be retrievable by the transmittor’s xxxxx- cial institution by reference to the name of the transmittor. If the transmittor is an established customer of the transmittor’s financial institu- tion and has an account used for trans- mittals of funds, then the information also shall be retrievable by account number. The information that a recipi- ent’s financial institution must retain under paragraphs (f)(1)(iii) and (f)(3) of this section shall be retrievable by the recipient’s financial institution by ref- erence to the name of the recipient. If the recipient is an established cus- tomer of the recipient’s financial insti- tution and has an account used for transmittals of funds, then the infor- mation also shall be retrievable by ac- count number. This information need not be retained in any particular man- ner, so long as the financial institution is able to retrieve the information re- quired by this paragraph, either by ac- cessing transmittal of funds records di- rectly or through reference to some other record maintained by the xxxxx- cial institution.
Sample 1
Retrievability. Pharmacy agrees to maintain, in a retrievable manner, the Electronic Third-Party Signature Claim Log for a period of not less than 6 years from the date the prescription was dispensed. Subject to a request from Medco Health, either in writing, during an on-site claims review, by telephone, or as otherwise required by Medco Health, Pharmacy agrees to retrieve, display, print, electronically transmit, and/or provide copies of Electronic Third- Party Signature Claim Logs to Medco Health. The information displayed, transmitted, or printed must be in a format that includes at least the Data Elements as outlined earlier in this section, including the unique signature of the Eligible Person or Authorized Representative, in an image format, obtained by Pharmacy at the time of dispensing. Pharmacy is not entitled to payment for any prescription claim for which the Pharmacy is unable to produce an Electronic Third-Party Signature Claim Log or for any claim in which the Electronic Third-Party Signature Log is not maintained in the required format as outlined above. Pharmacy certifies that the prescriptions referred to in the Electronic Third-Party Signature Claim Logs were lawfully dispensed to the person whose signature appears in the electronic record and the prescriptions comply with the conditions and applicable instructions of the third party program identified. Pharmacy also certifies that the information covering each transaction, is, to the best of Pharmacy’s knowledge, correct and that all documentation is available for audit. PROFESSIONAL AUDITS The Electronic Third-Party Signature Claim Log as detailed in this section provides an alternative to participating pharmacies that keeps pace with advancing technology. Pharmacy has the opportunity to replace their current Paper Third-Party Signature Claim Log with a computer-based Electronic Third-Party Signature Claim Log that meets the requirements of Medco Health’s plan sponsors as outlined above. MISCELLANEOUS PROVIDER ISSUES MISCELLANEOUS PROVIDER ISSUES MISCELLANEOUS PROVIDER ISSUES MISCELLANEOUS PROVIDER ISSUES Pharmacy’s providing of Covered Services to any Eligible Person is a reaffirmation of the terms and provisions of the Pharmacy’s Agreement with Medco Health as of the time the Covered Services are provided. Pharmacy is required to support the objectives of Sponsors whose Eligible Persons obtain Covered Services from Pharmacy, to advance Medco Health programs, to not take actions against the best inte...
Sample 1

Related to Retrievability

  • Grievability Denial of a petition for reinstatement is grievable. The grievance may not be based on information other than that shared with the Employer at the time of the petition for reinstatement.

  • Non-Grievability No dispute over a claim for any benefits extended by this Health and Welfare Fund shall be subject to the grievance procedure.

  • Database The LERG is available through Telcordia. ICONN is available through the Qwest web site.

  • Searchability Offering searchability capabilities on the Directory Services is optional but if offered by the Registry Operator it shall comply with the specification described in this section.

  • Evaluation Software If the Software is an evaluation version or is provided to You for evaluation purposes, then, unless otherwise approved in writing by an authorized representative of Licensor, Your license to use the Software is limited solely for internal evaluation purposes in non-production use and in accordance with the terms of the evaluation offering under which You received the Software, and expires 90 days from installation (or such other period as may be indicated within the Software). Upon expiration of the evaluation period, You must discontinue use of the Software, return to an original state any actions performed by the Software, and delete the Software entirely from Your system and You may not download the Software again unless approved in writing by an authorized representative of Licensor. The Software may contain an automatic disabling mechanism that prevents its use after a certain period of time. RESTRICTIONS

  • Encryption The Fund acknowledges and agrees that encryption may not be available for every communication through the System, or for all data. The Fund agrees that Custodian may deactivate any encryption features at any time, without notice or liability to the Fund, for the purpose of maintaining, repairing or troubleshooting the System or the Software.

  • Computer The Contractor shall maintain at its office for its use a computer with, at a minimum, a 1 GHz processor and an internet connection. The Contractor shall maintain individual email accounts for each of its project managers.

  • Compatibility 1. Any unresolved issue arising from a mutual agreement procedure case otherwise within the scope of the arbitration process provided for in this Article and Articles 25A to 25G shall not be submitted to arbitration if the issue falls within the scope of a case with respect to which an arbitration panel or similar body has previously been set up in accordance with a bilateral or multilateral convention that provides for mandatory binding arbitration of unresolved issues arising from a mutual agreement procedure case.

  • Workstation/Laptop encryption All workstations and laptops that process and/or store DHCS PHI or PI must be encrypted using a FIPS 140-2 certified algorithm which is 128bit or higher, such as Advanced Encryption Standard (AES). The encryption solution must be full disk unless approved by the DHCS Information Security Office.

  • Authoritative Root Database To the extent that ICANN is authorized to set policy with regard to an authoritative root server system (the “Authoritative Root Server System”), ICANN shall use commercially reasonable efforts to (a) ensure that the authoritative root will point to the top-­‐level domain nameservers designated by Registry Operator for the TLD, (b) maintain a stable, secure, and authoritative publicly available database of relevant information about the TLD, in accordance with ICANN publicly available policies and procedures, and (c) coordinate the Authoritative Root Server System so that it is operated and maintained in a stable and secure manner; provided, that ICANN shall not be in breach of this Agreement and ICANN shall have no liability in the event that any third party (including any governmental entity or internet service provider) blocks or restricts access to the TLD in any jurisdiction.

Time is Money Join Law Insider Premium to draft better contracts faster.