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

Enhancement to the CARE Scribe #8285

Closed
6 tasks
nihal467 opened this issue Aug 11, 2024 · 5 comments · Fixed by #8469
Closed
6 tasks

Enhancement to the CARE Scribe #8285

nihal467 opened this issue Aug 11, 2024 · 5 comments · Fixed by #8469
Assignees

Comments

@nihal467
Copy link
Member

nihal467 commented Aug 11, 2024

Follow-up : #8183 (comment)

Is your feature request related to a problem? Please describe.

  • he diagnosis is not being auto-filled based on the diagnosis code
    Note: Auto-fill only works if we say the name of the diagnosis cholera, not the code 1A00
  • We cannot discontinue a medicine using the scribe because the scribe is unaware of the currently filled data.
  • The errors are not normal user-friendly messages for example whisper failed, error creating scribe instance, something went wrong

Describe the solution you'd like

  • diagnosis autofill should be work based on code
  • scribe should be aware of currently filled data to interact with existing filled data
  • make the error message normal user friendly [ @shivankacker can you push a fix for this alone First, before working on the other enhancements ]
@bodhish
Copy link
Member

bodhish commented Aug 17, 2024

@nihal467 why should we autofill based on code? Is this a user requirment?

@nihal467
Copy link
Member Author

@bodhish no such requirement came from users so far, the enhancement was requested based on a hypothetical situation where user want to add a specific icd11 code itself via audio

@shivankacker
Copy link
Member

make the error message normal user friendly [ @shivankacker can you push a fix for this alone First, before working on the other enhancements ]

@nihal467 can you specify which error you are talking about and how I can replicate?

@nihal467
Copy link
Member Author

nihal467 commented Aug 21, 2024

image

@shivankacker One of the error message attached above, which was shown, last week, when scribe was not able to start because level of consciousness ID was changed. The error message won't make sense to a normal user

@shivankacker
Copy link
Member

@nihal467 I will remove the "Something went wrong..." and change "Error creating scribe instance" to "Scribe servers are down, please try again later". Does that sound good?

@shivankacker shivankacker moved this from Triage to Up Next in Care Aug 21, 2024
@github-actions github-actions bot added the stale label Sep 5, 2024
@shivankacker shivankacker moved this from Up Next to In Progress in Care Sep 13, 2024
@github-actions github-actions bot removed the stale label Oct 21, 2024
@shivankacker shivankacker moved this from In Progress to Review required in Care Nov 6, 2024
@github-project-automation github-project-automation bot moved this from Review required to Done in Care Nov 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

3 participants