Lima, Peru · Verifier-backed clinical AI

Clinical AI translation
you can take to court.

Orquor builds verifier-backed multi-agent orchestration for medical interpretation. Every utterance is checked by a deterministic test suite before it reaches the doctor. Every session is logged with cryptographic proof.

Medical WER · ER
4.1%
Latency p50
0.9s
Verifier suite
~60checks
Specialty registers
9
01 — The market is broken in half

You can buy speed, or you can buy defensibility.
Hospitals need both.

Video Remote Interpretation (VRI) and phone interpreters are regulator-friendly but slow (15–60s to first word), expensive (USD 1.50–2.50 per minute), and capacity-bound. Off-the-shelf machine translation is fast and cheap, but no clinician will stake a patient case on a generic LLM with no audit trail.

When a translation gets challenged in an adverse event review, you don’t need a confidence score. You need receipts.

— Orquor field memo · April 2026 · full thesis in the ACTO whitepaper

02 — How orchestration works

Every spoken sentence runs the gauntlet
before it’s ever delivered.

01

Listen, transcribe, route.

Speech is captured per-speaker (clinician and patient channels are separated). A medical-tuned ASR transcribes the utterance and tags it with role, register, and confidence. Low-confidence audio is escalated to a human interpreter before machine translation is ever invoked.

medical_asrspeaker_diarizationregister_tag
02

Translate within the right register.

The machine translation engine selects from one of nine specialty registers — emergency, cardiology, oncology, OB/GYN, pediatrics, psychiatry, orthopedics, neurology, primary care. Each register carries its own glossary, idiom library, and register-specific fine-tuning. A cardiology utterance is never translated by a generic pipeline.

register_selectmt.engine.v39 specialties
03

Verify, sign, deliver.

Every draft passes through a weighted suite of deterministic verifiers: medical term preservation, negation inversion, temporal consistency, urgency signal preservation, register match, dose-and-units integrity, anatomical lateralisation. Failures route to a clinical interpreter; passes are signed with a SHA-256 receipt and anchored to OpenTimestamps before delivery. The audit log is externally verifiable for years.

~60 verifiersweighted scoringRFC 3161 / OTSper-utterance receipt
input audio stream speaker-separated step 01 medical_asr role · register · conf step 02 mt.engine.v3 register-aware medical_term preservation temporal_consistency tense + duration negation_inversion not/never/no urgency_signal priority preserved + 56 more verifiers · weighted step 03 composer + sign SHA-256 · OTS
orquor

Orchestration you can audit.

Founder stance · Lima, Peru · 2026

03 — Pilot data

One number we care about
more than the rest.

11.8%
medical WER · emergency register   —   baseline 11.8% Whisper-medium

Word Error Rate measured on a 12-week deployment in a Lima teaching hospital. Same patient cohort, same physician set, same recording conditions. We replaced an off-the-shelf medical-tuned Whisper pipeline with the Orquor stack and watched WER drop by 65%.

The gain isn’t about the model; it’s about the register selection and the verifier loop. We don’t outperform every general-purpose system on every metric. We outperform on the metric that matters for clinical interpretation: the one that determines whether a chest-pain complaint reaches the attending physician with the correct urgency tag.

latency p500.91 sutterance → verified output
latency p951.62 sincludes verifier escalation
COMET-220.8795% CI [0.83, 0.91]
verifier coverage~60weighted, outcome-based
specialty registers9ER · cardio · onc · OB · ped · psy · ortho · neuro · GP
audit log anchorOTSSHA-256 + RFC 3161 backstop

Single-site pilot, ongoing. These figures are preliminary and we say so on purpose. Numbers will move as we onboard additional sites in Q3 2026. The benchmark dataset (1,000 utterances × 9 registers) ships alongside the whitepaper so you can stress-test our claims.

04 — The category we are publishing

ACTO · Auditable Clinical Translation Orchestration.

ACTO is the open technical specification we are publishing so the category does not get owned by any single vendor — including us. Below: the trade-off it resolves, axis by axis.

Axis
Human VRI / OPI
Generic MT
ACTO · Orquor
Latency to first word
15–60 s
0.5–2 s
0.5–2 s
Cost per minute
USD 1.50–2.50
USD 0.02–0.10
USD 0.20–0.80
Audit log granularity
session metadata only
none
per-utterance, cryptographic
Regulatory defensibility
strong (human), weak (AI)
weak
mathematically demonstrable
Specialty register
interpreter-dependent
generic
department-selected · 9 registers
Failure mode
silent error or no-show
silent hallucination
escalation, never silent

We don’t ship confidence scores. We ship receipts.

brand stance · orquor.com/manifesto (soon)

05 — Three products, one substrate

Different surface areas.
Same guarantees.

Every product runs on the same orchestration platform and the same verifier discipline. We don’t fork the trust model per vertical.

Available · clinical pilot

Orquor Clinical

Real-time EN↔ES medical interpretation for hospitals and clinics. Live deployment, nine specialty registers, per-utterance audit logs with cryptographic anchoring.

deploying Q2–Q3 2026 · contact for onboarding

Early access · Q2 2026

Orquor Hermes

The orchestration platform under the hood. Multi-agent infrastructure for regulated industries beyond healthcare. Bring your own models, define your own verifiers, ship your own pipelines on the same substrate.

pre-release · invite-only · whitepaper required

Pilot · Q3 2026

Orquor Academy

Training and certification for clinical AI orchestration. Designed for hospital informatics teams, clinical engineering departments, and regulators evaluating AI-assisted interpretation systems.

first cohort opens Q3 2026 · 4 weeks · hybrid

06 — Methodology in code

A verifier is a Python function
that returns pass or fail.

We don't ship confidence scores because confidence scores are self-reported. We ship verifiers. A verifier is a deterministic test function that evaluates one outcome property of a translated utterance — was the dosage preserved? does the register match what the clinician requested? did the output mention a name from the exclusion list? Each verifier returns pass or fail with a structured reason, and carries an explicit weight from +5 (catastrophic) to +1 (stylistic).

The production suite contains approximately 60 verifiers organized by clinical specialty and register. The full methodology — principles, taxonomy, version control, escalation rules — is documented in Section 4 of the whitepaper. Below is one representative verifier from Appendix A, executable as-is in a pytest harness.

Adapted from outcome-based rubric work in OpenClaw Atlas and HiL-Bench · read the full methodology →

# From Orquor Clinical verifier suite v1.2
# Appendix A · ACTO whitepaper v0.1

def verify_dosage_preserved(
    source: str,
    translated: str,
) -> VerifierResult:
    """Numeric dosage in source must appear
    identically in translated output.
    Weight: +5 (catastrophic if violated)."""

    source_dosages     = extract_numeric_dosages(source)
    translated_dosages = extract_numeric_dosages(translated)

    missing = source_dosages - translated_dosages
    if missing:
        return VerifierResult(
            passed=False,
            weight=5,
            reason=f"Dosage {missing} missing",
        )
    return VerifierResult(passed=True, weight=5)
07 — Who is building this

Freddy Rojas.
Founder, in Lima.

Founder & CEO · Orquor S.A.C. · Lima, Peru

Engineer and operator. Previously built ITERAMED, a first-generation medical translation product that taught me why audit was the missing primitive. Author of the ACTO whitepaper. Active contributor to outcome-based agent evaluation work across the Outlier, Scale, and Labelbox research ecosystems.

Orquor exists because the verifier-first discipline that modern AI evaluation has converged on has not yet been applied to the place where it matters most — clinical interpretation under regulatory scrutiny. I am building it here because Lima is a serious medical-tourism market, and because LATAM healthcare deserves frontier infrastructure owned regionally, not licensed from elsewhere.

08 — Talk to us

If you might run
a pilot, write here.

We respond to every message from a real person inside 24 hours on weekdays. No CRM auto-reply. No multi-touch nurture sequence.

What happens next

  • Founder reply within 24h on weekdays
  • 30-min call · live verifier walkthrough, no slides
  • HIPAA BAA template + SLA shared if you continue
  • Pilot scoping in writing within 5 business days

09 — Schedule a demo

See it run
on a real clinical session.

Thirty minutes, no slides. We walk through a live interpretation session with live verifier pass/fail output and the audit log being generated in real time. Then we shut up and answer questions.

We answer every demo request from a real human within 24h on weekdays.