> 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/platform-overview.md).

# Platform Overview

- [What Concurrence Does](https://docs.concurrence.com/platform-overview/what-amigo-does.md): How Concurrence combines a shared healthcare data foundation, configured agent workflows, and operational evidence within an existing organization.
- [Core Concepts](https://docs.concurrence.com/platform-overview/core-concepts.md): The relationships between workspace data, deployed configuration, live interactions, and outcome evidence in the Concurrence Platform.
- [Shared Context and Applications](https://docs.concurrence.com/platform-overview/shared-context-and-applications.md): How shared patient context, change events, and specialized applications work together without sharing one transaction or one set of permissions.
- [How It Works](https://docs.concurrence.com/platform-overview/how-it-works.md): Follow one appointment change through data retrieval, agent decisions, external action, human exceptions, and outcome evaluation.
- [Design Principles](https://docs.concurrence.com/platform-overview/design-principles.md): The engineering trade-offs behind source-aware data, bounded workflows, explicit action confirmation, and measured improvement.
- [Operating Model](https://docs.concurrence.com/platform-overview/operating-model.md): How clinical, operational, data, engineering, and Concurrence teams divide responsibility for a deployed workflow and its ongoing improvement.
- [Deployment Model](https://docs.concurrence.com/platform-overview/deployment-model.md): Define deployment scope, validate a candidate, select reviewed configuration, and manage release changes across isolated workspaces.
- [Evaluating Concurrence](https://docs.concurrence.com/platform-overview/evaluating-amigo.md): A technical evaluation path through architecture, data, control, delivery, measurement, and deployment, with concrete evidence to examine.
- [Technical Evaluation Packet](https://docs.concurrence.com/platform-overview/evaluation-packet.md): Build a technical decision packet with deployment boundaries, capability confirmations, pilot acceptance criteria, integration effort, and traceable outcome evidence.
- [Reference Deployment](https://docs.concurrence.com/platform-overview/reference-deployment.md): Review the logical boundaries, data flows, integration dependencies, and ownership decisions in a Concurrence deployment before selecting a pilot architecture.
- [Capability and Availability](https://docs.concurrence.com/platform-overview/capability-availability.md): Distinguish documented interfaces, managed provisioning, separately authorized services, and preview capabilities during deployment planning.
- [Data Residency](https://docs.concurrence.com/platform-overview/data-residency.md): Regional deployment endpoints, data-flow boundaries, and practical planning considerations for regulated deployments.
- [Cloud Ownership and Integration Boundaries](https://docs.concurrence.com/platform-overview/cloud-ownership.md): Separate software ownership, cloud execution, data storage, operating access, and billing when reviewing a customer-owned agent integration.
- [Cost and Latency Optimization](https://docs.concurrence.com/platform-overview/cost-and-latency.md): Plan deployment cost and latency measurements, distinguish customer billing from internal cost allocation, and understand runtime optimization trade-offs.


---

# 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/platform-overview.md?ask=<question>&goal=<user_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.