The rip-and-replace fear
When a specialty programme looks at new clinical software, the first worry is usually the EMR. Teams have invested years in their electronic medical record. It holds the system of record, the clinical documentation, and the workflows clinicians already know. Anything that looks like it might replace the EMR, or fight it for primacy, is a hard sell and a large risk.
That fear is reasonable, and it is also avoidable. The right model is augmentation, not replacement.
Augmentation, not replacement
Tessera works alongside your EMR. It does not replace it. If your EMR's care planning works for your programme, keep using it. Tessera is built to do what EMRs were never designed to do: run specialty registries, manage specialty care pathways, and extend a care team beyond the clinic to the family members, home nurses, teachers, and community specialists who are part of a patient's real care.
The EMR stays the system of record for general care. Tessera adds the specialty depth and the analytics-ready data contract on top, without asking you to migrate or rip anything out.
How it connects: FHIR R4 and SMART on FHIR
The connection is standards-based, which is what keeps it an augmentation rather than a custom integration project. Tessera is FHIR R4 native and supports SMART on FHIR, so it works with any FHIR-based EMR or EHR rather than a single vendor's stack. Patient identity is reconciled through provincial client registry integration, matching MRN and PHN so the same patient is the same patient across systems.
Because the integration uses the same interoperability standards Canadian health systems are already moving toward, the specialty platform reads from and writes to the same clinical reality the EMR sees, without becoming a parallel island of data.
The work EMRs were not designed for
An EMR is built to run general care for a whole hospital or practice. A specialty programme needs something different: a longitudinal registry of a defined cohort, care pathways specific to that condition or procedure, variance detection between the two, and a data contract that makes the results analytics-ready. These are not gaps in any particular EMR; they are simply outside what a general-purpose record was meant to do.
Specialty care also reaches past the clinic. Tessera supports care-team-wide data sharing that can include family members, teachers, home nurses, and community specialists alongside the clinical team, where that is appropriate for the programme. That is a natural fit for paediatric chronic disease and complex care, and it is not something a hospital EMR is structured to provide.
What stays, what is added
The division of labour is clean. The EMR keeps doing what it does well: encounters, orders, general documentation, the day-to-day clinical record. Tessera adds the specialty-programme layer the EMR was never meant to carry, with the governed data contract underneath so the data is analytics-ready from the point of capture.
See how the pieces fit together on the platform, or read the integration view written for IT and informatics leaders.