<aside> ⚠️
Breaking change to our APIs
</aside>
We recently made two changes that may affect your integrations. Here's what changed and what you need to do.
On June 7, 2026 we removed several GraphQL queries, subscriptions, and fields from our Orchestration API that had previously been marked as deprecated. These endpoints were removed to streamline the API. The replacements are faster and more performant.
Queries:
| Deprecated | New | Remark |
|---|---|---|
activities |
activitiesByPatient |
⚠ patientId is now required |
activities |
activitiesByCareflowDefinition |
⚠ careflowDefinitionId is now required |
pathwayActivities |
careflowActivities |
N/A |
myPendingActivities |
myActivities |
N/A |
pathwayElements |
N/A | No direct replacement (see note below) |
Field resolvers:
| Deprecated | New | Remark |
|---|---|---|
Pathway.activities |
Pathway.latestActivities |
N/A |
.dataPointDefinitions |
.data_point_definitions |
N/A |
Subscriptions:
| Deprecated | New | Remark |
|---|---|---|
elementCreated |
N/A | No direct replacement (see note below) |
elementUpdated |
N/A | No direct replacement (see note below) |
elementCompleted |
N/A | No direct replacement (see note below) |
Note on the pathwayElements query and element subscriptions: these no longer have a direct equivalent. If you were relying on them, please reach out and we'll work with you to find the best path forward.
What you need to do: if any of your integrations reference the removed queries, fields, or subscriptions, update them to use the alternatives above: they're already live and accept equivalent parameters.
<aside> ⚠️
Breaking change to our data model
</aside>
Patient data has moved to a new patient_data table in BigQuery. The legacy patient-profile table is now deprecated, and data stopped flowing into it as of June 7.
What you need to do: point any queries, models, or pipelines that read the old patient-profile table at patient_data instead. Our developer hub has full details on the new table schema.
Why we made this change: we've moved patient data into a centralized, patient-scoped store backed by unique patient identifiers and faster patient search. This is the first step in a larger shift: patient data becoming its own first-class entity in Awell rather than being locked inside individual care flows. There's more coming, and we'll share it as it ships.
Questions or need a hand with either migration? Reach out through your normal support channel, we’re happy to help.