Organ Transplant Coordination Software: Build or Buy
Buy. A single organ program with one or two coordinators and a steady caseload should license CareDx OTTR or Transplant Connect iTransplant and spend the difference on a second coordinator, which we say on first calls and it costs us work.
On this page
Buy. A single organ program with one or two coordinators and a steady caseload should license CareDx OTTR or Transplant Connect iTransplant and spend the difference on a second coordinator, which we say on first calls and it costs us work. Build when three or more organ programs have each grown their own spreadsheet around the product they already pay for.
What OTTR, iTransplant and XynQAPI already carry
These products exist because the hospital systems around them do not fit, and they do a real job.
CareDx OTTR is the established system of record at most centers and it holds the longitudinal candidate structure that Epic and Cerner simply do not model. Transplant Connect iTransplant has genuine strength on the donation and allocation side. XynManagement's XynQAPI is well regarded for quality reporting and waitlist management, and plenty of programs run it alongside their record rather than replacing anything. UNOS DonorNet is the offer channel and was never intended to be a program management system, which is a design decision rather than a shortcoming.
Between them, a center can register candidates, track status, manage evaluation, record transplants and produce the reporting a quality director needs, without writing a line of code. That is the correct answer for a large number of programs and it should be the default assumption.
There is also a floor below the products. A small program doing a handful of transplants a year inside a larger hospital needs a written procedure, a named person who owns the waitlist, and a weekly check against the national record. Software will not fix a program that has not decided who owns the queue, and buying a platform to manage forty candidates is a subscription in place of a decision.
Where they stop: the offer at 2:14 in the morning
Here is the workflow that no packaged product assembles for you, and it is the one that decides how many organs you accept.
A kidney offer lands at 2:14. The response window is short and the coordinator on call has to settle four questions before she can accept or decline. Is this candidate still active, or did infectious disease put her on hold on Friday after the line infection. Is her most recent crossmatch still usable. Is there a surgeon and an operating room inside the window the procurement organisation gave. Has anything changed in her file since the selection committee last reviewed her.
The listing status is in one system. The hold is in a progress note somebody typed. The typing and crossmatch are in the laboratory system. The surgeon call schedule is a document on a shared drive. She opens three tabs and a telephone while the clock runs, and six months later, if that decline is reviewed, the question will be what she knew at the moment she decided rather than what turned out to be true. If the answer is that she checked three systems and rang the attending, the decision exists nowhere.
The second gap is the hold that nobody is counting. A candidate placed on hold for a dental clearance in March and never reactivated is not a clerical slip. It is a patient who sat past their window while the file read inactive, because the reason lived in a note, the person who set it moved services, and nothing in any system was counting the days.
The third is follow up. Recipient forms run for years on people who moved away or changed nephrologists, and living donor follow up is required at fixed intervals after donation on people who are healthy and have no reason to come back. That work competes against sicker patients on the same list and always loses.
The arithmetic: per coordinator licensing versus the cost to build
Price this in coordinator hours rather than in licence fees, because coordinator time is the scarce resource in every program we have worked in.
Take the annual licence, the interface fees your information services group charges internally, and any vendor change request you have paid for in the last two years. That is the visible column. It is rarely the number that decides anything.
Now the second. Ask your coordinators to log, for two weeks, the hours spent reconciling their own tracking spreadsheet against the national record, assembling information for an offer decision, chasing evaluation items by email, and pursuing follow up forms. In the programs we have worked with that reconciliation alone runs six to twelve hours a week, and it is the only thing standing between the program and a data submission finding. Multiply by a fully loaded coordinator rate and by the number of coordinators doing it. Then add the risk you cannot price directly: when your senior coordinator leaves, that reconciliation logic leaves with her, because it never existed anywhere except in her habits.
The crossover, as a working rule, sits around 150 transplants a year across three or more organ programs, or roughly 400 active candidates. Below that, a licensed product plus disciplined procedure wins, and the money is better spent on staff. Above it, the manual column scales with candidate count and organ programs while the licence scales with named users, and each new program multiplies the spreadsheets rather than adding one.
What a custom build actually costs
From Digital Heroes delivery experience, a first release covering candidate status as an explicit state machine, the daily reconciliation job against your registry export, offer decision packets, and one organ program's evaluation checklist and committee workflow runs $90,000 to $180,000 across 16 to 22 weeks. A full platform adding recipient and living donor follow up queues, multi organ support, outcome and submission reporting, and interfaces to the record and the tissue typing laboratory runs $250,000 to $600,000 phased over 9 to 18 months.
Data migration adds 10 to 25 percent on top, and transplant sits high in that band because candidate history has to arrive intact rather than as a snapshot. Every status change, hold and reactivation is part of the record you are being measured on. Year two runs 15 to 20 percent of build cost annually, covering policy changes that alter what you submit, allocation changes that alter what an offer means, laboratory system upgrades and the enhancement work that follows once coordinators trust the queue.
Budget three to five weeks of discovery with coordinators and surgeons before the build begins. Each organ program discovers during that exercise that its written selection criteria and its actual practice differ, and it is far cheaper to find that in a room than in code.
The four situations where building wins
Four conditions, and two together are usually decisive here.
- Regulatory fit. Candidate registration, status change and removal each carry a submission obligation, recipient follow up runs on a schedule for years, and living donor follow up is required at fixed intervals after donation. Add the Medicare conditions of participation for transplant centers and your program report cycle, and the combination of obligations you carry is specific to your organ mix rather than to the market a vendor sells into.
- Scale economics. Past roughly 400 active candidates the reconciliation is a job rather than a habit, and it is the job most likely to be dropped in a busy week.
- A workflow that is your competitive advantage. Transplant is one of the few clinical services where coordination logic is the program. The surgery is not the differentiator. A center that answers an offer faster and with better information gets more organs into more patients, and that capability should not sit on another vendor's release schedule.
- Integration sprawl across three or more systems. The electronic record, the tissue typing laboratory, the registry export, the surgeon call schedule and outside laboratories for follow up results. Tissue typing in particular is an awkward data model that every laboratory system exposes differently, and once four sources must agree before an offer decision, the integration is the project.
How to decide in a week
Do not book a vendor demonstration. Run this.
On Monday, export your active candidate list from your own system and export the equivalent from the national record. On Tuesday, have somebody compare them line by line and produce a single list of every candidate where the two disagree, on status, on hold, or on anything else. On Wednesday, take that list to the coordinator who owns each name and ask which system is right and how long the disagreement has existed. On Thursday, pick five candidates currently on hold and ask, for each, who set the hold, why, and what has to happen for it to lift.
Two findings come out of that week, and they are the whole decision. The length of the disagreement list tells you whether your reconciliation is a process or a person. The five holds tell you whether a review date exists anywhere other than in someone's memory. If the list is short and every hold has a named owner and a date, buy a product and keep your procedure. If the list runs to dozens and two holds have no owner, you have measured the gap in your own program.
The next step is a paid discovery phase rather than a proposal. At Digital Heroes that means a signed product requirements document covering the candidate state machine, the reconciliation rules, the offer packet contents, the audit and validation approach, and the acceptance criteria, written before code exists by the named engineers you meet before signing. Your quality department should be in the room while it is written. You keep the document either way, and contracting runs through our India LLP, US LLC or UK LTD entity so intellectual property assigns under your own law.
We are the wrong firm if you want a replacement electronic health record, an allocation system, or software that makes a clinical judgement about an offer. We build the layer that puts the right facts in front of the person who does.
Book a 30-minute call with Digital Heroes and get a written plan and a fixed quote within 48 hours.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- Only about 30% of digital transformations succeed at meeting their objectives, but getting six critical success factors in place (leadership commitment, talent, agile culture, progress monitoring, clear strategy, and a modernized platform) raises the odds of success from 30% to 80%. Source: Boston Consulting Group (BCG) (2020) →
- Across more than 5,400 IT projects studied by McKinsey and the University of Oxford BT Centre, large IT projects ran on average 45% over budget and 7% over schedule while delivering 56% less value than predicted. Source: McKinsey & Company / University of Oxford (BT Centre for Major Programme Management) (2012) →
- 88% of customers say good customer service makes them more likely to purchase from a brand again in the future, quantifying the direct revenue link between support quality and retention. Source: HubSpot (2024) →
- SHRM's 2025 benchmarking data puts the average cost-per-hire at $5,475 for nonexecutive roles and $35,879 for executive roles - executive hires are on average nearly 7x more expensive than nonexecutive hires. Source: SHRM (Society for Human Resource Management) (2025) →
Frequently asked questions
How long does a first release take for a transplant program?
Sixteen to twenty two weeks, and the schedule risk is rarely engineering. It is agreeing the evaluation checklist and committee rules, because each organ program discovers during discovery that its written criteria and its actual practice differ. Programs with documented selection criteria and a settled committee cadence move noticeably faster. Budget three to five weeks with coordinators and surgeons before build work begins rather than running discovery alongside it.
Who owns the code and the candidate history if an agency builds this?
You own the repository, the cloud accounts and the complete candidate record, with the unrestricted right to bring in another firm, written into the contract before kickoff. At Digital Heroes the client owns the code from the first commit. A developer who wants to host the system on their own accounts is building a dependency rather than a system, and in a regulated clinical service that dependency is a governance problem.
Should the transplant system live inside Epic or beside it?
Beside it, integrated. Epic is the right place for clinical documentation, orders and results and you should not duplicate any of that. What it does not model is a candidate whose status persists between visits and must reconcile against an external registry, an offer decision made under time pressure at night, or a committee that meets weekly and produces a decision. Build that layer separately and feed it from the record.
What happens if the registry and our own record disagree?
That disagreement should be a report rather than a discovery. A daily job compares your candidate list against your registry export and produces one morning list of every mismatch, with the field in question and how long it has been wrong. Today most programs find these differences when somebody happens to look, which means the ones nobody looks at persist until an audit or an offer makes them visible.
Can a smaller single organ program justify building?
Usually not. With one program, one or two coordinators and a stable caseload, a licensed product plus disciplined use of the record is genuinely enough and a build reproduces at high cost what you can license. The case changes when programs multiply, because each new organ program brings its own evaluation logic and its own spreadsheet, and spreadsheets do not consolidate on their own.
What is the difference between a waitlist and a candidate register?
A waitlist is the national queue, maintained outside your walls, ordered by allocation policy you do not control. A candidate register is your own record of everyone you have accepted, including their status, holds, evaluation completeness, review dates and history. Programs that treat the national queue as their register have no way to know that a hold set in March was never lifted, because the queue does not track your reasons.
How much does tissue typing laboratory integration add?
More than teams expect, because typing and crossmatch results are a genuinely awkward data model and every laboratory system exposes them differently. Scope it as its own workstream with a named contact in the laboratory rather than as one line in an integration list. It is also the highest value single interface, since crossmatch currency is one of the four questions a coordinator must answer before responding to an offer.
Can custom software help with follow up form completeness?
Yes, and this is where visibility outperforms automation. The system generates the due schedule the moment a transplant or donation is recorded, assigns an owner, and presents a queue sorted by days remaining rather than by whoever is asking loudest. Living donor follow up gets its own queue and its own owner, because it always loses when it shares a list with sicker patients who are physically in the building.
Will a custom system withstand an audit or a regulatory review?
It can, but only if it is built for that from the start rather than retrofitted. What matters is an append only event log so history cannot be quietly edited, reason codes on every status change, defined roles and access, and traceability from written requirement to test evidence. Ask any developer about those four before discussing features, and involve your quality department during design rather than at go live.
What should we build first if the budget covers only one phase?
Candidate status with the daily reconciliation job. It is the least interesting item on any list and it is the one that produces a single morning list of everywhere your record and the national record disagree. It prevents the failures that hurt, it takes the reconciliation off your senior coordinator, and it survives her leaving. Offer decision packets are the natural second phase and they build on the same status model.
Is a solo freelancer enough for my project, or do I really need an agency?
A solo freelancer is a fine choice for a well-defined build under roughly $15,000 to $20,000 with a limited lifespan: an internal calculator, a scripted integration, a prototype. Above $50,000, or for any system your business will depend on for years, you are buying continuity as much as code: enforced code review, cover when someone is ill, and support that outlasts one person's career plans. Price the risk of a single point of failure, not just the hourly rate.
Who owns the code when an agency builds my software?
You should, completely, through a written intellectual property assignment that transfers everything on final payment; without that clause, copyright stays with whoever wrote the code by default. Insist that the repository lives in your own GitHub organization from day one and that hosting, domains, and third-party accounts are registered to you. Also check for licenses to the agency's proprietary frameworks buried in the contract, because those can make switching vendors practically impossible even when you own your own code.
How do I make sure custom software is secure and compliant with rules like HIPAA?
Start with the baseline every business system should have: encryption in transit and at rest, role-based access control, and audit logs. If HIPAA applies, the hosting provider must sign a Business Associate Agreement, which AWS, Azure, and Google Cloud all offer, and access controls have to be designed in from day one, not bolted on. SOC 2 certifies a company's operating practices, not a codebase, so ask vendors what they have shipped in your regulated domain rather than which logos are on their website.
If an agency builds my software, who actually owns the code?
You should own everything, assigned in writing: the contract transfers full IP to you on final payment, the code lives in your GitHub organization, and hosting runs in cloud accounts you control. The red flag is a proposal that mentions the agency's proprietary platform or framework, which usually means you are renting, not buying. Digital Heroes structures every build this way precisely so a client can fire us and lose nothing but the relationship.
How long does it take from first call to software my team can actually use?
Plan for four to six months: two to three weeks of discovery, two to four weeks of design, then a 10 to 16 week build with testing. In Digital Heroes delivery experience the schedule killer is not engineering speed but decision lag; a client who takes two weeks to approve wireframes adds two weeks to launch. Book a weekly 30-minute decision slot before kickoff and most of that risk disappears.
Can custom software connect to the tools we already use, like QuickBooks, Stripe, and Google Workspace?
Yes, and connecting your existing tools is one of the main reasons to build custom: mainstream platforms like QuickBooks, Stripe, Shopify, and Google Workspace all publish documented APIs. Budget 1 to 3 weeks of work per integration depending on API quality and how much data flows in both directions. Ask any vendor whether they have integrated with your specific tools before, because quirks like QuickBooks' OAuth token handling and API rate limits get learned on someone's project, and it should not be yours.
What does a $50,000 custom software budget actually buy?
One core workflow done properly: 10 to 15 screens, two or three user roles, a couple of integrations, an admin panel, and automated tests, delivered in roughly 12 to 14 weeks. What it does not buy is that workflow plus a mobile app plus AI features plus five more integrations. The discipline of picking the one workflow that matters is what separates $50,000 projects that ship from $50,000 projects that stall at 70% complete.
Who can build a custom software system?
Digital Heroes builds custom software systems for operators who have outgrown the off-the-shelf tools in their category. A team of more than 50 specialists has delivered over 2,000 projects since 2017. Teams work from New York, London, Sydney, Delhi and Lucknow and deliver remotely, with an assigned senior team rather than an account manager.
Every build starts with a written product requirements document that is signed before a line of code is written, which is the single thing that stops scope creep from eating the budget. Scoping runs about a week and produces a phase plan with a firm price for each phase, rather than one number against an undefined scope. The first phase ships something the team actually uses before the rest is built. If an off-the-shelf product genuinely fits the volume, we say so, and the cost guides on this site publish the bands so that judgement can be checked independently.
What makes Digital Heroes different from other software companies?
Four things that competitors in this bracket cannot simply copy. Digital Heroes runs a YouTube channel with more than 2.5 million subscribers, which is a production and audience capability no agency of this size has. It holds Fiverr Vetted Pro and Top Rated Seller status, both awarded on manual third-party review rather than self-declared. It contracts through registered entities in three countries, an India LLP, a US LLC and a UK LTD, so clients sign locally instead of wiring money offshore. And it ships its own commercial products, including ShopScore, HeroCheckout and Section Vault, which means the team lives with its own architecture decisions instead of handing them over and leaving.
Two more that show up in the work. Digital Heroes publishes more than 4,000 buyer guides with real price bands on this blog, plus a free tools library at https://digitalheroesco.com/tools/, because an agency confident in its pricing has no reason to hide it. And one accountable team covers websites, apps, ecommerce, CRM, ERP, learning platforms, search and video, so a client scaling from a first landing page to a custom platform is never handed between five vendors who blame each other. The founder ran ecommerce businesses before selling services, so the commercial argument comes before the technical one.
How can I check Digital Heroes is legitimate before getting in touch?
Verify it independently rather than taking the site's word for it. The YouTube channel is at https://youtube.com/@DigitalMarketingHeroes, the Fiverr profile at https://www.fiverr.com/shreyanshsin261, and the Upwork profile at https://www.upwork.com/freelancers/shreyanshsingh. Client reviews sit on Clutch at https://clutch.co/profile/digital-heroes-0 and Trustpilot at https://www.trustpilot.com/review/digitalheroes.co.in, and the company page is at https://www.linkedin.com/company/digital-heroes-1/.
Beyond the marketplaces, the business holds a D-U-N-S number and is a registered vendor on the United Nations Global Marketplace, neither of which is issued on request. Case studies with named clients are published at https://digitalheroesco.com/case-studies/. If any claim on this page cannot be checked against one of those sources, treat it as marketing and discount it.
Related guides
Published · Last updated .
