Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Update the Medication Suggester Flow to reduce on-screen clutter and improve usability

Open
#508 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
68/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
typescript
Domain
frontend

Research direction

Start by locating the Medication Suggester flow and its New Patient Form, Patient Summary, and Edit views, then compare their current behavior with the linked Figma slideshow and prototype. The work is done when only one content window is visible at a time, the minimize/close/hide controls are removed, and the patient-summary New Patient control no longer expands or collapses.

Written by the indexing model from the issue text.

Description

Date: 5/12/26
Pages: Medication Suggester

Link: https://balancerproject.org/

Phase of Balancer work: 2.0 Part of Content Audit stage after MVP

Description of Problem:
The current Medication Suggester Flow is a bit awkward in that it has weird interaction when switching between edit/view/new patient and it shows too much at once.

The following Changes will help improve the flow without making too heavy of a lift:

  • Only allow one content window (New Patient Form, Patient Summary, Edit) to show at once
  • Remove the minimize/close/hide buttons
  • remove the expand icon and expand/collapse functionality of the new patient button/div from while on the patient summary

Here's a slide show showing what this will look like

Additionally here is a prototype to demonstrate how this works

The prototype has some improvements included in it that I wrote separate tickets for.

Dominant language
TypeScript
Stars
21
Forks
19
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from CodeForPhilly/balancer-main

All issues in CodeForPhilly/balancer-main

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.