What makes DoctoPoint regulator-ready.
24 modules. Each implements a named obligation under the CCOA Standards of Practice, the Health Information Act or an Alberta directive — and each ends in an evidence export.
- Patient
- PT-04182
- Range
- 2024-01-01 → 2026-09-17
- Users
- All (7)
- Rows
- 1,284
Per patient, per user, per time range — with no spreadsheet in the middle.
The complete scope.
24 modules in seven groups, in the order a clinic needs them. Each entry links to its section below.
Foundation
3 modulesThe substrate every other module assumes: the record is available, every action is attributed, and consent is part of the note.
Privacy core
4 modulesEncryption, retention, the Information Manager Agreement, a live Privacy Impact Assessment and the full HIA administration programme — the artefacts a custodian has to produce.
Clinical safety
5 modulesWhat a practitioner may record, refer, publish or cause to occur — bounded at save time, with the evidence the CCOA expects.
- 014Scope of practice & restricted activitiesCCOA SP 4.1 · CCOA SP 4.4–4.9
- 015Clinical flag systemCCOA Psychosocial Directive · CCOA SP 3.2
- 016Professional boundariesCCOA SP 6.0–6.9 · HPA s. 45
- 018Disclosure of harmCCOA SP 3.3 · CCOA SP 5.1
- 022FGM prohibition & mandatory reportingCCOA SP 12.0 · HPA s. 1.11(1)
Communication & quality
4 modulesCharts another clinician can read, imaging that lands on the record, health information that leaves only through a secured channel, and published copy that passes the Directive.
Practice operations
5 modulesFees, contracts and prepayments; policies, equipment and support staff; fitness to practice, continuing competence and concluding care — the recurring obligations of running a clinic.
AI governance
1 moduleAn embedded assistant that drafts but never authors: off until the custodian enables it, scoped to what a human grants for one session, and recorded turn by turn in a tamper-evident ledger.
Specialist tracks & house rules
2 modulesAn opt-in research module for the rare clinic that conducts studies — and the rules this website itself is written under.
Foundation
The substrate every other module assumes: the record is available, every action is attributed, and consent is part of the note.
Available when the patient is in the room.
A published availability objective for chart load, measured in production. When a dependency fails, the record degrades to a labelled read-only mode instead of an opaque error.
- Read-only fallback serving the last-synced chart
- Offline note capture, reconciled on reconnect — conflicts shown, never overwritten
- Public status page with incident history; every error screen carries a support reference
- Monthly automated chaos test proves the fallback path end to end
Every action has a name on it.
Unique accounts, custodian-configurable roles, a second factor on every new device, and an append-only audit log that records views, edits, exports, denials — and every attempt to tamper with it.
- Roles and permissions configurable per clinic; changes logged with before and after
- Idle sessions end automatically; accounts lock after repeated failed logins
- Electronic signatures bound to signer identity, timestamp and content hash
- Audit export per patient, per user, per time range — ready for a regulator
Consent lives inside the note.
A SOAP entry cannot be finalised without signposting and consent to touch for that visit. Scoped declines, substitute decision-makers and the CCPA informed-consent version in force are part of the same record.
- Single confirmation step in the finalise flow; re-affirmation only for returning patients
- Scoped decline recorded together with the alternative offered
- Initial informed consent locked to the CCPA document version signed
- Re-consent flagged for every patient when a new document version is published
Privacy core
Encryption, retention, the Information Manager Agreement, a live Privacy Impact Assessment and the full HIA administration programme — the artefacts a custodian has to produce.
Encrypted, backed up, restorable, disposed.
Encryption in transit and at rest with keys held separately, verified backups, a quarterly restore test on record, integrity alerts, and a disposal attestation for every medium that ever held health information.
- Backups checksummed at write time and again at restore
- Quarterly recovery test logged with operator, recovery time and recovery point
- Integrity alert on any change made outside the application path
- Data residency pinned to a named region per clinic, producible as an attestation
Ten years, enforced at the record.
Every chart carries a retention floor computed from SP 5.4, and deletion before the floor is blocked. The Information Manager Agreement is signed before the first record and verified against every Appendix 4 component.
- Floor: 10 years from last entry, or 10 years past age 18 for a minor
- IMA versioned; material changes require explicit re-acknowledgement
- Named successor custodian with an executed agreement on file
- Named-patient inventory of off-site copies; destruction attestation at end of retention
A PIA that is never stale.
The workbook renders from a live fact graph: what the platform warrants, what the clinic configured, what the custodian attested. When a fact drifts, a finding opens and the features that depend on it fail closed.
- Regulatory authority bound on day one; no health information is processed before it
- Data-handling table built from the registered data-flow contract of every module
- Annual and event-triggered reviews; a sub-processor change flips the workbook to review
- OIPC submission package with a signed, byte-stable render and acknowledgement tracking
The whole programme, not just the PIA.
A designated HIA officer of record, public policies, tiered training, a periodic status-quo assessment, an access and correction request register with statutory deadlines, and a privacy compliance plan.
- §62 designation required before any health information is ingested
- Request files with due date, fee reference, severing rationale and recipient authentication
- Status-quo assessment across every Appendix 3 topic; gaps queued as owned actions
- One-operation export for a review by the Information and Privacy Commissioner
Clinical safety
What a practitioner may record, refer, publish or cause to occur — bounded at save time, with the evidence the CCOA expects.
Out-of-scope entries do not save.
A configuration-driven register of every restricted activity and directive: what is authorised, what needs Registrar authorisation and evidence, what is prohibited. Charts, treatment plans and invoice lines are checked at save time.
- Y-strap: manipulation blocked; traction only with training evidence attached
- CBCT routed to an external referral; the equipment itself registrable under SP 8.4
- Vaccine questions and psychosocial disclosures routed to templated referrals
- Internal coccygeal adjustment blocked until the CCOA consent form is on file
Red, orange, yellow — before the first touch.
Intake is screened against the CCOA indicator sets. Flags persist across every encounter until closed with evidence; red and orange flags block signing without a documented referral or a documented decline.
- Flags raised at intake, from inside a SOAP note, or from an inbound secure message
- Referral target, transmission and the returned report filed against the flag
- Chaperone consideration prompted for orange and yellow flags
- Clinical detail visible to clinical roles only; reception sees the operational impact
Boundaries recorded, not remembered.
A boundary checkpoint on any sensitive-area contact, structured responses to boundary indicators, registers for dual relationships, gifts and social media, and a duty-to-report workflow to the Complaints Director.
- An encounter with sensitive-area contact cannot be signed without the checkpoint
- SP 6.2 current-patient rule computed; former-patient attestation dated and signed
- Guards for off-hours bookings, non-clinical settings and no-charge services
- Criminal Code self-disclosure routed with the sanction implication shown
Harm is disclosed, and the record shows how.
A structured record of the harm, the conversation with the patient, the remedial care or referral, and the step taken to prevent recurrence — invokable from the chart, a critical event or a secure message.
- Harm category, date of awareness and the practitioner’s own account
- Deferral with rationale and a follow-up reminder when the patient is not yet ready
- Closure requires a prevention-of-recurrence link or a documented decision
- Tenant-level pattern alert when harms cluster around a modality or procedure
Impossible to chart. Mandatory to report.
Female genital mutilation cannot be recorded as a procedure in any clinic, under any configuration. Reasonable grounds about another regulated member open the HPA s. 127.2 report; a patient’s disclosure opens trauma-informed care instead.
- Categorical block citing HPA s. 1.11(1) and Criminal Code s. 268(3)
- Report captures the grounds, the named member and college; patient identity severed by default
- A patient’s disclosure raises an orange flag and the boundary checkpoint
- Reminder of separate criminal-reporting obligations, without claiming legal authority
Communication & quality
Charts another clinician can read, imaging that lands on the record, health information that leaves only through a secured channel, and published copy that passes the Directive.
Legible to the next clinician.
A practitioner-configurable exam library, reproducible findings with side tested and standard coding, validated outcome measures, ICD-10-CA diagnosis coding and a no-shorthand mode.
- Add an exam without engineering; labels render exactly as defined at entry time
- NDI, Oswestry and NPRS scored on the chart with progress over time
- Deprecated diagnosis codes flagged with a guided remap
- AB-2 / AB-4 instantiate fresh per visit; any copied field is visibly marked
Requisition and report, on the chart.
Every imaging requisition is attached at issuance with its metadata. Reports are filed against the requisition, unsolicited reports are triaged, and clinically significant findings queue a follow-up.
- Inbound by upload, email-to-attachment or a documented integration endpoint
- Patient identity checked before any report attaches
- Non-blocking warning when a diagnosis implies imaging and none is attached
- Imaging artefacts inherit the chart’s retention floor
No health information over text messages.
Health information leaves the chart only through a secured channel, and only once the PIA allows it. Every disclosure to a third party needs a structured authorisation and lands in the patient’s disclosure log.
- Cleartext email blocked by default; an explicit risk acknowledgement is recorded if a clinic enables it
- No path exists to SMS, messenger apps or social media
- Authorisation captures effective and expiry dates, purpose, recipient, acknowledgement, revocability and consent
- Disclosure history producible per patient on request
Published copy is scanned before it is public.
Website text, social posts, brochures, recall messages and testimonials composed in the platform are checked against the Professional Communication Directive at publish time — and re-checked when the lists change.
- Non-MSK efficacy claims, psychosocial and vaccine content, unauthorised “specialist” titles blocked
- Testimonial workflow with a no-pressure request, consent attestation and the unedited original
- An evidence record is required for every quantitative or attestational claim
- CCOA review response with cross-surface takedown and attestation
Practice operations
Fees, contracts and prepayments; policies, equipment and support staff; fitness to practice, continuing competence and concluding care — the recurring obligations of running a clinic.
Compliance is the default. Fraud is the friction.
Dated fee schedules with legislated fees included, a provider-contract register, prepayment caps enforced, a financial-agreement composer with every mandatory clause, and an invoice engine bound to signed encounters.
- Prepayment capped at $1,000 and a 10 % discount; unused balance refunded within 7 business days, no fee
- An invoice line must match a signed encounter, its date, its patient, the schedule rate and a single payer
- The agreement composer blocks case fees, unlimited care and referral incentives
- Contract register with sunset alerts and a one-shot Practice Visit export
IPC, critical events, equipment, support staff.
Jurisdiction-aligned templates adopted per clinic, with training logs and audits, a critical event log, an equipment register with maintenance reminders, and a support-staff register that enforces the SP 4.2 blocklist.
- Training events with attendee, content version and signed acknowledgement
- A critical event closes only when every corrective action has closed
- Equipment quarantined on recall and recommissioned after vendor clearance
- Support staff can neither be assigned nor record a blocklist activity
Cease or limit, enforced in the schedule.
Self- and colleague disclosure of incapacity, a cease-or-limit state that scheduling and charting honour, and a reinstatement path — with medical detail visible only to the practitioner and the disclosure roles.
- Disclosure package routed to the Complaints Director through the secure channel
- Bookings refused in cease state; restricted activities blocked in limit state
- Transfer-of-care planning fires for every active patient
- Reinstatement with attestations, supporting letters and any CCOA conditions
Credits, evidence, eligibility.
A CPD log with verified attendance, a renewal-eligibility check against the Council threshold, practice-visit preparation drawing on every module’s evidence, and Committee directives tracked to deadline.
- Entries without evidence queue as pending and are reminded
- Renewal-evidence package produced for CCOA submission
- Practice-visit pack assembled from the other modules’ exports
- Committee directives become tracked corrective tasks with closure evidence
Thirty days, in writing, with the refund.
A discharge workflow that screens the reason against prohibited grounds, composes the notice with every SP 11.0 clause, sends it through the secure channel and refunds unrendered fees immediately.
- Anti-discrimination check against the Alberta and Canadian Human Rights Acts
- Abridged-notice path with the safety evidence it requires
- Transfer process for the record, and a custodianship transition on clinic closure
- Registrar-guidance request whenever a step cannot be met
AI governance
An embedded assistant that drafts but never authors: off until the custodian enables it, scoped to what a human grants for one session, and recorded turn by turn in a tamper-evident ledger.
The assistant is locked. A human confirms.
The embedded assistant is off until the custodian enables it under a current IMA and a recorded sub-processor acknowledgement. It sees no patient unless a human grants access for that session, it proposes actions it cannot execute, and every turn lands in a tamper-evident ledger.
- Zero-access default: per-patient, per-session, per-scope grants that expire and die with the session
- Allow-listed actions only — draft a SOAP note, open an invoice, create a patient — proposed as a card, executed on confirmation under the user’s own permissions and every existing gate
- AI-drafted notes stay unsigned with provenance; signing requires a review attestation bound into the signature
- Append-only AI ledger with prompt, response, hashes, provider and model, mirrored into the audit log and the patient’s disclosure history
Specialist tracks & house rules
An opt-in research module for the rare clinic that conducts studies — and the rules this website itself is written under.
No enrolment before ethics approval.
An opt-in module: research proposal and ERB approval on file, the Registrar notified through the secure channel, per-patient research consent with disclosure scope, and research data segregated by role.
- Only Council-recognised Alberta ethics boards are accepted
- Every research disclosure appears in the patient’s HIA §41 history
- Lifecycle states with evidence and patient notification on early termination
- Retention per SP 5.4, or longer where the ERB requires it
The rules this page is written under.
Every claim on this website is present tense and producible on demand. No fabricated certifications, no invented customers, no absence labels, no implementation detail — checked before every release.
- A numeric or attestational claim needs a dated evidence record before it is published
- A customer name appears only with that clinic’s written permission on file
- Capabilities are described by what they do, never by what is missing
- The clause references on these pages come from the public standards index
- Internal — every customer-facing surface
The public standards index.
85 clauses, each mapped to the module that operationalises it. Read the standard, then see what was built against it.
Health Professions Act (Alberta)
10 clausesSource: Health Professions Act, RSA 2000, c H-7 — Alberta King’s Printer ↗- HPA s. 3(1)Health professions purpose / public protection017 · Practitioner communications
- HPA s. 45Specified Criminal Code offences016 · Professional boundaries
- HPA s. 102Conduct deserving of sanction017 · Practitioner communications
- HPA s. 118Reporting of conditions affecting safe practice019 · Fitness to practice
- HPA s. 127.2Mandatory reporting of FGM by regulated members022 · FGM prohibition & mandatory reporting
- HPA s. 1(1)(m.1)Definition of female genital mutilation022 · FGM prohibition & mandatory reporting
- HPA s. 1(1)(nn.1–nn.3)Sexual abuse / misconduct / sexual nature definitions016 · Professional boundaries
- HPA s. 1.11(1)Prohibition: a regulated member shall not procure or perform FGM022 · FGM prohibition & mandatory reporting
- HPA 51(3)(f)Equipment maintenance policy and records011 · Practice policy templates
- HPA Schedule 7.1 §2(1)(p)Psychosocial intervention as a restricted activity014 · Scope of practice & restricted activities015 · Clinical flag system
This index is descriptive, not legal advice. Verify the current versions of the Standards of Practice, the HIA and the CCPA document at theccoa.ca, oipc.ab.ca and ccpa-acpc.ca.