Integrations
Built to integrate with the systems you already use.
Occupational health sits between employers, clinicians and business systems. Occentra is designed to coordinate that work without becoming another system of record for everything around it.
Fit the landscape
Work alongside identity, HR, calendars and documents already in use
Clear ownership
Each system keeps responsibility for what it already manages well
Occupational health focus
Occentra owns referrals, cases, assessments and clinical workflows
Open interfaces
APIs and events make exchange deliberate and maintainable
Operational landscape
Where Occentra sits in the flow of information.
Integration is about how information moves through the organisation. Identity and HR systems establish people and access. Occentra runs occupational health workflows. Documents, reporting and business systems receive what they need downstream.
Information flow
Architecture
Occentra in the wider technology stack.
Identity sits above the platform. Occupational health work happens inside Occentra. HR systems, document platforms and operational reporting connect around it. The diagram is a model of responsibility, not a claim that every connector is already shipped.
Technology stack
Occentra
Integration philosophy
Reduce duplication. Do not replace what already works.
Occentra is built to coordinate occupational health workflows and exchange information with surrounding systems. It is not intended to become the organisation's HR system, identity provider or document archive.
- HR systems remain the source of employee information.
- Identity providers remain responsible for authentication.
- Document platforms continue to manage organisational documents where that is appropriate.
- Occentra focuses on occupational health workflows and coordinates information between systems.
System categories
The kinds of systems Occentra is designed to work with.
Grouped by role in the organisation, not as a product catalogue. Named platforms appear only where they are a clear design target or industry-standard reference.
Identity
- Microsoft Entra ID
- Single sign-on
HR systems
- Employee records
- Organisation structures
Calendars
- Microsoft 365
- Google Workspace
Documents
- SharePoint
- Document management systems
Communications
- SMS
- Notifications
APIs
- REST APIs
- Webhooks
Capability status
What is available, designed for, or planned.
Trust depends on clear boundaries. The lists below separate platform foundations from design targets and later work.
Available today
- Role-based access inside Occentra
- REST-oriented API architecture
- Webhook and event-driven integration patterns
- Document and attachment handling within cases
- Structured import and export for records and reports
Designed for
- Microsoft Entra ID and organisational single sign-on
- Microsoft 365 calendar and scheduling alignment
- Exchange with HR and employer systems
- Connection to document platforms such as SharePoint
- Notifications through email and related channels
Planned
- Deeper Microsoft 365 and SharePoint workflows
- Google Workspace calendar support
- SMS and richer notification channels
- Broader payroll and business-system connectors
- MCP-oriented tool integrations
APIs and automation
Built for integration from the outset.
Occentra treats external systems as expected participants. Interfaces are resource-oriented and predictable so other platforms can request data, receive events and automate work without brittle, one-off coupling.
- REST APIs for structured request and response workflows
- Webhooks to notify connected systems when events occur
- Predictable, resource-oriented interfaces that stay stable as the product evolves
- Automation paths for routine operational hand-offs
- Secure authentication for system-to-system access
- Clear boundaries so integrations with business systems stay maintainable
Integration architecture
Explicit APIs at the boundary, not direct database access
Built for extension
Add integrations without bespoke forks.
Occentra is built so new connections can be added without rewriting the core product. Integrations plug in through clear interfaces, which makes them easier to maintain as your other systems change.
- Clinical, operational and integration work stay separated where it matters
- External systems connect through documented APIs, not one-off exceptions
- Configuration is preferred over custom code that is hard to keep current
- New connectors can build on the same interfaces already in place
- The platform is designed to stay upgradeable over time
Future-facing architecture
Ready for assisted workflows as well as people.
A modern integration surface is useful for more than human operators. The same APIs and events that connect business systems can support assisted and machine-driven steps beside the usual interfaces. That is a consequence of clear interfaces, not a separate product story.
- Traditional user interfaces remain the primary way teams work today
- APIs and events provide a path for assisted operational steps later
- Accountability and role boundaries stay part of the design
Planned direction
Where integration work continues.
These items are direction, not available functionality today.
Planned, not currently available
Microsoft services
Further work with Microsoft identity, calendars, collaboration and document platforms.
AI-assisted workflows
Practical assistance where automation helps, with human oversight kept clear.
MCP integrations
Model Context Protocol as a controlled way to connect Occentra with surrounding tools.
Document ingestion
Bring documents into structured case context more effectively, with oversight of what becomes operational data.
Need to integrate Occentra with an existing system?
Talk to us about your workflow.