Awell

Care orchestration platform

Awell documentation

Build care flows that run themselves, so hand-offs between people and systems stop happening by hand. Start here.

Start hereAPI reference

New to Awell

Start hereGet startedWhat Awell is, the handful of concepts everything else builds on, and where to go next as a care flow author or as an engineer connecting systems to them.

Design and run care flows

For the people who decide what should happen, for whom, and when. No code required.

StudioDesign care flowsAuthor care flows in Awell Studio: build the structure with tracks and steps, collect data with forms, and use timers and decisions to move patients forward automatically.Care & PanelsCare deliveryDeliver live care flows: find a patient and act on what needs doing in Awell Care, or work a whole population from a panel.InsightsImprove & analyzeDecide what a care flow should improve, set up the measurement before it goes live, then see how it is actually performing and what to change.AdminAdminister & secureSet up an Awell organization: invite the team, control who can do what, apply branding, and connect single sign-on.

Connect Awell to everything else

For engineers wiring care flows to EHRs, APIs, and your own interfaces.

IntegrationsConnect systemsMove patients and data between Awell and existing systems: hospital EMRs over HL7, third-party APIs, and in-house services.WebhooksAutomate with eventsReact to what happens inside a care flow, and let other systems start one: outbound webhooks, incoming webhooks, and every way a care flow can be triggered.UIEmbed & hostPut care flow activities in front of patients and clinicians, using pages Awell hosts or a custom interface built with Navi.DataData & source controlGet care flow data out for analysis, keep track of what a care flow collects, and version care flows as code in a Git repository.

Reference and catalogues

ExtensionsExtensionsHow a care flow reaches other systems: using an extension from the marketplace, or building and deploying a new one.CatalogueMarketplaceEvery extension a care flow can use: what each one does, which actions it adds, and what to configure before it works.GraphQLAPI referenceExact queries, mutations, and fields for the Awell Orchestration API.ReleasesChangelogWhat changed in Awell, newest first, and who each update is for.

Care teams lose hours to work nobody should be doing: re-keying the same data into three systems, chasing a form that never came back, remembering who was supposed to follow up. A care flow handles that coordination.

These docs cover how to build one, how to run it, and how to connect it to the systems a team already has.

If you're new to Awell, start with 'Get Started'

Get started takes fifteen minutes and explains what a care flow is, how the parts of the platform fit together, and the vocabulary the rest of these pages assume.

Care flow authors decide what should happen, for whom, and when, in clinical and operational terms, without writing code.

Engineers wire care flows to the systems around them, so every activity has real data behind it.

Both paths reach Extensions, which is how a care flow reaches another system, and the Marketplace, which lists what already exists.

Page Labels

A page's purpose is clear before the first paragraph.

KindAnswers
ConceptWhat is this, and why does it matter?
How-toWhat are the steps for this one task?
ReferenceWhat are the exact fields, values, and options?
TutorialWalk me through building something end to end.

Pages also say who they're mainly for, and a page that needs an engineer's help says where to hand off.

Get started

What Awell is, the handful of concepts everything else builds on, and where to go next as a care flow author or as an engineer connecting systems to them.

On this page

If you're new to Awell, start with 'Get Started'Page Labels