Enterprise-Ready Architecture
Built by healthcare technologists who understand the unique demands of clinical systems. No shortcuts on security, compliance, or integration.
Technical Specifications
A modern architecture designed for healthcare interoperability and enterprise deployment.
FHIR R4 Native
Built on HL7 FHIR R4 from the ground up. Aligned with Canada Health Infoway's interoperability roadmap and ready for CA Core+ (2027).
SMART on FHIR
Launches directly from your EHR context with single sign-on. OAuth2/PKCE authentication, so sign-in does not disrupt the clinical workflow.
API-First Architecture
RESTful APIs for custom integrations. Webhook support for event-driven workflows. Full OpenAPI documentation.
Multi-Tenant SaaS
Enterprise-grade tenant isolation with shared infrastructure efficiency. Each organisation's data is completely segregated.
Azure Canada Hosted
All infrastructure in Azure Canada Central (Toronto) and Canada East (Quebec City). No data leaves Canadian borders.
SOC 2 Type II
Certification in progress. Security controls validated against trust services criteria for healthcare environments.
RESTful APIs
Full FHIR R4 endpoints plus Tessera-specific APIs for pathway management, variance detection, registry operations, and genomic surveillance.
- OpenAPI 3.0 specification available
- Webhook subscriptions for real-time events
- OAuth2 + SMART on FHIR authentication
Integration at a glance
Sources in
Tessera
FHIR R4 core
Downstream out
Tessera ingests from upstream systems and routes downstream where the data steward directs. Full API documentation available on request.
EMR/EHR Compatibility
Tessera works alongside your existing EMR/EHR, not against it. FHIR R4 integration means we can connect with any FHIR-enabled system.
Integration breadth
Tessera is built to ingest from upstream clinical and administrative systems and to route downstream to repositories, registries, and partner systems where the data steward directs. The TMS team has built and operated integrations across a wide range of source and destination systems at provincial scale.
Data contract architecture
Tessera enforces a platform-level data contract rather than leaving schema and value-list authority to each project. For architects, the design choices that matter are the ones that hold analytics stable as the platform evolves.
- Stable definitionIds and linkIds: question text can change without breaking the variable identifier.
- Schema deprecation discipline: retired questions are deprecated, never deleted, so historical data stays valid and queryable.
- Coded values from authoritative sources, integrated live where an authority maintains the codes.
- Validation enforced at the point of capture, not at export time.
- A point-in-time query model: observations are date-stamped at capture, so reproducible point-in-time queries are the default.
Local AI on a governed substrate
Tessera is designed to support local AI model integration on a governed substrate. The platform provides the governed, analytics-ready data that safe clinical AI requires; partner programmes and clinical AI vendors bring the models. Architectural detail is held for technical sales conversations; if this matters to your evaluation, reach out and we will walk through it.
Ready for a Technical Deep Dive?
Our technical team can walk you through architecture, security, and integration details specific to your environment.