API and interoperability
A platform that fits into your institutional environment.
Nagano offers a data REST API and several integration mechanisms to make it easier to link with your systems and your institution's technology environment.
- Data REST API
- Institutional authentication
- Exchanges between Nagano installations
Authentication
Authentication suited to your institution.
Nagano can use LDAP / Active Directory, OAuth2 — including Microsoft Entra ID depending on the configuration — or its own authentication mechanism.
-
LDAP / Active Directory
Users sign in through the institutional directory.
-
OAuth2 / Entra ID
Authentication through a configured provider, including Microsoft Entra ID depending on the deployment.
-
Nagano authentication
Accounts and passwords managed directly in the platform.
Data API
A REST API to integrate Nagano with your systems.
Nagano's REST API lets authorized systems consult the platform's data in a secure and structured way.
Access can be tied to a user or to an organization and limited to the authorized resources.
-
Projects
Consult and search the accessible projects.
-
Forms
Access the forms associated with projects.
-
Files
Retrieve the available documents and files.
-
Invoices
Consult the accessible billing data.
- API keys
- user or organization
- Controlled access
- by resource
- JSON format
- versioned API
- Documentation
- OpenAPI specification
Inter-Nagano
One researcher experience across multiple Nagano installations.
When a researcher works with several institutions using Nagano, their accounts can be linked across the relevant installations.
Their Workspace can then bring together projects and actions requiring attention in a single view, while preserving the originating institution and context.
- Actions to complete
- Upcoming projects
- Active projects
- Authorizations
Nagano installations exchange only the information required for supported workflows, including relevant projects, forms, statuses and documents.
Targeted integrations
Interfaces that match the institution's needs.
The API meets common data access needs. When an integration requires a particular behaviour or exchange with an institutional system, a targeted interface can also be set up depending on the context.
Integrations suited to the context
Each interface is developed or adapted according to the institution's needs and the systems involved.
-
Clinical or administrative systems
Integration with your existing systems, according to your needs.
-
Partners and collaborators
Data exchange with institutional or research partners.
-
Third-party services and tools
Links to other systems and services when required.