Advancing laboratory medicine in hospitals through health information exchange: a survey of specialist physicians in Canada
Bibliographic record
Abstract
Abstract Background Laboratory testing occupies a prominent place in health care. Information technology systems have the potential to empower laboratory experts and to enhance the interpretation of test results in order to better support physicians in their quest for better and safer patient care. This study sought to develop a better understanding of which laboratory information exchange (LIE) systems and features specialist physicians are using in hospital settings to consult their patients’ laboratory test results, and what benefit they derive from such use. Methods As part of a broader research program on the use of health information exchange systems for laboratory medicine in Quebec, Canada, this study was designed as on online survey. Our sample is composed of 566 specialist physicians working in hospital settings, out of the 1512 physicians who responded to the survey (response rate of 17%). Respondents are representative of the targeted population of specialist physicians in terms of gender, age and hospital location. Results We first observed that 80% of the surveyed physicians used the province-wide interoperable electronic health records (iEHR) system and 93% used a laboratory results viewer (LRV) to consult laboratory test results and most (72%) use both systems to retrieve lab results. Next, our findings reveal important differences in the capabilities available in each type of system and in the use of these capabilities. Third, there are differences in the nature of the perceived benefits obtained from the use of each of these two systems. Last, the extent of use of an LRV is strongly influenced by the IT artefact itself (i.e., the hospital’s LRV available capabilities) while the use of the provincial iEHR system is influenced by its organizational context (i.e. the hospital’s size and location). Conclusions The main contribution of this study lies in its insights into the role played by context in shaping physicians’ choices about which laboratory information exchange systems to adopt and which features to use, and the different perceptions they have about benefits arising from such use. One related implication for practice is that success of LIE initiatives should not be solely assessed with basic usage statistics.
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 imitationNot 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.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.002 | 0.008 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.004 |
| Science and technology studies | 0.003 | 0.001 |
| Scholarly communication | 0.002 | 0.001 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.002 | 0.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.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
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".