MétaCan
Menu
Back to cohort
Record W1994108236 · doi:10.1142/s0218194009004143

DESIGN OF DECOUPLED CLINICAL DECISION SUPPORT FOR SERVICE-ORIENTED ARCHITECTURES

2009· article· en· W1994108236 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

VenueInternational Journal of Software Engineering and Knowledge Engineering · 2009
Typearticle
Languageen
FieldComputer Science
TopicService-Oriented Architecture and Web Services
Canadian institutionsUniversity of Victoria
Fundersnot available
KeywordsComputer scienceService-oriented architectureService (business)Decoupling (probability)Loose couplingClinical decision support systemEmpirical researchComponent (thermodynamics)Service designDecision support systemArchitectureProcess managementRisk analysis (engineering)Knowledge managementService delivery frameworkWeb serviceWorld Wide WebEngineeringBusinessArtificial intelligence

Abstract

fetched live from OpenAlex

Computer-based clinical decision support (CDS) contributes to cost savings, increased patient safety and quality of medical care. Most existing CDS systems are stand-alone products (first generation) or part of complete electronic medical record packages (second generation). Experience shows that creating and maintaining CDS systems is expensive and requires effort that should be economized by sharing them among multiple users. It makes good economic sense to share CDS service installations among a larger set of client systems. The paradigm of a service-oriented architecture (SOA) embraces this idea of sharing distributed services. Some attempts making CDS services available to distributed health information systems exist. However, these approaches have not gained much adoption. We argue that they do not provide a sufficient level of decoupling between client and CDS in order to be broadly reusable in SOAs. In this paper, we present a new CDS service component called EGADSS, which has been designed and implemented with the declared objective to minimize the coupling between client and CDS server. We present our key design decisions, which are guided by empirical research in SOA development. We evaluate our result theoretically by measuring the level of decoupling achieved compared to existing CDS approaches. Furthermore, we report on an empirical evaluation of the resulting design, integrating the EGADSS service with an example client system.

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.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: Simulation or modeling · Consensus signal: Simulation or modeling
GenreCandidate signal: Methods · Consensus signal: Methods
Teacher disagreement score0.378
Threshold uncertainty score0.806

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0010.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0010.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.013
GPT teacher head0.284
Teacher spread0.271 · 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