JournalJournal of Applied Clinical Medical Physics
PublisherJohn Wiley and Sons Ltd.
MetadataShow full item record
AbstractPurpose: This article presents a solution for continuing radiation therapy without interruption in the event of a cyberattack to the radiation oncology information systems (ROIS). This process could be easily deployed to any radiation oncology practice, with little clinical overhead or burden. Methods and Materials: The solution automatically retrieves all essential information from the clinical ROIS for each under-treatment patient and periodically (e.g., daily) saves these data to a dedicated secure server for recovery. In the event that the clinical ROIS is not functioning as a result of a cyberattack, this essential information is used to build a new secondary ROIS server to continue radiotherapy treatments until the main ROIS is recovered. Once the cyberattack threat is cleared, the clinical ROIS server is rebuilt from the institution's enterprise backup. The newly accumulated treatment information for each patient is then exported from the secondary ROIS to bring the clinical ROIS up to date. Results: The Department of Radiation Oncology at the University of Maryland Medical System implemented this solution for clinical use with the Varian ARIA ROIS in the management of ~250 daily radiotherapy treatments, inclusive of a proton center. This solution was determined to be a feasible and affordable business continuity plan for the radiation oncology practice by minimizing radiation treatment downtime to a couple of hours in a simulated cyberattack drill. Conclusions: The proposed solution can achieve continuation of radiation therapy treatment without treatment breaks in the event of a cyberattack. It also provides cushion time for radiation oncology departments to rebuild their clinical ROIS systems from the enterprise data backup. Copyright 2020 The Authors.
Keywordbusiness continuity plan
contingency plan for radiation oncology
patient data security
radiation oncology information system
Identifier to cite or link to this itemhttps://www.scopus.com/inward/record.uri?eid=2-s2.0-85083847485&doi=10.1002%2facm2.12886&partnerID=40&md5=3c5fc4f10a4cb25d995e622f77b6da8c; http://hdl.handle.net/10713/12694