Hi everyone,

I wanted to share a project I've been working on that's focused on improving how transplant waitlists are managed and understood, with the ultimate goal of supporting better coordination and transparency around transplantation.

The project is called TransTrack. It's an open-source transplant waitlist management program designed to model how transplant centers track candidates, status changes, and readiness over time, aligned with UNOS/OPTN-style workflows. It's not a replacement for UNet, and it does not make allocation decisions. Instead, it's meant as a tool for:

Understanding waitlist status changes

Improving internal coordination and record-keeping

Supporting transplant program workflows and audits

Exploring ways technology can reduce administrative friction that indirectly affects patients and donors

I'm sharing it here because living donors and recipients often experience the consequences of system complexity firsthand, and I believe your perspectives are incredibly important. While this is a technical project, it's being built with the real-world transplant experience in mind.

🔹 The code is public on GitHub
🔹 It's early-stage and evolving
🔹 Feedback, ideas, and critiques are genuinely welcome

If you're curious, here's the repository:
👉 https://github.com/NeuroKoder3/TransTrackMedical-TransTrack.git

If you'd rather not look at code but want to share thoughts about:

pain points in waitlist communication

delays or confusion around status changes

areas where better tools could help patients, donors, or coordinators

I'd really value that input as well.

Thank you for taking the time to read, and thank you — sincerely — to everyone here who donates, advocates, or supports others through transplant journeys.

Wow! This is amazing. I've got lots of questions, but let me start with just a few:

• Are you connected to the donation community in some way -- as a recipient, a donor, relative...?
• It obviously took a lot of time to write the program and supporting documentation, and it appears you have knowledge of the transplantation process. What motivated you to write this program?
• The U.S. transplantation system is in some turmoil right now as HRSA moves to a multi-contractor model. UNOS retained its contract but not all of the services it previously provided. In this context, what do you see as the way forward to get your program adopted?

Thank you for the thoughtful questions. I appreciate the opportunity to clarify my perspective and intent.

I am not a transplant recipient, donor, or immediate family member of one. My connection to the community comes through professional and operational exposure rather than personal clinical experience. Over time, I have worked closely with healthcare systems and regulated clinical workflows, which has brought me into contact with transplant operations, coordination challenges, and the complexity of waitlist management. While I do not speak from lived transplant experience, I approach this work with respect for the community and an awareness that the stakes are exceptionally high.

The motivation came from observing how much of transplant coordination relies on complex, manual, and often opaque operational processes that sit alongside national systems. While allocation policy and national infrastructure appropriately remain centralized, there is a significant amount of day to day operational work that is handled locally and often with fragmented tools.

I was interested in exploring whether a transparent, auditable, and openly inspectable software model could help make those workflows easier to understand, reason about, and discuss. TransTrack began as a technical and conceptual exercise rather than a product initiative. The goal was to model waitlist state changes, readiness tracking, and audit trails in a way that makes assumptions explicit and workflows visible, not to automate decisions or replace existing systems.

The current shift toward a multi contractor model introduces both uncertainty and opportunity. In that context, I do not view adoption of TransTrack as a replacement for existing systems or as something that should be broadly deployed without careful evaluation. Instead, I see its role, if any, as incremental and collaborative. Potential paths forward would include use as a reference implementation, a training or modeling tool, or a platform for shared discussion about operational workflows rather than as a system of record. Any real world adoption would need to be guided by transplant centers and OPOs themselves, aligned with regulatory oversight, and responsive to the evolving governance structure under HRSA.

I believe the way forward involves transparency, interoperability, and open dialogue. Open source efforts can contribute by allowing the community to examine ideas, question assumptions, and explore alternatives without forcing premature decisions. Whether TransTrack itself is adopted is less important to me than whether it helps stimulate constructive conversation about how operational tools can better support donation and transplantation during a period of change.

I don't have any insights into the organ transplant process that would be helpful to your project, but I posted a link to your message on the LDO Facebook page and the LinkedIn group. Hope that helps!