Skip to main content

Glossary

A quick reference for the terms used throughout these docs. The authoritative, maintained glossary lives in the Cardinal documentation — Cockpit Glossary.

TermWhat it means
EnvironmentYour private space, bound to your email, created on registration; holds all your projects. In the SDK, a top-level Group. See Environment.
ProjectOne application/solution and its database (formerly "Solution"). In the SDK, an app Group. See Project.
TenantAn isolated database inside a project; multi-tenant projects hold several. In the SDK, a database Group. See Tenant.
UserThe login/account entity; linked to a data owner via healthcarePartyId / patientId / deviceId. See User.
Data ownerAn entity that holds encryption keys and owns encrypted data — an HCP, patient, device, or organization.
HCPA healthcare professional. In the SDK, a HealthcareParty. See HCP · Patient · Device.
OrganizationA company/clinic user (also a HealthcareParty); usually the parent organization holding the data-sharing key. See Organization.
Patient / DeviceEnd-user data owners (Patient / Device).
AdministratorSomeone who manages the backend in Cockpit, with Environment or Project access. See Administrators & Access Levels.
Environment Access / Project AccessThe two administrator access levels. See Administrators & Access Levels.
Authentication processThe email/SMS one-time-code flow your end users register and log in with. See Authentication Processes.
External ServicesThe email/SMS/captcha gateways (environment-wide). See External Services.
Spec IDThe identifier for your External Services configuration; passed to the SDK as externalServicesSpecId.
Project IDYour project's reverse-domain Application ID (set by you); passed to the SDK as projectId.
Operation tokenA one-time, single-use token authorising a project ownership transfer. See Transfer ownership.
Custom propertyTyped key–value metadata on a Group or user. See Custom Properties.
Role / PermissionA role is a named bundle of permissions assigned to users. See Roles & Permissions.
Auto-delegationA standing rule to auto-share newly created data with chosen data owners. See Auto-delegation.
Private key / Recovery keyThe encryption key a data owner needs, and its optional backup. See Recovery & Private Keys.

Where to go next​

Cardinal SDK reference: The Cardinal data model — definitions of the underlying SDK entities.