Workflow planning · English
Map a province-aware referral workflow in Canada
A referral document, an EMR task and a booking status are not interchangeable. Map how the practice receives, reviews and closes the loop on a referral before adding another tool.
Administrative workflow planning; urgency decisions and care recommendations remain with qualified clinicians.
Before you start
- Record the province, practice type, exact EMR and any referral or patient platform. PS Suite, Med Access and the Collaborative Health Record are separate products; a vendor-level label is insufficient.
- Confirm where referrals arrive and which system owns patient identity and referral status. Ocean’s published EMR relationships describe Ocean, not QuickIntell permissions.
- Ask the organisation’s privacy owner to assess the proposed data flow under the applicable framework. Define Québec French or bilingual input, documentation and support requirements independently.
Map the workflow and its human review
Use the following as an assessment structure, then adapt it with the people who own the real process. No step below asserts that QuickIntell currently performs it.
01Register receipt without inventing identity
Keep the received document attached to its intake item until authorised staff have resolved patient identity. Track the source channel and receipt status without multiplying parallel work queues.
- Expected output
- A traceable referral intake item.
- Human reviewer
- Referral administration team.
- Exception path
- Ambiguous patient matches, unreadable documents and duplicate referrals require staff resolution.
02Check administrative completeness
Define the practice’s checklist and show where each extracted detail came from. Preparation can identify a missing attachment; it must not invent a clinical history or decide urgency.
- Expected output
- A completeness checklist with original source references.
- Human reviewer
- Practice staff, with clinical questions escalated to a clinician.
- Exception path
- Missing or conflicting information remains open and prompts the approved clarification workflow.
03Hand off clinical prioritisation
Keep clinical review distinct from administrative preparation. Record the authorised clinician’s decision through the established process, then hand the approved next step to the booking team.
- Expected output
- A reviewed next action, not an AI urgency decision.
- Human reviewer
- Responsible clinician, then booking staff.
- Exception path
- An unreviewed referral cannot silently enter an urgency queue or trigger clinical instructions.
04Close the loop in the source of truth
Specify where acknowledgement, booking and return correspondence are recorded. Confirm whether the proposed transfer is manual export, read-only access or a permitted write for the installed product.
- Expected output
- Acknowledged status in the agreed record or referral platform.
- Human reviewer
- EMR administrator and referral owner.
- Exception path
- A failed handoff is a visible unresolved item; sending an email alone does not establish that the record was updated.
Agree acceptance checks before a pilot
Begin with synthetic or appropriately authorised test data. Name the assessor, method and target before testing; publish results only when approved and genuinely measured.
- Traceability
- Reviewers can locate the source for each prepared field without relying on generated text alone.
- Clinical boundary
- Synthetic urgency questions are routed to the designated clinician; no autonomous prioritisation is counted as an approved output.
- Language scope
- English and Québec French scenarios are reviewed separately when both are in scope.
- Operational result
- Measure completeness, duplicate handling, staff rework and time to acknowledged handoff against the existing process.
What this does not establish
- A universal Canadian EMR connector or province-wide certification.
- Provincial billing support inferred from referral handling.
- Legal compliance or Canadian-only processing inferred from an English or French website.
Primary sources and limits
These sources establish local product or infrastructure context. The workflow checklist is an editorial planning framework, not an official implementation specification, legal opinion or statement of QuickIntell compatibility. Verify the current requirements with the responsible organisation.
- TELUS Health: practitioner products
- OceanMD: EMR integrations
- Office of the Privacy Commissioner: provincial and territorial privacy laws
Content updated 2026-10-02. This is not a clinical, legal or product approval date.
Bring a specific workflow to the discussion
Share your operating country, care setting, system name and review requirements. Do not send patient records, credentials or identifiable clinical information.