← dps8020.ca · Version française

Process intelligence for Canadian healthcare & industrial operations: finding the real process before you fix it

WP-001 · Rev A · 2026-07 · DataProStudio, Inc. · English (version française en préparation)

DPS8020 is a platform in development, designed around the data-sovereignty and audit standards of the European market, and now piloting in Canada (Vancouver and Toronto) ahead of a broader 2027 launch. This paper describes the method and target architecture. Figures cited are indicative targets from comparable engagements — not guaranteed results, and validated case by case.

1. The problem: your systems describe the plan, not the operation

Every healthcare organization and industrial operation runs on a planned process: the intake protocol, the routing in the ERP, the referral pathway, the SOP binder. And every front-line team knows the real process deviates from it — a case that sits in a queue no dashboard tracks, an approval that waits two days in an inbox, a review step duplicated because two systems don’t talk to each other.

The gap between the planned process and the real one is where wait times, cost, and audit findings hide. Large organizations close this gap with consulting engagements that run for months. Smaller operations — a clinic, a distribution centre, a specialty manufacturer — can’t justify that cost, and by the time the report is finished, the operation has already changed.

2. The insight: the evidence already exists

Your systems already record what actually happens. Every intake form, referral, ERP transaction, and inspection is a time-stamped fact: this case, this activity, this moment. Process mining reconstructs the real process from those records — not from interviews, not from a workshop, from data you already generate.

The minimum viable input is an event log with three fields:

Most practice-management, ERP, and case-management systems can export this with no new instrumentation.

3. The method

1. Discover — connectors pull event data from your existing systems. No middleware vendor, no integrator project.
2. Prioritize — find the handful of bottlenecks actually costing you time and trust. Not a 40-item backlog — the 20% worth fixing first.
3. Optimize — redesign the workflow around that fix, and prove it works before reconfiguring any system.
4. Automate — only once the fix is proven. That’s when DPS8020 takes it from there.

Most software vendors start at step 4. This method starts by finding out where automation is actually worth it.

4. Why this doubles as audit evidence

Both healthcare and industrial operations face rising documentation pressure — from regulators, insurers, accreditation bodies, and larger customers. The event log that reveals your bottleneck is the same record that proves what happened, when, and under whose care or custody. A process-mining exercise that maps your real flow can generate that evidence at near-zero marginal cost.

5. Jurisdiction and data handling

Operational and, where applicable, personal health information is sensitive by nature. DPS8020 treats jurisdiction as an architectural requirement:

• Cloud deployment: hosted exclusively with Canadian- and European-owned infrastructure providers, designed to keep data under Canadian or EU jurisdiction. No US-owned vendors in the data path.
• On-premise / air-gapped deployment: for organizations where operational data, or patient data, cannot leave the building — dedicated hardware inside your facility, zero external connectivity.
• No customer data sent to third-party LLM APIs. Minimal telemetry.

For organizations handling personal health information, DPS8020 is designed to help align with Ontario’s PHIPA and BC’s PIPA documentation and access-logging requirements. This is a design goal, not a certification, and does not replace your organization’s privacy officer or compliance program. See the Compliance section of dps8020.ca for the full, hedged list of frameworks this is designed to support.

6. What process intelligence cannot do

• It cannot see what is not recorded. A paper-based or verbal step is invisible until there’s a minimal capture point for it.
• It shows flow and correlation, not root cause. It tells you where the time goes; your team still decides why and what to change.
• Data quality gates everything. The first phase of any pilot is a data-readiness check, and we say plainly if the data isn’t there yet.
• It is not a clinical or diagnostic tool, and does not process or interpret clinical content — it maps operational workflow (intake, queueing, review, disposition), not patient care decisions.
• Indicative improvement ranges are targets observed in comparable settings — never a promise for your specific organization.

7. Summary

The real process is already written down in your event data. DPS8020 reads it, prioritizes it, and turns it into two things every operation needs: shorter, more predictable case cycles, and audit evidence that’s ready before anyone asks for it. On Canadian and European infrastructure — or entirely inside your own four walls.

Contact: hello@dps8020.ca · dps8020.ca · DataProStudio, Inc., Vancouver, BC, Canada · See also: Implementation methodology (MET-001)