CLT.002.166

An official website of the United States government

Official websites use .gov
A .gov website belongs to an official government organization in the United States.

Secure .gov websites use HTTPS
A lock () or https:// means you've safely connected to the .gov website. Share sensitive information only on official, secure websites.

TMSIS Dataguide

Medicaid.gov

Version 3.27.0

THIRD-PARTY-COPAYMENT-DATE-PAID

Data Element

DE Number

CLT166

System DE Number

CLT.002.166

File Name

CLT - CLAIM LONG-TERM CARE

File Segment Number

File Segment Name

CLAIM-HEADER-RECORD-LT

Last updated

Overview Valid Values Related Rules Related DQ Measures Other Instances

Definition	The date the third party paid the copayment amount.
Size	9(8)
FLF Start Position	1101
FLF Stop Position	1108
Segment Key Field Identifier	Not Applicable
Coding Requirements	1. Value must be 8 characters in the form "CCYYMMDD" 2. The date must be a valid calendar date (i.e. Feb 29th only on the leap year, never April 31st or Sept 31st) 3. When populated, must have an associated Third Party Copayment Amount 4. Situational

Valid Value Code Set	Valid Value Code	Valid Value Name	Valid Value Description	Effective Start Date	Effective End Date

RULE ID	RULE Definition
RULE-1175	If a claim is a non-denied claim from an LT file, then the third party copayment date paid value reported must be a valid date of the form CCYYMMDD.

Measure ID	Measure Name

DE Number	System DE Number	DE Name	File Segment Number	File Segment Name
CIP219	CIP.002.219	THIRD-PARTY-COPAYMENT-DATE-PAID	CIP00002	CLAIM-HEADER-RECORD-IP
COT143	COT.002.143	THIRD-PARTY-COPAYMENT-DATE-PAID	COT00002	CLAIM-HEADER-RECORD-OT
CRX101	CRX.002.101	THIRD-PARTY-COPAYMENT-DATE-PAID	CRX00002	CLAIM-HEADER-RECORD-RX

Published Date	Data Guide Version	Data Element	Action	Field	Before	After
09/25/2023	3.14.0	CLT.002.166	UPDATE	Coding requirement	Value must be 8 characters in the form "CCYYMMDD"2. The date must be a valid calendar date (i.e. Feb 29th only on the leap year, never April 31st or Sept 31st)3. When populated, must have an associated Third Party Copayment Amount 4. Situational	1. Value must be 8 characters in the form "CCYYMMDD"2. The date must be a valid calendar date (i.e. Feb 29th only on the leap year, never April 31st or Sept 31st)3. When populated, must have an associated Third Party Copayment Amount4. Situational
08/29/2023	3.12.0	CLT.002.166	UPDATE	Necessity	Optional	Situational
08/23/2023	3.12.0	CLT.002.166	UPDATE	Coding requirement	1. Value must be 8 characters in the form "CCYYMMDD"2. The date must be a valid calendar date (i.e. Feb 29th only on the leap year, never April 31st or Sept 31st)3. Must have an associated Third Party Copayment Amount4. Situational	Value must be 8 characters in the form "CCYYMMDD"2. The date must be a valid calendar date (i.e. Feb 29th only on the leap year, never April 31st or Sept 31st)3. When populated, must have an associated Third Party Copayment Amount 4. Situational
08/23/2023	3.12.0	CLT.002.166	UPDATE	Coding requirement	1. Value must be 8 characters in the form "CCYYMMDD"2. The date must be a valid calendar date (i.e. Feb 29th only on the leap year, never April 31st or Sept 31st)3. Must have an associated Third Party Copayment Amount4. Optional	1. Value must be 8 characters in the form "CCYYMMDD"2. The date must be a valid calendar date (i.e. Feb 29th only on the leap year, never April 31st or Sept 31st)3. Must have an associated Third Party Copayment Amount4. Situational