<i>A Roundtable Discussion:</i> Enhancing Supportability of Healthcare Technology
Bibliographic record
Abstract
Sean Loughlin: What are your greatest concerns or frustrations related to the supportability of healthcare technology?Michael Mestek: From an industry perspective, my greatest concerns are that healthcare technology management (HTM) professionals feel that training isn't available or accessible and that service documentation is difficult to find.Those are key issues that need to be corrected in order for technology to be adopted and utilized in any clinical environment.Julio Huerta: Similarly, my biggest concern is having access to affordable technical documentation, which is instrumental to ensuring that the healthcare technology for which I am responsible is safe and working properly.The part that frustrates me is the unwillingness among stakeholders and organizations to work on finding common ground that fosters productive partnerships.Ken Maddock: I agree-due to the complexity of the support environment, HTM staff are spending too much time tracking down technical documentation.Michael Capuano: Original equipment manufacturers (OEMs) seem to have misgivings about on-site HTM personnel having the tools, training, and resources needed to effectively support their technology.Rather than believing that they're the best ones to do it, OEMs need to be aware that HTM departments are able to support the equipment. Sean Loughlin: The perspectives of HTM professionals and manufacturers were discussed this past November during the AAMI Forum on Supportability of Healthcare Technology. What common priorities or concerns among these two groups emerged from the forum?Ken Maddock: Everyone agreed that we need to make sure that the people who work on the equipment are confident in their ability to do so.We realized that HTM professionals and OEMs are not that far apart.The forum participants understood that a risk-based method can be used to ascertain the minimum level of competency and whether training is needed.We also agreed that frequent, ongoing, and documented communication is needed between manufacturers and HTM professionals.
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.026 | 0.056 |
| Meta-epidemiology (narrow) | 0.002 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.003 |
| Bibliometrics | 0.002 | 0.001 |
| Science and technology studies | 0.019 | 0.008 |
| Scholarly communication | 0.016 | 0.023 |
| Open science | 0.006 | 0.016 |
| Research integrity | 0.052 | 0.067 |
| Insufficient payload (model declined to judge) | 0.050 | 0.016 |
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".