Bibliographic record
Abstract
From the 1st of January 2026 a dramatic change should take place in the digitalization of healthcare. New communication standards developed by the Ministry of Health in the recent years should be gradually implemented for the communication between healthcare providers. How well are laboratories prepared for the coming change? Looking back we can say that in the year 1997 National Code List of Laboratory Items (NČLP) and Czech National Data Standard for information exchange in healthcare version 1 (DASTA) were already published for the purpose of data transfer between information systems of healthcare facilities. It could be expected that after a quarter of a century, communication should be flawless. However, the opposite is true and the authors demonstrate this with many examples from their 30-year practice. Many workplaces have so far not executed the implementation to their information systems correctly as if the staff don’t understand that if all of them will not be using a unified communication language they could put the lives of their patients at risk. Why is this occurring? It could be said that all parts of the system are partially guilty – laboratories, companies that produce information systems, professional societies that are responsible for the standardization of laboratory items. Organizations that are involved in certification and acreditation services also carring partial responsibility. Professionals specializing in electronic communications are missing on all of these levels. Therefore, in order for doctors to receive electronic results of adequate quality, even the best definition of a communication standard, whether new or old, is not enough. A compatible information system that fully supports this definition must be used. In laboratories the information systems have to be configured correctly and the configuration has to be maintained to be up to date and regularly inspected both internally and externally. For instance, the definition of the current standard DASTA 4 is extensive and very detailed but in spite of this the quality of the transferred data in practice is often poor. Authors speculate that a mere change in interface, even for a more modern design HL7 FHIR design, will not solve the issue and a lot of work is yet to be done by all people and organizations involved in the process of transfer of laboratory data in order to provide a solution.
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.003 | 0.004 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.002 | 0.001 |
| Science and technology studies | 0.002 | 0.002 |
| Scholarly communication | 0.008 | 0.003 |
| Open science | 0.001 | 0.003 |
| Research integrity | 0.003 | 0.004 |
| Insufficient payload (model declined to judge) | 0.101 | 0.060 |
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".