RESUMO
Objective: The purpose of this study was to conduct a scoping review of publications that explored blockchain technology in the context of interoperability and challenges of electronic health record (EHR) implementations. We synthesize the literature regarding standards and security, specifically regulation, regulatory operability, and conformance to standards. We review open practitioner questions that were not addressed in the studies as directions for further research. Materials and Methods: We conducted a literature search in the OVID databases (Medline and Embase) on terms blockchain, implementation, interoperability, EHRs, security, and standards. The search resulted in 152 nonduplicate, peer-reviewed manuscripts, of which 15 were relevant to our objective and included for synthesis. Results: Based on the search results, we analyzed the adoption of blockchain technology in the healthcare systems and challenges to EHR implementation of blockchain. From the synthesized research, we categorized and reported compelling factors of blockchain for EHR integration using current knowledge on blockchain research standardization and architectural challenges. Discussion: Our research showed promise in implementing blockchain technology associated with EHRs, especially with Health Information Exchanges. The studies relevant for both EHR (n = 5) and blockchain (n = 10) reported compelling factors and limitations of the architecture. Security (n = 4) and interoperability (n = 4) features were reported as compelling requirements with lingering challenges. Standardization literature (n = 3) reported implementation challenges. Conclusion: This study shows promise in implementing blockchain technology within EHR systems. The adoption is increasing; however, multiple implementation challenges remain from architectural perspectives (eg, scalability and performance), to security challenges (eg, legal requirements), and standard perspectives including patient-matching problems.
RESUMO
Clinical notes, which can be embedded into electronic medical records, document patient care delivery and summarize interactions between healthcare providers and patients. These clinical notes directly inform patient care and can also indirectly inform research and quality/safety metrics, among other indirect metrics. Recently, some states within the United States of America require patients to have open access to their clinical notes to improve the exchange of patient information for patient care. Thus, developing methods to assess the cyber risks of clinical notes before sharing and exchanging data is critical. While existing natural language processing techniques are geared to de-identify clinical notes, to the best of our knowledge, few have focused on classifying sensitive-information risk, which is a fundamental step toward developing effective, widespread protection of patient health information. To bridge this gap, this research investigates methods for identifying security/privacy risks within clinical notes. The classification either can be used upstream to identify areas within notes that likely contain sensitive information or downstream to improve the identification of clinical notes that have not been entirely de-identified. We develop several models using unigram and word2vec features with different classifiers to categorize sentence risk. Experiments on i2b2 de-identification dataset show that the SVM classifier using word2vec features obtained a maximum F1-score of 0.792. Future research involves articulation and differentiation of risk in terms of different global regulatory requirements.
RESUMO
BACKGROUND: Mobile health (mHealth) apps have facilitated symptom monitoring of COVID-19 symptoms globally and have been used to share data with health care professionals and support disease prediction, prevention, management, diagnostics, and improvements in treatments and patient education. OBJECTIVE: The aim of this review is to evaluate the quality and functionality of COVID-19 mHealth apps that support tracking acute and long-term symptoms of COVID-19. METHODS: We systematically reviewed commercially available mHealth apps for COVID-19 symptom monitoring by searching Google Play and Apple iTunes using search terms such as "COVID-19," "Coronavirus," and "COVID-19 and symptoms." All apps underwent three rounds of screening. The final apps were independently assessed using the Mobile Application Rating Scale (MARS), an informatics functionality scoring system, and the Center for Disease Control and World Health Organization symptom guidelines. The MARS is a 19-item standardized tool to evaluate the quality of mHealth apps on engagement, functionality, aesthetics, and information quality. Functionality was quantified across the following criteria: inform, instruct, record (collect, share, evaluate, and intervene), display, guide, remind or alert, and communicate. Interrater reliability between the reviewers was calculated. RESULTS: A total of 1017 mobile apps were reviewed, and 20 (2%) met the inclusion criteria. The majority of the 20 included apps (n=18, 90%) were designed to track acute COVID-19 symptoms, and only 2 (10%) addressed long-term symptoms. Overall, the apps scored high on quality, with an overall MARS rating of 3.89 out of 5, and the highest domain score for functionality (4.2). The most common functionality among all apps was the instruct function (n=19, 95%). The most common symptoms included in the apps for tracking were fever and dry cough (n=18, 90%), aches and pains (n=17, 85%), difficulty breathing (n=17, 85%), tiredness, sore throat, headache, loss of taste or smell (n=16, 80%), and diarrhea (n=15, 75%). Only 2 (10%) apps specifically tracked long-term symptoms of COVID-19. The top 4 rated apps overall were state-specific apps developed and deployed for public use. CONCLUSIONS: Overall, mHealth apps designed to monitor symptoms of COVID-19 were of high quality, but the majority of apps focused almost exclusively on acute symptoms. Future apps should also incorporate monitoring long-term symptoms of COVID-19 and evidence-based educational materials; they should also include a feature that would allow patients to communicate their symptoms to specific caregivers or their own health care team. App developers should also follow updated technical and clinical guidelines from the Center for Disease Control and the World Health Organization.