Allow Closing Enrollment Requests When Payer ID Changes
What’s New
-
Enrollment requests can now be moved to Closed status even if the associated plan’s Payer ID has changed.
-
Closure is permitted only when the enrollment is in On Hold status.
-
During closure under this exception, only the Status field can be modified.
-
Once moved to Closed, the enrollment becomes fully read-only.
-
No payer re-evaluation or remapping occurs during closure.
-
All other enrollment validation rules remain unchanged.
How It Works
-
An enrollment request is created using a plan mapped to a specific Payer ID.
-
The plan is later re-mapped to a different Payer ID.
-
The enrollment is placed in On Hold status (indicated by the red status bar).
-
The user updates the enrollment status to Closed.
Under the new logic:
-
The system allows the enrollment to be closed even though the Payer ID differs from the original mapping.
-
Only the Status field can be updated during this action.
-
Any attempt to modify other fields is blocked with a validation message.
-
If the enrollment is not in On Hold status, closure is blocked.
-
Once closed, the enrollment record becomes fully read-only, and no further updates are allowed.
Business Rules
-
Closure Exception Rule – Allows closure when Payer ID has changed, only if enrollment is On Hold.
-
Status-Only Update Rule – Blocks modification of any fields other than Status during closure.
-
Hold-State Requirement – Closure allowed only when enrollment is On Hold.
-
Immutability Rule – Closed enrollments are fully read-only.
-
Backward Compatibility – All other validation rules remain unchanged.
-
Operational Safety – No payer re-evaluation or remapping occurs during closure.
Benefits
-
Eliminates the need to temporarily revert payer mappings.
-
Reduces operational delays and manual workaround steps.
-
Preserves enrollment lifecycle audit integrity.
-
Maintains controlled validation while improving workflow efficiency.
-
Enhances stability in enrollment management without impacting existing processes.