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

ICD-11 Diagnosis code not working properly in CARE diagnosis module. #7769

Closed
dpnkr1 opened this issue May 7, 2024 · 3 comments · Fixed by coronasafe/care#2193
Closed

ICD-11 Diagnosis code not working properly in CARE diagnosis module. #7769

dpnkr1 opened this issue May 7, 2024 · 3 comments · Fixed by coronasafe/care#2193
Assignees
Labels
Backend P1 breaking issue or vital feature

Comments

@dpnkr1
Copy link

dpnkr1 commented May 7, 2024

**For some of the ICD diagnosis code when entered in CARE its shows no result found but after we delete the last character of that code the diagnosis comes up **

To Reproduce
Steps to reproduce the behavior:

  1. Go to 'cares consultation page then scroll down to the diagnosis part'
  2. Then open icd 11 and copy the code for copd "CA22.Z"
  3. Then come back to cares diagnosis part and paste or type the icd-11 code there.
  4. Then you will see that care is not able to find the diagnosis copd with that copd code copied from icd 11, but when we delete the last character of the code (CA22.Z) which is Z, you will see the diagnosis copd will come up.

Expected behavior
After putting the code in diagnosis part. which we take from icd-11, the diagnosis should come up.

Screenshots

07.05.2024_13.38.59_REC.mp4

Desktop (please complete the following information):

  • OS: [e.g. iOS]
  • Browser [e.g. chrome, safari]
  • Version [e.g. 22]

Smartphone (please complete the following information):

  • Device: [e.g. iPhone6]
  • OS: [e.g. iOS8.1]
  • Browser [e.g. stock browser, safari]
  • Version [e.g. 22]

Additional context
Add any other context about the problem here.

@rithviknishad
Copy link
Member

Related to: coronasafe/care#1838

@aparnacoronasafe aparnacoronasafe added the P1 breaking issue or vital feature label May 20, 2024
Copy link

⚠️ Refrain from assigning this issue to yourself if you have another P1 issue assigned that is not yet closed.

@aparnacoronasafe
Copy link
Member

@nihal467 @sainak @rithviknishad

Can we take this up as priority and close in 14 days?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Backend P1 breaking issue or vital feature
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants