MétaCan
Menu
Back to cohort
Record W4409792976 · doi:10.2196/62983

A Unique Way to Axe the Fax Through Using Business Automation Workflow to Expedite eReferral Adoption, Bridging eReferral, and Fax: Proof-of-Concept Study

2025· article· en· W4409792976 on OpenAlexaffvenueabout
Zhigang Tian, Kayla Wierts, Beth Gerritsen, Kim Lynch, Russell Buchanan, Mohamed Alarakhia

Bibliographic record

VenueJMIR Medical Informatics · 2025
Typearticle
Languageen
FieldBusiness, Management and Accounting
TopicHealthcare Systems and Technology
Canadian institutionsEastern Ontario Training BoardMcMaster UniversityPublic Health OntarioUniversity of Toronto
Fundersnot available
KeywordsWorkflowPreprintBridging (networking)AutomationComputer scienceWorld Wide WebSoftware engineeringDatabaseBusinessEngineeringComputer security

Abstract

fetched live from OpenAlex

Background: It is estimated that 88% of Ontario physicians still use fax technology to share patient information. Transitioning to electronic referral (eReferral) has been shown to have numerous benefits, but the major barrier to adoption of eReferral is the need for both sending and receiving clinicians on the same platform to enable information sharing. The traditional onboarding process takes time and effort. An innovative method is required to improve eReferral adoption by bridging the gap between eReferral senders and fax referral receivers. Objective: This study aimed to explore the technological feasibility of leveraging a business automation workflow (BAW) platform to connect the digital (eReferral) and nondigital referral platform (fax), enabling eReferral senders to send referrals to fax receivers, thereby improving the clinician experience. Methods: An eReferral via eFax solution was developed and evaluated on the BAW platform to connect the eReferral platform and the clinicians using fax. A selected number of fax receivers were identified and enabled on the eReferral platform as eFax receivers. Sending clinicians initiated eFaxes through the familiar eReferral workflow, with eFaxes transmitted to BAW and delivered to the target receiver via fax. Retry and reminder logic were built to improve the user experience. If the eFax failed after all retries, a message was sent to the sending clinician through the eReferral platform explaining the failure reason. The appointment information was entered into the eReferral platform by the sending clinicians to trigger patient email notifications. Surveys and focused interviews were conducted to collect clinicians' feedback. Results: From May 2022 to December 2023, 224 eFax receivers were enabled on the platform, processing 4504 eFaxes for 4132 unique patients and 843 unique senders across the province. Nearly 70% (3137/4504) of patients consented and received email notifications; 19% (875/4504) received appointment details after manual entry in the eReferral platform. On average, eFax referrals contained 5.6 pages, with a minimal 0.7% exceeding 30 pages. Initially, fax service retries were disabled to observe delivery error rates. This resulted in a 37.7% (1023/2712) fax failure. However, after implementing new retry logic in March 2023, the failure rate dropped significantly to 9.9% (304/3082), and 98.7% (2770/2806) of eFaxes were successfully delivered after automatic retries. Clinician feedback revealed a positive impact on sending clinicians' experience, maintaining their familiar workflow while accommodating fax-reliant receivers who can gradually transition to eReferral at their own pace. Conclusions: This project demonstrates the potential of the BAW platform to bridge the gap between fax and eReferral systems. It minimizes disruption for sending clinicians while allowing fax receivers to incrementally adopt the new platform. This technology can significantly expedite eReferral adoption by reducing the reliance on receiving clinics to adopt eReferral, ultimately enhancing the experience for both clinicians and patients.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

How this classification was reachedexpand

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.001
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Other design · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.887
Threshold uncertainty score0.658

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.002
Science and technology studies0.0000.000
Scholarly communication0.0000.001
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.040
GPT teacher head0.329
Teacher spread0.290 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it

Classification

machine, unvalidated

Machine predicted; a candidate call from one teacher head, not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designOther design
Domainnot available
GenreEmpirical

How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".

Quick stats

Citations1
Published2025
Admission routes3
Has abstractyes

Explore more

Same venueJMIR Medical InformaticsSame topicHealthcare Systems and TechnologyFrench-language works237,207