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: 1034
Function: getPubMedXML
File: /var/www/html/application/helpers/my_audit_helper.php
Line: 3152
Function: GetPubMedArticleOutput_2016
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
U.S. physician offices are experiencing a revolutionary change in the microprocesses that have been the norm for documenting and communicating in regard to patient care for decades. While this revolution is welcome for dozens of reasons, migration of data storage from the paper-based record to electronic form affects physician work well beyond what is immediately evident. Creation and implementation of these new systems is a huge challenge to all involved, particularly physicians and information technology (IT) professionals. This article provides advice to make the implementation process easier for all. The findings of the authors over years of participation in electronic medical record implementations substantiate the position that these implementations need more preparatory work than most other IT projects.
Download full-text PDF |
Source |
---|
Enter search terms and have AI summaries delivered each week - change queries or unsubscribe any time!