EDIS© - Further Information

Software Design

The EDIS system is built using open standard technologies and platforms. The base platform for the server "back end" is Linux, a stable, mature and well supported platform with an excellent record in performance and security. The handset software is built upon Android (itself built upon Linux) which has the added benefit of a large choice of handset form-factor. Apple iOS support is not implemented currently and would be subject to sufficient demand.

EDIS is accessible from EDIS handsets registered in a given installation and to computer-based terminals via a secure web-browser interface. Communication to the EDIS system from handsets or terminals can be via open (internet-based) or closed data networks. In either case connectivity to the server can be secured using industry standard SSL and certificate-based transport layer encryption, although this is not implemented currently. Security requirements will likely change from one installation/organisation to another so we have not engineered a particular solution.

We have designed the system with the following goals:

  • Simple. Requires minimal training and configuration. Handsets could either be pre-configured and deployed at the point of need, or configuration could take place ad-hoc, for example on authorised users' existing mobile phones.
  • Intelligent. The EDIS engine adapts seamlessly to the availability of the server, data connectivity and GPS for geo-tagging. EDIS data interchange can be delayed by lack of connectivity without affecting the resulting data held or audit trail when connectivity eventually occurs.
  • Robust. The system is designed to cope and offer benefit even when mobile networks and data connectivity are unavailable. In addition, the Android mobile platform guarantees the best possible choice of hardware for different deployments. Eg. handsets can be ruggedised, waterproof, can have extended battery performance, high-gain antennae and be of virtually any size.
  • Fast. The system has been designed to remain as responsive as possible in any given situation, and the handset operates using a finger-friendly interface that's been designed to minimise "fiddliness". Usability considerations for the needs of the target audience take precedence over "eye-candy".
  • Flexible and Adaptable. EDIS currently exists as a core technology, a working proof-of-concept that's designed to grow into the needs of particular applications and deployments. Choices of development platforms and strategies have been made to allows EDIS to grow into particular requirements with minimal rework.
  • Modular and Expandable. Features of EDIS will be added per requirements of a given application or organisation. Some will be specific to the handset eg. system security, data fields etc., while others will pertain to the PC/laptop-based administration side eg. reporting, analysis and enquiry tools. Both sides of EDIS can be expanded modularly through software extension.
  • Scalable. The typical model of an EDIS installation is many handset, one server. But by design, "server" refers to a virtual rather than a physical entity, so the "server" can be a load-balanced cluster operating across several datacenters. EDIS can theoretically be upscaled from a single organisation all the way up to national or beyond.

Target Users

  • Hospital Emergency Managers
  • Chief Executives of UK Ambulance Service Trusts
  • Senior Clinicians in A&E
  • Police Service Chief Officers
  • Immediate Care Clinicians
  • FEMA Operational Directors
  • Senior Officials Responsible for Emergency Management
  • Red Cross/Red Crescent Emergency Response Managers
  • Fire & Rescue Services Response Managers
  • Coroners and Coroner's Officers
  • Paramedics and Technicians
  • Police Officers
  • Local Authority Emergency Managers
  • Military support to civilian emergencies/National Guard