A PHP Error was encountered

Severity: Warning

Message: file_get_contents(https://...@pubfacts.com&api_key=b8daa3ad693db53b1410957c26c9a51b4908&a=1): Failed to open stream: HTTP request failed! HTTP/1.1 429 Too Many Requests

Filename: helpers/my_audit_helper.php

Line Number: 176

Backtrace:

File: /var/www/html/application/helpers/my_audit_helper.php
Line: 176
Function: file_get_contents

File: /var/www/html/application/helpers/my_audit_helper.php
Line: 250
Function: simplexml_load_file_from_url

File: /var/www/html/application/helpers/my_audit_helper.php
Line: 3122
Function: getPubMedXML

File: /var/www/html/application/controllers/Detail.php
Line: 575
Function: pubMedSearch_Global

File: /var/www/html/application/controllers/Detail.php
Line: 489
Function: pubMedGetRelatedKeyword

File: /var/www/html/index.php
Line: 316
Function: require_once

Quality in practice: integrating routine collection of patient language data into hospital practice. | LitMetric

Quality in practice: integrating routine collection of patient language data into hospital practice.

Int J Qual Health Care

Division of Primary Care Medicine, Department of Community Medicine, Primary Care and Emergency Medicine, University Hospitals of Geneva, 4, rue Gabrielle-Perret-Gentil, 1211 Geneva 14, Switzerland.

Published: September 2013

Quality Problem: Timely identification of patients' language needs can facilitate the provision of language-appropriate services and contribute to quality of care, clinical outcomes and patient satisfaction.

Initial Assessment: At the University Hospitals of Geneva, Switzerland, timely organization of interpreter services was hindered by the lack of systematic patient language data collection.

Choice Of Solution: We explored the feasibility and acceptability of a procedure for collecting patient language data at the first point of contact, prior to its hospital-wide implementation.

Implementation: During a one-week period, receptionists and triage nurses in eight clinical services tested a new procedure for collecting patient language data. Patients were asked to identify their primary language and other languages they would be comfortable speaking with their doctor. Staff noted patients' answers on a paper form and provided informal feedback on their experience with the procedure.

Evaluation: Registration staff encountered few difficulties collecting patient language data and thought that the two questions could easily be incorporated into existing administrative routines. Following the pilot test, two language fields with scroll-down language menus were added to the electronic patient file, and the subsequent filling-in of these fields has been rapid and hospital wide.

Lessons Learned: Our experience suggests that routine collection of patient language data at first point of contact is both feasible and acceptable and that involving staff in a pilot project may facilitate hospital-wide implementation. Future efforts should focus on exploring the sensitivity and specificity of the proposed questions, as well as the impact of data collection on interpreter use.

Download full-text PDF

Source
http://dx.doi.org/10.1093/intqhc/mzt035DOI Listing

Publication Analysis

Top Keywords

patient language
24
language data
24
collecting patient
12
language
10
routine collection
8
patient
8
collection patient
8
procedure collecting
8
data point
8
point contact
8

Similar Publications

Want AI Summaries of new PubMed Abstracts delivered to your In-box?

Enter search terms and have AI summaries delivered each week - change queries or unsubscribe any time!