Contact Protocol for Data Exchange Problems Sample Clauses

Contact Protocol for Data Exchange Problems. ‌ In all complex electronic data management programs there is the potential for an occasional breakdown in information exchange. If you have a program or technical problem involving your data exchange, the first person to contact is your own EDI Representative at the BCRC. Your EDI Representative should always be sought out first to help you find solutions for any questions, issues or problems you have. If after working with your EDI Representative, you think your problem could benefit from help at a higher level, please contact the EDI Director, Xxxxx Xxxxx, at 000-000-0000. His email address is: xxxxxx@xxxxxxxxxx.xxx. The BCRC Project Director, with overall responsibility for the EDI Department, is Xxx Xxxxx. Xx. Xxxxx can be reached at 000-000-0000. His email address is: XXxxxx@xxxxxxxxxx.xxx.
AutoNDA by SimpleDocs
Contact Protocol for Data Exchange Problems. In all complex electronic data management programs there is the potential for an occasional breakdown in information exchange. If you have a program or technical problem involving VDSA data exchange, the first person to contact is your own EDI Representative at the BCRC. Your EDI Rep should always be sought out first to help you find solutions for any questions, issues or problems you have. If after working with your EDI Rep, you think your problem could benefit from help at a higher level, please contact the EDI Supervisor, Xxxxxx Xxxxxxxx, at 000-000-0000. His email address is: jfarquhar @xxxxxxxxxx.xxx. If you feel further escalation is necessary, contact the EDI Manager, Xxxxxxx Xxxx, at 000-000-0000, Xx. Xxxx’x email address is: xxxxx@xxxxxxxxxx.xxx. The BCRC Project Director, with overall responsibility for the EDI Department, is Xxx Xxxxx. Xx. Xxxxx can be reached at 000-000-0000. His email address is: XXxxxx@xxxxxxxxxx.xxx. VDSA User Guide FREQUENTLY ASKED QUESTIONS TABLE OF CONTENTS Topic Page General 1 Terms of the Agreement 2 Record Layout / File Submissions 4 Part D and VDSAs 7 GENERAL Q1: Give me a high level explanation of the kinds of health plan coverage information you are capturing in order to better coordinate benefits between my health plan and Medicare? A1: VDSA partners and CMS exchange databases on a regular basis. The Non-MSP File (Non-Medicare secondary payer file) is used to capture and report drug coverage that is secondary to Medicare (such as benefits for covered retirees and their covered spouses and dependents). We need this specific drug coverage data to help the Part D plans calculate the beneficiaries’ True Out-Of- Pocket costs and to help pharmacies bill in the correct payer order at the pharmacy point of sale.
Contact Protocol for Data Exchange Problems. In all complex electronic data management programs there is the potential for an occasional breakdown in information exchange. If you have a program or technical problem involving VDSA data exchange, the first person to contact is your own EDI Representative at the COBC. Your EDI Rep should always be sought out first to help you find solutions for any questions, issues or problems you have. If after working with your EDI Rep you think your problem could benefit from help at a higher level, please contact the EDI Supervisor, Xxxxxxx Xxxx, at 000-000-0000. His email address is xxxxx@xxxxxxxxxxx.xxx. If you feel further escalation is necessary contact the EDI Manager, Xxxxxxx Xxxxxx, at 000-000-0000, Xx. Xxxxxx’x email address is xxxxxxx@xxxxxxxxxxx.xxx. The COBC Project Director, with overall responsibility for the EDI Department, is Xxxxxx XxXxxxx. Xx. XxXxxxx can be reached at 000-000-0000. Her email address is xxxxxxxx@xxxxxxxxxxx.xxx. You can also contact any of the CMS administrative contacts listed in the SPAP Data Sharing Agreement if you feel that the issues you are experiencing are ones that CMS should also be aware of. V: 2/20/08 VDSA User Guide FREQUENTLY ASKED QUESTIONS TABLE OF CONTENTS General 1 Terms of the Agreement… 3 Record Layout/File Submissions… 8 Part D and VDSAs 15 Retiree Drug Subsidy (RDS) Information… 18 General
Contact Protocol for Data Exchange Problems. In all complex electronic data management programs there is the potential for an occasional breakdown in information exchange. If you have a program or technical problem involving VDSA data exchange, the first person to contact is your own EDI Representative at the BCRC. Your EDI Rep should always be sought out first to help you find solutions for any questions, issues or problems you have. If after working with your EDI Rep, you think your problem could benefit from help at a higher level, please contact the EDI Supervisor, Xxxxxx Xxxxxxxx, at 000-000-0000. His email address is: jfarquhar @xxxxxxxxxx.xxx. If you feel further escalation is necessary, contact the EDI Manager, Xxxxxxx Xxxx, at 000-000-0000, Xx. Xxxx’x email address is: xxxxx@xxxxxxxxxx.xxx. The BCRC Project Director, with overall responsibility for the EDI Department, is Xxx Xxxxx. Xx. Xxxxx can be reached at 000-000-0000. His email address is: XXxxxx@xxxxxxxxxx.xxx. VDSA User Guide FREQUENTLY ASKED QUESTIONS TABLE OF CONTENTS Topic Page General 1 Terms of the Agreement 3 Record Layout / File Submissions 7 Part D and VDSAs 12 Retiree Drug Subsidy Information 14 GENERAL‌

Related to Contact Protocol for Data Exchange Problems

  • Loop Testing/Trouble Reporting 2.1.6.1 Think 12 will be responsible for testing and isolating troubles on the Loops. Think 12 must test and isolate trouble to the BellSouth portion of a designed/non- designed unbundled Loop (e.g., UVL-SL2, UCL-D, UVL-SL1, UCL-ND, etc.) before reporting repair to the UNE Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from BellSouth at the time of the trouble report, Think 12 will be required to provide the results of the Think 12 test which indicate a problem on the BellSouth provided Loop.

  • Required Procurement Procedures for Obtaining Goods and Services The Grantee shall provide maximum open competition when procuring goods and services related to the grant-assisted project in accordance with Section 287.057, Florida Statutes.

  • Disturbance Analysis Data Exchange The Parties will cooperate with one another and the NYISO in the analysis of disturbances to either the Large Generating Facility or the New York State Transmission System by gathering and providing access to any information relating to any disturbance, including information from disturbance recording equipment, protective relay targets, breaker operations and sequence of events records, and any disturbance information required by Good Utility Practice.

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

  • Benchmarks for Measuring Accessibility For the purposes of this Agreement, the accessibility of online content and functionality will be measured according to the W3C’s Web Content Accessibility Guidelines (WCAG) 2.0 Level AA and the Web Accessibility Initiative Accessible Rich Internet Applications Suite (WAI-ARIA) 1.0 for web content, which are incorporated by reference. Adherence to these accessible technology standards is one way to ensure compliance with the College’s underlying legal obligations to ensure that people with disabilities are able to acquire the same information, engage in the same interactions, and enjoy the same benefits and services within the same timeframe as their nondisabled peers, with substantially equivalent ease of use; that they are not excluded from participation in, denied the benefits of, or otherwise subjected to discrimination in any College programs, services, and activities delivered online, as required by Section 504 and the ADA and their implementing regulations; and that they receive effective communication of the College’s programs, services, and activities delivered online.

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

  • Access to Network Interface Device (NID 2.4.3.1. Due to the wide variety of NIDs utilized by BellSouth (based on subscriber size and environmental considerations), Mpower may access the on-premises wiring by any of the following means: BellSouth shall allow Mpower to connect its loops directly to BellSouth’s multi-line residential NID enclosures that have additional space and are not used by BellSouth or any other telecommunications carriers to provide service to the premise. Mpower agrees to install compatible protectors and test jacks and to maintain the protection system and equipment and to indemnify BellSouth pursuant to Section 8 of the General Terms and Conditions of this Agreement.

  • Testing/Trouble Reporting 1.15.1 TWTC will be responsible for testing and isolating troubles on Network Elements. TWTC must test and isolate trouble to the AT&T network before reporting the trouble to the Network Elements Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from AT&T at the time of the trouble report, TWTC will be required to provide the results of the TWTC test which indicate a problem on the AT&T network. Version: 4Q06 Standard ICA 11/30/06

  • Trunk Data Exchange 65.9.1 Each Party agrees to service trunk groups to the blocking criteria in Section 64.3.4 in a timely manner when trunk groups exceed measured blocking thresholds on an average time consistent busy hour for a twenty- one (21) Day study period. The Parties agree that twenty-one (21) Days is the study period duration objective unless mutually agreed otherwise. The study period will not include a holiday.

  • Data Encryption Contractor must encrypt all State data at rest and in transit, in compliance with FIPS Publication 140-2 or applicable law, regulation or rule, whichever is a higher standard. All encryption keys must be unique to State data. Contractor will secure and protect all encryption keys to State data. Encryption keys to State data will only be accessed by Contractor as necessary for performance of this Contract.

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