MCR.002.030

MANAGED-CARE-MAIN-REC-EFF-DATE

Data Element

DE Number

MCR030

System DE Number

MCR.002.030

File Name

MCR - MANAGED CARE PLAN INFORMATION

File Segment Number

MCR00002

File Segment Name

MANAGED-CARE-MAIN

Last updated

09/12/2024

Overview Valid Values Related Rules Related DQ Measures Other Instances

Definition	The first calendar day on which all of the other data elements in the same segment were effective.
Size	9(8)
FLF Start Position	117
FLF Stop Position	124
Segment Key Field Identifier	(a)
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. Value must be before or the same as the associated Segment End Date value 4. Mandatory 5. Value of the CC component must be in [18,19,20]

Valid Value Code Set	Valid Value Code	Valid Value Name	Valid Value Description	Effective Start Date	Effective End Date
No data available in table

Search:

Show entries

RULE ID	RULE Definition
RULE-2575	If a segment is a managed care main segment from an MCR file, then the managed care main record effective date value reported must be a valid date of the form CCYYMMDD.
RULE-2577	If managed care main record effective date and managed care main record end date are populated on a managed care main segment from a MCR file, then the managed care main record effective date value reported must be before or equal to the managed care main record end date value reported.

Search:

Show entries

Measure ID	Measure Name
MCR-58-001-1	Ratio of errors for overlapping segment eff/end dates [RULE-2578] to all active MANAGED-CARE-MAIN (MCR00002) segments across all reporting and coverage periods
MIS-10-001-1	% distinct STATE-PLAN-ID-NUMs with only missing values in any active segment: MANAGED-CARE-MAIN-REC-EFF-DATE (MCR00002)
RULE-2578	Ratio of errors for overlapping segment eff/end dates [RULE-2578] to all active MANAGED-CARE-MAIN (MCR00002) segments

Search:

Show entries

DE Number	System DE Number	DE Name	File Segment Number	File Segment Name
No data available in table

Published Date	Data Guide Version	Data Element	Action	Field	Before	After
09/12/2024	3.29.0	MCR.002.030	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. Value must be before or the same as the associated Segment End Date value4. Mandatory5. Value of the CC component must be in ['18', '19', '20']	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. Value must be before or the same as the associated Segment End Date value4. Mandatory5. Value of the CC component must be in [18,19,20]
09/21/2023	3.13.0	MCR.002.030	UPDATE	Segment key field identifier	Not Applicable	(a)