Adding new code (Change Type: N): New
This change type is for adding new codes into the system.
- 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 .EffectiveDate Change File Original_Start Yes
If Original_Start is not provided, system will consider Release_Date as effective date .ExpirationDate Change File Date_Terminated If Date_Terminated is not provided by user, system will set "12/31/9999" as default end date
.CodeDescription Base File SHORT_DESCRIPTION Yes Mandatory, because we can show atleast one description for each code on UI
.FullDescription Base File FULL_DESCRIPTION .LongDescription Base File LONG_DESCRIPTION .FAC_TOTAL_RVU Base File FAC_TOTAL_RVU .NF_TOTAL_RVU Base File NF_TOTAL_RVU .Seq_Order Base File SEQ_ORDER .Status Change File Release_Date Yes Original_Start/Release_Date must be mandatory .StatusIndicator Change File Status_indicator .Resequenced Base File Resequenced .Version NA "1.0" Default “1.0”, set by system .PlaceHolder Base File PLACE_HOLDER ICD10 Dx .Code Change File CODE Yes Mandatory in both base and change files .EffectiveDate Change File Original_Start Yes
If Original_Start is not provided, system will consider Release_Date as effective date
.ExpirationDate Change File Date_Terminated .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 Yes Original_Start/Release_Date must be mandatory .StatusIndicator Change File Status_indicator .CodeType Base File CODE_TYPE .Version NA "1.0" Default “1.0”, set by system HCPCS .HCPC Change File HCPCS_CODE Yes Mandatory in both base and change files .EffectiveDate Change File Original_Start Yes
If Original_Start is not provided, system will consider Release_Date as effective date
.ExpirationDate Change File Date_Terminated .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 Base File Release_Date Yes Original_Start/Release_Date must be mandatory .StatusIndicator Change File Status_indicator .Version NA "1.0" Default “1.0”, set by system
- Example: CPT
- Base file:
- Change file:
This is the valid combination to import with “N”. System will take Original_Start, Status_indicator, Release_Date and process the record.
- Scenario 1: We give Date_Terminated.
- Scenario 2: In this we don’t give Date_Terminated, so End date will
be defaulted by system.
- After importing (Scenario 2): New code will be added. Version: 1.0.
(New Record)
EffectiveDate: Original_Start, EndDate: Default date given by system
Previous topic Scenarios with different change types Next topic Updating existing code (Change_Type: C and U) : Change or Unrecognized change