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

Data inconsistency in marking coverages #11263

Open
Tanuj1718 opened this issue Mar 12, 2025 · 2 comments
Open

Data inconsistency in marking coverages #11263

Tanuj1718 opened this issue Mar 12, 2025 · 2 comments
Labels
needs-triage question Further information is requested

Comments

@Tanuj1718
Copy link
Contributor

Describe the bug
New coverage is appended at the top and get marked as Coverage 1. But it should be the Current total coverage + 1 ( like if there are 5 coverages, the new coverage should be 6th one).

To Reproduce
Steps to reproduce the behavior:

  1. Go to https://care.ohc.network/facility/490a6d07-1baf-47f3-9f0f-18be27284fcb/patient/f512be5d-2705-4f26-a071-d880a36fbbef/encounter/a1d305e7-4007-4f0e-81cd-b65b0d5a2458/claims
  2. Create a new coverage
  3. See error

Expected behavior

  1. If we are appending the latest coverage at the top, then it should be the n-th coverage ,not the first coverage.
  2. Practically we should append the latest coverage at the last and give number accordingly.

Screenshots

Screen.Recording.2025-03-12.at.10.05.01.PM.mov

🚨 DO NOT EDIT BELOW THIS LINE 🚨

Instructions for Requesting Assignment:

To request assignment, please clearly outline your solution and timeline by commenting on the issue using the format below:

Describe your solution clearly:
Provide a detailed explanation of your proposed solution, including your approach, key implementation steps, and relevant examples or references. Mention any dependencies, assumptions, or risks you foresee that might affect your timeline or implementation.

Expected Timeline:

  • End date: [Expected submission date of a completed Pull Request]

Additional Context:
Include any other relevant context, links, screenshots, or resources that support your proposed solution.

🚨 Your assignment may be unassigned if there is no activity or progress within the stated timeline unless communicated clearly and agreed upon.

@Tanuj1718
Copy link
Contributor Author

Tanuj1718 commented Mar 12, 2025

@rithviknishad if it is valid, i would like to work on it
ETA: 14 March

@vivekbisen04
Copy link

@Tanuj1718 are you working on this issue?

@github-actions github-actions bot added needs-triage question Further information is requested labels Mar 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-triage question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants