Enhancing Hospital Services: Achieving High Quality Under Resource Constraints
Bibliographic record
Abstract
Objectives: This research aims to enhance the quality of hospital services by utilizing Quality Function Deployment (QFD) with a novel Multi-Dimensional House of Quality (MD-HOQ) approach. This method integrates Service Quality (SERVQUAL) analysis and considers resource constraints, such as financial and workforce limitations, to select and prioritize technical requirements effectively. Methods: The proposed MD-HOQ approach was applied to a private hospital in Tehran, Iran. Data were gathered from a sample of 8 experts and a sample of 386 patients, using 2 in-depth interviews and 4 questionnaires. The process included identifying hospital sections and determining their importance using the Analytic Hierarchy Process. Patients' needs in each section were then identified and weighted through SERVQUAL analysis. Subsequently, technical requirements to meet these needs were listed and weighted using MD-HOQ. A mathematical model was employed to determine the optimal set of technical requirements under resource constraints. Results: Application of the MD-HOQ approach resulted in the identification of 50 patient needs across 5 hospital sections. Additionally, 40 technical requirements were identified. The highest implementation priorities were assigned to "training practitioners and nurses," "improving the staff's sense of responsibility," and "using experienced specialists, physicians, and surgeons." Conclusions: The integrated QFD approach, utilizing MD-HOQ and SERVQUAL analysis, provides a comprehensive framework for hospital managers to prioritize technical requirements effectively. By considering resource constraints and the gap between patient expectations and perceptions, this method ensures that resources are allocated to the most impactful technical requirements, leading to improved patient satisfaction and better overall hospital service quality. This approach not only enhances the quality of hospital services but also ensures efficient utilization of resources, ultimately benefiting patient satisfaction.
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.005 | 0.013 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.002 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.003 | 0.002 |
| Open science | 0.001 | 0.003 |
| 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".