For each change record a new version will get added to the system.

(Functionally for both change types are similar i.e. Change and Un-recognized change)

Property mappings:

CodeSetType	Pega property	Base File/Change File	File property (Base file or Change file)	Is mandatory (From files)	Note
CPT	.Code	Change File	CPT_Code	Yes	Mandatory in both base and change files
	.CodeDescription	Base File	SHORT_DESCRIPTION	Yes	Mandatory, because we can show atleast one description for each code on UI
	.EffectiveDate	Change File	Revised_Start/Release_Date	Yes	If Revised_start is not available, Release_Date is considered as effective date
	.ExpirationDate	Change File	Date_Terminated/"Version_End- 1"/Release_Date		If version_End is not available, Release_Date is considered as end date Version_End is decrement by -1 because in case we receive same value for Version_End and Release_Date, we don't want any conflicts with the dates. Refer example for more details
	.FAC_TOTAL_RVU	Base File	FAC_TOTAL_RVU
	.FullDescription	Base File	FULL_DESCRIPTION
	.LongDescription	Base File	LONG_DESCRIPTION
	.NF_TOTAL_RVU	Base File	NF_TOTAL_RVU
	.Seq_Order	Base File	SEQ_ORDER
	.Status	Change File	Release_Date	Yes	"Changed as part of Release"+Release_Date
	.StatusIndicator	Change File	Status_indicator
	.Resequenced	Base File	Resequenced
	.Version	NA	Previous version+"0.1"		System will take previous version of the code and increment it by +"0.1"
ICD10 Dx	.Code	Change File	CODE	Yes	Mandatory in both base and change files
	.EffectiveDate	Change File	Revised_Start/Release_Date	Yes	If Revised_start is not available, Release_Date is considered as effective date
	.ExpirationDate	Change File	Date_Terminated/"Version_End- 1"/Release_Date		If version_End is not available, Release_Date is considered as end date Version_End is decrement by -1 because in case we receive same value for Version_End and Release_Date, we don't want any conflicts with the dates. Refer example for more details
	.ShortDescription	Base File	SHORT_DESCRIPTION	Yes	Mandatory, because we can show atleast one description for each code on UI
	.Full_Description	Base File	FULL_DESCRIPTION
	.LongDescription	Base File	LONG_DESCRIPTION
	.Validity	Base File	VALIDITY		If Validity is "C", value is set to "1", if Validity=="I", value is set to "0".
	.Status	Change File	Release_Date		"Changed as part of Release"+Release_Date
	.StatusIndicator	Change File	Status_indicator
	.CodeType	Base File	CODE_TYPE
	.Version	NA	Previous version+"0.1"		System will take previous version of the code and increment it by +"0.1"
HCPCS	.HCPC	Change File	HCPCS_CODE	Yes	Mandatory in both base and change files
	.EffectiveDate	Change File	Revised_Start/Release_Date	Yes	If Revised_start is not available, Release_Date is considered as effective date
	.ExpirationDate	Change File	Date_Terminated/"Version_End- 1"/Release_Date		If version_End is not available, Release_Date is considered as end date Version_End is decrement by -1 because in case we receive same value for Version_End and Release_Date, we don't want any conflicts with the dates. Refer example for more details.
	.ShortDesc	Base File	SHORT_DESCRIPTION	Yes	Mandatory, because we can show atleast one description for each code on UI
	.FullDescription	Base File	FULL_DESCRIPTION
	.LongDesc	Base File	.LONG_DESCRIPTION
	.Status	Change File	Release_Date	Yes	"Changed as part of Release"+Release_Date
	.StatusIndicator	Change File	Status_indicator
	.Version	NA	Previous version+"0.1"		System will take previous version of the code and increment it by +"0.1"

Example: Importing CPT files

Base file:

Change file: (we have two scenarios here as well; we can give Date_Teminated or not. Both are valid scenarios).

This is the valid combination to import with “C” or “U”.

After importing: New version gets added into the system with Version: 1.1 (New record).

EffectiveDate: Revised_Start, EndDate: Default date given by system.

Existing record with Version 1.0, gets updated with End date (Version_End - 1). EndDate: Version_End.