Public Health Surveillance Software: Custom vs Off-the-Shelf
Buy. Most health departments should run the NEDSS Base System or Conduent Maven and put their money into staff, and we say that to health officers directly.
On this page
Buy. Most health departments should run the NEDSS Base System or Conduent Maven and put their money into staff, and we say that to health officers directly. Build when your epidemiologists cannot publish a new condition or questionnaire without a vendor support ticket, or when laboratory volume makes deduplication a daily cost measured in professional staff rather than in minutes.
What the NEDSS Base System and Conduent Maven actually do well
Both products were built by serious people for a job that is genuinely hard, and neither is the reason your department struggles.
The NEDSS Base System exists precisely so that jurisdictions do not each build this, and it carries the national notifiable disease plumbing you would otherwise implement yourself: the message handling, the condition structures, and the outbound path into national surveillance. For a small county receiving a modest volume of reports on a standard condition list, with a state provided instance available, buying is not a compromise. It is the correct answer and you should stop there.
Conduent Maven is a mature commercial platform with condition modules, a long track record, and a vendor keeping pace with guidance changes so your team does not have to. For a mid-sized department that can live inside a release cycle, it is defensible and it is what we would recommend over a build.
What both give you, beyond features, is somebody else maintaining the parts that are identical in every jurisdiction. Message parsing. Vocabulary tables. National reporting formats that change on a schedule you do not set. Rebuilding that is not clever, it is expensive rework with a long tail of small correctness problems you will discover during an event rather than in testing.
The buy case is stronger here than in almost any category we write about, because a surveillance system that fails during an outbreak fails in public. Continuity has real value and vendors price it into the contract.
Where they stop: the morning queue and the questionnaire nobody can change
A positive result leaves a hospital laboratory at 6:12pm, travels through an interface engine, and lands in a queue overnight. In the morning an epidemiologist opens 340 results. Sixty are repeat tests on people already under investigation. Twelve are the same person tested at three sites with three spellings and two dates of birth. Four should have triggered a call to the investigator on duty last night, because the state rule says immediately reportable, and nobody called.
That queue is the whole job, and it is an identity problem before it is a disease problem. Electronic laboratory reporting arrives as HL7 messages, and the standard gives you structure, not quality. Names truncate. A hospital sends the ordering facility as the performing laboratory. A reference laboratory reports under a different identifier than last month. Tests are coded with LOINC in one feed and free text in another, and the same organism reads as positive, detected and reactive in three systems. Get the match wrong one way and you overcount and dispatch investigators twice. Get it wrong the other way and you merge two people, which is a genuine harm and hard to unwind. Products ship matching, but the weights are theirs, and the naming conventions, transliteration patterns and address quality of your jurisdiction should be driving them.
The second wall is authorship. Your reportable condition list is state law and it changes. Case definitions get revised. During an emerging event, an investigation questionnaire can change three times in a month, and the version used last week has to stay intact for the cases collected under it. In a packaged product, adding a question means a change request, a vendor estimate and a place in somebody else's release calendar. In a slow year that is irritating. During an outbreak it is disqualifying, because the questions you need on Thursday were not knowable on Monday.
The third is the graph. Contacts, shared exposure venues, households, congregate facilities and genomic relatedness edges are relationships, and stored as rows with a parent case identifier they are invisible until somebody notices the pattern in a Tuesday meeting.
The arithmetic: cost per result against the cost to build
Use laboratory volume as the denominator, because that is what actually scales.
A focused build covering result intake, person matching and deduplication, automated case creation and condition specific workflow with the statutory clock lands around $160,000. Support and enhancement at 18 percent a year brings five years to roughly $304,000, or $60,800 annually. At 340 results a day, about 124,000 a year, that is close to 49 cents per result.
Now price what it displaces. If queue triage and deduplication consume two hours a day across your epidemiology staff, that is a fraction of a post. If it consumes more than one full-time epidemiologist, which is common above 400 to 500 results a day, you are spending more on manual matching every year than the entire build costs annually. That is the crossover, and it is a volume threshold rather than a population one, which is why a mid-sized department with three large hospital senders can cross it before a larger department with a fragmented feed.
The second figure has no dollar sign. Count the conditions in the last two years that missed a statutory notification timeframe because routing depended on somebody reading a queue. If that number is not zero, the case for building the clock as a first class object writes itself.
One more figure belongs in the comparison and it is easy to collect. Ask your investigators how much of an interview gets written twice, once on paper in a hospital corridor or a car and again at five o'clock from memory. A mobile capture path removes an entire class of transcription error and gives you accurate attempt timestamps, which is what your timeliness measures actually depend on. That is rarely enough to justify a build alone, and it is frequently what makes the rest of one worth funding.
What a custom surveillance build actually costs
Across the projects Digital Heroes has delivered, a focused first release covering laboratory result intake, person matching and deduplication, automated case creation, and condition specific investigation workflow with the statutory clock runs $90,000 to $200,000 and ships in 16 to 24 weeks. A full platform adding contact tracing with a relationship graph, outbreak and cluster detection, provider and laboratory reporting portals, national notifiable disease messaging, mobile investigator interfaces and surge scaling runs $250,000 to $700,000 phased over 9 to 18 months.
Two lines belong in the budget from the first draft. Data migration runs 10 to 25 percent of build cost, and the expensive part is not case records, it is reconciling person identities across years of records that were never resolved, plus the vocabulary mapping tables that every historical feed used differently. Year two onward runs 15 to 20 percent of build cost annually, driven by feed changes rather than features, because sending facilities change identifiers and formats without notice.
What raises the number: the count of distinct laboratory senders, since each facility is its own mapping and testing exercise regardless of the standard. Electronic case reporting from clinical systems, which is a different message shape arriving with different gaps. Outbound national messaging, where the mapping guides are detailed and validation is strict. Interfaces to your immunisation registry, vital records and environmental health systems, each a negotiation as much as a technical task. And your procurement process, which is genuinely part of the timeline.
Four situations where building the layer pays
Regulatory fit. Your state has reportable conditions or investigation requirements the packaged product cannot express without a change request, or timeframes measured in hours that require paging rather than queuing. Add restricted conditions: sexually transmitted infection and HIV related records carry stricter disclosure rules in most states, and condition level access control with logging is not an enhancement.
Scale economics. Above roughly 400 to 500 results a day, manual matching costs more each year than owning the intake and matching layer outright.
A workflow that is your advantage. Authorship is the one. If a trained analyst can publish a new condition, a new question and a new routing rule in an afternoon, with the previous version preserved, your department can respond to an emerging event at the speed the event moves. That capability is the difference between the two paths.
Integration sprawl. Count them: laboratory feeds, electronic case reporting, the immunisation registry, vital records, environmental health, and the state system you report into. Once three or more must agree about one person, identity is the actual product.
How to decide in a week, with two measurements
Take one full week of laboratory results and classify every one: matched automatically and correctly, matched manually, duplicated, or missed. Have two people review a sample of the automatic matches independently, because the errors you care about are the confident ones. At the end you have a defensible percentage and an hours figure, and both go straight into a funding request.
Then run the authorship test, which takes ten minutes and settles more than the volume study. Ask your vendor what it takes to add one question to an investigation form for a condition you already collect. If the answer involves an estimate, a change order or a release window, you have measured the constraint you would be buying your way out of. If a trained analyst can already do it and preserve the old version, stay where you are.
Third, pull the last ten immediately reportable conditions and check how each was routed after hours. Paged, queued, or noticed in the morning.
Then commission a paid discovery phase of two to four weeks ending in a signed product requirements document covering the matching model and thresholds, the condition and questionnaire authoring structure, feed inventory by sending facility, access control for restricted conditions, acceptance criteria and a fixed price. Digital Heroes writes that before any code, with more than fifty specialists behind it, and the department keeps the document regardless of who builds. We are the wrong firm if you want staff embedded in your building, because we have no local office anywhere.
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.
- The average developer spends more than 17 hours a week dealing with maintenance issues such as debugging and refactoring, and about four of those hours on 'bad code' - waste that equates to nearly $85 billion annually worldwide in opportunity cost. Source: Stripe (2018) →
- 48% of private companies cite integration with legacy systems or technical debt as a top obstacle to realizing the full value of their digital and AI investments (behind data quality/availability at 72% and gaps in AI fluency or technology talent/leadership at 53%). Source: Deloitte (2026) →
- A study (led by Prof. Pak-Lok Poon, published in Frontiers of Computer Science, 2024) reviewing decades of spreadsheet-quality research found that about 94% of spreadsheets used in business decision-making contain errors, illustrating the hidden risk of manual spreadsheet workarounds that custom software is built to replace. Source: Central Queensland University / phys.org (Prof. Pak-Lok Poon et al.) (2024) →
- One in four US employees report lacking career advancement opportunities; 48% of employees who participated in mentorship programs report high job satisfaction versus 29% of non-participants, and access to advancement opportunities ranges from 33% at organizations under 10 employees to 74% at those with 1,000+. Source: Gallup (2025) →
Frequently asked questions
How long does a surveillance intake and matching build take?
Sixteen to twenty four weeks for a first release covering laboratory intake, person matching, automated case creation and condition workflow with the statutory clock. The variable is feeds. Each sending facility is its own mapping and test cycle, and the realistic plan starts with your three largest senders and your five highest volume conditions, which usually covers most message traffic before the long tail begins.
Who owns the code and the surveillance data in a custom build?
The health department should hold the repository, the cloud accounts and the data from the first commit, settled in writing before kickoff. In government work this is not a preference. It is the difference between a system you control across administrations and a vendor you cannot leave during an event. At Digital Heroes the client owns everything from the first commit and it runs in their own environment.
Can we keep our current system and build only the intake layer?
Yes, and it is usually the right sequence. The incumbent stays the case system of record while the custom layer handles message ingestion, vocabulary mapping, probabilistic person matching with an auto merge band and a manual review band, and clean handoff of resolved cases. It targets the daily cost without a migration, and it teaches you exactly which other parts you have outgrown.
What is the difference between a surveillance system and a laboratory system?
A laboratory information management system belongs to the laboratory and manages specimens, testing and result production. A surveillance system belongs to the health department and turns reported results into people, cases, investigations and notifications. They exchange messages and they answer different questions, which is why a department running a public health laboratory still needs both rather than one stretched across the gap.
Should a small county health department build anything?
Almost certainly not. If your state offers a shared instance and your conditions follow the standard list without local variation, buying is correct and building would put a critical function on a small technical base. The improvements available to you are usually operational: routing rules, on-call procedures, and agreements with your largest laboratory senders about data quality.
How much does migrating years of case records cost?
Ten to twenty five percent of the build, and identity resolution dominates it. Historical records were often created without a resolved person index, so the same individual exists several times across years and conditions. Decide early whether history needs to be fully resolved or archived searchable, because full resolution is defensible work with a real price and archive-only is a fraction of it.
What happens if two patient records merge that should not have?
You need an unmerge that restores the original records rather than approximating them, and every match decision stored with its score and the rule version that produced it. Ask any developer this question first. A firm that cannot describe unmerge has not run a master person index in production, and you will find out during an outbreak rather than during testing.
Can epidemiologists change case definitions without a developer?
In a properly built system, yes, and it is the main reason to build. Conditions, case definitions, questionnaires and routing rules should be versioned configuration with an approval step, publishable by a trained analyst in an afternoon, with the previous version preserved so a case investigated in March still shows the March form. If the answer is that the vendor does it, you have bought the constraint back.
How do we design for a surge in cases and temporary staff?
Three things carry it. Narrow role based access so a temporary contact tracer can do one job with no reach into unrelated records, provisioned in minutes rather than by ticket. Intake and matching that scale horizontally, since the laboratory feed collapses first. And supervised bulk operations with an audit trail, because during surge people will need to close thousands of cases at once and will otherwise do it in the database.
Does contact tracing need a graph database specifically?
Not necessarily a specific technology, but it does need relationships modelled as typed edges rather than as a parent case identifier. Named contact, shared exposure venue, same household, same congregate facility and genomic relatedness are different edges answering different questions. Once they exist, a cluster becomes a query and a new positive result can be scored against existing clusters at intake instead of at a weekly meeting.
How many SaaS seats do we need before building custom becomes cheaper?
The crossover usually shows up between 20 and 50 seats on premium tiers. Salesforce Enterprise lists at $165 per user per month, so 40 users cost about $79,000 a year in subscriptions, which is real money against a custom system you would own outright. Run the comparison over three years: if subscription spend beats the build cost plus 15-20% annual maintenance, custom wins on price before you even count workflow fit.
What happens to my software if the agency shuts down or we stop working together?
Nothing dramatic, if the engagement was set up correctly: the code sits in your repository, hosting runs on your cloud account, and a handover document explains how to deploy and operate the system. Any competent replacement team can then take over in days rather than months. If the agency controls the repo, the servers, or the domain, fix that now, because renegotiating access during a dispute is the most expensive place to discover the problem.
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.
Is it cheaper to customize Salesforce than to build a custom CRM from scratch?
If you use less than a third of what Salesforce does, a custom CRM is often cheaper by year three. Salesforce Enterprise lists at $165 per user per month, so 25 seats cost about $49,500 a year before admin and consultant fees, while a focused custom CRM runs $60,000 to $100,000 once plus 15 to 20% a year in maintenance. If you genuinely need Salesforce's ecosystem, reporting, and app marketplace, customizing it beats rebuilding it; the mistake is paying enterprise prices to use it as a glorified contact list.
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.
Should I ask for a fixed price or pay the agency hourly?
Fixed price for the first version, hourly or retainer for what comes after launch. A fixed-scope, fixed-price V1 puts the estimation risk on the agency, which is exactly where you want it while trust is unproven; hourly billing on an unscoped greenfield build is a blank check. After launch, flip it, because maintenance and small features arrive unpredictably and fixed-pricing every ticket wastes everyone's time.
Should I hire a freelancer or an agency for my software project?
A skilled freelancer is the right call for a single-discipline scope under roughly $15,000, like a website, a plugin, or one integration. Above that, projects need design, backend, testing, and project management at once, and a solo builder becomes the single point of failure: if they get sick or take a bigger client, your project simply stops. Agencies bill 20-40% more per hour but carry continuity, code review, and someone to escalate to, which is what you are actually buying.
What should I prepare before contacting a software development agency?
A one-page brief beats a 40-page requirements document: the business problem in plain words, who will use the system, the 5 to 10 workflows it must handle, the tools it must connect to, and your budget range and deadline driver. You do not need wireframes, a specification, or technical vocabulary; producing those is the agency's job during discovery. Stating a budget range up front is the single best move, because it gets you honest scoping instead of a quote engineered to win the meeting.
What questions should I ask a development agency on the first call?
Ask who exactly will build it, what happens when scope changes mid-project, what their maintenance terms are after launch, and what they will need from you every week. Then ask them to describe a project that went wrong and what they changed afterward; teams that have shipped at real volume have war stories, and teams claiming a perfect record are hiding something. The scope-change answer matters most: a disciplined shop describes a written change-order process, not a vague promise to be flexible.
What happens if I stop paying for maintenance after launch?
Nothing breaks on day one, which is what makes it dangerous. Within 6 to 18 months, unpatched dependencies accumulate known vulnerabilities, an integrated API like Stripe ships a breaking change, and the first fix requires a developer to relearn a stale codebase at full price. Budget 15 to 20% of the build cost per year for upkeep; it is the difference between a $500 patch and a $15,000 emergency.
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 .
