MétaCan
Menu
Back to cohort
Record W2045313255 · doi:10.4103/2153-3539.150256

Reqscan: An open source solution for laboratory requisition scanning, archiving and retrieval

2015· article· en· W2045313255 on OpenAlexaffabout
Eviatar Bach, Daniel T. Holmes

Bibliographic record

VenueJournal of Pathology Informatics · 2015
Typearticle
Languageen
FieldMedicine
TopicClinical Laboratory Practices and Quality Control
Canadian institutionsSt. Paul's HospitalUniversity of British Columbia
Fundersnot available
KeywordsRequisitionBarcodeDigitizationComputer scienceDocumentationPython (programming language)SoftwareOpen sourceWorld Wide WebOperating systemTelecommunicationsBusiness

Abstract

fetched live from OpenAlex

Requisition storage and retrieval are an integral part of the outpatient laboratory testing process. It is frequently necessary to review an original requisition to confirm the ordering physician, patient demographics, diagnostic information, and requested tests. Manual retrieval of a paper requisition is time-consuming and tedious. Although commercial solutions exist for the scanning and archiving of barcoded paper requisitions, the tools to accomplish this are freely available from the open source software community. We present a simple dedicated piece of software, Reqscan, for scanning patient laboratory requisitions, finding all barcode information, and saving the requisition as a portable document format named according the barcode(s) found. This Python application offers a simple solution to patient requisition digitization. Reqscan has been successfully tested and implemented into routine practice for storage and retrieval of outpatient requisitions at St. Paul's Hospital, Department of Pathology and Laboratory Medicine in Vancouver, British Columbia, Canada.

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 machine prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.

metaresearch head score (Codex)0.005
metaresearch head score (Gemma)0.017
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: Not applicable
GenreCandidate signal: Software · Consensus signal: Software
Teacher disagreement score0.079
Threshold uncertainty score0.263

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0050.017
Meta-epidemiology (narrow)0.0030.002
Meta-epidemiology (broad)0.0010.002
Bibliometrics0.0040.003
Science and technology studies0.0010.001
Scholarly communication0.0030.005
Open science0.0060.008
Research integrity0.0020.003
Insufficient payload (model declined to judge)0.0790.065

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.101
GPT teacher head0.412
Teacher spread0.311 · 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 source (direct Gemma or distilled Codex), not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designNot applicable
Domainnot available
GenreSoftware

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

Citations3
Published2015
Admission routes2
Has abstractyes

Explore more

Same venueJournal of Pathology InformaticsSame topicClinical Laboratory Practices and Quality ControlFrench-language works237,207