- Browse by Subject
Browsing by Subject "Electronic medical record systems"
Now showing 1 - 2 of 2
Results Per Page
Sort Options
Item Indianapolis Emergency Medical Service and the Indiana Network for Patient Care: Evaluating the Patient Match Algorithm(American Medical Informatics Association, 2012) Park, Seong C.; Finnell, John T.; Emergency Medicine, School of MedicineIn 2009, Indianapolis launched an electronic medical record system within their ambulances and started to exchange patient data with the Indiana Network for Patient Care (INPC) This unique system allows EMS personnel to get important information prior to the patient’s arrival to the hospital. In this descriptive study, we found EMS personnel requested patient data on 14% of all transports, with a “success” match rate of 46%, and a match “failure” rate of 17%. The three major factors for causing match “failure” were ZIP code 55%, Patient Name 22%, and Birth date 12%. We conclude that the ZIP code matching process needs to be improved by applying a limitation of 5 digits in ZIP code instead of using ZIP+4 code. Non-ZIP code identifiers may be a better choice due to inaccuracies and changes of the ZIP code in a patient’s record.Item OpenMRS as an emergency EMR—How we used a global good to create an emergency EMR in a week(Elsevier, 2021) Mamlin, Burke W.; Shivers, Jennifer E.; Glober, Nancy K.; Dick, Jonathan J.; Medicine, School of MedicineBackground: As the coronavirus pandemic progressed through the United States, Indianapolis Emergency Medical Services (IEMS) identified a gap between the health system capacity and the projected need to support an overwhelmed health care system. In addressing emergencies or special cases, each medical institution in a metropolitan area typically has a siloed process for capturing emergency patient records. These approaches vary in technical capabilities and may include use of an electronic medical record system (EMR) or a hybrid paper/EMR process. Given the projected volume of patients for the COVID-19 pandemic and the proposed multi-institutional team approach needed in case of significant provider illness, IEMS sought a simple, efficient, consolidated EMR solution to support planning for the potential capacity gap. IEMS approached Regenstrief Institute (RI), an established partner with experience in supporting OpenMRS, a global good EMR platform that had been deployed in multiple settings globally. Objective: The purpose of this project was to determine if OpenMRS, a global good, could be used to quickly stand up a system that would meet the needs for health emergency data collection and reporting. Design and implementation methods: The team used an "all hands on deck" approach, bringing together technical and subject matter experts, and a human-centered and iterative process to ensure the system met the key needs of IEMS. The OpenMRS Reference Application was adapted to the specific need and deployed as Docker containers to servers within the Indiana Health Information Exchange. Project outcomes and lessons learned: In less than two weeks, the Regenstrief team was able to install, configure and set up a working version of OpenMRS to support the desired electronic record requirements for the IEMS disaster field clinics. Using a human-centered approach, the RI team developed, tested, and released a user-friendly, installation-ready solution complete with an end user manual and a base support plan. IEMS and RI are sharing this approach to demonstrate how a global good can quickly generate a solution for COVID-19 and other disaster responses. Conclusions: Open source global goods can rapidly be adapted to meet local needs in an emergency. OpenMRS can be adapted to meet the needs of basic emergency medical services registration, triage, and basic data collection.