Not Even a Needle Goes Unaccounted For: The Three-Phase Evolution of DMAT's Deployment Inventory System

The Chiayi Disaster Medical Assistance Team (DMAT) is the core force behind Chiayi City’s response to major medical disasters. Earthquakes, typhoons, mass-casualty events — this team has to mobilize fast, get its supplies in order, and deploy the moment a call comes in.

Before the digital system was built, every pre-deployment prep cycle relied heavily on manual work: flipping through logbooks, checking quantities, verifying expiration dates, packing boxes. With supplies spanning hundreds of items — instruments needing function checks, consumables needing expiration verification, special medications needing individual counts — a single round of pre- and post-deployment supply prep often consumed a huge amount of manpower and time.

In 2021, DMAT approached Estab-Zenith to fundamentally change this process.

---

Phase 1: laying the paperless foundation

Phase 1 had a clear goal: digitize supply management first.

The core of a supply warehouse management system is, obviously, the supplies themselves — moving items in and out of inventory absolutely cannot be difficult. The system supports fast barcode-scanner-based check-in/check-out, so every item’s arrival time, storage location, and quantity status is fully recorded. Alongside this, the team built a tiered expiration alert mechanism — expired items are flagged in red, items nearing expiration in yellow — turning expiration-date management from manual memory into automatic system alerts.

The side navigation integrated four core module entry points — supplies, packing labels, storage locations, and deployment events — establishing the system’s structural skeleton for everything that followed.

---

The packing module solves the core pain point

After Phase 1 launched, the DMAT team fed back one core pain point: supply packing.

Every deployment’s supply combination varies dramatically depending on the nature of the mission. Earthquake search-and-rescue needs trauma-care consumables; infectious-disease response needs personal protective equipment; a mass-casualty event needs a full kit of intubation, first-aid, and transport equipment.

Previously, this “packing logic” existed entirely in the heads of experienced team members, with no systematic process backing it up.

Phase 2 redesigned the system around the packing module as its core:

The packing label system lets supplies be tagged and layered by mission scenario. Once a tag hierarchy is established, the system can automatically retrieve supplies that meet the criteria (including expiration-priority selection logic).

The deployment template feature lets DMAT pre-build scenario templates like “intubation kit,” “trauma response module,” and “earthquake disaster template.” Before deployment, staff simply select the mission type, and the system automatically generates the supply checklist and warehouse pick list. Once team members confirm quantities, packing is complete — dramatically cutting prep time.

---

Offline operation for extreme conditions

DMAT’s deployment scenarios sometimes take them to remote mountain areas, sites with damaged post-disaster infrastructure, or hospital internal networks. What these environments share in common: unreliable network access, sometimes none at all.

In Phase 3, Estab-Zenith built a local-network offline version of the system, packaging the full system into an environment that can run entirely on local hardware. Without relying on any external cloud service, the site team can still fully operate supply management, deployment check-in, and supply tracking with zero network access.

The offline version itself wasn’t the hard part — the real challenge was in the data handling details: once back on the network, changes made offline needed to sync seamlessly back into the live production system.

After this phase’s offline version was delivered and formally accepted, DMAT’s deployment inventory system officially achieved full-scenario adaptability.

---

Technical architecture

• Frontend framework: Vue.js + Nuxt.js + Vuetify
• Backend: Node.js
• Deployment model: cloud version + local-network offline packaged version
• Hardware integration: barcode scanner for inbound/outbound, label printer support
• Scope of work: UI/UX planning, system process design, multi-phase iterative development

---

The core lesson from this project

A deployment inventory system doesn’t need a huge feature list — what it needs is to stay simple and usable, even as the volume of supplies keeps growing.

When a DMAT team member opens the system before deployment, what they need to confirm is: “I can use this to find what I need, and what I find is correct.” That trust takes time to build, and it takes every single maintenance cycle not letting them down.

The three-phase development taught us that the real requirements of a complex system often only surface after it’s actually in use. Phase 1 solved the “can’t find it” problem — and only then did we learn that the packing process was the real pain point. Phase 2 solved prep efficiency — and only then did we learn that no network access on-site was another hurdle. Iterative development isn’t a sign that earlier planning wasn’t good enough — it’s because a user’s real needs only become clearer and clearer once the system actually exists.