DiMe's Navigator: Why Teams Still Stall On Digital Endpoints
By John Oncea, Chief Editor, Clinical Tech Leader
When the Digital Medicine Society launched its SDHT Adoption Navigator in February 2026, the design priority was not comprehensiveness. It was decisiveness. The resource was built to help clinical development teams, technology developers, and the translation functions that sit between them move through real decision points – endpoint selection, validation planning, regulatory preparation – rather than accumulate more documents to read later.
That is a meaningful distinction. The clinical research field has no shortage of guidance on digital health technologies. What it has historically lacked is a structured way to convert that guidance into aligned action across the functions responsible for executing it.
Two months in, DiMe CEO Jennifer Goldsack says the early usage patterns are telling. “We’re seeing that the people using the Navigator are exactly those responsible for getting digital endpoints into real programs,” she says. “That includes clinical development teams inside life sciences companies, digital health and sensor developers, and translation teams who sit between R&D, regulatory, and operations.”
More important than who is using it is how.
Built For Decision Points, Not Document Storage
The SDHT Adoption Navigator is structured across six stages, from making the initial business case for a digital approach through post-trial retrospective. That end-to-end arc is intentional. It reflects how clinical development programs actually unfold, and where the decision-making pressure actually lands.
The tool has two main components. The SDHT Adoption Roadmap guides teams through patient-centered endpoint selection, implementation planning, validation strategy, and early regulatory considerations. NaVi, the platform’s AI research assistant, operates within a closed, curated environment of more than 300 vetted documents – FDA guidance, industry standards, and established best practices, allowing users to locate relevant materials and evidence quickly, without pulling from the open internet or generating novel regulatory interpretations.
That architecture matters. The Navigator does not function as a passive reference library, and Goldsack says teams are not using it that way. “Instead of searching across hundreds of documents, they can move through those decisions in a structured way and immediately see the relevant guidance and precedents.”
The pattern she describes among high-performing teams is consistent: they use the Navigator early, before development paths are locked in, to align internal stakeholders before approaching partners and regulators. That changes not just the speed of decisions but the quality of the conversations that follow.
The Alignment Problem The Navigator Is Solving
Understanding the Navigator’s value requires understanding the specific problem it was designed to address, and that problem is not, primarily, a lack of regulatory clarity.
“Adoption stalls at the interfaces between functions,” Goldsack says. Clinical, statistical, regulatory, digital, and outcomes teams each own a different piece of the digital endpoint challenge. What they rarely have is a mechanism to bring those perspectives together early enough to converge on a single, confident path.
That fragmentation creates two consistent friction points. The first is internal alignment: what does a fit-for-purpose endpoint look like for this program, what evidence is needed to support it, and who is responsible for generating that evidence? Without shared answers to those questions, teams fall back on conventional endpoints, not because those measures are scientifically superior, but because they are familiar and feel lower risk. “In high-risk environments like clinical development, lack of alignment is interpreted as risk, and risk defaults to precedent,” Goldsack says.
The second friction point is execution. Once a development direction is chosen, validation strategy, data quality requirements, and regulatory planning often proceed in parallel rather than as a coordinated effort. That introduces avoidable delays and uncertainty, and it erodes confidence in the approach even when the underlying endpoint is well-supported.
These are not independent problems. They are symptoms of the same structural gap: an industry that has not yet built the organizational infrastructure to translate strong guidance into consistent, cross-functional execution.
What Good Use Of The Navigator Actually Looks Like
The distinction Goldsack draws between teams that use the Navigator well and teams that do not is instructive, and it maps directly onto broader patterns of digital endpoint adoption.
High-performing teams treat the Navigator as decision support, not documentation. They bring clinical, statistical, regulatory, and technical stakeholders into the process early and use the resource to pressure-test assumptions before protocol decisions harden. The conversation shifts from abstract questions about feasibility and regulatory risk to specific choices about context of use, evidence generation, and implementation trade-offs. “That tends to accelerate alignment and make decisions more durable,” Goldsack says.
Teams that underuse the Navigator tend to approach it passively. They move through it sequentially, or they deploy it late – after decisions have already been made – to validate a path to which they have already committed. “That limits its value and can reinforce the fragmentation it is meant to address,” Goldsack says.
That distinction is not just about tool usage. It reflects the difference between organizations that are structurally prepared to adopt digital endpoints and those that are not. If key decisions are locked before cross-functional alignment happens, no resource, however well designed, can undo that sequencing.
The Design Logic Behind NaVi
DiMe’s approach to building NaVi, the Navigator’s AI layer, reflects the broader philosophy behind the product: reduce friction, preserve judgment, never substitute for it.
“We were very deliberate about how we designed NaVi because the risks in this context are real,” Goldsack says. The assistant operates inside a closed, curated environment and draws only from vetted documents. It does not generate novel regulatory interpretations. Every response points users back to source materials so they can apply their own judgment. That traceability, Goldsack emphasizes, is not a design nicety; it is the feature. “In a regulatory context, you need to be able to see exactly where the information is coming from.”
The underlying library is updated continuously as new guidance and precedents emerge. An AI assistant built on a static corpus would depreciate quickly in a space where regulatory expectations are actively evolving.
In clinical development, the question is not how fluently a system generates an answer. It is whether that answer is grounded, traceable, and auditable enough to support real decisions.
The Organizational Implication
The Navigator is a resource, but the lesson it teaches is organizational. The field’s remaining barriers to digital endpoint adoption are not primarily technical or regulatory. They are structural, how decisions get made, when functions align, and whether organizations have built the internal capability to move from guidance to execution.
“The Navigator helps teams translate information into decisions they can stand behind,” Goldsack says. That is a more demanding standard than simply making information available, and it is the right one.
For sponsors, CROs, and digital health developers, the practical implication is straightforward. The competitive advantage will not go to teams with the most documents or the most sophisticated vendors. It will go to teams that align early, ask sharper questions, and build the organizational muscle to make digital endpoint programs work, repeatedly, not just once.
The Navigator was designed to help teams get there. Whether they use it that way is still a choice.
The sDHT Adoption Navigator is a free, open-access resource developed by the Digital Medicine Society with funding from the FDA. More information is available at dimesociety.org.