Methodology for Collecting Pharmacy-Reported Variables Sample Clauses

Methodology for Collecting Pharmacy-Reported Variables. If the household member with the prescription gave written permission to release his or her pharmacy records, pharmacy providers identified by the household were contacted by telephone for the pharmacy follow-back component. Following an initial telephone contact, the signed permission forms and materials explaining the study were faxed (or mailed) to cooperating pharmacy providers. The materials informed the providers of all persons participating in the survey who had prescriptions filled at their place of business and requested a computerized printout of all prescriptions filled for each person. Pharmacies can choose to report information in computer assisted telephone interviews (CATI). The CATI instrument was also used to enter information from printouts. For each medication listed, the following information was requested: date filled; national drug code (NDC); medication name; strength of medicine (amount and unit); quantity (package size/amount dispensed); and payments by source. When an NDC was provided, often the drug name and other drug characteristics were obtained from secondary proprietary data sources.
AutoNDA by SimpleDocs
Methodology for Collecting Pharmacy-Reported Variables. If the respondent with the prescription gave written permission to release his or her pharmacy records, pharmacy providers identified by the household were contacted by telephone for the pharmacy follow-back component. Following an initial telephone contact, the signed permission forms and materials explaining the study were faxed (or mailed) to cooperating pharmacy providers. The materials informed the providers of all persons participating in the survey who had prescriptions filled at their place of business and requested a computerized printout of all prescriptions filled for each person. For each medication listed, the following information was requested: date filled; national drug code (NDC); medication name; strength of medicine (amount and unit); quantity (package size/amount dispensed); total charge; and payments by source.
Methodology for Collecting Pharmacy-Reported Variables. If the household member with the prescription gave written permission to release his or her pharmacy records, pharmacy providers identified by the household were contacted by telephone for the pharmacy follow-back component. Following an initial telephone contact, the signed permission forms and materials explaining the study were faxed (or mailed) to cooperating pharmacy providers. The materials informed the providers of all persons participating in the survey who had prescriptions filled at their place of business and requested a computerized printout of all prescriptions filled for each person. Starting with the 2009 pharmacy data collection, pharmacies could choose to report information in computer assisted telephone interviews (CATI). The CATI instrument was also used to enter information from printouts. For each medication listed, the following information was requested: date filled; national drug code (NDC); medication name; strength of medicine (amount and unit); quantity (package size/amount dispensed); and payments by source. Starting with the 2009 pharmacy data collection, when an NDC was provided, often the drug name and other drug characteristics were obtained from secondary proprietary data sources.

Related to Methodology for Collecting Pharmacy-Reported Variables

  • Local Interconnection Data Exchange for Billing 7.7.1 There are certain types of calls or types of Interconnection that require exchange of Billing records between the Parties, including, for example, alternate billed and Toll Free Service calls. The Parties agree that all call types must be routed between the networks, accounted for, and settled among the Parties. Certain calls will be handled via the Parties' respective operator service platforms. The Parties agree to utilize, where possible and appropriate, existing accounting and settlement systems to xxxx, exchange records and settle revenue.

  • Purchase Order Flip via Ariba Network (AN) The online process allows suppliers to submit invoices via the AN for catalog and non- catalog goods and services. Contractors have the ability to create an invoice directly from their Inbox in their AN account by simply “flipping” the purchase order into an invoice. This option does not require any special software or technical capabilities. For the purposes of this section, the Contractor warrants and represents that it is authorized and empowered to and hereby grants the State and the third-party provider of MFMP the right and license to use, reproduce, transmit, distribute, and publicly display within the system the information outlined above. In addition, the Contractor warrants and represents that it is authorized and empowered to and hereby grants the State and the third-party provider the right and license to reproduce and display within the system the Contractor’s trademarks, system marks, logos, trade dress, or other branding designation that identifies the products made available by the Contractor under the Contract.

  • 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).

  • Data Collection Some downloaded software included in the Materials may generate and collect information about the software and usage and transmit it to Intel to help improve Intel’s products and services. This collected information may include product name, product version, time of event collection, license type, support type, installation status, hardware and software performance, and use. 9.

  • Recovery Schedule If the initial schedule or any current updates fail to reflect the Work’s actual plan or method of operation, or a contractual milestone date is more than fifteen (15) days behind, Owner may require that a recovery schedule for completion of the remaining Work be submitted. The Recovery Schedule must be submitted within seven (7) calendar days of Owner’s request. The Recovery Schedule shall describe in detail Construction Contractor’s plan to complete the remaining Work by the required Contract milestone date. The Recovery Schedule submitted shall meet the same requirements as the original Construction Schedule. The narrative submitted with the Recovery Schedule should describe in detail all changes that have been made to meet the Contract milestone dates.

  • Name Collision Report Handling 6.3.1 During the first two years after delegation of the TLD, Registry Operator’s emergency operations department shall be available to receive reports, relayed by ICANN, alleging demonstrably severe harm from collisions with overlapping use of the names outside of the authoritative DNS.

  • Loss Leader; Recycled Products Contractor shall not sell or use any article or product as a “loss leader” as defined in Section 17030 of the Business and Professions Code. If Contractor will sell to the Judicial Council, or use in the performance of this Agreement, goods specified in PCC 12207 (for example, certain paper products, office supplies, mulch, glass products, lubricating oils, plastic products, paint, antifreeze, tires and tire-derived products, and metal products), then with respect to those goods: (i) Contractor shall use recycled products in the performance of this Agreement to the maximum extent doing so is economically feasible, and (ii) upon request, Contractor shall certify in writing under penalty of perjury, the minimum, if not exact, percentage of post consumer material as defined in the PCC 12200, in such goods regardless of whether the goods meet the requirements of PCC 12209.

  • Price Adjustments for OGS Centralized Contracts Periodic price adjustments will occur no more than twice per year on a schedule to be established solely by OGS. Pricing offered shall be fixed for the first twelve (12) months of the Contract term. Such price increases will only apply to the OGS Centralized Contracts and shall not be applied retroactively to Authorized User Agreements or any Mini-bids already submitted to an Authorized User. Price Decreases Price decreases may be made at any time. Additionally, some price decreases shall be calculated in accordance with Appendix B, section 17, Pricing.

  • DISTRIBUTION OF CONTRACTOR PRICE LIST AND CONTRACT APPENDICES Contractor shall provide Authorized Users with electronic copies of the Contract, including price lists and Appendices, upon request. OGS CENTRALIZED CONTRACT MODIFICATIONS Contract Updates will be handled as provided in Appendix C – Contract Modification Procedures.

  • RECOVERY PROCEDURES The nature and severity of any disaster will influence the recovery procedures. One crucial factor in determining how BellSouth will proceed with restoration is whether or not BellSouth's equipment is incapacitated. Regardless of who's equipment is out of service, BellSouth will move as quickly as possible to aid with service recovery; however, the approach that will be taken may differ depending upon the location of the problem.

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