MétaCan
Menu
Back to cohort
Record W2942078150 · doi:10.3233/978-1-61499-951-5-140

Use of Agile Project Methodology in Health Care IT Implementations: A Scoping Review

2019· review· en· W2942078150 on OpenAlexaff
Rav Goodison, Elizabeth M. Borycki, André Kushniruk

Bibliographic record

VenueStudies in health technology and informatics · 2019
Typereview
Languageen
FieldBusiness, Management and Accounting
TopicBig Data and Business Intelligence
Canadian institutionsUniversity of Victoria
Fundersnot available
KeywordsAgile software developmentImplementationHealth careProject managementProcess managementScheduleMedical recordKnowledge managementComputer scienceMedicineEngineering managementBusinessEngineeringSystems engineeringPolitical scienceSoftware engineering

Abstract

fetched live from OpenAlex

Health care organizations are investing in system solutions that can be leveraged across the continuum of care (i.e. electronic medical records (EMR's); electronic health records (EHR's); health information exchanges (HIE's) and patient portals. The importance of these systems and how they have evolved over the past 30 years has been well researched. The value and benefits of these systems are therefore well known; however, it is estimated that most projects are typically 100% over budget and a year behind schedule [1, p. 2]. In this paper the authors examine what literature is available on agile project management methodologies in health care settings. A scoping review of the literature available specifically on agile methods use in implementing systems within health care was undertaken. Findings revealed there is very little literature available on agile project management methodologies used in health care IT systems implementations. The authors identify there is a strong need for research to look into project management methodologies and identify areas in the project lifecycle, where change is needed to increase clinical systems adoption.

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.023
metaresearch head score (Gemma)0.068
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Systematic review · Consensus signal: none
GenreCandidate signal: Review · Consensus signal: Review
Teacher disagreement score0.023
Threshold uncertainty score0.120

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0230.068
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0030.003
Bibliometrics0.0160.020
Science and technology studies0.0010.002
Scholarly communication0.0040.004
Open science0.0020.003
Research integrity0.0020.002
Insufficient payload (model declined to judge)0.0030.001

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.719
GPT teacher head0.586
Teacher spread0.133 · 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 designSystematic review
Domainnot available
GenreReview

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

Citations19
Published2019
Admission routes1
Has abstractyes

Explore more

Same venueStudies in health technology and informaticsSame topicBig Data and Business IntelligenceFrench-language works237,207