We’ve got good news for the billions of people
that can’t call a reliable number like 911
to get help for critical emergency medical conditions.

mHealth

Text Message-based
Emergency Medical Dispatching

“9-1-1 where there is none”

About Beacon

BEACON is an open-source text message-based emergency medical dispatching platform designed by Trek Medics International, and developed specifically for communities where consistent ambulance response is not available. By relaying text messages from the scene of an emergency to trained responders throughout the community, Beacon enables the nearest available emergency care providers to quickly locate, treat, and transport emergency victims to local hospitals.

A Need For Urgent Innovation
Right now there are 4-5 billion mobile phone subscribers in the developing world who have no way to call for help in the event of an emergency using a number like 9-1-1. Yet, according to the World Bank, “Nowhere is the demand for efficient communication and rapid transportation more critical than in emergency medical care.”[i]

About The Software
Developed in partnership with Vision Point Systems (Blacksburg, VA), Beacon mimics dispatching technologies used in developed countries, yet utilizes an emphasis on over-the-top  implementation to offer a cost-effective solution that’s both scalable and sustainable for resource-limited health systems.

Additional Features:

  • Low-tech set-up — A single internet connected-device is required to launch
  • Universal accessibility — Can be used on any mobile phone, whether smartphone or feature phone, with or without internet connectivity for daily operations
  • Easy-to-use interface — Text message interactions require minimal input, are easily followed and predictable; responsive Admin and Dispatch interface makes platform accessible from any smartphone
  • Automated control – After creating the initial alert, all resource coordination is automated, eliminating the need for dispatchers to micromanage individual resources
  • Low-maintenance operations — No need to download apps or worry about updates; just register the Responder’s mobile phone number and they’re ready to go
  • Modular architecture for easy customization — Beacon v2.0 has been re-built using a modular architecture to enable custom changes to message content and response sequence workflow
  • Remote access or local installation — The Beacon platform is open source and freely available. However, not everyone has software programmers on staff, so we can make Beacon available to you at a nominal cost via access to our remote servers. For installation on local servers, we’re also available to discuss more

[i] Kobusingye O, Hyder A, Bishai D, et al. “Emergency Medical Services.” In: Jamison D, ed. Disease Control Priorities Project. 2011 Chap. 68, p.1261–1279.

Read about the different ways you can use Beacon
to improve emergency medical care anywhere.

Prehospital Emergency Care
Prehospital Emergency Care9-1-1 where there is none
mch
Maternal Child HealthConnecting labor to delivery
referral
Inter-Facility Transfer NetworksManage patient flow
Outbreak map splash_IMG
Disease OutbreakStay ahead of the epidemiological curve
RTI wp
Road Traffic InjuriesImmediate post-crash care
Tent City_HAI_IMG
Disaster Response & RecoveryManagement tools for austere deployments
© Dorine Van Ophalvens
DisabilityInclusive access to inclusive services

How Beacon works

BEACON SENDS >

Beacon

STEP 1. INITIAL ALERT

beacon2.0 msg1_eng_initial alert_web-img

RESPONDER REPLIES "8"

cabs

“8” = estimated time of arrival

BEACON SENDS >

Beacon

STEP 2: CONFIRM ARRIVAL ON-SCENE

beacon2.0 msg2_eng_proceed to location_web-img

RESPONDER CONFIRMS "1"

cabs

“1” = Patient located

BEACON SENDS >

Beacon

STEP 3: CONFIRM ADDITIONAL RESOURCES

beacon2.0 msg3_eng_addtional resources_web-img

RESPONDER REPLIES "0"

cabs

“0” = No additional vehicles necessary
(“2 FRs” = two first responders en route)

BEACON SENDS >

Beacon

STEP 4: CONFIRM HOSPITAL TRANSPORT

beacon2.0 msg4_eng_confirm transport_web-img

RESPONDER REPLIES "1.2.20""

cabs

“1” = Transport destination: St. Stephen’s hospital
“2” = Number of patients being transported FRs
“20” =Estimated time of arrival (in minutes)

 

[*This message and information is also relayed to the receiving hospital]

BEACON SENDS >

Beacon

BEACON SENDS >

Beacon

STEP 5: CONFIRM HOSPITAL ARRIVAL

beacon2.0 msg5_eng_confirm arrival_web-img
Response times are for illustration only

RESPONDER CONFIRMS "1""

cabs

“1” = Arrived at destination hospita

 

A summary of the response times is sent upon completion of the incident.

Beacon v2.1 developed with generous funding from:

google.org_

And in collaboration with:

VisionPointSystems-logo-box
What can Beacon do for you?

Send us an email about how you think Beacon might be able to help your service.

Not readable? Change text.