A Health Care Project Management Office's Strategies for Continual Change and Continuous Improvement
Why this work is in the frame
A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.
Bibliographic record
Abstract
Health care organizations need project and change management support in order to achieve successful transformations. A project management office (PMO) helps support the organizations through their transformations along with increasing their capabilities in project and change management. The aim of the present study was to extend understanding of the continuous improvement mechanisms used by PMOs and to describe PMO's strategies for continual change and continuous improvement in the context of major transformation in health care. This study is a descriptive case study design with interviews conducted from October to December 2015 with PMO's members (3 managers and 1 director) and 3 clients working with the PMO after a major redevelopment project ended (transition to the new facility). Participants suggested a number of elements including carefully selecting the members of the PMO, having a clear mandate for the PMO, having a method and a discipline at the same time as allowing openness and flexibility, clearly prioritizing projects, optimizing collaboration, planning for everything the PMO will need, not overlooking organizational culture, and retaining the existing support model. This study presents a number of factors ensuring the sustainability of changes.
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.
Full frame distilled prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.003 | 0.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.008 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.000 | 0.001 |
| Insufficient payload (model declined to judge) | 0.000 | 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 it