MétaCan
Menu
Back to cohort
Record W4413937386 · doi:10.61132/neptunus.v3i3.1048

Implementasi Sistem Pakar Diagnosa Penyakit Tifus dengan Metode Certainty Factor

2025· article· en· W4413937386 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

VenueNeptunus · 2025
Typearticle
Languageen
FieldBusiness, Management and Accounting
TopicDecision Support System Applications
Canadian institutionsKootenay Association for Science & Technology
Fundersnot available
KeywordsComputer science

Abstract

fetched live from OpenAlex

Typhoid fever is a significant health issue caused by the Salmonella Typhi bacteria, leading to symptoms such as fever, abdominal pain, diarrhea, muscle pain, and serious complications if not treated promptly. A common challenge faced by society is limited access to medical professionals, especially in remote areas, and delays in recognizing symptoms. To address this problem, this study designs and implements a web-based expert system using the Certainty Factor (CF) method, which helps diagnose typhoid fever quickly and accurately. The Certainty Factor method is used to calculate the certainty level of the symptoms experienced by the patient, providing a diagnosis result in the form of early-stage typhoid, mild typhoid, or severe typhoid. The system was developed using PHP programming language and MySQL database, and tested at RSUD Djoelham Binjai City. The research data was obtained from patients at RSUD Djoelham Binjai with a case study on patient number 22. The processing of symptoms through Certainty Factor calculation showed that the patient is most likely to have severe typhoid with a certainty value of 0.9443 or 94.43%. This result proves that the Certainty Factor method can be used to assist in providing an accurate early diagnosis of typhoid fever with a high degree of accuracy.

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.000
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMeta-epidemiology (narrow), Insufficient payload (model declined to judge)
Consensus categoriesInsufficient payload (model declined to judge)
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: Not applicable
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.563
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

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

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.026
GPT teacher head0.290
Teacher spread0.264 · 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