Research & Methodology

Trust is built with methodology.

Clinician in command
By design, not by policy
Representative data
Diverse, not convenient
Governance framework
Pre-committed, not reactive

Why this page matters: Research shows most people remain uncomfortable with providers relying on AI in healthcare decisions. Trust increases with demonstrated performance, clinician presence, governance mechanisms, and representative data. Every section below maps directly to those evidence-based trust drivers.

Research Foundations

Original research that grounds our approach

NAVSurgical is built on a foundation of peer-reviewed research by our team—spanning perceptual expertise in surgery, digital surgery definition, and robotic surgical education.

Defining digital surgery: a SAGES white paper (2024)

SAGES Digital Surgery Working Group; Ali JT, Yang G, Green CA, et al. Surg Endosc. 2024. PMID: 38180541.

View on PubMed →
Enhancing robotic efficiency through the eyes of robotic surgeons (2023)

Green CA, Lin J, O'Sullivan P, Huang E, Higgin R. Surg Endosc. 2023;37:571-579. PMID: 35579701.

View on PubMed →
Expertise in perception during robotic surgery – ExPeRtS (2022)

Green CA, Lin J, Higgins R, O'Sullivan PS, Huang E. Am J Surg. 2022;224(3):908-913. PMID: 35637018.

View on PubMed →
Transforming Surgical Education through a Resident Robotic Curriculum (2021)

Green CA, Chern H, Rogers S, Reilly L, O'Sullivan P. Annals of Surgery Open. 2021;2(3):e076. PMID: 37635816.

View on PubMed →
Integrating Robotic Technology into Resident Training (2019)

Green CA, Mahuron K, O'Sullivan P, Harris H. Academic Medicine. 2019;94(10):1532-1538. PMID: 30998574.

View on PubMed →
Teaching in the robotic environment (2019)

Green CA, Chu S, Huang E, Chern H, O'Sullivan P. American Journal of Surgery. June 2019. PMID: 31208624.

View on PubMed →
A Robotic Teaching Session (2019)

Green CA, Chern H, O'Sullivan PS. Journal of Robotic Surgery. Jan 2019.

View on PubMed →
Is robotic surgery highlighting critical gaps in resident training? (2018)

Green CA, Abrahamson D, Chern H, O'Sullivan P. J Grad Med Educ. 2018;10(5):491-493. PMID: 30377478.

View on PubMed →

Media

Data-driven Surgery: The Next Step in Improving Care and Operational Efficiency

Anantha V. MedTech Intelligence.

Read →
The Evolution of Surgical Automation, Robotics, and AI

Nasdaq.

Watch →
Teaching To Technology: Will Robots in the OR Shift the Surgical Instruction Model?

UCSF Department of Surgery. February 2018.

Read →
Courtney Green Awarded CESERT Robotic Grant from ASE Foundation

UCSF Department of Surgery. December 2017.

Read →
Safety & Guardrails

Safety by design.

Real-time intraoperative guidance carries real responsibility. These commitments define the boundaries of what NAVSurgical does and does not do.

Surgeon Authority

The surgeon retains full decision authority at all times. The system surfaces context and options—never commands or overrides.
Every signal the system surfaces can be dismissed, ignored, or overridden with zero friction. No confirmation dialogs. No guilt patterns.
The system logs all interactions transparently, including surgeon overrides, to support quality improvement without creating surveillance.
Explicit boundaries
The system will never issue directives, instructions, or orders.
The system will never lock out or restrict surgeon actions.
The system will never claim to 'know better' than the operating surgeon.

Automation Bias Mitigation

Automation bias—the tendency to over-rely on automated suggestions—is a named design target, informed by the FDA's January 2026 CDS guidance.
Confidence calibration is available for every signal. The system identifies uncertainty.
Anticipates decision making and mitigates deskilling — a common concern integrating AI in surgery.
Explicit boundaries
The system will never display binary yes/no recommendations.
The system will never use urgent alert patterns (flashing, alarms) for non-critical signals.

Cognitive Load & Alert Fatigue

The interface is built on a minimal cognitive load philosophy. Surgeons in time-critical, high-stakes moments cannot process noisy, cluttered information.
Alert fatigue mitigation is a core design principle. Fewer, higher-quality signals outperform a stream of low-confidence notifications.
Human factors testing with practicing surgeons informs every interface decision—before deployment, not after complaints.
Explicit boundaries
The system will never flood the surgical field with persistent overlays.
The system will never require the surgeon to acknowledge or interact with a prompt to proceed.
Data Transparency

What trains the system.

Our data sources, their constraints, and their limitations.

01

Real Operative Video

Thousands of de-identified surgical videos capturing on-screen behaviors, visual cues and decision signals that distinguish expert performance.

Initial focus: visceral, thoracic, and orthopedic procedures
Annotation guide driven by perceptual expertise framework
Self-supervised learning using expert annotations
02

Synthetic Data

Generated from small, high-quality clinical datasets using validated synthesis techniques. Synthetic data extends training coverage without compromising patient privacy—and we state clearly where it's used and where it's not.

Based on published breakthroughs in synthetic surgical video generation
Used to augment edge cases and rare anatomy variants
Always identified as synthetic in our methodology documentation
Bias & Generalizability

Building representative data over time.

Patient trust in medical AI correlates with the use of representative, diverse data. Here is where we are today and where we're headed.

CURRENT STATE

Where we are now

ProceduresVisceral surgeries, thoracic surgeries, orthopedic total joint replacements
SourcesInstitutional partnership video libraries, de-identified
SurgeonsMultiple experience levels, expert-labeled ground truth
EquipmentStandard surgical video capture systems across multiple modalities
Patient diversityBuilding from initial institutional demographics; not yet representative at population scale
ROADMAP COMMITMENT

Where we're headed

Multi-siteValidation across community hospitals, academic centers, and rural settings
Multi-surgeonDiverse experience levels, training backgrounds, and practice patterns
Multi-equipmentRobotic platforms, standard laparoscopic, and advanced imaging modalities
Diverse anatomyDeliberate inclusion of anatomic variants, different body habitus, and rare presentations
Procedure expansionSystematic extension to additional high-risk, video-enabled procedures
Human Factors in the OR

Designed for the surgeon's cognitive reality.

The operating room is not a dashboard. Cognitive load is already maximal. Our interface starts from that reality.

Design Principles

Minimal cognitive load

Information is filtered to the surgeon's current context. The system shows less, not more—presenting only signals relevant to the active procedural phase.

Peripheral awareness, not central demand

Critical signals are designed to enter awareness without demanding direct attention. The surgeon's primary visual focus stays on the operative field.

Graded, not binary

Risk signals use a continuous scale with calibrated confidence, not red/green binary states that force premature categorization of ambiguous situations.

Graceful degradation

If the system loses confidence or encounters novel scenarios, it reduces its visual footprint rather than escalating alerts.

Testing & Validation Approach

Surgeon-in-the-loop usability testing

Interface prototypes are tested with practicing surgeons in simulated intraoperative conditions before any clinical deployment.

Cognitive task analysis

Systematic analysis of the surgeon's decision-making workflow during target procedures to identify when information helps versus when it distracts.

Iterative refinement protocol

Usability findings drive interface changes before the next testing cycle. No feature ships without surgeon validation.

Regulatory Awareness

Regulatory-aware design.

We don't claim a specific regulatory pathway prematurely. Our design decisions are informed by current guidance, and we plan to engage regulators early as the product matures.

FDA CDS Guidance

The FDA's Clinical Decision Support guidance, finalized in January 2026, explicitly addresses automation bias in time-critical decision support. NAVSurgical's design philosophy was informed by this guidance from the outset.

Automation bias as a named design constraint
Uncertainty display as a core feature, not an edge case
Surgeon authority preserved by interface architecture

Software & OTS Documentation

We build on established software infrastructure with appropriate documentation. The FDA provides specific guidance on off-the-shelf software used in medical devices, and our quality system reflects those expectations.

Proven infrastructure with a differentiated surgical reasoning layer
Clinical data and validation as the defensible value, not commodity components
Quality management practices appropriate to device-class expectations

Staged Regulatory Strategy

Our three-stage product maturity model is designed around regulatory reality. We start in lower-risk territory (capture and insight), build evidence, and approach higher-risk functionality (guidance) only with the validation to support it.

Stage A capabilities designed for minimal regulatory friction
Stage B/C capabilities deployed only with supporting clinical evidence
Regulatory engagement planned before submissions, not after rejections
Security & Hospital Readiness

Built for the hospital IT environment from day one.

Cybersecurity and data governance are not afterthought features for intraoperative systems. The FDA's February 2026 cybersecurity guidance for medical devices sets expectations we design to meet—not scramble to add later.

Data Encryption

End-to-end encryption in transit and at rest. No operative video leaves the hospital network without explicit institutional authorization and de-identification protocols.

Access Controls

Role-based access with principle of least privilege. Audit logging for every data access event. Integration with hospital identity management systems.

Network Architecture

Designed for hospital network segmentation requirements. Operates within existing security zones. No external dependencies required during intraoperative use.

Compliance Readiness

HIPAA-aligned data handling practices. SOC 2 Type II target. Penetration testing and vulnerability management as ongoing practice, not periodic audit.

Interested in what we're building?

We're working with surgical teams and institutional partners who share our commitment to evidence-based, surgeon-centered intraoperative intelligence.