• Int J Med Inform · May 2013

    A study of user requests regarding the fully electronic health record system at Seoul National University Bundang Hospital: challenges for future electronic health record systems.

    • Sooyoung Yoo, Seok Kim, Seungja Lee, Kee-Hyuck Lee, Rong-Min Baek, and Hee Hwang.
    • Center for Medical Informatics, Seoul National University Bundang Hospital, Republic of Korea.
    • Int J Med Inform. 2013 May 1;82(5):387-97.

    ObjectiveAlthough the adoption rates for Electronic Health Records (EHRs) are growing, significant opportunities for further advances in EHR system design remain. The goal of this study was to identify issues that should be considered in the design process for the successful development of future systems by analyzing end users' service requests gathered during a recent three-year period after a comprehensive EHR system was implemented at Seoul National University's Bundang Hospital in South Korea.MethodsData on 11,400 service requests from end users of the EHR system made from 2008 through 2010 were used in this study. The requests were categorized as program modification/development, data request, insurance-fee identification/generation, patient-record merging, or other. The authors further subcategorized the requests for program modification/development into the following nine areas of concern: (1) indicators and statistics, (2) patient safety and quality of care, (3) special task-oriented functionalities, (4) ease of use and user interface, (5) system speed, (6) interoperability and integration, (7) privacy and security, (8) customer service, and (9) miscellaneous. The system users were divided into four groups--direct care, care support, administrative/insurance, and general management--to identify each group's needs and concerns.ResultsThe service requests for program modification/development, data request, insurance-fee identification/generation, patient-record merging, and other issues constituted approximately 49.2%, 33.9%, 11.4%, 4.0%, and 1.5% of the total data set, respectively. The number of data-request service requests grew over the three years studied. Different groups of users were found to have different concerns according to their activities and tasks. Within the program-modification/development category, end users were most frequently concerned with ease of use and user interface (38.1% of the total) and special task-oriented functionalities (29.3% of the total) in their use of the EHR system, with increasing numbers of requests in both categories over the three years. Users in the direct-care group differed from the other groups in that they most frequently submitted requests related to ease of use and user interface, followed by special functionalities, patient safety and quality care, and customer service, while users in other groups submitted requests concerning ease of use and user interface and special functionalities with a similarly high frequency.ConclusionsUsers have continued to make suggestions about their needs and requirements, and the EHR system has evolved to optimize ease of use and special functionalities for particular groups of users and particular subspecialties. Based on our experiences and the lessons we have learned in the course of maintaining full-EHR systems, we suggest that the key goals to be considered for future EHR systems include innovative new user-interface technologies; special extended functions for each user group's specific task-oriented requirements; powerful, easy-to-use functions to support research; new flexible system architecture; and patient-directed functions.Copyright © 2012 Elsevier Ireland Ltd. All rights reserved.

      Pubmed     Full text   Copy Citation     Plaintext  

      Add institutional full text...

    Notes

     
    Knowledge, pearl, summary or comment to share?
    300 characters remaining
    help        
    You can also include formatting, links, images and footnotes in your notes
    • Simple formatting can be added to notes, such as *italics*, _underline_ or **bold**.
    • Superscript can be denoted by <sup>text</sup> and subscript <sub>text</sub>.
    • Numbered or bulleted lists can be created using either numbered lines 1. 2. 3., hyphens - or asterisks *.
    • Links can be included with: [my link to pubmed](http://pubmed.com)
    • Images can be included with: ![alt text](https://bestmedicaljournal.com/study_graph.jpg "Image Title Text")
    • For footnotes use [^1](This is a footnote.) inline.
    • Or use an inline reference [^1] to refer to a longer footnote elseweher in the document [^1]: This is a long footnote..

    hide…