This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| claim_pended [2016/09/19 09:40] – lisa.maloney | claim_pended [2025/09/18 18:53] (current) – tina.robles | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| __**Claims Pended**__ | __**Claims Pended**__ | ||
| + | |||
| + | The Claims Pended screen can be accessed by clicking Pended in the Claim -> Claim View menu. | ||
| + | |||
| + | {{: | ||
| The Claims Pended grid displays all claims in a Pended status and a option to view claims by Reason Code. | The Claims Pended grid displays all claims in a Pended status and a option to view claims by Reason Code. | ||
| Line 11: | Line 15: | ||
| This column displays the Grouping Description hierarchy for the group which has visibility to the claim based on Claimant. This column can be filtered to a group by entering the text in the column filter and clicking enter. | This column displays the Grouping Description hierarchy for the group which has visibility to the claim based on Claimant. This column can be filtered to a group by entering the text in the column filter and clicking enter. | ||
| - | {{:pasted:20160919-093105.png}} | + | {{:pasted:20240820-170218.png}} |
| __Visibility Indicator__ | __Visibility Indicator__ | ||
| - | This column displays True or False. | + | This column displays True or False. |
| + | |||
| + | There is an Access Role (managed by an admin user) labeled "Claim – Visibility All" which allows users to view all pendings, not limited by visibility. | ||
| In the screenshot below, the user is in both the hierarchy2 and level A groups, but not the level 2 group. | In the screenshot below, the user is in both the hierarchy2 and level A groups, but not the level 2 group. | ||
| - | {{:pasted:20160919-093424.png}} | + | {{:pasted:20240820-170235.png}} |
| ----- | ----- | ||
| Line 26: | Line 33: | ||
| This displays the date of the oldest Pend reason for the Claim. | This displays the date of the oldest Pend reason for the Claim. | ||
| - | {{:pasted:20160423-200003.png}} | + | {{:pasted:20240820-170257.png}} |
| ----- | ----- | ||
| Line 33: | Line 40: | ||
| Clicking the Contract ID will open a new tab for the contract selected. | Clicking the Contract ID will open a new tab for the contract selected. | ||
| - | {{:pasted:20160423-204749.png}} | + | {{:pasted:20240820-170339.png}} |
| ----- | ----- | ||
| **Contract Creator** | **Contract Creator** | ||
| Line 39: | Line 46: | ||
| The Contract Creator First Name and Last Name display on the Pending grid. These columns will be blank if the Contract has not resolved to a specific version, or if there is no Contract assigned to the claim. | The Contract Creator First Name and Last Name display on the Pending grid. These columns will be blank if the Contract has not resolved to a specific version, or if there is no Contract assigned to the claim. | ||
| - | {{:pasted:20160817-094753.png}} | + | {{:pasted:20240820-170406.png}} |
| ----- | ----- | ||
| + | |||
| + | **Claim Notes** | ||
| + | |||
| + | There is a column in the Claim Pended grid titled "Claim Notes" | ||
| + | |||
| + | {{: | ||
| + | |||
| + | To view the note, or to add a new note, highlight a pending claim row and click the Claim Notes button at the bottom of the screen. | ||
| + | |||
| + | {{: | ||
| + | |||
| + | ----- | ||
| + | |||
| **Column Filters** | **Column Filters** | ||
| - | All columns have a filter option. | + | All columns have a filter option. |
| - | {{:pasted:20160919-094012.png}} | + | {{:pasted:20240820-171135.png}} |
| ----- | ----- | ||
| **Filter Reason Codes** | **Filter Reason Codes** | ||
| Line 53: | Line 73: | ||
| In the below screenshot, 9.87% of claims are pending for Missing manufacturer sku. Clicking on this row in the Filter Reason Codes grid automatically filters by this reason code. | In the below screenshot, 9.87% of claims are pending for Missing manufacturer sku. Clicking on this row in the Filter Reason Codes grid automatically filters by this reason code. | ||
| - | {{:pasted:20160423-201625.png}} | + | {{:pasted:20240820-171359.png}} |
| ----- | ----- | ||
| NOTE: Claims and line items can pend for multiple reasons. | NOTE: Claims and line items can pend for multiple reasons. | ||
| - | {{:pasted:20160423-201810.png}} | + | {{:pasted:20240820-171505.png}} |
| ----- | ----- | ||
| - | __Pie Chart__ | + | **Multi-Claim Assign Contract** |
| + | |||
| + | If there are multiple claims which need to be assigned to a single contract, that action can be done here for users with permissions. | ||
| + | |||
| + | Select the claims to assign to the contract by either [ctrl + click] to select records one at a time or [shift + click] to select a group of records. | ||
| + | |||
| + | {{: | ||
| + | |||
| + | This will open up the Contract Search with default criteria of Claimable = True and Contract End Date greater than or equal to today' | ||
| + | |||
| + | {{: | ||
| + | |||
| + | Once the contract is assigned to the claim, that claim will no longer be in a pended state as it needs to run through the calculate claim process to determine its updated state. | ||
| + | ----- | ||
| + | **Mass Update Pending Lines and Mass reject claims at the header** | ||
| + | |||
| + | Multiple claims can be actioned at once to reject, recalc, override or unhold pending lines. | ||
| + | |||
| + | Multiple claims can also be mass rejected at once. This would be used for a batch of claims where you want to reject the entire claim. | ||
| + | |||
| + | {{: | ||
| + | |||
| + | |||
| + | Click on the pending reason to action and then click Commit. | ||
| + | |||
| + | {{: | ||
| + | |||
| + | ----- | ||
| + | |||
| + | **Report - Claim Line Item Pending** | ||
| + | |||
| + | A detail report is available at the bottom of the Claims Pended screen. | ||
| + | |||
| + | To run this report, click the report button. | ||
| + | |||
| + | {{: | ||
| + | |||
| + | Click the Generate button. | ||
| + | |||
| + | {{: | ||
| + | |||
| + | A wait message will display while the report is being generated. | ||
| + | |||
| + | {{: | ||
| + | |||
| + | To open the report, click the hyperlink in the Generated Reports section. | ||
| + | |||
| + | {{: | ||
| + | |||
| + | ----- | ||
| + | |||
| + | __Chart__ | ||
| + | |||
| + | There is a Chart that displays a visual representation of Pendings by Reason Code. | ||
| + | |||
| + | {{: | ||
| + | |||
| + | To view the claims pending for a specific reason, click on that portion of the chart and the data will display in the grid on the left. | ||
| + | |||
| + | The count related to each reason will display on hover over that reason. | ||
| + | |||
| + | Data can be removed/ | ||
| + | |||
| + | {{: | ||
| + | |||
| + | **Enhanced Claim Line Item Status Classification** | ||
| + | |||
| + | A new pending reason designation has been implemented to improve claim processing accuracy. Claims associated with | ||
| + | terminated contract versions will now display a specific Terminated Contract status indicator, replacing the previous Out of Time Frame designation. This enhancement provides more precise identification of claim status rationale. | ||
| + | |||
| + | {{: | ||
| + | ----- | ||
| + | |||
| + | **Automated Claims Rejection Enhancement** | ||
| + | |||
| + | Contract Hint Mapping - NPGS Integration | ||
| + | |||
| + | Feature Overview | ||
| + | An intelligent automated rejection system has been implemented to streamline claims processing for contracts designated as "Not Paid at GoSimple" | ||
| + | |||
| + | __Functional Specifications__ | ||
| + | |||
| + | **Trigger Mechanism** | ||
| + | * Contract Hint Mapping: When a contract hint is configured with NPGS - Not paid at GoSimple designation | ||
| + | * Automatic Processing: Claims associated with NPGS-mapped contracts undergo immediate automated rejection upon creation | ||
| + | * Real-Time Execution: Rejection occurs instantaneously during the claim creation workflow | ||
| + | |||
| + | **Process Automation** | ||
| + | * Elimination of Manual Tasks: Removes requirement for manual claim rejection activities | ||
| + | * Processing Efficiency: Significantly reduces time-to-resolution for NPGS-designated claims | ||
| + | * Workflow Optimization: | ||
| + | |||
| + | __System Behavior__ | ||
| + | |||
| + | **Automated Actions** | ||
| + | - Claim Creation Detection: System identifies newly created claims | ||
| + | - Contract Hint Validation: Evaluates associated contract hint mappings | ||
| + | - NPGS Status Check: Determines if contract is designated as "Not paid at GoSimple" | ||
| + | - Automatic Rejection: Executes immediate claim rejection for NPGS-mapped contracts | ||
| + | - Documentation: | ||
| + | |||
| + | **Audit & Documentation** | ||
| + | * Automated Notation: System-generated notes clearly identify claims rejected through NPGS automation | ||
| + | * Process Transparency: | ||
| + | * Audit Trail: Maintains comprehensive record of all automated rejection activities | ||
| + | |||
| + | __Business Benefits__ | ||
| + | |||
| + | **Operational Efficiency** | ||
| + | * Time Reduction: Eliminates manual processing time for NPGS-designated claims | ||
| + | * Resource Optimization: | ||
| + | * Consistency: | ||
| + | |||
| + | **Process Improvements** | ||
| + | * Error Reduction: Minimizes human error in NPGS claim identification and rejection | ||
| + | * Standardization: | ||
| + | * Scalability: | ||
| - | There is a Pie Chart that displays a visual representation of Pendings by Reason Code. | + | **Technical Implementation** |
| + | * Integration Point: Seamless integration with existing contract hint mapping infrastructure | ||
| + | * Performance Impact: Minimal system overhead with real-time processing capabilities | ||
| + | * Configuration Management: Centralized NPGS designation management through contract hint interface | ||
| - | There are some future enhancements coming | + | **Quality Assurance** |
| + | * Validation Logic: Robust validation ensures accurate NPGS identification | ||
| + | * Exception Handling: Comprehensive error management | ||
| + | * Monitoring: Automated tracking of rejection volumes and processing metrics | ||
| + | {{: | ||