Discrepancy Type Legend Sample Clauses

Discrepancy Type Legend. CF Prescription Not on File — There was no hard copy prescription on file at the pharmacy which corresponded to the claim billed. NRR The pharmacy had no record of a refill being dispensed on the date billed. CQ/R The quantity dispensed by the pharmacy was reduced from the amount authorized by the prescriber and allowed under the applicable Medco Health Plan. OD Overqualified Dispensing — The prescription as written by the prescriber allowed for generic substitution, however, the pharmacy dispensed and billed for the brand-name medication. DG Dispensed Generic, Billed Brand — The pharmacy dispensed the generic medication to the patient while billing for the more expensive brand- name product. UR Unauthorized Refill — The pharmacy exceeded the prescriber’s refill authorization. OBQ Over-billed Quantity — The pharmacy submitted the claim with a metric quantity in excess of the quantity actually dispensed. XDB Incorrect Drug Billed — The medication billed by the pharmacy differs entirely from the medication identified on the prescriber’s prescription order. EPL Exceeds Plan Limits — The quantity of medication dispensed by the pharmacy exceeded the amount allowed under the applicable Medco Health plan. DISP > RX The quantity dispensed exceeded the amount authorized by the prescriber. No Sig Log On File There was no signature log on file at the pharmacy corresponding to the claim billed. Pack Size The pharmacy submitted the claim with the NDC of a smaller package size than should have been dispensed. Comp RX Overpriced compounded prescription. Mail RX The prescription was not personally picked up, nor received through a local delivery service. This definition encompasses mail and other remote delivery carriers. Claim was not authorized as a mail service prescription. MD Not ID Based on the information provided by the pharmacy the prescriber could not be identified. Patient Contests The patient contests receiving the prescription claim reimbursed Receipt under his Member ID number. Prescriber Contests The prescriber contests authorizing the prescription. PND Patient name different — The last name of the patient identified on the prescription differs from the name under which the claim was billed. Return to Stock The claim in question was not picked up by the patient and returned to the pharmacy’s stock. Refill > Than 1 Year The pharmacy dispensed a refill more than one year from the date that the particular prescription was originally written.
AutoNDA by SimpleDocs

Related to Discrepancy Type Legend

  • Accuracy of Orders; Customer Signatures You shall be responsible for the accuracy, timeliness and completeness of any orders transmitted by you on behalf of your customers by any means, including wire or telephone. In addition, you agree to guarantee the signatures of your customers when such guarantee is required by the Company and you agree to indemnify and hold harmless all persons, including us and the Funds’ transfer agent, from and against any and all loss, cost, damage or expense suffered or incurred in reliance upon such signature guarantee.

  • FORMAT AND CONTENT FOR REGISTRY OPERATOR MONTHLY REPORTING Registry Operator shall provide one set of monthly reports per gTLD, using the API described in draft-­‐xxxxxx-­‐icann-­‐registry-­‐interfaces, see Specification 2, Part A, Section 9, reference 5, with the following content. ICANN may request in the future that the reports be delivered by other means and using other formats. ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Specification 3, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).

  • ODUF Packing Specifications 6.3.1 A pack will contain a minimum of one message record or a maximum of 99,999 message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of 99 packs and a minimum of one pack.

  • Project Delivery Order Procedures The TIPS Member having approved and signed an interlocal agreement, or other TIPS Membership document, may make a request of the awarded vendor under this Agreement when the TIPS Member has services that need to be undertaken. Notification may occur via phone, the web, email, fax, or in person. Upon notification of a pending request, the awarded vendor shall make contact with the TIPS Member as soon as possible, but must make contact with the TIPS Member within two working days. Scheduling of projects (if applicable) may be accomplished when the TIPS Member issues a Purchase Order and/or an Agreement or Contract that will serve as “the notice to proceed” as agreed by the Vendor and the TIPS Member. The period for the delivery order will include the mobilization, materials purchase, installation and delivery, design, weather, and site cleanup and inspection. No additional claims may be made for delays as a result of these items. When the tasks have been completed the awarded vendor shall notify the client and have the TIPS Member or a designated representative of the TIPS Member inspect the work for acceptance under the scope and terms in the Purchase Order and/or Agreement or Contract. The TIPS Member will issue in writing any corrective actions that are required. Upon completion of these items, the TIPS Member will issue a completion notice and final payment will be issued per the contractual requirements of the project with the TIPS Member. Any Construction contract prepared by the TIPS Member’s Legal Counsel may alter the terms of this subsection, “Scheduling of Projects”.

  • Pricing for Registry Services (a) With respect to initial domain name registrations, Registry Operator shall provide ICANN and each ICANN accredited registrar that has executed the registry-­‐registrar agreement for the TLD advance written notice of any price increase (including as a result of the elimination of any refunds, rebates, discounts, product tying or other programs which had the effect of reducing the price charged to registrars, unless such refunds, rebates, discounts, product tying or other programs are of a limited duration that is clearly and conspicuously disclosed to the registrar when offered) of no less than thirty (30) calendar days. Registry Operator shall offer registrars the option to obtain initial domain name registrations for periods of one (1) to ten (10) years at the discretion of the registrar, but no greater than ten (10) years. (b) With respect to renewal of domain name registrations, Registry Operator shall provide ICANN and each ICANN accredited registrar that has executed the registry-­‐registrar agreement for the TLD advance written notice of any price increase (including as a result of the elimination of any refunds, rebates, discounts, product tying, Qualified Marketing Programs or other programs which had the effect of reducing the price charged to registrars) of no less than one hundred eighty (180) calendar days. Notwithstanding the foregoing sentence, with respect to renewal of domain name registrations: (i) Registry Operator need only provide thirty (30) calendar days notice of any price increase if the resulting price is less than or equal to (A) for the period beginning on the Effective Date and ending twelve (12) months following the Effective Date, the initial price charged for registrations in the TLD, or (B) for subsequent periods, a price for which Registry Operator provided a notice pursuant to the first sentence of this Section 2.10(b) within the twelve (12) month period preceding the effective date of the proposed price increase; and (ii) Registry Operator need not provide notice of any price increase for the imposition of the Variable Registry-­‐Level Fee set forth in Section 6.3. Registry Operator shall offer registrars the option to obtain domain name registration renewals at the current price (i.e., the price in place prior to any noticed increase) for periods of one (1) to ten (10) years at the discretion of the registrar, but no greater than ten (10) years. (c) In addition, Registry Operator must have uniform pricing for renewals of domain name registrations (“Renewal Pricing”). For the purposes of determining Renewal Pricing, the price for each domain registration renewal must be identical to the price of all other domain name registration renewals in place at the time of such renewal, and such price must take into account universal application of any refunds, rebates, discounts, product tying or other programs in place at the time of renewal. The foregoing requirements of this Section 2.10(c) shall not apply for (i) purposes of determining Renewal Pricing if the registrar has provided Registry Operator with documentation that demonstrates that the applicable registrant expressly agreed in its registration agreement with registrar to higher Renewal Pricing at the time of the initial registration of the domain name following clear and conspicuous disclosure of such Renewal Pricing to such registrant, and (ii) discounted Renewal Pricing pursuant to a Qualified Marketing Program (as defined below). The parties acknowledge that the purpose of this Section 2.10(c) is to prohibit abusive and/or discriminatory Renewal Pricing practices imposed by Registry Operator without the written consent of the applicable registrant at the time of the initial registration of the domain and this Section 2.10(c) will be interpreted broadly to prohibit such practices. For purposes of this Section 2.10(c), a “Qualified Marketing Program” is a marketing program pursuant to which Registry Operator offers discounted Renewal Pricing, provided that each of the following criteria is satisfied: (i) the program and related discounts are offered for a period of time not to exceed one hundred eighty (180) calendar days (with consecutive substantially similar programs aggregated for purposes of determining the number of calendar days of the program), (ii) all ICANN accredited registrars are provided the same opportunity to qualify for such discounted Renewal Pricing; and (iii) the intent or effect of the program is not to exclude any particular class(es) of registrations (e.g., registrations held by large corporations) or increase the renewal price of any particular class(es) of registrations. Nothing in this Section 2.10(c) shall limit Registry Operator’s obligations pursuant to Section 2.10(b). (d) Registry Operator shall provide public query-­‐based DNS lookup service for the TLD (that is, operate the Registry TLD zone servers) at its sole expense.

  • Additional Provisions Required in Global Security Unless otherwise specified as contemplated by Section 3.1, any Global Security issued hereunder shall, in addition to the provisions contained in Sections 2.2 and 2.3, bear a legend in substantially the following form: THIS SECURITY IS A GLOBAL SECURITY WITHIN THE MEANING OF THE INDENTURE HEREINAFTER REFERRED TO AND IS REGISTERED IN THE NAME OF A DEPOSITARY OR A NOMINEE OF A DEPOSITARY. THIS SECURITY IS EXCHANGEABLE FOR SECURITIES REGISTERED IN THE NAME OF A PERSON OTHER THAN THE DEPOSITARY OR ITS NOMINEE ONLY IN THE LIMITED CIRCUMSTANCES DESCRIBED IN THE INDENTURE AND MAY NOT BE TRANSFERRED EXCEPT AS A WHOLE BY THE DEPOSITARY TO A NOMINEE OF THE DEPOSITARY OR BY A NOMINEE OF THE DEPOSITARY TO THE DEPOSITARY OR ANOTHER NOMINEE OF THE DEPOSITARY, EXCEPT IN THE LIMITED CIRCUMSTANCES DESCRIBED IN THE INDENTURE.

  • Escrow Format Specification Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-xxxxx-xxxxxxx-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-xxxxx-xxxxxxx-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.

  • Payment – Invoicing Instructions The Contractor will provide an invoice on the Contractor’s letterhead for goods delivered and/or services rendered. In the case of goods, the Contractor will leave an invoice with each delivery. Each invoice will have a number and will include the following information: A. Contractor’s name and address B. Contractor’s remittance address, if different from A above C. Contractor’s Taxpayer ID Number

  • Determination to Honor Drawing Request In determining whether to honor any request for drawing under any Letter of Credit by the beneficiary thereof, Agent shall be responsible only to determine that the documents and certificates required to be delivered under such Letter of Credit have been delivered and that they comply on their face with the requirements of such Letter of Credit and that any other drawing condition appearing on the face of such Letter of Credit has been satisfied in the manner so set forth.

  • INVOICING INSTRUCTIONS The A-E will provide an invoice on the A-E’s letterhead. Each invoice will have a unique number and will include the following information: A. A-E’s name and address B. A-E’s remittance address, if different from (A), above C. Name of COUNTY agency/department D. Delivery/service address E. CONTRACT number F. Service Date G. Description of Services H. Total I. Taxpayer ID number Invoices and support documentation are to be forwarded to:

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!