Clinical Tools

Current built-in world tools for patient lookup, scheduling, clinical reads, and source-attributed writes.

The Platform runtime has a built-in catalog of world tools for patient, scheduling, clinical, and operational workflows. A catalog entry is a supported tool definition, not a promise that every agent can call it. Actual exposure depends on the runtime, service, Context Graph state, channel, authorization, and resolved patient scope.

Earlier note-authoring and semantic patient or event search tools are retired. Current capabilities are grouped by workflow below. Use explicit patient identifiers and typed lookups rather than natural-language entity search.

World write tools record structured, source-attributed events. Event acceptance, entity projection, review, connector eligibility, and external delivery are separate milestones. A successful tool result does not by itself prove that an external system changed.

Patient Data

Capability	Type	What It Does
Patient lookup	Read	Searches by a known entity ID or supported demographic and source identifiers, including date of birth, name, phone, email, or medical record number.
Patient create	Write	Creates a person event after the tool's supported duplicate check.
Patient update	Write	Records supported demographic and contact changes for a resolved patient.
Save patient	Write	Updates a supplied entity or performs the supported lookup-and-create path when no entity is supplied.

Scheduling

Capability	Type	What It Does
Slot search	Read	Finds supported available slots by date and optional location, appointment type, provider, specialty, or time constraints.
Appointment lookup	Read	Searches appointments using the supported patient, status, and date filters.
Schedule appointment	Write	Records a booking from a supported slot reference and resolved patient.
Cancel appointment	Write	Records cancellation of a resolved appointment.
Confirm appointment	Write	Records confirmation of a resolved appointment.
Reschedule appointment	Write	Records cancellation of the prior appointment and creation of its replacement. These are related writes, not one universal external transaction.

Clinical Context

Capability	Type	What It Does
Medication lookup	Read	Retrieves supported prescription records for a resolved patient.
Prescription refill	Write	Records a refill-request event for a selected prescription.
Encounter lookup	Read	Retrieves supported visit and encounter history.
Insurance create	Write	Records a coverage event for a resolved patient.
Payer and reference-data lookup	Read	Searches configured payer information or other supported workspace reference data.
Typed clinical lookups	Read	Query supported conditions, allergies, observations, medication statements, notes, family history, questionnaires, uploads, care plans, goals, tasks, service requests, consents, and diagnostic reports. Coverage depends on projected source data.

Operations

Capability	Type	What It Does
Queue lookup	Read	Reads projected outbound-task state using supported status, phone, ordering, and limit filters.
Ticket create	Write	Records a support or operations ticket event.
Log call	Write	Records a supported call-outcome event for a resolved patient.
Log triage	Write	Records the structured outcome supplied for a triage conversation. It is not an independent clinical decision service.

Scheduled outbound voice work is created through explicit outbound-task actions or workflows, not a semantic search tool or a general built-in agent tool. See Outbound.

Tool Exposure

Context Graph state bindings can expose eligible built-in tools for that state. Supported runtimes can also add narrowly scoped system tools or other configured tool families. State membership alone is not authorization, and presence in the global catalog does not mean a tool is active for a particular service.

For the live catalog and service-specific resolution endpoints, see Tool Testing.

Verification

Clinical write capabilities do not push raw conversation output directly into external systems. They validate structured tool input, enforce the applicable workspace and patient scope, and attempt a source-attributed world-model event write. Some runtimes suppress only identical writes that overlap in flight; that is not general request idempotency.

Connector policy determines whether an eligible event becomes an external mutation. Where the private-preview review flow is enabled, a configured path can create an external write proposal. Approval authorizes the proposal but does not prove downstream delivery.

Workspaces can add other eligible capabilities through Platform Functions, workspace queries, integrations, and Skills.