Align eCare
Align eCare / Align eCare

Align eCare

Privacy, interoperability and physician authority

Align eCare’s trust approach combines defined purposes for information use, professional approval, source-linked preparation and explicit deployment boundaries. These are product commitments and design requirements. Hosting, retention, access controls, subprocessors and integrations must be evidenced before a clinical pilot handles health information. This site does not claim a compliance certification or a live clinical service.

In development
Request a pilot How it works

Advisor, Technology and Security

Meaghan Law, Advisor, Technology and Security at Align eCare, head-and-shoulders portrait in a black blazer
Meaghan Law, Advisor, Technology and Security

Meaghan Law

Advisor, Technology and Security

Meaghan Law brings a background in IT, security systems, AI, programming, and software development. As a technology and security advisor to Align eCare, she helps review its technical plans, privacy safeguards, and security approach. Her review covers Align eCare's core commitments: patient data stays in Canada under Canadian data sovereignty, patient data is never used to train AI models, and all handling meets PIPEDA and New Brunswick's PHIPAA. Meaghan is the daughter of Align eCare founder Karolyn Law, and a proud mom of two beautiful children.

meaghan@alignecare.ca

No patient or clinic information for AI training

Align eCare’s policy commitment is that patient and clinic information will never be used to train AI models. This must be enforced through vendor contracts, service settings, access restrictions and operational verification before clinical processing. A no-training commitment is separate from retention and is not a claim of zero data retention.

Canadian data sovereignty

Canadian data sovereignty is a design requirement. Deployment review must establish where primary data, backups, logs and processing reside, who can access them, and which laws and vendors govern that access. A Canadian storage region alone does not verify Canadian-only processing.

PIPEDA alignment and provincial requirements

Deployment review must identify the applicable law, including New Brunswick’s Personal Health Information Privacy and Access Act (PHIPAA), Ontario’s Personal Health Information Protection Act (PHIPA), and Nova Scotia’s Personal Health Information Act (PHIA), as relevant to the clinic and information flow. These names do not imply certification.

OPC: provincial health information laws

PIPEDA’s fair information principles provide a foundation for accountability, purpose limitation, consent, safeguards and access. The laws and roles relevant to each clinic must be assessed for that deployment. Align eCare’s privacy program and technical implementation remain to be validated.

Source: Office of the Privacy Commissioner: PIPEDA fair information principles.

FHIR and integration status

HL7 FHIR is a standard for exchanging healthcare information electronically. Align eCare’s intended interoperability approach is FHIR-informed. Each connection still requires confirmation of version, supported resources, permissions, data mapping and tests. No EMR, pharmacy, portal or device integration is described as live.

Source: HL7: FHIR overview.

Clinician approval and evidence

The design presents the exact item, supporting information, unresolved uncertainty, destination and next action for review. A provenance record should identify the source, version, reviewer, approval and routing outcome. Cryptographic controls and tamper-evidence require implementation evidence; they are not asserted as deployed.

Read the privacy white paper

Privacy and clinical data governance: commitments, controls and deployment gates