Built to the standard PHIPA requires of a custodian.

The layer in between

MedUnity is the trusted infrastructure between Canada’s health custodians and the patients whose records they hold. It is the Canadian-owned layer that lets a patient bring the fragments together and direct who sees what, for how long, and why.

Every access is refused unless the patient permitted it, and every access is recorded in a ledger nobody — including MedUnity — can alter.

Not a competing record. Not another silo. The rails, the consent, and the proof.

Who is accountable, and when

MedUnity is infrastructure for interoperability between health data custodians. It will not hold health information until there is a named, accountable custodian for it.

Custodianship is modelled as something that can be transferred, and it is recorded over time — so the question "who is accountable for this record, right now" always has an answer, and so does the same question asked about a date two years ago.

Whether MedUnity is itself classified as a custodian, an agent, or a network provider is an open legal question. We have scoped it and we are resolving it, and we built to the strictest reading in the meantime, because no answer to it makes that work wasted.

The commitments

• We do

  FHIR R4 native from the first commit

  With CA Core+ as the profile target. A target is not a conformance claim, and we do not write it as one.

• We do

  An open integration surface

  The SMART on FHIR model: a standard way for authorised applications to connect, so that a patient’s choice of software is not a vendor’s decision.

• We do

  No data blocking

  A record that can be sent can be sent. The practice Bill S-5 exists to prohibit is not one we make money from.

• We do

  Independent non-profit governance

  The consent and audit layer is intended to be governed by an independent non-profit, so that the rules about access are not owned by the company that benefits from access.

• We do

  Canadian ownership and Canadian residency

  Canadian-owned, and every byte of health information in Canadian regions, enforced by an organisation-level policy rather than by convention.

• We do

  WCAG 2.2 Level AA, checked on every build

  AODA makes it a legal obligation in Ontario. It is a blocking check in continuous integration, on this site and in the application.

What "built to the standard" means, precisely

It means the controls a health information custodian is required to have are the controls we built, and that we did not wait for a legal classification to tell us which ones applied.

It does not mean we have been certified, accredited, or determined to be compliant by anyone. Nobody has made that determination, and a company claiming it before it is made should be read carefully.

The specifics

This page states the position. The next one states what has been built, what has been proven, and what has not.