VortexQL
VortexQL is ArdentMC’s cloud-based, emergency management message routing system. VortexQL provides data aggregation, data publishing, and data GIS transformation of emergency management information for the first responder community.
Challenge
VortexQL is not only supposed to be the API gateway for the Responder Cloud toolset, but should also be a sure-fire way for developers, responders, and dispatchers to look up, locate, and add-in incidents, reports, and resources. While commonly APIs are only used in development cases, VortexQL provides the option for end-to-end transperancy for all users in a responder scenario to access. VortexQL needs to display large amounts of information to the user without being overbearing and confusing. VortexQL’s API integrates directly with Swagger to help with functionality. WatchTower also has the capability of displaying VortexQL on any mobile device when the user chooses to “View More Details” about a point on the map.
1.
2.
3.
Identifying the type of pre-hospital event, as well as discerning and assigning the closest and most appropriate response resources.
Routing to the correct emergency medical facilities; sometimes the closest hospital may be full, or may be inaccessible because of traffic or damage.
Effectively communicating information about an event to the next level of care (medical facilities)
EMT
User Research
While VortexQL is primarily an API gateway, it is also designed to help users find more definitive details about an event or resource that may not be deemed important within the incident, but could be beneficial in post-incident reporting.
Dispatcher
Often operating in poor weather and lighting, and with high potential for personal physical over-stress.
Dealing with reduced dexterity in restrictive personal protective equipment (PPE), including wearing heavy equipment that changes balance and center of gravity and gloves that preclude easy manipulation of device screens or buttons.
Developers
Clean, clear, and user friendly. No guessing game as to where a developer can find proper documentation.
Represent client use of the API for multiple client technologies, including cURL and the most popular programming languages in use by web and native client developers.
The API Reference section documents each and every endpoint: HTTP routes, input requests, output responses, and what each domain object and its attributes mean.
Responder
In a debriefing situation, responders need to be able to pull up all information of an event for documentation.
Information should be displayed legibly and divided out amongst categories for easy to find information.
Systems should be easy to adapt to and understand with little or no prior knowledge of programming.
Analysis
First responders are often unfamiliar with API gateways and how their supposed to be used, leaving for many questions left unanswered. VortexQL would often be used in a back-end development situation, but we didn’t want to limit our responders to not being able to access information. Our goal was to create an API system that is functional at a base-level and reduce cognitive load.
Wireframes
VortexQL is designed mainly for a desktop, but first responders often have to access the API through their mobile devices when they are responding in the field. The main layout goal is to create a system that responds easily on all interfaces.
VortexQL Home Page
Query
Query Home
New User Profile
New Device Sender
New Agency
Submit
Submit
Submit
Confirm
Added to
Database
API Lookup
VortexQL integrates with Swagger Custom API for easy access to information. Users are able to obtain a LookupID from the dashboards or mobile application to use in different lookup scenarios. Users are also able to use the Query tab to find LookupIDs to navigate and create commands through the API.
Query
Copy
LookupID
API
Swagger API
GET
DE Lookup
Product Screens
Outcomes
VortexQL supports over 500 calls being made every minute across multiple tools and platforms. Responders are able to access information regarding incidents on virtually any machine with ease and no stress.
500+
Calls Every
Minute
Can Support
10,000
Users
50+
Supported
Hospitals
700
Current
Data
Senders