Development of Mobile Platform Integrated with Existing Electronic Medical Records
2
조회
0
다운로드
1
인용
0
참고문헌
키워드
초록
Objectives: This paper describes a mobile Electronic Medical Record (EMR) platform designed to manage and utilize the existing EMR and mobile application with optimized resources. Methods: We structured the mEMR to reuse services of retrieval and storage in mobile app environments that have already proven to have no problem working with EMRs. A new mobile architecture-based mobile solution was developed in four steps: the construction of a server and its architecture; screen layout and storyboard making; screen user interface design and development; and a pilot test and step-by-step deployment. This mobile architecture consists of two parts, the server-side area and the client-side area. In the server-side area, it performs the roles of service management for EMR and documents and for information exchange. Furthermore, it performs menu allocation depending on user permission and automatic clinical document architecture document conversion. Results: Currently, Severance Hospital operates an iOS-compatible mobile solution based on this mobile architecture and provides stable service without additional resources, dealing with dynamic changes of EMR templates. Conclusions: The proposed mobile solution should go hand in hand with the existing EMR system, and it can be a cost-effective solution if a quality EMR system is operated steadily with this solution. Thus, we expect this example to be shared with hospitals that currently plan to deploy mobile solutions.
Abstract
Objectives: This paper describes a mobile Electronic Medical Record (EMR) platform designed to manage and utilize the existing EMR and mobile application with optimized resources. Methods: We structured the mEMR to reuse services of retrieval and storage in mobile app environments that have already proven to have no problem working with EMRs. A new mobile architecture-based mobile solution was developed in four steps: the construction of a server and its architecture; screen layout and storyboard making; screen user interface design and development; and a pilot test and step-by-step deployment. This mobile architecture consists of two parts, the server-side area and the client-side area. In the server-side area, it performs the roles of service management for EMR and documents and for information exchange. Furthermore, it performs menu allocation depending on user permission and automatic clinical document architecture document conversion. Results: Currently, Severance Hospital operates an iOS-compatible mobile solution based on this mobile architecture and provides stable service without additional resources, dealing with dynamic changes of EMR templates. Conclusions: The proposed mobile solution should go hand in hand with the existing EMR system, and it can be a cost-effective solution if a quality EMR system is operated steadily with this solution. Thus, we expect this example to be shared with hospitals that currently plan to deploy mobile solutions.
참고문헌 (6)
- Abraham C, "Ubiquitous access:on the front lines of patient care and safety", Commun ACM, 51(6), pp.95~99 (2008)
- "CDA Release 2" (2013)[URL]
- Muller M, "The Clinical Document Architecture (CDA)enables electronic medical records to wireless mobile computing", Stud Health Technol Inform, 107(Pt 2), pp.1448~1452 (2004)
- 우현식, "Hospital Wireless Local Area Network-Based Tracking System", Healthcare Informatics Research, 17(1), pp.18~23 (2011), 대한의료정보학회
- 여기호, "Pitfalls and Security Measures for the Mobile EMR System in Medical Facilities", Healthcare Informatics Research, 18(2), pp.125~135 (2012), 대한의료정보학회[DOI]
- Wu F, "A mobile clinical information system based on iPad", Proceedings of the 1st International Symposium on Future Information and Communication Technologies for Ubiquitous HealthCare, pp.1~4 (2013)