Galeno · Onboarding plan
Your organisation, live on Galeno in six steps.
Galeno is a common health-data platform. Your systems connect to it through standard interfaces and custom adapters, so Galeno is never redesigned for your organisation.
Section 1
What the onboarding process looks like
| Step | Title | What happens | Owner | You get |
|---|---|---|---|---|
| 01 | Create the workspace | The organisation establishes its Galeno environment and appoints an owner or administrator. | Together | Your workspace and its owner |
| 02 | Inventory your software | Identify which systems need to connect: EHR, lab systems, imaging, pharmacy, devices, databases or custom applications. | Your admin | The list of systems to connect |
| 03 | Choose the integration model | Decide whether each connection should be private, shared, or centralized. | Together | A model for every connection |
| 04 | Authenticate and configure | Authorise access, select data scope, configure credentials and choose the users or groups who can use the connection. | Your admin | Authorised, scoped connections |
| 05 | Test and validate | Check retrieval quality, access restrictions and, if write actions are enabled, whether the intended actions work safely. | Together | Signed-off test results |
| 06 | Deploy and maintain | Make integrations available, monitor failures and permissions, and maintain the connections as your software changes. | Galeno | Live connections, monitored |
Section 2
The integration models
Step 3 in detail. Every connection in your workspace uses one of these four.
| Model | Mirrors access from the source? | Set up by | Access managed by | Typical use |
|---|---|---|---|---|
| Private | Yes | Each user, for their own account | The user's own permissions | A patient's Apple Health or Health Connect |
| Centralized | Yes | Workspace owner | The source system | The hospital EHR or lab system |
| Shared | No | Workspace owner | Galeno, set by your admin | A department's imaging reports |
| Custom connector | Set by your server | Workspace owner | Your server and Galeno | An internal or proprietary application |
These are not merely different login methods. They represent different decisions about who configures the connection, whose credentials are used, and how access is controlled.
Section 3
When your software has no Galeno integration
Your systems reach Galeno through a custom connector. You or your software provider supply the endpoint; Galeno is configured to use it.
- GalenoUnderstands the user's request
- Custom connectorDefines the available tools, inputs and outputs
- Your serverAuthentication, business logic and API calls
- Your existing softwareEHR, lab system, internal application or other system
The setup
- An administrator adds a custom integration in workspace settings.
- The administrator specifies the connection details and the tools to expose.
- The administrator chooses which users or groups can access the integration.
- Users connect and authenticate if required.
- Galeno can use the configured tools, subject to the permissions granted.
Section 4
Built into the core design
Part of the platform itself, never an optional integration setting.
Patient consentThe patient decides what each clinic sees.
Organisation isolationEach workspace is kept apart.
Role-based accessOwners, admins, doctors, patients.
Audit trailsEvery record view is recorded.
Data provenanceEvery record shows its source.
Section 5
Who uses Galeno
The same platform serves everyone around the patient.