Sectors · Healthcare
AI for health systems and providers.
Clinical documentation, records search and administrative automation for health authorities and hospitals, built to health-information law.
The constraints
Health data is the most sensitive data a person has. Its use is governed by provincial health-information acts, and a tool that touches clinical care faces a higher bar again.
Health-information law
PHIPA in Ontario and its equivalents set strict rules on collection, use and disclosure.
Clinical safety
Software that informs diagnosis or treatment may be regulated as a medical device.
Clinician time
A tool that adds clicks will not be used, however good its model.
Interoperability
Electronic medical record systems and standards such as HL7 FHIR that new tools must work with.
What we build
Where AI earns its place. Tasks with a measurable cost today, where a person stays accountable for the outcome.
Clinical documentation
Drafting notes and discharge summaries from the record for a clinician to review and sign.
Referral and intake triage
Summarising referrals and checking completeness before they reach a scheduler.
Policy and protocol search
Answers from the organisation’s own protocols, cited to the version in force.
Administrative automation
Coding support, scheduling correspondence and claims preparation.
Frameworks we design to
The rules your auditors use. Each one shapes the design from the first workshop, not a checklist at the end.
- PHIPA and provincial health acts
- Personal health information handled to the act that governs the custodian.
- Health Canada SaMD guidance
- Scoping to determine whether a tool is a medical device before it is built.
- HL7 FHIR
- Integration with clinical systems through standard interfaces.
- Privacy Impact Assessments
- Data flows and safeguards documented for the custodian’s PIA.
Talk to the team that builds it.
Briefings are technical, run by the engineers who would deliver the work, and held under NDA where needed.