Merged
Conversation
inteee
requested changes
Mar 6, 2026
Contributor
inteee
left a comment
There was a problem hiding this comment.
Please scope SSE fan-out by clinic. Right now queue update events are broadcast to every connected stream subscriber, which can leak one clinic’s queue movements to another clinic’s clients.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I added a real-time clinic queue board for LumenHealth EHR so staff can easily see which patients are waiting in the lobby, with the nurse, or with the doctor. To unblock frontend development, I created a mock JSON array with five encounters in different states (WAITING, TRIAGE, and CONSULTATION) so the UI could be built and tested independently before the backend integration was completed.
On the backend, I implemented
GET /api/v1/queue/today, which aggregates encounters created today that are inOPENorIN_PROGRESSstates, and added Server-Sent Events (SSE) so the frontend automatically receives updates whenever an encounter state changes. On the frontend, I built a Kanban-style board with columns for Waiting Room, Triage, and Consultation that displays patient cards with their name, system ID, and wait time, and allows staff to move patients between stages via drag-and-drop or a dropdown. The UI updates within five seconds of backend state changes without requiring a hard refresh and preserves scroll position without flickering when new data arrives.closes #116