Terminology
The platform has one set of names, and the API, the portal and the apps all use them. You may arrive with your own: a health coach says "action plan", someone who used the previous Intervengine says "card". Those words are listed beside ours so you can find your way in; this site uses ours.
Content
| Our term | What it is | You might call it |
|---|---|---|
| Atom | One thing on a screen: a question, a page of text, a picture, a button, an exercise. Its type fixes what is shown and what a response stores. | An activity element (previous Intervengine), a question, a step |
| Sequence | An ordered set of pages of atoms a participant works through in one sitting. | An activity, a card, a form, a check-in, a questionnaire |
| Score and band | A named number a sequence works out from the responses, and the name of the range that number falls in. | A total, a subscale, a severity level |
| Journey | A graph of nodes and transitions: what a participant is given next depends on what they did and how they responded. | A programme, a pathway, a care plan, a course |
| Node, transition, action | A step of a journey; a one-way way out of it; something a node does when a participant arrives. | A stage, a branch, a trigger |
| Condition | A rule that is true or false about one participant right now, used on transitions, actions, pages and atoms. | A rule, a filter, a criterion |
| Surface | A named, styled part of the participant's home screen that user sequences are placed on. | A home screen section, the to-do list |
| Asset | An uploaded file that content, tenants and users reference. | Media, an upload |
| Version | One saved state of an atom, sequence or journey. The published version is the newest one with a publish date. | A revision, a draft |
A participant
| Our term | What it is | You might call it |
|---|---|---|
| User sequence | One sequence assigned to one participant, with its schedule, surface and behaviour. Action planning is done with user sequences. | An action plan, an assigned card, a to-do |
| Occurrence | One due slot of a user sequence. A daily user sequence has one a day. | A due date, an instance |
| Response | What a participant submitted for one occurrence: the values, and the scores and bands. | An answer, a submission, an entry |
| User journey | A participant's enrolment in a journey. | An enrolment, a pathway instance |
| Biomarker | Something the phone or watch measures, such as steps, sleep or heart rate. A user biomarker is one value of it from the phone's health store. | Biometrics, wearable data, vitals, health events |
| Chat | A conversation between a participant and staff. | Secure messaging, an inbox |
People and organisation
| Our term | What it is | You might call it |
|---|---|---|
| Tenant | One organisation's own space, isolated from every other's. Shared library content lives in the DEFAULT tenant. | A customer, a client, an organisation, a workspace |
| Cohort | A named group of participants inside a tenant, with its own sign-up code. | An intake, a site, a wave |
| Identity | One person across every tenant they belong to. Credentials live with the identity provider. | A login, an account |
| User | A person in one tenant, with one role. | A member, a profile |
| Participant | A user with the participant role: the person using the app. | A patient, a client, a member, an employee |
| Coach | A user with the coach role, working with the tenant's participants. The word stands for whoever does that job in your service. | A nurse, a physiotherapist, a navigator, a case manager |
| Invitation | An offer to join a tenant with a role, sent to an address. | An invite |
| Tag, group, extra | A label on a person; a set of people; a typed custom field holding one value per person. | Segments, flags, custom fields |
| Relationship | A kind of relationship between a participant and the staff who look after them. | A care team role, a key worker |
| Task | A work item for staff about participants, never seen by the participant. | A follow-up, a case action |
| Configuration | A per-tenant setting, keyed by a dotted code. | A setting, a feature flag |
Access and integration
| Our term | What it is | You might call it |
|---|---|---|
| Session | A signed-in person's, or an API key's, standing with the API, in one tenant at a time. | A login session, a token |
| Role | A named set of permissions, the same in every tenant: participant, coach, admin, sales, platform admin, or API client for an API key. | A user type, an access level |
| Permission | One thing a role may do, by code. | A privilege, a scope |
| API key | A credential for an outside system, signing in as its own service account. | An integration token, a machine credential |
| Webhook | A signed request the platform sends to your endpoint when something happens. | A callback, an event notification |
| MCP | The platform's server for AI assistants, reaching content under the person's own permissions. | An AI connector |
| Report | An analytics site embedded in the portal, per tenant and role. | A dashboard |