THE JARVIS PLATFORM
An Intelligent Workspace for EDC Design
Jarvis brings protocol understanding, clinical knowledge, CRF generation, Edit Check specification, human review, collaboration, and downstream EDC preparation into a single workflow. Instead of replacing clinical expertise, Jarvis helps Data Managers apply that expertise more efficiently.
Protocol-to-EDC
Start With the Study Requirements
Every study is different. Jarvis begins by identifying and structuring the clinical requirements that drive data collection.
A key starting point is the Schedule of Activities, where Jarvis uses intelligent automation informed by clinical knowledge to identify visits, assessments, timing, and other information needed to establish the study’s data collection framework.
This creates structured study information that can be used throughout the CRF design process.
Schedule of Activities → Structured Requirements
CRF Design
Start With a Meaningful First Draft
A Data Manager shouldn’t have to start every study with a blank screen.
Jarvis uses structured study requirements, clinical knowledge, standards, and available organizational content to generate candidate CRFs for the study. The user selects the CRFs that belong in the design, and Jarvis builds the initial structured CRF design from those selections.
Where an existing CRF is appropriate, Jarvis can map study requirements to the available design. Where a suitable design does not exist, intelligent generation capabilities can help create an initial CRF for review.
“The objective is not autonomous design. The objective is a high-quality starting point that moves the Data Manager more quickly to the decisions that require clinical expertise.”
Clinical Knowledge
More Than Standards
Standards are important — but clinical data collection requires more than knowing a standard.
- Study visits and visit schedules
- Schedules of Activities
- Clinical assessments and procedures
- Data collection requirements
- Relationships between protocol requirements and CRFs
- CRF structure and design patterns
- CDASH and other applicable standards
- Sponsor-specific standards and conventions
- Historical and organizational CRF libraries
This clinical knowledge helps Jarvis interpret requirements within the context of clinical data management rather than treating the protocol as generic text.
Collaborative Design
Work With Jarvis. Stay in Control.
Jarvis is designed around the people responsible for the study design. Data Managers can review proposed CRFs and fields, modify the design, provide instructions and feedback, and iterate as the study evolves.
Review Inside Jarvis
Users can enter comments directly against forms and individual items within Jarvis. Those comments can be interpreted and translated into structured design updates.
Review Through a PDF Casebook
Jarvis can export the CRF design as a PDF casebook with comment areas aligned to each form and each item. Reviewers can work through the casebook in a familiar document format, enter natural-language instructions, and return the reviewed PDF to Jarvis.
When the commented casebook is imported, Jarvis uses language-model capabilities to understand the reviewer intent and translate that intent into defined CRF design actions. The resulting changes are applied to the structured design for review.
This gives teams flexibility in how they review while preserving a controlled, structured EDC design underneath the process.
EDC Integration
Connect Design to Database Development
Once the EDC design is finalized, Jarvis can generate structured outputs to support downstream EDC development.
By carrying structured design information forward, organizations can reduce redundant specification and programming work between design and implementation.
See the Jarvis Workflow in Action
See the Jarvis Workflow in Action
Discover a more intelligent approach to protocol-to-EDC design.