Built by surgeons, for surgeons

Most software gets bolted onto the opearing room. Surge-ID was built inside it, by surgeons who needed it, with the engineers and researchers who could make it real.

What better surgical data changes in a hospital

Structured surgical activity is not a reporting exercise — it changes how an OR runs, how surgeons train and how the institution spends.

OR & Workflow

Real-time visibility on caseload, operative time, and team allocation. Surgeons spend less time on paperwork,hospitals plan blocks with actual data rather than estimates.

Clinical Outcomes

Complication and morbidity tracking at the procedure level. Patterns surface earlier, training gaps become visible,and outcomes improve through measurement, not assumption

Cost & Insurance

Structured procedure data feeds directly into billing and insurance workflows, particularly relevant in fragmented systems like Switzerland (LAMal, LAA, complementary insurers). Less time on coding, fewer rejected claims, cleaner audits.

Our Vision

Surgical activity should be measurable, comparable, and reusable. Not as an administrative burden, as the raw material for better-trained surgeons, safer hospitals, and stronger clinical evidence. Surge-ID was created at the intersection of surgery, technology, and research to make that possible, starting in the OR, ending in the literature.

Questions we get from surgeons, hospitals and industry

Who owns my data?

You do. Your logbook entries, certificates and training recordsbelong to you, not the institution. Hospitals see aggregateactivity, not your personal portfolio.

Can I take it with me?

Yes. Export the full record in standard formats when you changeinstitution. Continuity is a design principle, not a paid upgrade.

How does it integrate?

Standalone or alongside your HIS/EMR. Standard interfaces(HL7/FHIR) are available where needed; many departments startstandalone and integrate later.

Where is the data hosted?

In Switzerland, on infrastructure compliant with the Swiss FederalAct on Data Protection (nFADP) and GDPR. Hospital data stayswithin the institution's tenant.

How long does deployment take?

A department typically goes live in 4–6 weeks: account setup,role mapping, light training, then production. No heavy IT lift.

Is it MDR / FDA-grade?

The data structure, audit trail and traceability are aligned withMDR PMCF requirements and FDA real-world evidence guidance.Documentation is available under NDA.

Multi-centric studies?

Yes. Run protocols across departments and institutions on theplatform surgeons already use — no parallel CRF, harmoniseddata by design.

Ethics & consent?

Patient identifiers stay inside the institution. Studies operate onde-identified, structured data; consent workflows align with localethics committee requirements.