Changelog

What changed in Awell, newest first. Each entry notes who it's for and what to do about it.

Faster Orchestration APIs and a centralized patient data store

Developersorchestrationapidata

Two changes this month may affect your integrations. Both are breaking — here's what changed and what to do.

Breaking changes

Deprecated GraphQL queries and subscriptions removed

On June 7, 2026 we removed several previously-deprecated GraphQL queries, subscriptions, and fields from the Orchestration API. The replacements are already live, accept equivalent parameters, and are faster.

Queries

RemovedUse insteadNote
activitiesactivitiesByPatientpatientId is now required
activitiesactivitiesByCareflowDefinitioncareflowDefinitionId is now required
pathwayActivitiescareflowActivities
myPendingActivitiesmyActivities
pathwayElementsNo direct replacement

Field resolvers

RemovedUse instead
Pathway.activitiesPathway.latestActivities
.dataPointDefinitions.data_point_definitions

Subscriptions: elementCreated, elementUpdated, and elementCompleted were removed with no direct replacement.

What you need to do: update any integration that references the removed queries, fields, or subscriptions to use the alternatives above. If you relied on pathwayElements or the element subscriptions, reach out through your normal support channel and we'll help you find the best path forward.

Patient data moved to a new BigQuery table

Patient data now lives in a centralized, patient-scoped patient_data table in BigQuery. The legacy patient-profile table is deprecated, and data stopped flowing into it on June 7, 2026.

What you need to do: point any queries, models, or pipelines that read patient-profile at patient_data instead. The BigQuery data schema has the full new schema.

Why: this is the first step toward patient data becoming a first-class entity in Awell — backed by unique patient identifiers and faster patient search — rather than living inside individual care flows.

Fixes

  • Fixed questionnaire answers not saving for some patients.
  • Fixed care flows occasionally completing prematurely.
  • Fixed an orchestration timeout when activities shared the same stakeholder session.
  • Fixed patient creation occasionally failing with an "Argument Validation Error".
  • Improved contrast and readability of form answer text.
  • Scaled and stabilized the extension server under heavy load.