Canada Health Infoway’s Connected Care Conformance Platform tests whether digital health solutions meet specified requirements for exchanging information. That is a narrower question than whether a particular patient’s complete record will reach the right clinician during everyday care.
The distinction matters for teams reading an interoperability claim. A useful test result identifies what was tested, against which specification and version, and under what conditions. “Connected” on its own leaves those details open. Platform purpose and capabilities
A common place to test the exchange
Infoway launched the platform in November 2025 as a shared environment for testing and validating health-data interoperability standards. Its current description includes automated testing, reporting, validators and simulators, with support for specification families such as PS-CA, CA:eReC, HALO and CA:Core+. Launch announcement, Current platform description
Those tools have different roles. Validation checks the requirements covered by a specification or test case. A simulator provides a counterpart for an exchange without requiring the final live partner. Reporting makes the observed result available for inspection. None should be read as an unlimited test of everything a system might do.
The platform description also labels some capabilities as future developments. A feature mentioned in a roadmap needs separate confirmation before it becomes part of a purchasing requirement or a claim about what is available now.
Four questions behind a conformance result
The following is a way to read technical evidence, rather than a certification of any product or deployment.
| Question | Why the answer matters |
|---|---|
| Which specification and version? | A result needs an identifiable set of requirements. |
| Which interactions and test cases? | Passing one exchange does not establish coverage of every workflow. |
| What was simulated, and what was tested with the actual partner? | A controlled counterpart and a live integration supply different evidence. |
| What happens after a software or interface change? | The original result describes the tested configuration. |
For example, a successful test of one message cannot answer whether an organisation has supplied every relevant historical record. That is a difference in the question being asked, rather than a failure of conformance testing. The test may be useful and correctly passed while the broader service remains incomplete.
Permission to exchange is a separate part of the system
Infoway’s Connected Care Trust Framework describes shared rules, governance, legal agreements and technical foundations for exchanging information. It is presented as a federated approach that respects provincial, territorial and Indigenous authority. Infoway explicitly says the framework does not replace existing systems or centralise their data. Trust Framework definition
This supplies an important companion to the technical story. A system may be able to form and receive a message, while the participating organisations still need the appropriate arrangements for exchanging it. Conversely, an agreement to share information does not prove that an interface has been implemented correctly.
These Canadian arrangements also have their own scope. They should not be treated as the Canadian names for England’s different shared-record services, or as a substitute for another jurisdiction’s assurance process.
Ask for the result that matches the claim
For a supplier’s statement that a product conforms to a named standard, the relevant evidence is the bounded test result. For a statement that information reaches a working care pathway, the relevant evidence includes the actual exchange and its use in that setting.
Infoway’s documents describe the national testing and trust infrastructure. They do not establish the completeness, lawful access or clinical usefulness of any named local installation. Keeping those claims separate makes a conformance result easier to use without asking it to prove more than it tested.