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

Stop Users from Repeating the Same Symptom/Diagnosis in an Encounter #11299

Open
AdityaJ2305 opened this issue Mar 14, 2025 · 1 comment · May be fixed by #11302
Open

Stop Users from Repeating the Same Symptom/Diagnosis in an Encounter #11299

AdityaJ2305 opened this issue Mar 14, 2025 · 1 comment · May be fixed by #11302
Assignees
Labels

Comments

@AdityaJ2305
Copy link
Contributor

AdityaJ2305 commented Mar 14, 2025

Description

Currently, users can add the same symptom or diagnosis multiple times within a single encounter. This leads to redundancy and potential confusion in medical records. We need to implement a validation mechanism to prevent duplicate entries.

Expected Behavior

  • The system should detect and prevent duplicate symptoms or diagnoses in an encounter.

Screenshot

Image

References

https://rebuildearth.slack.com/archives/C010GQBMFJ9/p1741965051628559

originally reported by @bodhish


🚨 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.

@AdityaJ2305
Copy link
Contributor Author

Hey Team, I would like to work on this
Eta: 2 days
approach: Frontend validation while adding new item

@abhimanyurajeesh abhimanyurajeesh marked this as a duplicate of #11300 Mar 14, 2025
@AdityaJ2305 AdityaJ2305 linked a pull request Mar 14, 2025 that will close this issue
7 tasks
@github-project-automation github-project-automation bot moved this to Triage in Care Mar 15, 2025
@rithviknishad rithviknishad moved this from Triage to In Progress in Care Mar 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: In Progress
Development

Successfully merging a pull request may close this issue.

2 participants