When Electronic Health Records (EHRs) Talk, Everyone Can Win: Our Experience Creating a Software Link Between Hospital and Radiation Oncology EHRs
2015; Elsevier BV; Volume: 94; Issue: 1 Linguagem: Inglês
10.1016/j.ijrobp.2015.09.012
ISSN1879-355X
Autores Tópico(s)Scientific Computing and Data Management
ResumoIn 2015, Boston Medical Center (BMC) implemented the Epic (Verona, WI) electronic health record (EHR). To integrate oncology services throughout our hospital, the radiation oncology department implemented an interface to transfer radiation oncology treatment data from the record and verify system, ARIA (Varian Medical Systems, Palo Alto, CA) to Epic; this interface is commercially available from Varian, but not widely used. Building an interface between ARIA and Epic had a variety of potential advantages. 1.The need to copy/paste data between systems is eliminated. Copy/paste can propagate erroneous information forward in patients' charts ( 1 Botsis T. Hartvigsen G. Chen F. et al. Secondary use of EHR: Data quality issues and informatics opportunities. AMIA Jt Summits Transl Sci Proc. 2010; 2010: 1-5 PubMed Google Scholar ). The Joint Commission has warned against using copy/paste ( 2 The Joint Commission, Division of Health Care Improvement. Preventing copy-and-paste errors in EHRs. Quick Safety: Issue 10, February 2015. Available at: www.jointcommission.org/assets/1/23/Quick_Safety_Issue_10.pdf. Accessed August 1, 2015. Google Scholar ). 2.Radiation oncology data would be available in real time in Epic. Other oncology providers could know treatment progress continuously. 3.Radiation oncology treatment data would be a permanent part of the health record in a common database. This can facilitate abstracting of data and enables future comparative effectiveness research ( 3 Miriovsky B.J. Shulman L.N. Abernethy A.P. Importance of health information technology, electronic health records, and continuously aggregating data to comparative effectiveness research and learning health care. J Clin Oncol. 2012; 30: 4243-4248 Crossref PubMed Scopus (113) Google Scholar ).
Referência(s)