Skip to content

AI-Assisted Triage

Routing support your clinicians stay in control of.

Interpret structured symptoms against routing workflows you configure, surface potential warning signs, and give clinicians organized information to decide faster.

POST /v1/triage/assessSynthetic example
response.json
{
  "assessment_id": "demo_triage_wselyl",
  "workflow_id": "primary_care_default",
  "normalized_symptoms": [
    "chest discomfort",
    "shortness of breath"
  ],
  "warning_signs": [
    {
      "rule": "chest_symptoms",
      "level": "high",
      "message": "Chest symptoms reported. Workflow requires prompt clinician assessment."
    }
  ],
  "suggested_route": "priority_clinician_review",
  "requires_clinician_review": true,
  "rationale": "Route selected by workflow rules matching the warning signs above.",
  "disclaimer": "Decision-support draft for clinician review. Not a diagnosis."
}

Responsible use

AI-assisted triage outputs do not independently establish a diagnosis, replace professional medical judgment, or authorize emergency-care decisions. Capabilities shown are under development and have not been clinically validated.

Capabilities

Configurable routing with a human in the loop.

Status labels show what is in development today and what is planned.

  • Symptom interpretation

    In development

    Maps reported symptoms to normalized terms.

  • Configurable routing workflows

    In development

    Your routes, your rules, your escalation paths.

  • Potential warning-sign identification

    In development

    Flags rule matches that need prompt clinician attention.

  • Structured output for clinician review

    In development

    The rule that matched and why — never a black box.

  • Human-in-the-loop by design

    In development

    Every suggested route requires clinician confirmation.

  • Workflow versioning & audit

    Planned

    Track which workflow version produced each suggestion.

Workflow

How it fits your product

Key output fields
suggested_routewarning_signs[]rationalerequires_clinician_review
Typical host systems
Hospital information systemsCall centersTelemedicine
  1. 1

    Structured symptoms in

    From Evergate Intake or your own forms.

  2. 2

    Workflow rules evaluated

    Warning signs flagged with the matching rule.

  3. 3

    Clinician decides

    Suggested route shown for review and confirmation.

Playground

Try the request and response

All examples on this site use synthetic data. No real patients, recordings, or inference requests are involved.

Demo mode · syntheticProposed
POST/v1/triage/assess
Examples

Valid JSON

ResponseAwaiting request

No response yet.

Run the request to inspect the structured JSON response.

Responses are generated in your browser by deterministic demo rules over your request. They show the response schema — they are not results of a real inference request. Do not enter real patient data.

Your healthcare software deserves intelligence.

Integrate medical AI into the systems you already use.

Evergate — Medical Intelligence Infrastructure