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 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 for the hot-deck imputations, 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 restri...
AutoNDA by SimpleDocs

Related to Office-Based Provider Visit Data Editing and Imputation

  • Switching System Hierarchy and Trunking Requirements For purposes of routing CSTC 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 CSTC, the subtending arrangements between CSTC Tandem Switches and CSTC End Office Switches shall be the same as the Tandem/End Office subtending arrangements that CSTC 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.

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

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

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