Claim Missing Document
Check
Articles

Found 12 Documents
Search

Requirements for an EMR-Based Virtual Reality Application for PROLANIS Education: A Literature and Process-Mapping Synthesis Setya Wijayanta; Adhani Windari; Mochammad Arief Darmawan; Sylvia Anjani; Faik Agiwahyuanto
Jurnal Infokes Vol 16 No 2 (2026): Jurnal Ilmiah Rekam Medis dan Informatika Kesehatan
Publisher : Universitas Duta Bangsa Surakarta

Show Abstract | Download Original | Original Source | Check in Google Scholar | DOI: 10.47701/dx5mcf46

Abstract

Background: PROLANIS participants require repeatable chronic-disease education, while electronic medical records (EMRs) and virtual reality (VR) offer opportunities for personalized and interactive delivery. Before prototype development, requirements must reflect health literacy, workflow, privacy, and VR safety. Methods: This descriptive initial Research and Development stage used a literature- and document-informed requirements synthesis, a proposed PROLANIS process map, and minimum EMR data-element mapping for Sidorejo Lor and Sidorejo Kidul Community Health Centers, Salatiga City. No interviews, focus-group discussions, participant surveys, direct observations, or patient-level EMR extraction were conducted at this stage. Candidate requirements were organized into domains and provisionally prioritized using MoSCoW as design input requiring later stakeholder validation. Results: Five preliminary requirement groups were identified: concise chronic-disease education, EMR-based personalization, adult- and older-user accessibility, data security and confidentiality, and operational support for health workers. Proposed must-have functions include a patient education profile, simple visualization of examination results, and hypertension and diabetes modules. Non-functional requirements include simple navigation, large text, audio narration, seated mode, short sessions, stop/pause options, and role-based data access. Conclusion: The study provides an initial, literature- and process-mapping-based requirements model rather than empirically validated local user needs. Participatory co-design, stakeholder validation, usability testing, VR-safety assessment, data-governance review, and evaluation of patient understanding are required before implementation claims can be made
Design and Development of a Web-Based Disaster Health Information System Prototype for Medical Record and Health Information Students Mochammad Arief Darmawan; Pradita Ayu Fernanda; Isnaeni Anggun Sari
Jurnal Kecerdasan Buatan dan Teknologi Informasi Vol. 5 No. 3 (2026): September 2026 In progress.
Publisher : Ninety Media Publisher

Show Abstract | Download Original | Original Source | Check in Google Scholar | DOI: 10.69916/jkbti.v5i3.571

Abstract

Disaster-response documentation requires rapid linkage of victim, healthservice,logistics, and reporting data, while Medical Record and Health Informationstudents have limited access to disaster-specific learning environments.This study designed a web-based Disaster Health Information System prototypeas an educational simulation for disaster health information management.Requirements were synthesized from disaster-documentation needs, policy andstandards, prior literature, and intended student learning workflows; the studydid not report interview-, focus-group-, or questionnaire-based requirementselicitation and did not conduct respondent usability testing. An iterativeprototype cycle covered quick design, DFD/ERD modeling, interface development,and scenario-based design verification with synthetic display data. Theprototype established a role-based learning workflow that connects disasterevents with victim records, health services, urgent logistics, dashboard summaries,and crisis reporting. Design verification confirmed traceability amongmajor processes and seven core data entities, while interface evidence wasstrongest for login and dashboard functions; other modules were verified at thedesign-traceability level. The educational novelty is the structured simulationworkflow linking patient-level documentation with event-level logistics andreporting, rather than the individual use of dashboards, DFDs, ERDs, or rolebasedaccess. The prototype demonstrates a coherent learning-oriented designbut does not establish usability, performance, interoperability, or operationaleffectiveness.