In the 5 years preceding the war, significant efforts were made to develop a digital casualty documentation system. This initiative sought to establish a network-based solution that integrated medical monitoring, data processing, and communication capabilities to facilitate information transfer throughout the evacuation chain and to support informed decision-making [8]. However, this system had not reached operational maturity as the war commenced. Consequently, there was an urgent need for a practical and immediate solution to replace the traditional paper casualty cards. To meet this need, the development of DCCS was guided by several key considerations to address the urgent operational demands.

A Minimal Viable Product approach was adopted, recognizing the solution’s ad hoc nature and limitations. In collaboration with civilian volunteers from an Israeli health care software company (K Health), a dedicated IDF-MC team developed DCCS to improve the accuracy and efficiency of field documentation. DCCS was built to streamline real-time data capture, enhance information transfer along the evacuation chain, and improve battlefield casualty care. To enable rapid deployment, the team focused on a simple, user-friendly application and deliberately excluded advanced features such as sensor integration and real-time data exchange between echelons. This Minimal Viable Product approach demonstrated that, with clear priorities, rapid feedback and tight collaboration between end users and developers, a functional field-ready product could be delivered within weeks, succeeding where more complex systems have often struggled.

The DCCS was designed as a simple, intuitive tool for documenting casualties in the field. Military-grade tablets run a dedicated application, which connect to a plastic near field communication (NFC) “dog tag” placed around the casualty’s neck by life support providers at the point of injury. The “dog tag” stores the digital record when direct tablet contact cannot be established. This allows medical teams at each echelon to record status and treatments, append follow-up information, and deliver a complete record to hospitals in Israel, supporting continuity and accuracy of care and data transfer.

Hospital data are then transferred to an information system that interfaces with the IDF-MC Trauma and Combat Medicine Branch and the IDF Trauma Registry (IDF-TR). Because of security, technical constraints, and the urgent rollout, hospital databases were not directly connected to the military network; so DCCS records had to be uploaded manually—a limitation expected to be resolved in future updates. Even without full integration, the DCCS already supports continuous learning, strengthens legal accountability through standardized records, reduces evacuation delays and data loss, and ensures that medical data travel with the casualty. Figure 1 presents a schematic overview of the DCCS workflow described above.

The DCCS hardware consists of military-grade, Android-based tablets, and plastic NFC “dog tags.” Because battlefield communication is tightly restricted, only an air-gapped platform was permitted; so, communication-disabled tablets were used solely for medical documentation. Compact and lightweight, they are equipped with NFC to transfer data to and from the digital “dog tags,” which serve as portable casualty records. Any compatible tablet can access and update the tag, ensuring that “data moves with the casualty” and that data are continuously added at each echelon of care. Tablets were also preloaded with manuals, educational materials, operational lessons, and clinical guidelines, exploiting the fact that they remain with frontline caregivers throughout deployment. The tablet and digital dog tag are shown in Figure 2.

The DCCS software was designed to be user-friendly. The application requires medical teams to enter comprehensive casualty data with minimal manual actions. By analyzing our data registries during casualty treatment, we sought to achieve a balance between capturing all clinically important information and ensuring that the documentation process would be practical under operational pressure. This required repeated refinement of the interface, prioritizing usability while preserving the critical data needed for continuity of care and future performance improvement. The application supports the documentation of vital signs, treatments, and medical procedures administered to the casualty, along with patient identification, details of the medical team on the scene, and specifics of the injury, such as the mechanism, affected anatomical areas, and bodily systems involved.

The manual data entry process was designed to be highly intuitive and touchscreen-based to enhance usability. For example, clinicians can indicate injured areas on a graphical representation of the human body and select options from predefined multiple-choice lists, rather than inputting text manually. This approach is intended to streamline and shorten the time of data entry, reduce errors, and improve the efficiency and accuracy of medical documentation. However, some data such as vital signs must still be entered manually as text. Figure 3 presents the user interface of DCCS.

Within 2 weeks of the project's initiation, the first version of the system entered the implementation process as a pilot with various MEDEVAC units, ground forces MEDEVAC units, and aeromedical evacuation unit. This pilot phase followed an agile methodology, allowing for iterative development and refinement based on feedback.

A designated instructor from the development team oversaw DCCS deployment. He visited frontline units and bases, provided on-site, hands-on training, and demonstrated practical use of the system. Each unit received structured instruction, and feedback from the field was relayed to Trauma and Combat Medicine Branch and developers for rapid refinement. Medical staff were encouraged to practice independently to gain proficiency under battlefield conditions. In parallel, dedicated training teams at the IDF Military Medicine Academy and other facilities integrated DCCS into formal curricula, addressing a long-standing gap in emphasizing documentation and reinforcing its clinical and operational importance. By embedding DCCS training within medical education, the initiative sought to instill a deeper understanding of the clinical and operational importance of proper documentation. Initially, 2 previous configurations of the DCCS were developed but subsequently upgraded due to negative feedback. The 3 different versions and their key features are described in Table 1.

Throughout this process, feedback was actively sought from the medical staff across various IDF units. Their suggestions and critiques were invaluable, and they were integrated into subsequent updates to further refine and improve the DCCS. For example, QR code scanning for data transfer between tablets proved too time-consuming and cumbersome under combat conditions, requiring precise alignment and slowing down patient handoff. Version 2 integrated NFC for faster data transfer, but it still required proximity, creating delays and increasing risk under fire. Based on these limitations, version 3 was developed, utilizing an NFC-enabled memory chip embedded in a plastic dog tag, which was placed on casualties upon reaching them. This innovation allowed the data to “move with the casualty,” ensuring access to medical information at all levels of care without requiring device-to-device interaction, significantly improving efficiency and safety in the field. Such continuous feedback loop was therefore crucial in tailoring the system to real operational needs, ensuring its functionality and usability in real-world conditions (Figures 4-5).

The data presented are registry-based from the IDF-TR. The IDF-TR is a web-based digital prehospital trauma registry, relying on data from point-of-injury casualty cards (DCCS), after-action reports, and data entry by on scene and en route providers. It contains data collection, including event type, age, sex, mechanism of injury, type of injury, outcome, medical treatment, and type of evacuation.

Categorical variables are presented as frequencies and percentages, with continuous variables as medians and interquartile ranges (IQRs). Statistical analyses were performed using R software (version 4.2.1; R Foundation for Statistical Computing).

The rapid development of the DCCS progressing through 3 functional versions within weeks was not merely a technical achievement but a reflection of an exceptional sense of urgency, organizational culture, and leadership support. The outbreak of war created a powerful sense of immediacy that helped to overcome the typical pace of organizational processes. It enabled the team to make fast, pragmatic decisions, accept trade-offs where necessary, and mobilize key personnel, including volunteers and external experts. Crucially, the IDF-MC senior leadership recognized the system's potential early on, granted operational freedom, and actively supported its deployment when needed. The project was led by a dedicated professional team, with high-level organizational support playing a crucial role in aligning resources, removing barriers, and driving the system’s implementation.

Given this urgency, the DCCS was designed as a quick, “low-tech,” and simple solution for easy implementation during an ongoing war. Previous efforts to develop systems incorporating sensors, automatic data capture, and transmission proved infeasible for rapid development and deployment under the given conditions. Consequently, a major limitation of the current system is its reliance on manual data entry—keeping the “man in the loop” introduces the potential for human error and inconsistencies.

Low compliance with prehospital documentation is likely multifactorial. Although a limited awareness about the importance of documentation is a probable contributor, it is not the sole cause. Prehospital medical teams often must perform several tasks simultaneously, sometimes under hostile conditions. These tasks demand significant time and workforce, making documentation one of the first tasks to be neglected, as it may detract from the ability to provide immediate care. However, evidence suggests that mobile apps can significantly enhance documentation practices in deployed environments. Kenney et al [9] demonstrated that user-friendly mobile apps have the potential to improve the completeness, accuracy, and speed of casualty care documentation, even with minimal additional training.

Despite the introduction of DCCS, documentation remains a manual task, now digital rather than paper-based; so, the underlying human factors driving low compliance are not yet fully resolved. DCCS is intended to simplify completion of casualty cards and improve the consistency, completeness, and clinical use of data along the evacuation chain. Accurate documentation also has a crucial legal role: it supports accountability; demonstrates adherence to international standards, Israeli law, and the Geneva convention; and provides clear evidence of care, thereby protecting both patients and providers.

Future development should prioritize on reducing manual data entry by integrating real-time data feeds from monitors and devices, allowing clinicians to concentrate on direct care while improving accuracy and consistency. Speech-to-text solutions powered by generative artificial intelligence could further streamline documentation by enabling hands-free, voice-based recording during treatment. This remains technologically challenging, with few reports from prehospital environments and none from combat settings. Recent work on passive-sensor–based automated documentation in simulated combat casualty care nevertheless suggests a path toward eventual speech-to-text integration [10]. Alignment of these tools with IDF-MC protocols could also provide real-time decision support for critical situations, ultimately enhancing documentation efficiency, care quality, and patient outcomes.

Enhancing DCCS interoperability with other medical and logistical systems could further improve continuity and quality of care. In network-enabled environments, integration with hospital electronic health records, telemedicine platforms, and related systems would allow seamless information flow from point of injury to definitive care. Such integration would also give command and control centers real-time visibility of force health and support more accurate tasking of evacuation assets.

Electronic health record connectivity could help hospitals anticipate incoming casualties, prepare staff and resources, reduce turnaround times for teams and ambulances, and potentially enable automatic billing. Longitudinal studies are needed to assess the long-term effects of digital documentation on patient outcomes, training, and operational efficiency. Sustained success will depend on continuous user feedback, iterative refinement based on field experience, and ongoing technological advances that open new applications and opportunities.

The report's limitations include incomplete data capture due to the reliance on manual entry and variability in the completeness of after-action reports. Since the data documented on DCCS for each patient are manually entered into IDF-TR, the presented data do not fully represent all casualties reported via the system at the time of writing, as some records have not yet been entered into the registry. Additionally, the report is limited to the context of a specific conflict and geographic region, which may affect the generalizability of the findings to other military or civilian settings. The rapid implementation and scaling of the system may have led to variations in training and familiarity among users, potentially impacting the consistency and accuracy of the data collected.

This project serves as proof of concept for a digitized field medical documentation system, streamlining information transfer between levels of care and ensuring data integrity. The deployment of DCCS during an ongoing war demonstrated substantial improvements in both documentation rates and the quality of data collected in the field compared to traditional paper-based methods. Beyond the technological innovation, the project also reflects an organizational and cultural success: it was driven by a clear sense of urgency, decisive leadership, and a structured, focused, and adaptive development process. The key to its success was a willingness to compromise where necessary, seize emerging operational opportunities, and maintain consistent collaboration between headquarters and field units. DCCS stands not only as a technological achievement but as a model of how mission-driven innovation can be embedded even in complex situations under and during pressure.