Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Duplicated documents on claims history #18

Open
luticm opened this issue Sep 21, 2023 · 3 comments
Open

Duplicated documents on claims history #18

luticm opened this issue Sep 21, 2023 · 3 comments

Comments

@luticm
Copy link
Contributor

luticm commented Sep 21, 2023

After clicking "View history" for a claim, the detail pane is shown with the history pane. The combination of both shows the last document repeated, which is confusing.

The interface should exhibit detail pane with latest document and history pane with (N-1 documents).

@luticm luticm changed the title Duplicated records on claims history Duplicated documents on claims history Sep 21, 2023
@joelhulen
Copy link
Collaborator

This has already been addressed. Here's a screenshot viewing the entire claim history for one of the items:

image

@joelhulen
Copy link
Collaborator

Here's the site where I pulled up the history: https://webcoreclaimsf391c.z13.web.core.windows.net/adjudicator/claims

@joelhulen
Copy link
Collaborator

@fonsecamar do you see the code block that removes the duplicate claim header for the history? https://github.com/Azure/Medical-Claims-Transaction-Processing-at-scale/blob/main/src/CoreClaims.Infrastructure/Repository/ClaimRepository.cs#L127

            // Remove duplicate claim history item that matches the current claim header.
            if (header != null && details.Any())
            {
                var duplicate = details.FirstOrDefault(d => d.AdjustmentId == header.AdjustmentId);
                if (duplicate != null)
                {
                    details.Remove(duplicate);
                }
            }

If you have this code in your local clone, then it's possible that the AdjustmentId values don't match up for some reason. Please let me know.

hatboyzero pushed a commit that referenced this issue May 15, 2024
…e-for-adjudicator-manager

Apply discount should be able for adjudicator manager
hatboyzero pushed a commit that referenced this issue May 15, 2024
Initial front end styling and component clean up
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants