Office-Based Provider Visit Data Editing and Imputation Sample Clauses

Office-Based Provider Visit Data Editing and Imputation. ‌ Expenditures for office-based provider visits were developed in a sequence of logical edits and imputations. “Household” edits were applied to sources and amounts of payment for all events reported by HC respondents. “MPC” edits were applied to provider-reported sources and amounts of payment for records matched to household-reported events. Both sets of edits were used to correct obvious errors (as described above) in the reporting of expenditures. After the data from each source were edited, a decision was made as to whether household- or MPC- reported information would be used in the final editing and in the predictive mean matching or hot-deck imputations for missing expenditures. The general rule was that MPC data would be used for events where a household-reported event corresponded to an MPC-reported event (i.e., a matched event), since providers usually have more complete and accurate data on sources and amounts of payment than households. One of the more important edits separated flat fee events from simple events. This edit was necessary because groups of events covered by a flat fee (i.e., a flat fee bundle) were edited and imputed separately from individual events covered by a single charge (i.e., simple events). (See Section 2.5.5 for more details on flat fee groups). Logical edits also were used to sort each event into a specific category for the imputations. Events with complete expenditures were flagged as potential donors while events with missing expenditure data were assigned to various recipient categories. Each event with missing expenditure data was assigned to a recipient category based on the extent of its missing charge and expenditure data. For example, an event with a known total charge but no expenditure information was assigned to one category, while an event with a known total charge and partial expenditure information was assigned to a different category. Similarly, events without a known total charge and no or partial expenditure information were assigned to various recipient categories. The logical edits produced eight recipient categories in which all events had a common extent of missing data. Separate hot-deck imputations were performed on events in each recipient category. For hospital inpatient and emergency room events, the donor pool was restricted to events with complete expenditures from the MPC. Due to the low ratio of donors to recipients for hospital outpatient and office based events there were no donor pool ...
AutoNDA by SimpleDocs

Related to Office-Based Provider Visit Data Editing and Imputation

  • Switching System Hierarchy and Trunking Requirements For purposes of routing ECI traffic to Verizon, the subtending arrangements between Verizon Tandem Switches and Verizon End Office Switches shall be the same as the Tandem/End Office subtending arrangements Verizon maintains for the routing of its own or other carriers’ traffic (i.e., traffic will be routed to the appropriate Verizon Tandem subtended by the terminating End Office serving the Verizon Customer). For purposes of routing Verizon traffic to ECI, the subtending arrangements between ECI Tandem Switches and ECI End Office Switches shall be the same as the Tandem/End Office subtending arrangements that ECI maintains for the routing of its own or other carriers’ traffic.

  • COVID-19 Protocols Contractor will abide by all applicable COVID-19 protocols set forth in the District’s Reopening and COVID-19 Mitigation Plan and the safety guidelines for COVID-19 prevention established by the California Department of Public Health and the Ventura County Department of Public Health.

  • Service Types Where you are funded for more than one service type under this Activity, and you have met the requirements within one of these service areas, you may shift all or part of any remaining funds to another service type you support under this Activity. You must advise us of resource attributions annually through the Activity Work Plan Report as detailed in Item E.

  • Review Protocol A narrative description of how the Claims Review was conducted and what was evaluated.

  • Standard Service Features Ethernet Access allows Customer to terminate single and/or multiple Ethernet Virtual Circuits (EVCs) from Customer equipment onto a single Ethernet Access UNI.

  • Additional Acceptable Uses of Student Data Contractor is prohibited from using Student Data for any secondary use not described in this agreement except:

  • Specification and Service Levels The Specification sets out the Services that the Contractor has undertaken to provide. The Specification includes Service Levels setting out particular levels of service that the Contractor has undertaken to meet.

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

  • Operating and Maintenance Manuals 58.1 If “as built” Drawings and/or operating and maintenance manuals are required, the Contractor shall supply them by the dates stated in the Contract Data.

  • Forecasting Requirements for Trunk Provisioning Within ninety (90) days of executing this Agreement, Reconex shall provide Verizon a two (2) year traffic forecast. This initial forecast will provide the amount of traffic to be delivered to and from Verizon over each of the Local Interconnection Trunk groups over the next eight (8) quarters. The forecast shall be updated and provided to Verizon on an as-needed basis but no less frequently than semiannually. All forecasts shall comply with the Verizon CLEC Interconnection Trunking Forecast Guide and shall include, at a minimum, Access Carrier Terminal Location (“ACTL”), traffic type (Local Traffic/Toll Traffic, Operator Services, 911, etc.), code (identifies trunk group), A location/Z location (CLLI codes for Reconex-IPs and Verizon-IPs), interface type (e.g., DS1), and trunks in service each year (cumulative).

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