MétaCan
Menu
Back to cohort

An Evaluation Framework for Business Process Modeling Languages in Healthcare

2009· article· en· W2147526451 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueJournal of theoretical and applied electronic commerce research · 2009
Typearticle
Languageen
FieldBusiness, Management and Accounting
TopicBusiness Process Modeling and Analysis
Canadian institutionsUniversity of Ottawa
Fundersnot available
KeywordsBusiness process modelingProcess (computing)Health careBusiness Process Model and NotationProcess managementComputer scienceBusiness processProcess modelingArtifact-centric business process modelBusiness process managementKnowledge managementBusinessProgramming languageMarketingWork in processPolitical science

Abstract

fetched live from OpenAlex

Web services composition is an emerging paradigm for enabling inter and intra organizational integration, and a landscape of languages and techniques for modeling business processes in web service based environments has emerged and is continuously being enriched. With the advent of modeling standards, different business sectors are investigating the options for modeling their workflows. In terms of business process modeling, healthcare is a rather complex sector of activity. Indeed, modeling healthcare processes presents special requirements dictated by the complicated and dynamic nature of these processes as well as by the specificity and diversity of the actors involved in these processes. Little effort has been dedicated to evaluating the capabilities and limitations of modeling languages based on healthcare requirements. This paper presents a set of healthcare modeling requirements and proposes an evaluation framework for process modeling languages based on these requirements. The suitability of two major process based service composition languages, namely BPEL and WS-CDL, is evaluated.

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.

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.005
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: Theoretical or conceptual · Consensus signal: Theoretical or conceptual
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.302
Threshold uncertainty score0.450

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0050.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0010.001
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.001
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.046
GPT teacher head0.407
Teacher spread0.362 · 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