Include relevant user inputted patient details and patient summary details when a user reports an issue from the Medication Suggestor
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 52/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- typescript
- Domain
- frontend
Research direction
Start at the Medication Suggester page and trace the report issue button into the issue form submission. Reproduce a report from a patient summary or patient list, then identify how the user inputs and resulting patient summary are available. Done means the relevant details are submitted with the report, or the Medication Suggester report feature is removed while Leave Feedback remains available.
Written by the indexing model from the issue text.
Description
Pages: Medication Suggester
Link: https://balancerproject.org/
Description of Problem:
Currently the report issue button in the medication suggester does not include information that the user input to get the results for the patient they are reporting an issue on. Since the report issue button is on the patient summary and patient list, it suggests to users that they're reporting an issue with that exact patient/suggester result.
Expected Behavior:
We should include the relevant user input data and the resulting patient summary in the report issue form submission when a user reports an issue from the medication suggester. If we can't do that, then we should cut this feature from the medication suggester altogether. It will still be accessible from the "Leave Feedback" page.
- Dominant language
- TypeScript
- Stars
- 21
- Forks
- 19
- PR merge metrics
- No merged PRs in 30d
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from CodeForPhilly/balancer-main
-
Bug
Difficulty 1/5 1-3 hours Newbie friendliness 72/100
CodeForPhilly/balancer-main#509 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 76/100
CodeForPhilly/balancer-main#503 ·
-
Bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
CodeForPhilly/balancer-main#502 · 1 comment ·
-
Bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
CodeForPhilly/balancer-main#488 ·
-
Documentation
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
CodeForPhilly/balancer-main#478 ·
All issues in CodeForPhilly/balancer-main
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
lichess-org/api#678 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
PostHog/posthog.com#20628 ·
Maintainers usually reply within 1 day
-
bug status:Needs Triage
Difficulty 1/5 Under an hour Newbie friendliness 92/100
jupyterlab/jupyterlab#19964 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
agentscope-ai/QwenPaw#8064 · 1 comment ·
Maintainers usually reply within 1 day
-
area: notebooks-jupyter bug theme: new notebook frontend
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
posit-dev/positron#16347 · 1 comment ·
Maintainers usually reply within 1 day