Abstract 13: Evaluation of a FHIR-based Clinical Decision Support Tool for Calculating CHA2DS2-VASc Scores
Zameer AbedinRobert M. HoernerKensaku KawamotoJoseph HabbousheYi LuPhillip B. WarnerDavid ShieldsRashmee U. Shah
6
Citation
0
Reference
10
Related Paper
Citation Trend
Abstract:
Background: Oral anticoagulants reduce stroke risk among atrial fibrillation (AF) patients, yet treatment rates remain low. A technology known as SMART on FHIR allows third party apps to integrate with electronic medical records (EMR) and provide decision support tools. University of Utah Health implemented an alpha version of an integrated MDCalc app - MDCalc on FHIR (MoF) - in the Epic EHR using a SMART on FHIR interface to enable multiple calculations, one of which was the CHA2DS2-VASc calculation. While MDCalc on FHIR is designed to automate inputs that are then reviewed by the practicing clinician with an opportunity to override with clinical judgment, we prospectively compared the automated app score - without physician oversight - with the clinician score, as an early measurement to evaluate accuracy and identify areas for improvement. Methods: We identified outpatient AF patients who were seen in the University of Utah’s cardiovascular clinics between 11/5/2018 and 12/7/2018. We used the MoF app to automatically calculate the CHA2DS2-VASc score within 24 hours of the identified clinic visit - without the MoF feature of allowing clinician interaction - and compared these values to the score documented by the clinician. We also categorized patients as either low risk of stroke or high risk of stroke and calculated the net reclassification index (NRI) using the app compared to documentation. Patients with an app score ≥2 were considered high risk, while patients with a documented score of ≥2 or were prescribed an oral anticoagulant were considered high risk. Results: We identified 200 AF patients, of whom 111 had a documented clinician score. The mean MoF app score was 3.79 (SD 1.86) compared to a mean clinician score of 3.25 (SD 1.63; p=0.02). The NRI was 13.5% (27 of 200) using the app compared to documentation. Ten percent (19 of 200) of patients were “up-classified” by the app, meaning they were high risk by app and low risk by the clinician. Four percent (8 of 200) of patients were “down-classified” by the app, meaning they were low risk by the app and high risk by the clinician. Upon review of these cases, and after accounting for patients who were or were not anticoagulated for a clinically relevant reason (history of bleeding, recent cardioversion, or patient preference), we found that three percent (5 of 200) of patients were “up-classified” by the app, and two percent (3 of 200) of patients were “down-classified” by the app, making the adjusted NRI 4% (8 of 200). Conclusion: SMART on FHIR enables third party vendors to create EMR-based apps, which could provide decision support and improve care. We found that our FHIR-app based approach tended to identify more comorbidities by using medication data to assign conditions, resulting in a higher CHA2DS2-VASc score compared to clinicians. These differences would have had a 4% effect on the actual decision to anticoagulate.Keywords:
Stroke
Medical record
The professional literature concerning teacher evaluation is extensive, but the sources specific to documentation are relatively limited. Here is a practical synthesis of the relevant sources; the five types of documentation memoranda; and the leading lessons for doing documentation successfully.
Cite
Citations (3)
Developer documentation helps developers learn frameworks and libraries. To better understand how documentation in open source projects is created and maintained, we performed a qualitative study in which we interviewed core contributors who wrote developer documentation and developers who read documentation. In addition, we studied the evolution of 19 documents by analyzing more than 1500 document revisions. We identified the decisions that contributors make, the factors influencing these decisions and the consequences for the project. Among many findings, we observed how working on the documentation could improve the code quality and how constant interaction with the projects' community positively impacted the documentation.
Internal documentation
Technical documentation
Software documentation
Code (set theory)
Cite
Citations (115)
ABSTRACT The documentation of seven academic institutional repositories (IRs) was compared and contrasted. This was followed by semi‐structured interviews with six practitioners experienced in the set‐up, management and maintenance of IRs, including representatives of three JISC FAIR projects. The aim was to identify the requirements of policy documentation provided by IRs. Although many issues were found to be handled differently, several common factors emerged. These included the importance of developing documentation in collaboration with academics, departments and senior management. Policies should be formulated only when the aims of the IR have been clearly defined and the documentation itself should be concise and understandable, with the rights and responsibilities of stakeholders clearly presented.
Internal documentation
Technical documentation
Cite
Citations (22)
Good documentation is crucial for frameworks to be used correctly. One important kind of framework documentation are tutorials. They tell how to use the framework and provide additional code examples. However, tutorials are rare compared to other kinds of documentation such as API documentation due to high creation and maintenance costs. In this paper we highlight the problems of writing and maintaining tutorials. Then we present the development environment for tutorials (DEFT), which provides support to address the identified problems.
Technical documentation
Code (set theory)
Internal documentation
Cite
Citations (8)
Based on the development of China documentation from 20th century to this day,this article summarizes the three characteristics of the documentation research.This paper analyzes from the three aspects: the change of the visual angle,the view of integral documentation coming into being,the development of specialized documentation and research.In the end,the author gives some advices to the documentation developing for the future.
Research development
Documentation science
Technical documentation
Cite
Citations (0)
It is acvantageous for standardized college documentation to quicken the velocity of documentation and improve the quality of document.The points to realize it read as follows:Ⅰ.Deepening secretary personnel's understanding about standardized college documentation.Ⅱ.Formulating relevant systems to aggrandize the control of documentation.Ⅲ.Strengthening technologic training and study.Ⅳ.Introducing advanced office equipment.
Technical documentation
Cite
Citations (0)
Computational notebooks allow data scientists to express their ideas through a combination of code and documentation. However, data scientists often pay attention only to the code, and neglect creating or updating their documentation during quick iterations, which leads to challenges in sharing their notebooks with others and future selves. Inspired by human documentation practices from analyzing 80 highly-voted Kaggle notebooks, we design and implement Themisto, an automated documentation generation system to explore the Human-AI Collaboration opportunity in the code documentation scenario. Themisto facilitates the creation of different types of documentation via three approaches: a deep-learning-based approach to generate documentation for source code (fully automated), a query-based approach to retrieve the online API documentation for source code (fully automated), and a user prompt approach to motivate users to write more documentation (semi-automated). We evaluated Themisto in a within-subjects experiment with 24 data science practitioners, and found that automated documentation generation techniques reduced the time for writing documentation, reminded participants to document code they would have ignored, and improved participants' satisfaction with their computational notebook.
Code (set theory)
Internal documentation
Technical documentation
Software documentation
Cite
Citations (6)
The growing importance of APIs creates a need to support developers with effective documentation. Prior research has generated important findings regarding information needs of developers and expectations they form towards API documentation. Several guidelines have been proposed on the basis of these findings, but evidence is lacking whether such guidelines actually lead to better documentation. This paper contributes the results of an empirical test that compared the performance of two groups of developers working on a set of pre-defined tasks with an API they were unfamiliar with. One group had access to documentation which was optimized following guidelines for API documentation design proposed in the literature whereas the other group used non-optimized documentation. Results show that developers working with optimized documentation made fewer errors on the test tasks and were faster in planning and executing the tasks. We conclude that the guidelines used in our study do have the intended effect and effectively support initial interactions with an API.
Internal documentation
Software documentation
Technical documentation
Empirical Research
Cite
Citations (6)
A definition is established for the terms 'Document' and 'Documentation'. The beginning of documentation has been a result of social forces. The genesis and the development of documentation are under the triangle of the three forces emanating from the great increase in the number of research personnel, in the output of research as documents, and in the inner urge of the library profession to give its best to the well-being of the society. Controversies about the agencies for documentation and about the techniques for documentation have been going on from the beginning of the century. Just now they appear to be nearing a satisfactory end. Incidentally India's role in this matter is mentioned.
Technical documentation
Internal documentation
Documentation science
Cite
Citations (0)
One major priority and responsibility of physical therapist educators today is to teach physical therapy students the purposes and the process of documentation. This article reviews the American Physical Therapy Association Documentation Guidelines.1 In addition, it systematically provides educational teaching strategies that assist in the development of documentation skills. Lastly, the article discusses documentation models.
Cite
Citations (3)