> For the complete documentation index, see [llms.txt](https://docs.concurrence.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.concurrence.com/agent/clinical-tools.md). # 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. {% hint style="info" %} Capabilities are grouped by workflow below. Use explicit patient identifiers and typed lookups; there is no natural-language entity search tool. {% endhint %} World write tools record structured, source-attributed events. Event acceptance, entity projection, 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. | Outbound calls are placed through the Outbound Calls API, not a general built-in agent tool. See [Outbound](/channels/outbound.md). ## 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](https://docs.concurrence.com/developer-guide/platform-api/functions/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. A world-model event is not delivered to an external system by itself. An external mutation happens through a tool the agent calls, such as an integration endpoint, and its result is the evidence of what the destination accepted. Workspaces can add other eligible capabilities through [Platform Functions](/agent/platform-functions.md), workspace queries, integrations, and Skills. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.concurrence.com/agent/clinical-tools.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.