Valid Value Code Set | Valid Value Code | Valid Value Name | Valid Value Description | Effective Start Date | Effective End Date |
---|---|---|---|---|---|
No data available in table |
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.
Data Element
COT033
COT.002.033
Definition | For services received during a single encounter with a provider, the date the service covered by this claim was received. For services involving multiple encounters on different days, or periods of care extending over two or more days, this would be the date on which the service covered by this claim began. For capitation premium payments, the date on which the period of coverage related to this payment began. For financial transactions reported to the OT file, populate with the first day of the time period covered by this financial transaction. For sub-capitation payments, this represents the first date of the period the sub-capitation payment covers. |
---|---|
Size | 9(8) |
FLF Start Position | 178 |
FLF Stop Position | 185 |
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 Type of Claim is not in [2,4,B,D,V] value must be less than or equal to associated End of Time Period value 4. Value must be less than or equal to associated Ending Date of Service value 5. When Type of Claim is not in [2,4,B,D,V] value must be less than or equal to associated Adjudication Date value 6. Value must be less than or equal to associated Date of Death (ELG.002.025) value when populated 7. Value must be less than or equal to at least one of the eligible's Enrollment End Date (ELG.021.254) values 8. Mandatory |
RULE ID | RULE Definition |
---|---|
RULE-1352 | If a claim is a non-denied claim from an OT file, then the beginning date of service value reported must be a valid date of the form CCYYMMDD. |
RULE-1354 | If beginning date of service is populated on a non-denied claim from an OT file that is not a Medicaid or Medicaid-expansion, S-CHIP, or Other Capitated Payment and end of time period is populated on the file header, then the beginning date of service value reported must be before or equal to the end of time period value reported. |
RULE-1355 | If the beginning date of service and ending date of service are populated on a non-denied claim from an OT file, then the beginning date of service value reported must be before the ending date of service value reported. |
RULE-1356 | If adjudication date and beginning date of service are populated on a non-denied claim from an OT file that is not a Medicaid or Medicaid-expansion, S-CHIP, or Other Capitated Payment, then the beginning date of service value reported must be before or equal to the adjudication date value reported. |
RULE-1357 | If a non-denied OT claim has a value populated for beginning date of service and the date of death is populated on the primary demographics eligibility segment, then the claim beginning date of service must be less than or equal to the date of death. |
RULE-7196 | If plan ID is populated on a non-denied, non-void Medicaid, S-CHIP, or Other encounter from an OT file, then the plan ID must be equal to the plan ID on a managed care participation segment from an ELG file with the same MSIS ID and enrollment effective and end dates that overlap the beginning date of service. |
RULE-7200 | If plan ID is populated on a non-denied Medicaid, S-CHIP, or Other encounter from an OT file, then the plan ID must be equal to the plan ID on a managed care main segment from an MCR file where the beginning date of service on the claim is within the contract effective and end dates on the managed care main segment. |
RULE-7215 | If a claim is a non-denied claim and is an original claim or a replacement/resubmission claim payment from an OT file, and is a Medicaid or Medicaid-expansion CHIP, Medicaid or Medicaid-expansion CHIP encounter, separate CHIP FFS or encounter claim or CHIP capitated or separate CHIP capitated payment, then the beginning date of service must be populated. |
RULE-7392 | If a claim is a non-denied, non-void claim from an OT file, and is a Medicaid/Medicaid-expansion CHIP or S-CHIP service tracking claim and is an original claim or a replacement/resubmission claim payment then the claim header beginning date of service must be populated. |
RULE-7424 | If a claim in a non-denied, original or adjustment FFS or Encounter crossover claim from an OT file, and the MSIS ID is populated and the beginning date of service is populated with a date that overlaps with the reported eligibility determinant effective and end dates, and the primary eligibility group indicator is equal to '1', then the dual eligible code is equal to '01', '02', '04', '08' |
RULE-7552 | If the 1115A demonstration indicator is equal to 1 (yes) on a non-denied claim from an OT file, and the beginning date of service is within the 1115A effective and end dates, then the 1115A demonstration indicator value reported on the 1115A demonstration information segment must be populated with a 1 value. |
RULE-7702 | If plan ID is populated on a non-denied Medicaid, S-CHIP, or Other capitation from an OT file, then the plan ID must be equal to the plan ID on a managed care main segment from an MCR file where the beginning date of service on the claim is within the contract effective and end dates on the managed care main segment. |
RULE-7706 | If plan ID is populated on a non-denied Medicaid, S-CHIP, or Other capitation from an OT file, then the plan ID must be equal to the plan ID on a managed care participation segment from an ELG file with the same MSIS ID and effective and end dates that overlap the beginning date of service. |
RULE-7722 | If a claim is on a non-denied claim and is an original claim or a replacement/resubmission claim payment from an OT file, and is a Medicaid or Medicaid-expansion CHIP encounter or separate CHIP Encounter claim, then the claim header beginning date of service must be populated. |
RULE-7726 | If a claim is a non-denied claim and is an original claim or a replacement/resubmission claim payment from an OT file, and is a Medicaid or Medicaid-expansion CHIP Capitation or separate CHIP Capitation claim, then the claim header beginning date of service must be populated. |
RULE-7741 | If a claim in a non-denied, original or adjustment Encounter crossover claim from an OT file, and the MSIS ID is populated and the beginning date of service is populated with a date that overlaps with the reported eligibility determinant effective and end dates, and the primary eligibility group indicator is equal to '1', then the dual eligible code is equal to '01', '02', '04', '08' |
RULE-7772 | If a claim is a non-denied claim from an OT file, and the waiver type is populated, and the claim beginning date of service is between the waiver enrollment effective and end dates, then the claim waiver type is equal to the waiver participation waiver type. |
RULE-7804 | If a claim is on a non-denied claim and is an original claim or a replacement/resubmission claim payment from an OT file, and is a Medicaid or Medicaid-expansion CHIP Fee for Service or Separate CHIP Fee for Service claim, then the claim header beginning date of service must be populated. |
RULE-7983 | If a claim in a non-denied, original or adjustment FFS crossover claim from an OT file, and the MSIS ID is populated and the beginning date of service is populated with a date that overlaps with the reported eligibility determinant effective and end dates, and the primary eligibility group indicator is equal to '1', then the dual eligible code is equal to '01', '02', '04', '08' |
Measure ID | Measure Name |
---|---|
ALL-13-001-1 | % of MSIS IDs limited to family planning (RESTRICTED-BENEFITS-CODE = 6) with non-family planning services (PROGRAM-TYPE not equal 2) |
ALL-13-004-4 | % of MSIS IDs with alien restricted benefits code status (RESTRICTED-BENEFITS-CODE = 2) with non-emergency room services |
ALL-13-004-6 | % of MSIS IDs with alien restricted benefits code status (RESTRICTED-BENEFITS-CODE = 2) with services that are not emergency room or pregnancy-related |
ALL-14-003-3 | % of MSIS IDs on crossover claim headers not enrolled as duals (QMB, QMB Plus, SLMB Plus, Other) on Beginning Date of Service |
ALL-14-007-7 | % of MSIS IDs on crossover claim headers enrolled as premium only dual groups (SLMB, QI, QDWI) on Beginning Date of Service |
ALL-21-003-3 | % of BILLING-PROV-NUM on claim headers that do not have a match in PRV00007 with active provider enrollment status (PROV-MEDICAID-ENROLLMENT-STATUS-CODE in (1, 2, 3, 4, 5, 6) on Beginning Date of Service |
FFS-25-003-3 | % of MSIS IDs enrolled on Beginning Date of Service |
FFS-25-007-7 | % of MSIS IDs enrolled on Beginning Date of Service |
MCR-31-003-3 | % of MSIS IDs enrolled on Beginning Date of Service |
MCR-31-004-4 | % of MSIS IDs enrolled on Beginning Date of Service |
MCR-31-008-8 | % of MSIS IDs enrolled on Beginning Date of Service |
MCR-31-009-9 | % of MSIS IDs enrolled on Beginning Date of Service |
MIS-25-001-1 | % missing: BEGINNING-DATE-OF-SERVICE (COT00002) |
MIS-29-001-1 | % missing: BEGINNING-DATE-OF-SERVICE (COT00002) |
MIS-59-001-1 | % missing: BEGINNING-DATE-OF-SERVICE (COT00002) |
MIS-6-003-3 | % missing: BEGINNING-DATE-OF-SERVICE (COT00002) |
MIS-83-001-1 | % missing: BEGINNING-DATE-OF-SERVICE (COT00002) |
RULE-1337 | % of claim headers with an MSIS ID not enrolled on Beginning Date of Service |
RULE-1540 | % of claim headers with a Billing Provider Number that is not found on the provider file during the dates of service |
RULE-7196 | % of claim headers with a valid value for Plan ID Number that do not have a corresponding ELG Managed Care Participation segment for the same time period |
RULE-7200 | % of claim headers with a valid value for Plan ID Number that do not have a corresponding MCR Managed Care Main segment for the same time period |
RULE-7392 | % missing: BEGINNING-DATE-OF-SERVICE (COT00002) |
RULE-7441 | % of claim headers with a BILLING-PROV-NUM that does not have a match in PRV00007 with active provider enrollment status (PROV-MEDICAID-ENROLLMENT-STATUS-CODE in (1, 2, 3, 4, 5, 6) on Beginning Date of Service |
RULE-7644 | % of claim headers with an MSIS ID not enrolled on Beginning Date of Service |
RULE-7646 | % of claim headers with an MSIS ID not enrolled on Beginning Date of Service |
DE Number | System DE Number | DE Name | File Segment Number | File Segment Name |
---|---|---|---|---|
CIP243 | CIP.003.243 | BEGINNING-DATE-OF-SERVICE | CIP00003 | CLAIM-LINE-RECORD-IP |
CIP290 | CIP.002.290 | BEGINNING-DATE-OF-SERVICE | CIP00002 | CLAIM-HEADER-RECORD-IP |
CLT048 | CLT.002.048 | BEGINNING-DATE-OF-SERVICE | CLT00002 | CLAIM-HEADER-RECORD-LT |
CLT196 | CLT.003.196 | BEGINNING-DATE-OF-SERVICE | CLT00003 | CLAIM-LINE-RECORD-LT |
COT166 | COT.003.166 | BEGINNING-DATE-OF-SERVICE | COT00003 | CLAIM-LINE-RECORD-OT |
Published Date | Data Guide Version | Data Element | Action | Field | Before | After |
---|---|---|---|---|---|---|
09/12/2024 | 3.29.0 | COT.002.033 | UPDATE | Definition | For services received during a single encounter with a provider, the date the service covered by this claim was received. For services involving multiple encounters on different days, or periods of care extending over two or more days, this would be the date on which the service covered by this claim began. For capitation premium payments, the date on which the period of coverage related to this payment began. For financial transactions reported to the OT file, populate with the first day of the time period covered by this financial transaction.For sub-capitation payments, this represents the first date of the period the sub-capitation payment covers. | For services received during a single encounter with a provider, the date the service covered by this claim was received. For services involving multiple encounters on different days, or periods of care extending over two or more days, this would be the date on which the service covered by this claim began. For capitation premium payments, the date on which the period of coverage related to this payment began. For financial transactions reported to the OT file, populate with the first day of the time period covered by this financial transaction. For sub-capitation payments, this represents the first date of the period the sub-capitation payment covers. |
09/12/2024 | 3.29.0 | COT.002.033 | 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. When Type of Claim is not in ['2', '4', 'B', 'D', 'V'] value must be less than or equal to associated End of Time Period value4. Value must be less than or equal to associated Ending Date of Service value5. When Type of Claim is not in ['2', '4', 'B', 'D', 'V'] value must be less than or equal to associated Adjudication Date value6. Value must be less than or equal to associated Date of Death (ELG.002.025) value when populated7. Value must be less than or equal to at least one of the eligible's Enrollment End Date (ELG.021.254) values8. Mandatory | 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 Type of Claim is not in [2,4,B,D,V] value must be less than or equal to associated End of Time Period value4. Value must be less than or equal to associated Ending Date of Service value5. When Type of Claim is not in [2,4,B,D,V] value must be less than or equal to associated Adjudication Date value6. Value must be less than or equal to associated Date of Death (ELG.002.025) value when populated7. Value must be less than or equal to at least one of the eligible's Enrollment End Date (ELG.021.254) values8. Mandatory |
08/09/2023 | 3.11.0 | COT.002.033 | UPDATE | Definition | For services received during a single encounter with a provider, the date the service covered by this claim was received. For services involving multiple encounters on different days, or periods of care extending over two or more days, this would be the date on which the service covered by this claim began. For capitation premium payments, the date on which the period of coverage related to this payment began. For financial transactions reported to the OT file, populate with the first day of the time period covered by this financial transaction. | For services received during a single encounter with a provider, the date the service covered by this claim was received. For services involving multiple encounters on different days, or periods of care extending over two or more days, this would be the date on which the service covered by this claim began. For capitation premium payments, the date on which the period of coverage related to this payment began. For financial transactions reported to the OT file, populate with the first day of the time period covered by this financial transaction.For sub-capitation payments, this represents the first date of the period the sub-capitation payment covers. |
07/15/2022 | 3.0.1 | COT033 | UPDATE | Data Dictionary | DE NO| DATA ELEMENT NAME COMPUTING|DEFINITION COT033|BEGINNING-DATE-OF-SERVICE|For services received during a single encounter with a provider, the date the service covered by this claim was received. For services involving multiple encounters on different days, or periods of care extending over two or more days, this would be the date on which the service covered by this claim began. For capitation premium payments, the date on which the period of coverage related to this payment began. For financial transactions reported to the OT file, populate with the first day of the time period covered by this financial transaction. |
DE NO| DATA ELEMENT NAME COMPUTING|DEFINITION COT033|BEGINNING-DATE-OF-SERVICE|For services received during a single encounter with a provider, the date the service covered by this claim was received. For services involving multiple encounters on different days, or periods of care extending over two or more days, this would be the date on which the service covered by this claim began. For capitation premium payments, the date on which the period of coverage related to this payment began. For financial transactions reported to the OT file, populate with the first day of the time period covered by this financial transaction. For sub-capitation payments, this represents the first date of the period the sub-capitation payment covers. |
05/08/2020 | 2.4.0 | BEGINNING-DATE-OF-SERVICE (COT033-0003) | UPDATE | Data Dictionary | The beginning date of service must occur before or be the same as the end of time period. | The beginning date of service must occur before or be the same as the end of time period for all claims except capitation payments and service tracking payments. |
05/08/2020 | 2.4.0 | BEGINNING-DATE-OF-SERVICE (COT033-0005) | UPDATE | Data Dictionary | Date must occur before or be the same as adjudication date. | Date must occur before or be the same as adjudication date for all claims except capitation payments and service tracking payments. |