readme with demo - #2
Conversation
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request updates the README.md to document the broader vision of CommitMatch as a blood coordination intelligence platform, detailing features such as the Bridge Network Model, confidence-aware response analysis, and hyperlocal emergency response. The review feedback correctly identifies discrepancies between this new documentation and the actual codebase, noting that the automated broader pool allocation is not implemented (requests are instead escalated) and that features like hyperlocal emergency response and outbreak-aware risk management are currently only mocked in the frontend. The reviewer suggests updating the README to accurately reflect these as roadmap items or manual workflows.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
| - **1 Standby Donor** — notified in advance that they may be activated if the primary is unavailable | ||
| - **Additional compatible donors** within the patient's bridge network | ||
|
|
||
| If the primary donor declines or fails to confirm, the standby donor is automatically promoted. If both become unavailable, CommitMatch expands beyond the bridge and allocates donors from the broader compatible pool — ensuring continuity of care without coordinator intervention. |
There was a problem hiding this comment.
The README states that if both primary and standby donors become unavailable, the system automatically expands beyond the bridge and allocates donors from the broader compatible pool. However, in lambda/standby_promoter.py, if no standby is found, the system logs a warning and marks the request as escalated without further automated allocation. Please update this description to clarify that coordinator intervention is required upon escalation, or implement the automated broader pool allocation logic.
| If the primary donor declines or fails to confirm, the standby donor is automatically promoted. If both become unavailable, CommitMatch expands beyond the bridge and allocates donors from the broader compatible pool — ensuring continuity of care without coordinator intervention. | |
| If the primary donor declines or fails to confirm, the standby donor is automatically promoted. If both become unavailable, the request is escalated to the coordinator dashboard for manual intervention and broader pool allocation. |
| - **Hyperlocal emergency response** — accelerated outreach and blood bank notification for critical incidents | ||
| - **Outbreak-aware risk management** — deprioritizes donors from regions affected by health alerts |
There was a problem hiding this comment.
The key features list Hyperlocal emergency response and Outbreak-aware risk management as active capabilities. However, these are currently only represented as mock data in the frontend (IncidentResponse.jsx) and are not implemented in the backend matching engine (prioritizer.py or eligibility.py). Please clarify in the README that these are conceptual/roadmap features, or implement the corresponding backend prioritization and filtering logic.
| - **Hyperlocal emergency response** — accelerated outreach and blood bank notification for critical incidents | |
| - **Outbreak-aware risk management** — deprioritizes donors from regions affected by health alerts | |
| - **Hyperlocal emergency response (Roadmap)** — planned accelerated outreach and blood bank notification for critical incidents | |
| - **Outbreak-aware risk management (Roadmap)** — planned regional health alert integration to deprioritize affected donors |
1 participant
No description provided.