The first thing to fail at DSS was paper. In 1991, brothers Ron, Mark and Joe Byers were working from a Colorado basement and staring at a health-care system that still treated folders, forms and handwriting as infrastructure. They believed records belonged on computers. Three years later, the West Palm Beach division of the Department of Veterans Affairs had mountains of paperwork and hired the young company to help digitize it.
That job produced the pattern DSS still sells: do not ask a hospital to stop while software catches up. Connect the new tool to the system already carrying the work. At the VA, that system was VistA, the sprawling electronic health record built by the government and used across the country's largest integrated care network. DSS wrote graphical interfaces, documentation tools and connectors around it. The basement company became an interpreter between generations of technology.
The adapter is the product
A moat made of dependencies
VistA is routinely called legacy software, which is accurate but incomplete. Legacy systems are not museum pieces. They schedule appointments, carry orders, expose lab results and sit inside routines that clinicians cannot simply abandon on Monday morning. Replacing one can feel less like installing an app and more like renovating an airport while the planes keep landing.
DSS learned where those routines snag. Its Consult Tracking Manager follows referrals and community-care decisions that otherwise jump between queues. Order Tracking Manager gives dermatology, lab, oncology and radiology teams a shared view of tasks and writes data back to VistA/CPRS. CyberREN centralizes dialysis records, alerts and reports. Other products touch infusion therapy, mental health, perioperative care, prosthetics, revenue cycles and supply chains. The common product is not a screen. It is continuity.
The company says its intellectual property covers roughly 49 percent of VistA APIs and its document knowledgebase, and that more than 70 commercial applications run across VHA health and corporate portfolios. Those are company figures, but they describe the competitive position neatly. Oracle Health, Epic and MEDITECH can sell a broad EHR. Accenture, Leidos and Booz Allen can run federal modernization programs. DSS occupies the seam: the VA-specific clinical logic required to let a specialist application coexist with the installed record.
“Our partnership with VA has defined who we are.”Mark Byers, co-founder, president and CEO
What changed the equation
From wrapping VistA to hosting what comes next
For years, the sensible move was to build around VistA. Then the federal market shifted toward cloud-first systems, stricter security baselines and an EHR transition that made coexistence even more important. DSS did not renounce the adapter strategy. It moved the adapter into a controlled cloud.
Modernization without the trapdoor
DSS Health Cloud runs in AWS GovCloud as a multi-tenant platform for health applications. The VA granted it an Authority to Operate in June 2026. On July 27, the federal marketplace marked it FedRAMP Certified at Class D, the High category used for sensitive workloads. DSS says the process required more than 400 controls. The platform hosts its own tools, including e-prescribing, suicide-prevention management, telehealth triage and Juno EHR, but the larger bet is external: other software vendors can bring applications into a compliant environment instead of building the entire security stack themselves.
That is the change in mind-set. DSS once sold the bridge into a government record. Now it can also rent the fortified ground beneath the bridge. Its subsidiary SBG Technology Solutions provides onboarding, architecture, cybersecurity and federal authorization help. Juno Health, the commercial division, takes the company's EHR and workflow experience to acute-care, rural, behavioral-health and public-health organizations. The family is designed to catch a customer at three layers: software, integration services and infrastructure.
The price of boring reliability
Six figures per facility, millions to keep the lights on
Government software pricing is usually a fog. DSS's public GSA schedule offers a useful window. In the August 2025 list, Consult Tracking Manager Plus with its advanced dashboard cost $112,564.94 per facility for a one-year limited license. A perpetual license was $183,530.48, followed by $51,388.82 for a year of maintenance. Annual Order Tracking Manager Radiology licenses listed for roughly $52,000 to $59,000, depending on facility level.
At enterprise scale, sustainment becomes the business. In June 2026, DSS announced a VA contract worth about $29.6 million to maintain and support the Supply Chain Graphical User Interface Overlay through March 2029. The work covers deployed instances, operational support and long-term performance. This is what “modernization” often means in practice: new capability on one side, dependable maintenance on the other, and no dramatic cutover scene for the press release.
The model mixes annual and perpetual licenses, maintenance, SaaS and cloud fees, implementation and integration work, plus multiyear federal service contracts. DSS is private and does not publish audited revenue. A supplied company-data estimate puts annual revenue near $20 million, but contract awards and catalog prices should not be confused with recognized revenue.
Who buys, and why
The customer is the person chasing the missing handoff
DSS's defining buyer is the VA, but its users are schedulers deciding where a consult belongs, nurses reconciling tasks, pharmacists checking an order, renal teams watching a trend, and logistics staff trying to locate an item before it becomes a care delay. They buy fewer blind spots. A central dashboard is valuable only because the underlying integration makes it current.
Commercially, Juno Health sells a cloud-native, ONC-certified EHR and related tools to organizations that may be too specialized or too small for a giant-system rollout. Through partnerships, DSS widens the catalog without pretending to invent every clinical specialty. Sightview supplies eye-care software that DSS connects into VA workflows. Diasyst adds remote monitoring for diabetes and hypertension. InterSystems certification supports the interoperability work. AWS supplies the cloud substrate.
That breadth also explains why DSS looks less like a conventional SaaS company than a cabinet of highly specific tools. A dialysis clinic and a prosthetics buyer do not share much surface workflow, yet both need reliable patient identity, orders, permissions and reporting. DSS can reuse the integration layer while selling a screen shaped for each job. The customer pays for specialization without taking on a completely isolated system. The trade-off is complexity: every additional connection must be monitored, upgraded and defended for as long as the surrounding systems remain in service.
Steal this carefully
The DSS playbook - and its limits
The useful lesson is not “sell software to Washington.” Federal procurement is slow, specialized and expensive to navigate. The copyable strategy is more precise:
- Find an installed system whose replacement would interrupt real work.
- Map the handoffs users perform outside it - spreadsheets, calls, duplicate entry and memory.
- Build the bidirectional connector before polishing the dashboard.
- Bring nurses, clinicians and administrators into design early enough to change the workflow.
- Treat compliance and maintenance as product features, with prices and owners, not post-sale chores.
It will not work everywhere. A young clinic with no VistA dependency may prefer a simpler EHR that starts clean. A software vendor handling low-risk data may have no reason to pay for FedRAMP High. A customer able to standardize on one modern platform can avoid a thicket of adapters. Deep domain knowledge becomes overhead when the domain is not deep.
There is also concentration risk in building so closely around one federal customer and one aging architecture. The VA's long-running Oracle EHR transition can create integration work, but it can also retire parts of the environment that made DSS essential. Juno, SBG and Health Cloud are answers to that problem: take the expertise outward, from VistA-specific software to federal services, commercial hospitals and compliant hosting.
DSS has grown from six employees in its early years to roughly 700-plus today. Its own culture language - family, synergy, pioneers, agility, teamwork and quality - is earnest enough to sound like a break-room poster. The more revealing detail is that the workforce includes physicians, nurses, pharmacists and Veterans alongside engineers. For clinical software, that mix is not decoration. It is how a team notices that the technically correct button sits in the wrong part of a nurse's day.
The company has tried to make that knowledge portable. Its public materials emphasize agile delivery, DevOps, quality systems and a Veteran-focused integration process. In 2026, more than 470 DSS and Juno Health employees reportedly completed an internal AI fluency program. AI may improve search, prediction or administrative work, but here it inherits the same rule as every DSS interface: a clever model is useful only after identity, permissions, source data and the clinical handoff are trustworthy.
Thirty-five years after the basement, DSS still works on the same problem in a different costume. The record is digital now. The friction has moved into interfaces, permissions, queues and security controls. The company's wager is that health care will continue to pay for someone who understands the old system, the new one and the human being standing unhappily between them.