# Awell Docs > Awell is a care orchestration platform: it coordinates the activities a patient and care team move through over time, so hand-offs between people and systems happen automatically. These docs cover how the platform works and how to build with it. ## For agents If you are an agent reading this site, start with the skill(s) below before exploring — they explain the URL scheme, where the full dump lives, and how to fetch pages as Markdown. - [navigating-the-docs](https://docs.awellhealth.com/skills/navigating-the-docs.md): How external agents should navigate docs.awellhealth.com — the URL scheme, where the index lives, and how to fetch pages as Markdown. Read this first. ## Documentation - [Awell documentation](https://docs.awellhealth.com/docs.md): Build care flows that run themselves, so hand-offs between people and systems stop happening by hand. Start here. - **Start here** - Get started - [Get started](https://docs.awellhealth.com/docs/get-started.md): 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. - [What is a care flow?](https://docs.awellhealth.com/docs/get-started/what-is-a-care-flow.md): A care flow is a series of steps performed for, with, or by a patient to reach or maintain good health: whatever an organization calls it. - [Awell platform overview](https://docs.awellhealth.com/docs/get-started/awell-platform-overview.md): The five parts of Awell: Studio to design care flows, Care and Panels to deliver them, Orchestration to power them, and organization settings, and which one each role actually uses. - [Key terms](https://docs.awellhealth.com/docs/get-started/key-terms.md): The Awell vocabulary: care flow, track, step, action, data point, variable, and activity, defined once and used consistently across these docs. - [How a care flow is built](https://docs.awellhealth.com/docs/get-started/how-a-care-flow-is-built.md): The building blocks assembled in Awell Studio: tracks with triggers, steps joined by transitions, and actions assigned to the people who carry them out. - [What happens when a care flow runs](https://docs.awellhealth.com/docs/get-started/what-happens-when-a-care-flow-runs.md): How a designed care flow becomes activities once a patient is enrolled: and why activities, not steps, are what to read, query, and build integrations against. - **Design & deliver care** - Design care flows - [Design care flows](https://docs.awellhealth.com/docs/design-care-flows.md): Author 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. - **Structure** - [Care flow overview](https://docs.awellhealth.com/docs/design-care-flows/care-flow-overview.md): The page Design opens on, listing every care flow in the organization, the shared form library, and Awell's template flows. - [Monolithic vs modular care flow design](https://docs.awellhealth.com/docs/design-care-flows/monolithic-vs-modular-care-flow-design.md): How to decide where one care flow ends and another begins, and how much to put in a single track, based on what Awell has seen work. - [Create a new care flow](https://docs.awellhealth.com/docs/design-care-flows/create-a-new-care-flow.md): Start a brand new care flow in Studio, name it, and find the care flow ID that identifies it everywhere else. - [Organize your care flow with tracks](https://docs.awellhealth.com/docs/design-care-flows/organize-your-care-flow-with-tracks.md): Split a care flow into phases so it stays readable, and understand how tracks decide what happens when and for whom. - [Set your track triggers](https://docs.awellhealth.com/docs/design-care-flows/set-your-track-triggers.md): How a track activates, from "when the care flow starts" to data-point and scheduled triggers, and when to use each. - [Create and name a step](https://docs.awellhealth.com/docs/design-care-flows/create-and-name-a-step.md): Add a step to a track, name it so a colleague understands it, and learn what a step actually holds. - [Duplicate steps](https://docs.awellhealth.com/docs/design-care-flows/duplicate-steps.md): Copy a step that is already configured, instead of rebuilding a near-identical one. - [Label your steps](https://docs.awellhealth.com/docs/design-care-flows/label-your-steps.md): Use colored labels to make a busy canvas readable, grouping steps by whoever or whatever matters in the care flow. - [Add steps to your step library](https://docs.awellhealth.com/docs/design-care-flows/add-steps-to-your-step-library.md): Save a configured step to the step library to reuse it across tracks in the same care flow instead of maintaining duplicate copies. - [Duplicate a care flow](https://docs.awellhealth.com/docs/design-care-flows/duplicate-a-care-flow.md): Copy an existing care flow instead of rebuilding it, and know what the copy does not bring with it. - [Track looping](https://docs.awellhealth.com/docs/design-care-flows/track-looping.md): Model repeating care directly by looping a track, with a maximum number of iterations and an optional condition that ends the loop early. - [Tips for building faster](https://docs.awellhealth.com/docs/design-care-flows/the-fast-lane-to-efficient-building.md): Small habits that save time in Studio, from keyboard shortcuts to reusing questions and steps you have already built. - **Forms & questions** - [Add a form to a step](https://docs.awellhealth.com/docs/design-care-flows/add-a-form-to-a-step.md): Attach a form action to a step, choose who fills it in, and remove one that is no longer needed. - [Build a form](https://docs.awellhealth.com/docs/design-care-flows/build-a-form.md): Create a form's questions in the form builder, from the validated-questionnaire library or from scratch, and understand what the data feeds later. - [Build forms with Shelly](https://docs.awellhealth.com/docs/design-care-flows/build-forms-with-shelly.md): Describe an assessment in plain language and have Shelly draft the questions, or upload an existing form and have it recreated. - [Edit a form's questions](https://docs.awellhealth.com/docs/design-care-flows/edit-a-forms-questions.md): Change, reorder, or delete questions and answer options in an existing form, after checking every care flow the form is used in. - [Encode questions and answer options](https://docs.awellhealth.com/docs/design-care-flows/encode-questions-and-answer-options.md): Give forms, questions and answers stable keys and clinical codes, so the data is findable in logic, comparable across systems, and usable for analysis. - [Add conditions to your questions](https://docs.awellhealth.com/docs/design-care-flows/add-conditions-to-your-questions.md): Show a question only when an earlier answer calls for it, using visibility logic in the form builder. - [Configure your slider question](https://docs.awellhealth.com/docs/design-care-flows/configure-your-slider-question.md): Every setting on a slider question, also known as a visual analogue scale, and what each one does to what the respondent sees. - [Configure your ICD question](https://docs.awellhealth.com/docs/design-care-flows/configure-your-icd-question.md): Collect medical conditions using ICD-10 codes, and use both the code and its name later in variables and conditional logic. - [Set a display mode for your forms](https://docs.awellhealth.com/docs/design-care-flows/set-a-display-mode-for-your-forms.md): Show a form one question at a time or all at once, set per form action, and know the one place the setting applies. - [Import and export form questions](https://docs.awellhealth.com/docs/design-care-flows/import-export-form-questions.md): Bring questions in from the validated-questionnaire library or a JSON file, including a spreadsheet template that maps to the right format. - [Collect files and images](https://docs.awellhealth.com/docs/design-care-flows/file-upload.md): Let respondents upload documents and images through a form, and connect the Google Cloud Storage or Amazon S3 bucket those files are written to. - [Add a calculation](https://docs.awellhealth.com/docs/design-care-flows/add-a-calculation.md): Turn data collected in a care flow into a score, using a validated calculation from the Awell Score suite, then configure its inputs. - **Actions, messages & logic** - [The Timer component](https://docs.awellhealth.com/docs/design-care-flows/the-timer-component.md): Pause a care flow for a set duration or until a specific date, with the timing visible on the canvas and skippable while testing. - [Decision component](https://docs.awellhealth.com/docs/design-care-flows/decision-component.md): Express conditional logic as a readable decision table instead of chains of if-else transitions, with a catch-all rule for anything unmatched and a test run in Studio before it reaches a patient. - [Add an in-app message](https://docs.awellhealth.com/docs/design-care-flows/add-and-configure-an-in-app-message.md): Show a message to a patient or care team member inside Awell, and know when to use this instead of email. - [Send email notifications](https://docs.awellhealth.com/docs/design-care-flows/send-email-notifications.md): Send templated emails from a care flow using an email extension, configured with the organization's own provider account. - [Add files, images and videos](https://docs.awellhealth.com/docs/design-care-flows/add-files-images-and-videos.md): Enrich a message with inline media or attachments, and avoid the one embedding mistake that stops a video displaying. - [Use variables in your actions](https://docs.awellhealth.com/docs/design-care-flows/use-variables-in-your-actions.md): Insert care flow data into messages, clinical notes and API calls with the slash command, so one action adapts to each patient. - [Clinical note](https://docs.awellhealth.com/docs/design-care-flows/clinical-note.md): Turn collected answers into a readable, structured summary that can be exchanged over the API, instead of making staff read raw form responses. - [Checklist](https://docs.awellhealth.com/docs/design-care-flows/checklist.md): Give a care team member or patient a list of tasks to tick off inside a care flow, with a separate checklist per stakeholder if needed. - [Add a custom action to a step](https://docs.awellhealth.com/docs/design-care-flows/add-a-custom-action-to-a-step.md): Use an installed extension's action in a care flow, and choose whether to store what it returns as data points. - [Control when messages and forms expire](https://docs.awellhealth.com/docs/design-care-flows/message-and-form-expiration.md): Skip a message or form automatically after a set period so late responses don't land in the wrong follow-up, and know when not to use expiration. - **Document your work** - [Add documentation to your care flow](https://docs.awellhealth.com/docs/design-care-flows/add-documentation-to-your-care-flow.md): Record why a care flow is built the way it is, so the clinicians who use it later understand the reasoning behind it. - [Add a sticky note](https://docs.awellhealth.com/docs/design-care-flows/add-a-sticky-note.md): Leave yourself or a colleague a reminder on the canvas about an open question, with no effect on how the care flow runs. - [Enrich your care flow with baseline data](https://docs.awellhealth.com/docs/design-care-flows/enrich-your-care-flow-with-baseline-data.md): Pass information from another system into a care flow at start or at runtime, and avoid the optional data point that halts a flow without an error. - **Publish & promote** - [Publish and set your care flow live](https://docs.awellhealth.com/docs/design-care-flows/publish-set-your-care-flow-live.md): Publish a care flow to create a recorded version, set a version live so patients can be enrolled, and switch versions later. - [Sandbox to production promotion](https://docs.awellhealth.com/docs/design-care-flows/sandbox-production-promotion.md): Build and test in Sandbox, then promote a care flow to Production, keeping the identifiers your integrations depend on. - [Go-live checklist](https://docs.awellhealth.com/docs/design-care-flows/go-live-checklist.md): The Production configuration to verify before running a promoted care flow with real patients, especially the first time. - Care delivery - [Care delivery](https://docs.awellhealth.com/docs/run-care-flows.md): Deliver live care flows: find a patient and act on what needs doing in Awell Care, or work a whole population from a panel. - [How you work in Awell Care](https://docs.awellhealth.com/docs/run-care-flows/how-you-work-in-awell-care.md): The views Awell Care provides out of the box, from patient lists to task lists to the activity feed, and which one fits which way of working. - [Create patients](https://docs.awellhealth.com/docs/run-care-flows/create-patients.md): Create a patient manually in Awell Care or through the Orchestration API, since a care flow cannot start without one. - [Start a care flow](https://docs.awellhealth.com/docs/run-care-flows/start-a-care-flow.md): Enroll a patient in a published care flow from Awell Care or through the API, including the baseline data the flow may ask for. - [View and edit a patient profile](https://docs.awellhealth.com/docs/run-care-flows/view-edit-a-patient-profile.md): Review and update a patient's details, see all their care flows, and delete a profile when someone exercises the right to be forgotten. - [Review and interact with care flow activities](https://docs.awellhealth.com/docs/run-care-flows/review-and-interact-with-care-flow-activities.md): Read messages, submit forms, and understand what a care flow did using the activity feed, the timeline, and the audit logs. - [Follow up on pending activities](https://docs.awellhealth.com/docs/run-care-flows/follow-up-on-pending-activities.md): See what is outstanding across the whole patient population for one care flow, filtered by role or activity, so nothing sits unnoticed. - [Prefill form fields](https://docs.awellhealth.com/docs/run-care-flows/prefill-form-fields-in-awell-care.md): Pull up a patient's earlier answers to the same form and revise what changed, instead of completing a long form from scratch. - [Edit a care flow's tracks](https://docs.awellhealth.com/docs/run-care-flows/edit-a-care-flows-tracks.md): Add or stop a track on a care flow that is already running, when circumstances change or a phase needs repeating. - [Stop or delete a care flow](https://docs.awellhealth.com/docs/run-care-flows/stop-or-delete-a-care-flow.md): End a running care flow or remove it and its data entirely, with a clear warning that neither action can be undone. - [What Panels is](https://docs.awellhealth.com/docs/run-care-flows/what-is-panels.md): Awell Panels is a live list of patients or tasks that a care team works from, built from the data a care flow already collects. - [Panels and views](https://docs.awellhealth.com/docs/run-care-flows/panels-and-views.md): A panel holds the columns and settings; views built on it are tailored for a particular job. Which changes affect everyone, and which affect one view. - [Set the accent color in Panels](https://docs.awellhealth.com/docs/run-care-flows/set-the-accent-color-in-panels.md): One accent color in Panels settings drives the sort and filter button, the marker on a sorted column, the selected view tab, the Add Task button and the background tint. Set it once for everyone in the project. - Improve & analyze - [Improve & analyze](https://docs.awellhealth.com/docs/improve-and-analyse.md): Decide 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. - [Decide what to improve](https://docs.awellhealth.com/docs/improve-and-analyse/decide-what-to-improve.md): Name the thing that should change before building anything: a direction, a number that defines it, a target, and the kinds of outcome a care flow can move. - [Awell Score](https://docs.awellhealth.com/docs/improve-and-analyse/awell-score.md): A CE-marked library of more than 170 clinical calculations and validated outcome measures, browsable before a care flow is built and callable from inside one. - [Know whether it worked](https://docs.awellhealth.com/docs/improve-and-analyse/know-whether-it-worked.md): State a change as a hypothesis, test it as a time-boxed bet, and translate the movement into money using the organization's own numbers. - [Ask Shelly about your care flows](https://docs.awellhealth.com/docs/improve-and-analyse/instant-care-flow-insights-with-shelly.md): Get insights from care flow data by asking questions in plain English, and learn how to ask them so the answers are useful. - [Flow Path](https://docs.awellhealth.com/docs/improve-and-analyse/flow-path.md): A Sankey-style visualization of how patients move through a care flow, showing where they engage and where they drop off. - [Debug integrations with Monitor](https://docs.awellhealth.com/docs/improve-and-analyse/debug-integrations-with-monitor.md): Find and investigate failures in third-party connections and integrations, where problems most often surface. - **Integrate & extend** - Connect systems - [Connect systems](https://docs.awellhealth.com/docs/connect-systems.md): Move patients and data between Awell and existing systems: hospital EMRs over HL7, third-party APIs, and in-house services. - [How Awell connects to other systems](https://docs.awellhealth.com/docs/connect-systems/healthcare-interoperability.md): How Awell exchanges data with healthcare systems using HL7 and FHIR through an integration engine, and the storage constraint that shapes every integration. - [Ways to connect an EMR](https://docs.awellhealth.com/docs/connect-systems/getting-started-with-integrations.md): The mechanisms for getting patients from a hospital EMR into Awell, what each one requires from the hospital, and how to choose between them. - [EMR integration terminology](https://docs.awellhealth.com/docs/connect-systems/emr-integration-terminology.md): The vocabulary used in Awell's EMR integrations, from HL7 and Mirth to ADT, SIU and ORU messages, with what each is used for. - [Patient identifiers](https://docs.awellhealth.com/docs/connect-systems/patient-identifiers.md): How Awell uses FHIR-style system and value pairs so one patient can carry several identifiers from several systems without losing which is which. - [Patient creation with SIU messages](https://docs.awellhealth.com/docs/connect-systems/patient-creation-with-siu-messages.md): Drive care flows from hospital appointment messages, so scheduling an appointment starts a care flow and canceling it stops one. - [Patient Demographics Query (PDQ)](https://docs.awellhealth.com/docs/connect-systems/patient-demographics-query.md): The PDQ integration reference: how Awell searches a Patient Demographics Supplier by identifier, what the request and response look like, and how Awell Care reacts. - [The API call action](https://docs.awellhealth.com/docs/connect-systems/the-api-call-action-graphql-and-rest.md): Call any REST or GraphQL API from inside a care flow to fetch or send data, and store the response in data points the flow can build logic on. - [Connecting to systems that require OAuth](https://docs.awellhealth.com/docs/connect-systems/oauth-client-credentials.md): Use two API call actions to fetch an OAuth access token and then call the real API with it, using the client credentials grant. - [Store static values in constants](https://docs.awellhealth.com/docs/connect-systems/store-static-values-in-constants.md): Define an API URL, key or other unchanging value once and reuse it across a care flow or an entire organization. - [Integrate with extensions](https://docs.awellhealth.com/docs/connect-systems/integrate-with-extensions.md): Install a prebuilt connector for an EHR, messaging provider or e-signature service, and get custom actions and webhooks without configuring API calls. - [Awell and Healthie](https://docs.awellhealth.com/docs/connect-systems/awell-healthie.md): What connecting Awell to Healthie's EMR makes possible, and how a care flow automates actions in Healthie through its GraphQL API. - [Set up a GraphQL API call to Healthie](https://docs.awellhealth.com/docs/connect-systems/healthie-graphql-api-call.md): Configure a GraphQL API call action against Healthie, including which environment to point at and how to handle authentication. - [Send an email with Mailchimp or Mandrill](https://docs.awellhealth.com/docs/connect-systems/send-an-email-with-mailchimp-mandrill.md): Send a transactional email from a care flow through Mailchimp's Mandrill API, using a REST API call action. - Events & triggers - [Automate with events](https://docs.awellhealth.com/docs/automate-with-events.md): React 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. - [Before you trigger a care flow](https://docs.awellhealth.com/docs/automate-with-events/before-you-trigger-a-care-flow.md): Whichever way a care flow starts, every trigger needs a patient and the data the flow's logic depends on. - [Enrollment triggers](https://docs.awellhealth.com/docs/automate-with-events/enrollment-triggers.md): The section in the app for viewing and managing what starts each care flow, including webhook-based enrollment through an extension. - [Trigger a care flow from Awell Care](https://docs.awellhealth.com/docs/automate-with-events/trigger-from-awell-care.md): Start a care flow by hand in Awell Care, the option that needs no engineering work and is the fastest way to test a flow. - [Trigger with a Hosted Pages link](https://docs.awellhealth.com/docs/automate-with-events/trigger-with-a-hosted-pages-link.md): Generate a shareable link or QR code that starts a care flow and drops the patient straight into their activities, so they can self-enroll. - [Trigger from a file upload](https://docs.awellhealth.com/docs/automate-with-events/trigger-from-a-file-upload.md): Start care flows in batches by uploading a CSV to an Awell FTP server, with almost no engineering work. - [ADT feeds](https://docs.awellhealth.com/docs/automate-with-events/adt-feeds.md): Start, update or stop care flows from a hospital's admission, discharge and transfer messages, processed through Mirth. - [Trigger with the API](https://docs.awellhealth.com/docs/automate-with-events/trigger-with-the-api.md): Start care flows through the Orchestration API, the most flexible option and the one that needs engineering time. - [Start a care flow from an incoming webhook](https://docs.awellhealth.com/docs/automate-with-events/start-a-care-flow-from-an-incoming-webhook.md): Let another system start a care flow by posting to an Awell URL: create the webhook, map payload data to baseline data points, attach a patient, and read the logs. - [Webhooks and events](https://docs.awellhealth.com/docs/automate-with-events/webhooks-and-events.md): What a webhook is in Awell, the difference between events Awell sends out and webhooks sent to Awell, and what a payload contains. - [Receive webhook events](https://docs.awellhealth.com/docs/automate-with-events/receive-webhook-events.md): Build an endpoint that receives Awell's outbound webhook events: choose the events, verify the signature, respond correctly, then move from a test endpoint to production. - [Configure webhooks in Studio](https://docs.awellhealth.com/docs/automate-with-events/configure-webhooks-in-studio.md): Turn webhooks on for a care flow, give the receiving engineer the public key they verify with, and check whether what was sent actually arrived. - [Configure webhooks for all care flows](https://docs.awellhealth.com/docs/automate-with-events/configure-webhooks-for-all-care-flows.md): Set up an outgoing webhook once in CareOps and it applies to every published care flow, with its own events, custom headers and a test endpoint. - [Webhook event catalog](https://docs.awellhealth.com/docs/automate-with-events/webhook-event-catalog.md): Every event Awell can send to a subscribed endpoint, grouped by what it is about, with what each one reports and what it does not. - [Configure API call retries](https://docs.awellhealth.com/docs/automate-with-events/configure-api-call-retries.md): Change how Awell retries a failed API call from a care flow, at organization level or per care flow, and which setting wins. - [React to Healthie events with your own listener](https://docs.awellhealth.com/docs/automate-with-events/react-to-healthie-events.md): Act on Healthie webhook events through the extension's built-in events, or build a custom listener when those are not enough. - Extensions - [Extensions](https://docs.awellhealth.com/docs/extensions.md): How a care flow reaches other systems: using an extension from the marketplace, or building and deploying a new one. - [Browse the Marketplace](https://docs.awellhealth.com/docs/marketplace.md) - [What are Awell Extensions?](https://docs.awellhealth.com/docs/extensions/what-are-awell-extensions.md): Extensions connect a care flow to the outside world: health records, messaging, scheduling, and in-house apps, so data and actions move automatically instead of by hand. - [What are custom actions?](https://docs.awellhealth.com/docs/extensions/what-are-custom-actions.md): What installing an extension adds to a care flow — new action types that talk to a third-party system, alongside Awell's native ones. - [Build your own extension](https://docs.awellhealth.com/docs/extensions/get-started.md): Why an extension gets built, whether it should be public or private, and what needs installing to start. - [Create an extension](https://docs.awellhealth.com/docs/extensions/create-an-extension.md): The folder structure and properties an extension needs, from its README and changelog to the actions it exposes. - [Extension settings](https://docs.awellhealth.com/docs/extensions/extension-settings.md): Define what the person installing an extension configures, including the secure way to handle API keys. - [Store secrets](https://docs.awellhealth.com/docs/extensions/store-secrets.md): Keep API keys and credentials out of extension code by declaring them as settings, with different values per environment. - [Create an action](https://docs.awellhealth.com/docs/extensions/create-an-action.md): Define a custom action — its metadata, how a care flow author configures it in Studio, and the logic that runs when a care flow activates it. - [Action fields](https://docs.awellhealth.com/docs/extensions/action-fields.md): The field types available when defining how a care flow author configures a custom action in Studio. - [The onEvent function](https://docs.awellhealth.com/docs/extensions/on-event.md): The function called when a care flow activates a custom action, with its payload, its callbacks, and the helpers available to it. - [onActivityCreated (deprecated)](https://docs.awellhealth.com/docs/extensions/on-activity-created.md): The onActivityCreated function was deprecated on 1 September 2024. Use onEvent instead. - [Test your extension](https://docs.awellhealth.com/docs/extensions/test-your-extension.md): Run unit tests against extension code with jest, or run the full extension server locally against the pub/sub emulator. - [Deploy your extension](https://docs.awellhealth.com/docs/extensions/deploy-your-extension.md): Register an extension so the extensions server picks it up, by adding it to the exported extensions array. - [Versioning](https://docs.awellhealth.com/docs/extensions/versioning.md): How extension versions are tracked, and why every extension needs a changelog. - [Contributing guidelines](https://docs.awellhealth.com/docs/extensions/contributing-guidelines.md): How to contribute to Awell's public extensions repository — discussions, issues, pull requests, coding style, and what to expect from review. - Marketplace - [Marketplace](https://docs.awellhealth.com/docs/marketplace.md): Every extension a care flow can use: what each one does, which actions it adds, and what to configure before it works. - [Airtop](https://docs.awellhealth.com/docs/marketplace/airtop.md): Effortlessly scrape and control any site with inexpensive and scalable AI-powered cloud browsers - [athenahealth](https://docs.awellhealth.com/docs/marketplace/athenahealth.md): Athena offers medical groups, hospitals, and health systems cloud-based EHR, practice management, and patient engagement services that seamlessly connect care and drive results for every client. - [Availity](https://docs.awellhealth.com/docs/marketplace/availity.md): Availity's two-sided network allows payers and providers to share accurate, up-to-date information earlier in the healthcare lifecycle. - [Awell Workflow](https://docs.awellhealth.com/docs/marketplace/awell.md): Enrich your care flows with powerful Awell actions. - [Awell Tasks](https://docs.awellhealth.com/docs/marketplace/awelltasks.md): Connect to Awell Tasks - [Bland.ai](https://docs.awellhealth.com/docs/marketplace/bland.md): Automate your phone calls with AI - [Braze](https://docs.awellhealth.com/docs/marketplace/braze.md): Braze is a customer engagement platform that helps you communicate with your patients. - [Cal.com](https://docs.awellhealth.com/docs/marketplace/caldotcom.md): Enable scheduling in your care flows with Cal.com. - [Calendly](https://docs.awellhealth.com/docs/marketplace/calendly.md): ** In beta ** Enable scheduling in your care flows with Calendly. - [Canvas Medical (BETA)](https://docs.awellhealth.com/docs/marketplace/canvasmedical.md): Canvas Medical allows the collection and manage data through a digital device that contains all of the patient's medical history - [Cerner](https://docs.awellhealth.com/docs/marketplace/cerner.md): Cerner EMR is an electronic medical records system that helps healthcare organizations improve patient care and increase efficiency. - [Cloudinary](https://docs.awellhealth.com/docs/marketplace/cloudinary.md): Cloudinary is a cloud-based image and video management platform for storing, managing, and delivering digital media assets. - [cm.com](https://docs.awellhealth.com/docs/marketplace/cmdotcom.md): cm.com is a communications Platform for Messaging & Voice - [Advanced data collection](https://docs.awellhealth.com/docs/marketplace/collectdata.md): This extension allows you to collect data from your users using a variety of advanced input types and data sources. - [Customer.io](https://docs.awellhealth.com/docs/marketplace/customerio.md): Customer.io is a customer engagement platform designed to create personalized customer journeys that engage, convert, and scale. - [Date Helpers](https://docs.awellhealth.com/docs/marketplace/datehelpers.md): A set of utility actions to help with common and useful date and time operations. - [Dock Health](https://docs.awellhealth.com/docs/marketplace/dockhealth.md): HIPAA-compliant task management and workflow automation for healthcare. Assign, track, automate, and complete administrative to-do lists. - [Documo](https://docs.awellhealth.com/docs/marketplace/documo.md): Documo extension for Awell - [DocuSign](https://docs.awellhealth.com/docs/marketplace/docusign.md): DocuSign makes your business faster, simpler and more cost-efficient with electronic agreements. Agree with confidence, with intuitive signing experiences across virtually any device. - [Dropbox Sign](https://docs.awellhealth.com/docs/marketplace/dropboxsign.md): Dropbox Sign (formerly HelloSign) is the easiest way to send, receive and manage legally binding electronic signatures. - [Elation](https://docs.awellhealth.com/docs/marketplace/elation.md): Elation is a clinical-first EHR and patient engagement tool. It's designed for the craft of primary care medicine. - [Epic](https://docs.awellhealth.com/docs/marketplace/epic.md): Epic is an Electronic Health Records (EHR) system for healthcare organizations, hospitals and large practices. - [External Server](https://docs.awellhealth.com/docs/marketplace/external-server.md): External server used for prototyping. See README for additional documentation. - [Formsort](https://docs.awellhealth.com/docs/marketplace/formsort.md): Formsort is a fully-managed form-building platform. - [Freshdesk](https://docs.awellhealth.com/docs/marketplace/freshdesk.md): Freshdesk is a cloud-based customer service software that helps businesses manage and streamline their customer support operations. - [Freshsales](https://docs.awellhealth.com/docs/marketplace/freshsales.md): Freshsales is a cloud-based, AI-powered customer relationship management (CRM) software designed to help sales teams organize, manage, and close deals more efficiently. - [Gridspace](https://docs.awellhealth.com/docs/marketplace/gridspace.md): Use AI phone conversations to communicate with your patients. - [Healthie](https://docs.awellhealth.com/docs/marketplace/healthie.md): Easily orchestrate actions in Healthie and receive webhooks events. - [HubSpot](https://docs.awellhealth.com/docs/marketplace/hubspot.md): HubSpot is a customer relationship management (CRM) platform that provides a suite of tools for marketing, sales, customer service, and content management. - [Identity Verification](https://docs.awellhealth.com/docs/marketplace/identityverification.md): Verify the patient's identity by asking for a piece of personal information, such as their date of birth. - [Infobip](https://docs.awellhealth.com/docs/marketplace/infobip.md): Infobip is a global cloud communications platform that provides a wide range of communication and customer engagement solutions for businesses. - [Iterable](https://docs.awellhealth.com/docs/marketplace/iterable.md): Iterable is an email marketing automation platform that allows creating, sending, and tracking personalized email campaigns. - [Landing.ai](https://docs.awellhealth.com/docs/marketplace/landingai.md): Turn your documents and images into visual intelligence. LandingAI’s cutting-edge software platform makes computer vision easy for a wide range of applications across all industries. - [Mailchimp](https://docs.awellhealth.com/docs/marketplace/mailchimp.md): Mailchimp is an all-in-one marketing platform that helps businesses to design, send, and manage email campaigns. - [Mailgun](https://docs.awellhealth.com/docs/marketplace/mailgun.md): Mailgun is a cloud-based email service provider that allows for sending transactional emails. - [Math](https://docs.awellhealth.com/docs/marketplace/math.md): The Math extension provides some useful actions to perform simple mathematical operations. - [Medplum](https://docs.awellhealth.com/docs/marketplace/medplum.md): Medplum is the open source healthcare developer platform that helps you build, test, and deliver any healthcare product or service. - [MessageBird](https://docs.awellhealth.com/docs/marketplace/messagebird.md): MessageBird is a cloud-based communication platform with support for a variety of channels including WhatsApp, voice, live chat and more. - [Metriport](https://docs.awellhealth.com/docs/marketplace/metriport.md): Metriport helps digital health companies access and manage health and medical data, through a single universal API. - [REST](https://docs.awellhealth.com/docs/marketplace/rest.md): A utility extension with more advanced options to make REST API calls - [Salesforce](https://docs.awellhealth.com/docs/marketplace/salesforce.md): Salesforce.com is a cloud-based customer relationship management (CRM) software used to manage customer data, sales processes, marketing campaigns, and customer service activities - [Sendbird](https://docs.awellhealth.com/docs/marketplace/sendbird.md): Sendbird is a cloud-based chat and messaging platform. - [Sendgrid](https://docs.awellhealth.com/docs/marketplace/sendgrid.md): SendGrid is a cloud-based email delivery platform that provides services for sending and managing email campaigns, transactional emails, and other types of messages. - [Shelly](https://docs.awellhealth.com/docs/marketplace/shelly.md): Library of AI-powered actions - [Slack](https://docs.awellhealth.com/docs/marketplace/slack.md): Send messages to Slack channels from your care flows to keep your team informed. - [SRFax](https://docs.awellhealth.com/docs/marketplace/srfax.md): Retrieve faxes from SRFax and extract text using LandingAI OCR. - [Stedi](https://docs.awellhealth.com/docs/marketplace/stedi.md): Automate healthcare transactions like real-time eligibility checks and claims processing with APIs that support thousands of payers. - [Stripe (alpha)](https://docs.awellhealth.com/docs/marketplace/stripe.md): Stripe powers online and in-person payment processing and financial solutions for businesses of all sizes. - [Talkdesk](https://docs.awellhealth.com/docs/marketplace/talkdesk.md): Talkdesk is a cloud-based customer experience and contact center software company. - [Text-em-all](https://docs.awellhealth.com/docs/marketplace/text-em-all.md): Send text messages to your patients. - [TextLine](https://docs.awellhealth.com/docs/marketplace/textline.md): Textline's business texting software offers solutions for sales, marketing, customer service, and beyond. Utilize the power of SMS to grow quickly. - [Transform](https://docs.awellhealth.com/docs/marketplace/transform.md): Transform is an extension on Awell's Marketplace with utility functions that allows you to transform data from one type to another. - [Twilio](https://docs.awellhealth.com/docs/marketplace/twilio.md): Add robust messaging capabilities to your care flow. - [WestFax](https://docs.awellhealth.com/docs/marketplace/westfax.md): Send faxes securely and in compliance with HIPAA regulations using WestFax. - [Workramp](https://docs.awellhealth.com/docs/marketplace/workramp.md): An LMS platform. The system identifier used is https://www.workramp.com/ - [Zendesk Support](https://docs.awellhealth.com/docs/marketplace/zendesk.md): Zendesk Support is a customer service platform that provides ticketing, knowledge base, and customer communication tools. - [Zendesk Sell](https://docs.awellhealth.com/docs/marketplace/zendesksell.md): Zendesk Sell is a customer service and support platform that provides a suite of tools and software for businesses to manage their customer interactions. - [Zoom](https://docs.awellhealth.com/docs/marketplace/zoom.md): Zoom is a communications platform that allows users to connect with video, audio, phone, and chat. - **Build on Awell** - Embed & host - [Embed & host](https://docs.awellhealth.com/docs/embed-and-host.md): Put care flow activities in front of patients and clinicians, using pages Awell hosts or a custom interface built with Navi. - [Awell Hosted Pages](https://docs.awellhealth.com/docs/embed-and-host/overview-hosted-pages.md): A prebuilt app that lets patients and stakeholders complete their care flow activities, with no interface to build. - [Built-in and customizable features](https://docs.awellhealth.com/docs/embed-and-host/built-in-and-customizable-features.md): What Hosted Pages provides by default, from accessibility and internationalization to form auto-save, and which parts are configurable. - [Sessions and links](https://docs.awellhealth.com/docs/embed-and-host/sessions-and-links.md): How to get a Hosted Pages URL for a patient, and how to choose depending on whether Awell or the integrating system decides the timing. - [Embed or redirect to Hosted Pages](https://docs.awellhealth.com/docs/embed-and-host/redirect-or-embed.md): Put Hosted Pages in an iframe inside a host app, or send the stakeholder to it, and control where they end up when they finish. - [Hosted Pages settings](https://docs.awellhealth.com/docs/embed-and-host/hosted-pages-settings.md): Customize how Hosted Pages looks and behaves, per care flow or across the whole organization. - [Set a custom domain for Hosted Pages](https://docs.awellhealth.com/docs/embed-and-host/set-a-custom-domain-for-hosted-pages.md): Serve Hosted Pages from a custom domain instead of Awell's, so links look like they come from the care organization. - [Care flow design with Hosted Pages](https://docs.awellhealth.com/docs/embed-and-host/care-flow-design-with-hosted-pages.md): How to design a care flow whose activities are completed on Hosted Pages, and why system activities in the wrong place make a patient wait. - [Link to an activity from email or SMS](https://docs.awellhealth.com/docs/embed-and-host/link-to-an-activity-from-email-or-sms.md): Put a link to a pending activity into an email or text message, so a stakeholder can act straight from the message. - [Tracking and attribution](https://docs.awellhealth.com/docs/embed-and-host/tracking.md): Attribute Hosted Pages sessions to campaigns, partners and traffic sources using UTM or custom parameters, then query the results in BigQuery. - [What is Navi?](https://docs.awellhealth.com/docs/embed-and-host/what-is-navi.md): An embeddable, production-ready UI layer that renders care flow activities inside an existing product, with branding, validation and events built in. - [Navi quickstart](https://docs.awellhealth.com/docs/embed-and-host/quickstart.md): Get a care flow activity rendering in a host app with Navi, using a publishable key and a few lines of setup. - [Activity model and lifecycle](https://docs.awellhealth.com/docs/embed-and-host/activity-model-and-lifecycle.md): What an activity is in Navi, the types it supports, the states it moves through, and where validation happens. - [Sessions and JWTs](https://docs.awellhealth.com/docs/embed-and-host/sessions-and-jwts.md): How Navi grants access using a short-lived JWT inside a longer session, and why the two lifetimes are different. - [Navi architecture and security](https://docs.awellhealth.com/docs/embed-and-host/navi-architecture-and-security.md): How Navi isolates embedded activities using a separate-origin iframe, scoped cross-origin messaging, and tokenization. - [Branding and theming](https://docs.awellhealth.com/docs/embed-and-host/branding-and-theming.md): Control how Navi looks, either organization-wide in the CareOps portal or with per-app overrides through the SDK. - [Build your own UI](https://docs.awellhealth.com/docs/embed-and-host/build-your-own-ui.md): Build a custom interface on Awell's API when neither Hosted Pages nor Navi gives enough control. - Data & source control - [Data & source control](https://docs.awellhealth.com/docs/data.md): Get care flow data out for analysis, keep track of what a care flow collects, and version care flows as code in a Git repository. - [Getting data out of Awell](https://docs.awellhealth.com/docs/data/getting-data-out-of-awell.md): How to work with care flow data: stream events as they happen, or query the data repository in BigQuery. - [Get access to BigQuery](https://docs.awellhealth.com/docs/data/getting-access.md): How to reach the BigQuery datasets, through BigQuery Studio or a read-only service account for external BI tools. - [Data schema](https://docs.awellhealth.com/docs/data/data-schema.md): How care flow data is structured in the repository, and the definition-versus-instance distinction that every query depends on. - [Monthly active patients (MAPs)](https://docs.awellhealth.com/docs/data/monthly-active-patients.md): What makes a patient count as active in a given month, and therefore what Awell bills on. - [Data catalog](https://docs.awellhealth.com/docs/data/data-catalog.md): The overview of every data point a care flow collects, where to find it, and what it shows. - [Configure and use your data catalog](https://docs.awellhealth.com/docs/data/configure-use-your-data-catalog.md): Flag data points as PII, add metadata, and export the catalog, so the data a care flow collects stays understandable and handled correctly. - [Source Control](https://docs.awellhealth.com/docs/data/source-control.md): Sync care flows as code to GitHub or GitLab, so changes are versioned, reviewable, and can gate publication. - [Set up Source Control](https://docs.awellhealth.com/docs/data/set-up-source-control.md): Connect a care flow to a GitHub or GitLab repository, including creating the access token Awell needs. - [How syncing works](https://docs.awellhealth.com/docs/data/syncing-to-scm.md): The limits of Source Control today: one repository per care flow per environment, and a one-way sync from Awell to the repository. - [Protect care flows](https://docs.awellhealth.com/docs/data/protect-care-flows.md): Let anyone design a care flow while requiring an engineer-approved merge before it can be published. - [Deploy care flows](https://docs.awellhealth.com/docs/data/deploy-care-flows.md): Deploy care flows to Awell's default environments or a custom environment from a CI/CD pipeline. - [Care flow components as code](https://docs.awellhealth.com/docs/data/components.md): The JSON files and folder structure Awell writes to the repository when a care flow is synced. - [API reference](https://docs.awellhealth.com/api-reference.md) - **Operate & govern** - Administer & secure - [Administer & secure](https://docs.awellhealth.com/docs/administer-and-secure.md): Set up an Awell organization: invite the team, control who can do what, apply branding, and connect single sign-on. - [Team, roles and permissions](https://docs.awellhealth.com/docs/administer-and-secure/roles-and-permissions.md): Invite team members, manage their access, and see exactly which actions each role allows. - [Set your organization's branding](https://docs.awellhealth.com/docs/administer-and-secure/branding.md): Apply an organization's logo and styling to the Awell platform and to the Hosted Pages patients see. - [Set working hours for patient contact](https://docs.awellhealth.com/docs/administer-and-secure/working-hours.md): Set the hours when a care flow may contact patients, and see how activities held outside those hours are released when the window opens. - [Single sign-on](https://docs.awellhealth.com/docs/administer-and-secure/single-sign-on.md): What SSO gives an organization, the protocols Awell supports, and how just-in-time provisioning creates users on first login. - [Set up SSO](https://docs.awellhealth.com/docs/administer-and-secure/set-up-sso.md): The SSO setup process, which starts by contacting Awell, plus the details to gather from the identity provider. - [SSO with Google](https://docs.awellhealth.com/docs/administer-and-secure/sso-with-google.md): Integrate Google Workspace as the identity provider for Awell, using a custom SAML app. - [SSO with Okta](https://docs.awellhealth.com/docs/administer-and-secure/sso-with-okta.md): Integrate Okta as the identity provider for Awell, using a SAML app integration. - [Platform, security and compliance FAQ](https://docs.awellhealth.com/docs/administer-and-secure/faq.md): Direct answers to the questions prospects, security reviewers and procurement teams ask most about Awell's architecture, security posture, data handling and regulatory position. ## API Reference - [API reference](https://docs.awellhealth.com/api-reference.md): The Awell Orchestration API is a single GraphQL endpoint for reading and writing patients, care flows, activities, and more. - Guides - [Guides](https://docs.awellhealth.com/api-reference/guides.md): How to work with the Awell Orchestration API, covering authentication, what the API returns, and specific integration jobs. - [Getting started](https://docs.awellhealth.com/api-reference/guides/getting-started.md): Make your first authenticated request to the Awell Orchestration API, covering the endpoint, the auth header, and a working query. - [Authentication](https://docs.awellhealth.com/api-reference/guides/authentication.md): How to obtain an Awell Orchestration API key and send it with every request. - [Environments](https://docs.awellhealth.com/api-reference/guides/environments.md): The Awell Orchestration API environments and regions, the GraphQL endpoint for each, and how an API key maps to one. - [Pagination](https://docs.awellhealth.com/api-reference/guides/pagination.md): How list queries in the Awell Orchestration API page and sort results using count, offset, and sorting parameters. - [Errors](https://docs.awellhealth.com/api-reference/guides/errors.md): How the Awell Orchestration API signals success and failure through the code and success envelope, plus GraphQL errors. - [Rate limits](https://docs.awellhealth.com/api-reference/guides/rate-limits.md): Awell does not publish request-rate limits for the Orchestration API. What is documented is the per-query result cap, and how to behave when a request fails. - [Mutations](https://docs.awellhealth.com/api-reference/guides/mutations.md): An orientation to the write operations in the Awell Orchestration API and where to find them. - [E.164 phone numbers](https://docs.awellhealth.com/api-reference/guides/e164-phone-numbers.md): The Awell Orchestration API accepts phone numbers only in E.164 format: the validation rules applied, what they do and don't prove, and how to convert numbers stored another way. - [Webhooks](https://docs.awellhealth.com/api-reference/guides/webhooks.md): How Awell care flows send webhook calls to your systems, and how to inspect and retry them. - [Domain model](https://docs.awellhealth.com/api-reference/guides/domain-model.md): The objects the Orchestration API works with, and the lifecycle of a typical integration from creating a patient to submitting a form. - [Start a care flow](https://docs.awellhealth.com/api-reference/guides/start-a-care-flow.md): Start a care flow through the API: the prerequisites, which start mutation to use, how versions are selected, and starting a hosted-pages session at the same time. - [Query activities](https://docs.awellhealth.com/api-reference/guides/query-activities.md): How to look up activities, the server-side filters available, and how to page through results. - [Work with forms](https://docs.awellhealth.com/api-reference/guides/work-with-forms.md): Render a form, evaluate its conditional logic on every answer, and submit responses in the string format the API expects. - [Manage patients](https://docs.awellhealth.com/api-reference/guides/manage-patients.md): Create and update patients through the API, including the identifier behavior that replaces existing identifiers. - [Versions and releases](https://docs.awellhealth.com/api-reference/guides/versions-and-releases.md): Why every care flow query needs the right release_id, and how a patient stays on the version they started on. - [Webhook payloads](https://docs.awellhealth.com/api-reference/guides/webhook-payloads.md): The payload shape for each webhook event Awell sends, grouped by the object the event is about. - Reference - [Reference](https://docs.awellhealth.com/api-reference/reference.md): The Awell Orchestration API operations, grouped by the domain object they act on (patients, care flows, activities, tracks, and more). - [Patients](https://docs.awellhealth.com/api-reference/reference/patients.md): Create, find, update, and manage patients and their data points in the Awell Orchestration API. - [Care flows](https://docs.awellhealth.com/api-reference/reference/care-flows.md): Start, stop, pause, and inspect care flows, their activities, and their data points. - [Activities](https://docs.awellhealth.com/api-reference/reference/activities.md): Query the activities in a care flow and retry, expire, or annotate them. - [Activity types](https://docs.awellhealth.com/api-reference/reference/activity-types.md): Work with the specific activity types — forms, checklists, messages, clinical notes, calculations, and EMR reports. - [Tracks](https://docs.awellhealth.com/api-reference/reference/tracks.md): Query and schedule tracks — the groupings of steps within a care flow. - [Stakeholders](https://docs.awellhealth.com/api-reference/reference/stakeholders.md): Look up the stakeholders that participate in a care flow. - [Timers](https://docs.awellhealth.com/api-reference/reference/timers.md): Query and expire the timers that delay steps in a care flow. - [Hosted sessions & pages](https://docs.awellhealth.com/api-reference/reference/hosted-sessions.md): Start and complete Awell-hosted sessions and hosted pages for stakeholders to complete activities. - [API calls & webhooks](https://docs.awellhealth.com/api-reference/reference/api-calls-and-webhooks.md): Inspect the API calls and webhook calls a care flow makes, and retry failed ones. - [Subscriptions](https://docs.awellhealth.com/api-reference/reference/subscriptions.md): Real-time GraphQL subscriptions for activity, session, care flow, API call, and webhook events. - [Tenant](https://docs.awellhealth.com/api-reference/reference/tenant.md): Read information about the current tenant. - Awell Score - [Awell Score](https://docs.awellhealth.com/api-reference/score.md): Awell Score is a separate, CE-marked REST API that calculates validated clinical and patient-reported outcome measures. - [Awell Score API](https://docs.awellhealth.com/api-reference/score/awell-score-api.md): The standalone REST API for calculating validated clinical and patient-reported outcome scores, separate from the Orchestration GraphQL API. - Tools - [Tools](https://docs.awellhealth.com/api-reference/tools.md): The playground, Postman collection, and SDKs for exploring and building against the Awell Orchestration API. - [API tools and SDKs](https://docs.awellhealth.com/api-reference/tools/api-tools.md): The playground, Postman collection, and SDKs available for working with the Awell Orchestration API. ## Changelog - [Faster Orchestration APIs and a centralized patient data store](https://docs.awellhealth.com/changelog#2026-06-07-orchestration-api-and-patient-data): Deprecated GraphQL queries and subscriptions were removed in favor of faster replacements, and patient data moved to a new centralized BigQuery table. Both changes are breaking and need action from any integration with the Orchestration API or the data warehouse. - [Archive care flows and richer activity queries](https://docs.awellhealth.com/changelog#2026-05-01-archive-care-flows-and-richer-activity-queries): Care flows that are no longer in use can be archived, and activity queries expose more data with refreshed developer docs. - [Calculations that read the form they belong to](https://docs.awellhealth.com/changelog#2026-04-01-calculations-scoped-to-a-form): A calculation can now be tied to a specific form, so it reads that form's answers instead of stale data, alongside fixes for promotion, outgoing webhooks, and Hosted Pages. - [Score labels in more languages, and webhook keys that stay hidden](https://docs.awellhealth.com/changelog#2026-03-01-score-labels-and-hidden-webhook-keys): Score labels now support languages other than English, outgoing webhook headers accept global constants so authentication keys stay hidden, and Hosted Pages can return stakeholders to an organization's own URL. - [Model decisions and repeating care explicitly](https://docs.awellhealth.com/changelog#2025-12-01-decision-component-and-track-looping): The Decision component puts branching logic in one dedicated node, track looping models care that repeats, forms are private to their care flow by default, and any care flow can be summarized in seconds. - [Care flow logs stream to Datadog](https://docs.awellhealth.com/changelog#2025-06-01-log-streaming-to-datadog): Orchestration logs can be streamed to Datadog, so failed and stale activities can be alerted on in the tooling a team already watches. Discarding paths in a care flow is also about 55% faster. - [Validation rules on text inputs, and separate publish and release rights](https://docs.awellhealth.com/changelog#2025-05-01-form-validation-and-publishing-roles): Short text inputs can be validated with built-in rules or a regular expression, and the Publisher and Releaser roles separate who can publish a care flow from who can put it live in Production. - [Promote a care flow to Production without waiting on Awell](https://docs.awellhealth.com/changelog#2025-04-01-promote-care-flows-to-production): Care flows can be promoted from Sandbox to Production directly in the app, so releasing no longer depends on an Awell team member being available. - [Activate a step at a chosen hour, collect files, and manage extensions in one place](https://docs.awellhealth.com/changelog#2025-03-01-timer-file-upload-and-central-extensions): The Timer component activates a step at a specific hour in the patient's timezone, forms accept file and image uploads, extensions are configured once for the whole organization, and enrollment triggers have their own view. - [Describe a form in words, and read and write Epic data from a care flow](https://docs.awellhealth.com/changelog#2025-01-01-shelly-in-the-form-builder-and-epic): Shelly turns a description of an assessment into form questions, and the Epic extension reads and writes data to an Epic instance from inside a care flow. - [Define a value once, and collect conditions with ICD-10](https://docs.awellhealth.com/changelog#2024-12-01-global-constants-and-icd-questions): Global constants let a value be defined once and reused across care flows, the ICD question collects medical conditions using ICD-10, and extension action fields support dropdowns. - [See where patients move through a care flow, and where they stop](https://docs.awellhealth.com/changelog#2024-11-01-flow-path): Flow Path shows how patients and care teams move through each step of a care flow, so engagement and drop-off are visible per step. Awell is also SOC 2 certified. - [Monitoring makes failing activities and integrations visible](https://docs.awellhealth.com/changelog#2024-10-01-monitoring): Monitoring is a stage in the platform, with counts of started care flows, recent failed activities and their errors, and filters to drill into a specific activity. - [Verify a patient's identity with date of birth before a session starts](https://docs.awellhealth.com/changelog#2024-09-01-date-of-birth-verification): A date of birth action in Hosted Pages adds a verification step before a stakeholder reaches the care flow, plus an email question type and a query that returns every data point value for a care flow. - [Worklists give care teams one list to work from](https://docs.awellhealth.com/changelog#2024-08-01-worklists-in-awell-care): Worklists are embedded in the platform, with customizable views so a team, a department, or a role sees only the patients and activities relevant to it. - [Update and delete records in third-party systems from a care flow](https://docs.awellhealth.com/changelog#2024-07-01-more-http-verbs-for-api-calls): API call actions support PATCH, PUT, and DELETE, and accept non-JSON responses, so a care flow can update or remove records in a third-party system without a custom extension. - [Ask questions of care flow data, and duplicate a care flow in a few clicks](https://docs.awellhealth.com/changelog#2024-06-01-shelly-data-chat-and-duplication): Shelly answers questions about care flow data in plain language instead of a dashboard or a SQL query, and a care flow can be duplicated to build a variation of it. - [A Node.js SDK for the Orchestration API](https://docs.awellhealth.com/changelog#2024-05-01-nodejs-sdk): A server-side SDK wraps Awell's GraphQL APIs, removing the boilerplate and providing auto-completion, validation, type safety, and the exported GraphQL types. - [Track one patient under identifiers from every system](https://docs.awellhealth.com/changelog#2024-03-01-patient-identifiers): Patients can carry multiple business identifiers from external systems, and those identifiers can be used to retrieve patients and start care flows. Number and date questions also accept validation rules. - [Start a care flow from a third-party event, and send HIPAA-compliant faxes](https://docs.awellhealth.com/changelog#2024-02-01-care-flow-triggers-and-westfax): Trigger types can be browsed and configured in Awell Studio, including webhook-triggered care flows without writing code, the WestFax extension sends HIPAA-compliant faxes, and select questions accept text values. - [Expire stale actions, sign in with SSO, and finish activities on-site](https://docs.awellhealth.com/changelog#2024-01-01-action-expiration-and-sso): Forms and messages can expire after a period of inactivity so a care flow isn't stuck waiting, single sign-on is available, the slider question no longer records an answer nobody gave, and a QR code in Awell Care lets a patient finish pending activities during a visit. - [Care flows as code, versions that roll back, and audit logs](https://docs.awellhealth.com/changelog#2023-11-01-source-control-and-care-flow-versions): Care flows sync as code to GitHub or GitLab, any published version can be set live, audit logs record why every track, step, and action fired, and a Hosted Pages link starts a care flow with one click. - [Data variables work in more fields, and activities load faster in Hosted Pages](https://docs.awellhealth.com/changelog#2023-10-01-extensions-and-data-variables): Constants and dynamic variables are unified as data variables and work in the endpoint and header fields of API call actions, several extensions gained actions, and activities load faster in Hosted Pages. - [Infinite loop control, and shareable links to a single activity](https://docs.awellhealth.com/changelog#2023-09-01-infinite-loop-control): Orchestration has preventive measures against infinite loops, an activity can be opened directly from the working list and shared as a link, and the patient ID is available as a data point. - [Import patient demographics, and attach metadata to forms](https://docs.awellhealth.com/changelog#2023-08-01-form-metadata-and-patient-demographics): A Patient Demographics Query integration imports patient details from an external system, forms and questions carry a JSON metadata object for the systems that render them, and conversational forms progress automatically. - [Control what happens when an API call fails, and stop a care flow from Awell Care](https://docs.awellhealth.com/changelog#2023-07-01-api-call-retries-and-form-display-modes): Retry logic for failed API calls is configurable per organization and per care flow, outgoing calls carry an idempotency key, a care flow can be stopped from Awell Care, and forms can be displayed one question at a time or all at once. - [Manage API keys in the app, and branch on missing data](https://docs.awellhealth.com/changelog#2023-06-01-api-keys-and-new-condition-operators): API keys can be created and managed in the Awell platform, and the "has no value", "has any value", and "is today" operators make conditional logic possible on data that's absent or dated today. ## Beyond these docs Awell services that the navbar links to but this documentation does not describe. - [System Status](https://status.awellhealth.com/): Awell's live platform status, current incidents, and scheduled maintenance. These docs never carry real-time status; this page is the only place that reports whether Awell is up right now.