Common use of Correction of State Input Data Clause in Contracts

Correction of State Input Data. In the event State is unable or requests Contractor to create input data to utilize the Quality Intelligence Application to process data and produce correct results, State will send its then-current input data (“State-Formatted Input Data”) to the Contractor for analysis and processing. Once analyzed, the Contractor shall do one of the following: (1) If the State-Formatted Input Data is determined to be incorrectly formatted for input to the Quality Intelligence Suite, the Contractor shall create a State translation process (“State Data Translation”) and translate State-Formatted Input Data (at the Contractor’s standard support rate set out in Attachment B) in order for State-Formatted Input Data to correctly be presented as input to the Quality Intelligence Application. If data that is required for the Quality Intelligence Application was omitted from State-Formatted Input Data, the State agrees to modify State- Formatted Input Data as requested by the Contractor and send such data to the Contractor as needed. Once the State Data Translation is developed, the Contractor will provide a “plug-in” to its Quality Intelligence Application, which will incorporate the State Data Translation into the Quality Intelligence Application for State to use for future HEDIS runs. The State agrees to utilize the State-Formatted Input Data format for future runs of the Quality Intelligence Application. (2) If the State-Formatted Input Data is determined to be correctly formatted but is not accepted by the Licensed Software, the Contractor shall correct the problem at no charge. (3) Any orders that are pended in a “needs information” status for longer than 28 days without response or direction from the State will be automatically cancelled.

Correction of State Input Data. In the event that State is unable or requests Contractor unwilling to create input data to utilize the Quality Intelligence Application Engine to process data and produce correct results, State will send its then-current input data (“State-Formatted Input Data”) to the Contractor for analysis and processing. Once analyzed, the Contractor shall will do one of the following: (1) If the State-Formatted Input Data is determined to be incorrectly formatted for input to the Quality Intelligence SuiteEngine, the Contractor shall will create a State client translation process (“State Data Translation”) and translate State-Formatted Input Data (at the Contractor’s standard support rate set out in Attachment B) in order for State-Formatted Input Data to correctly be presented as input to the Quality Intelligence ApplicationEngine. If data that is required for the Quality Intelligence Application Engine was omitted from State-Formatted Input Data, the State agrees to modify State- State-Formatted Input Data as requested by the Contractor and send such data to the Contractor as needed. Once the State Data Translation is developed, the Contractor will provide a “plug-in” to its Quality Intelligence ApplicationEngine, which will incorporate the State Data Translation into the Quality Intelligence Application Engine for State to use for future HEDIS runs. The State agrees to utilize the State-Formatted Input Data format for future runs of the Quality Intelligence ApplicationEngine. (2) If the State-Formatted Input Data is determined to be correctly formatted but is not accepted by the Licensed Softwaresoftware, the Contractor shall will correct the problem at no charge. (3) Any orders that are pended in a “needs information” information status for longer than 28 days without response or direction from the State will be automatically cancelled.

Correction of State Input Data. In the event that the State is unable or requests Contractor unwilling to create input data to utilize the Quality Intelligence Application VERISK Engine to process data and produce correct results, the State will send its then-current input data (“State-Formatted Input Data”) to the Contractor systems for analysis and processing. Once analyzed, the Contractor shall will do one of the following: (1a) If the State-Formatted Input Data is determined to be incorrectly formatted for input to the Quality Intelligence Suite‘VERISK’ Engine, the Contractor shall will create a State client translation process (“State Data Translation”) and translate State-State- Formatted Input Data (at the Contractor’s standard support rate set out in Attachment B) in order for State-Formatted Input Data to correctly be presented as input to the Quality Intelligence Application‘VERISK’ Engine. Such expenses shall be billed under the Ad Hoc budget at a rate of $180 per hour. If data that is required for the Quality Intelligence Application ‘VERISK’ Engine was omitted from State-Formatted Input Data, the State agrees to modify State- State-Formatted Input Data as requested by the Contractor Contractor, and send such data to the Contractor as needed. Once the State Data Translation is developed, the Contractor will provide a “plug-in” to its Quality Intelligence Application‘VERISK’ Engine, which will incorporate the State Data Translation into the Quality Intelligence Application ‘VERISK’ Engine for State to use for future HEDIS runs. The State agrees to utilize the State-Formatted Input Data format for future runs of the Quality Intelligence Application. (2) ‘VERISK’ Engine at State’s site. If the State-Formatted Input Data is determined to be correctly formatted but is not accepted by the Licensed Softwareformatted, the Contractor shall will correct the problem and provide a corrected version of the ‘VERISK’ Engine to State at no charge. (3) Any orders that are pended in a “needs information” status for longer than 28 days without response or direction from the State will be automatically cancelled.

Correction of State Input Data. In the event State is unable or requests Contractor to create input data to utilize the Quality Intelligence Application Suite to process data and produce correct results, State will send its then-current input data (“State-Formatted Input Data”) to the Contractor for analysis and processing. Once analyzed, the Contractor shall will do one of the following: (1) If the State-Formatted Input Data is determined to be incorrectly formatted for input to the Quality Intelligence Suite, the Contractor shall will create a State client translation process (“State Data Translation”) and translate State-Formatted Input Data (at the Contractor’s standard support rate set out in Attachment B) in order for State-Formatted Input Data to correctly be presented as input to the Quality Intelligence ApplicationSuite. If data that is required for the Quality Intelligence Application Suite was omitted from State-Formatted Input Data, the State agrees to modify State- State-Formatted Input Data as requested by the Contractor and send such data to the Contractor as needed. Once the State Data Translation is developed, the Contractor will provide a “plug-in” to its Quality Intelligence ApplicationSuite, which will incorporate the State Data Translation into the Quality Intelligence Application Suite for State to use for future HEDIS runs. The State agrees to utilize the State-Formatted Input Data format for future runs of the Quality Intelligence ApplicationSuite. (2) If the State-Formatted Input Data is determined to be correctly formatted but is not accepted by the Licensed Software, the Contractor shall will correct the problem at no charge. (3) Any orders that are pended in a “needs information” status for longer than 28 days without response or direction from the State will be automatically cancelled.