All,
I am looking for an example, presentation, or other detail of setting up or testing a MESH to support a medical disaster. I have searched the forums and the net but not found anything. We want to approach 2 regional hospitals with the idea to link them via a mesh network and provide emergency services in an emcomm situation. Would like to show them an example of how it would work, what services could be provided, etc. Would be great to show if some other group has already set up a similar function.
Thanks in advance for any help,
Ron K7OPA
I am looking for an example, presentation, or other detail of setting up or testing a MESH to support a medical disaster. I have searched the forums and the net but not found anything. We want to approach 2 regional hospitals with the idea to link them via a mesh network and provide emergency services in an emcomm situation. Would like to show them an example of how it would work, what services could be provided, etc. Would be great to show if some other group has already set up a similar function.
Thanks in advance for any help,
Ron K7OPA
Here is the report:
A toxic chemical spill occurred at PPG on Pittsburgh Dr, in the Delaware industrial district.
End of report.
All you guys with mountains may snivel at our efforts to go just 2 miles, but believe me that trees are a way of life in much of America, and we have to struggle
to get thru them.
Subsequent testing showed that we could get good video thru one intermediate tower node, but not 2. And a water tower gave us a good reflected signal.
Bob W8ERD
Ron K7OPA
It's like any other IT support effort.
First thing I would do is get principles from both hospitals in a room together (very important) and get a list of requirements started.
Once you do that and bounce it against what you know you can provide, then you can craft a presentation that will not oversell your capabilities (also very important).
I'm an IT professional for a very large, if not the largest, supplier of computers and associated equipment in the world. If we didn't start with a really complete set of requirements when we initiate a project we'd be dead in the water.
I really would not use any kind of a generic presentation. This kind of thing should nearly always be tailored to the project at hand and the customer's needs.
It take a bit more effort but is well worth it. The customer gets what they need and you, importantly, come across as professionals.
I'd be happy to chat with you if you like.
Cheers!
Chuck...
Chuck Killian
WB6YOK
The Los Angeles Section of Amateur Radio Emergency Service ("ARESLAX") encompasses all of Los Angeles County, California, with its land area of more than 4000 square miles, and its more than 10 million residents. ARESLAX is the largest ARES Section, and the only one comprised of a single county.
As its primary mission, ARESLAX provides backup and emergency communications support to the Los Angeles County Medical Alert Center and almost 70 hospitals throughout the County, including virtually all "911 receiving" hospitals (those with emergency departments). ARESLAX is recognized as a formal component of the Los Angeles County Emergency Medical Services Agency Emergency Communications Plan.
The Los Angeles Emergency Communications Team ("LAECT") is a group of dedicated individuals committed to training and education related to emergency communications and management. LAECT works cooperatively with ARESLAX and, for various reasons, our mesh efforts are being led by LAECT. There is a significant overlap of participants between the two organizations.
At this time LAECT has its primary mesh installation at one hospital in Pasadena. From there we are linked to the Jet Propulsion Laboratory (W6JPL) and from there to Pleasants Peak, the Orange County mesh and beyond. We provide mesh access to much of Pasadena and surrounding cities from the hospital and a few other sites.
Whenever we have the chance, we demonstrate the AREDN mesh and the enhanced capabilities it can provide to other hospitals and government entities. Its a long and winding road. It has taken us well over a year working with the one hospital to establish our "hub". Installing permanent equipment at hospitals is a trying process, thanks to California oversight regulations. But we have great hope!
Because we are currently supporting the defined mission, we understand what is needed, and how we can improve using mesh networking. For our purposes we emphasize Winlink email for sending digital forms (using local Telnet post offices, in addition to full gateway access when appropriate), FTP for file transfer and VOIP to link various command centers.
Like many others, we have issues with trees. Our larger problem, however, is the terrain, consisting of the numerous hills and valleys created by eons of seismic activity. We are in earthquake country.
Gary, W6GSW
DEC, ARESLAX Northeast
KA6ECT Trustee
Michael
We continue to work on a simple connection between our rural hospital and a nearby (17miles) clinic. One concern is how to keep the use of the system simple but robust. We don't want to have to train local users on RMS Express or other apps if not necessary. One idea is to set up a local NAS on the mesh, with specific folders, where users can drag and drop files without having to understand a lot of 'ham stuff'. What is your opinion on this?
Ron K7OPA
They don't allow non-hospital equipment to be on the hospital LAN, so they'll have to "thumb-net" the file to the ham radio communications room, but they're OK with that for starters.
There really is two ways to do this in my mind. Each has advantages and disadvantages: I always see an operator needing to be present at the facility however to handle the system and ensure compliance.
Basically, the more you put on the served agency, the more training needs to be done by the way I figure it.
Served Agency operates the system:
Requires training of staff on how to properly use the features and programs. Includes training on how to recognize a program is non functional and the need to switch over or to contact the radio operator to resolve.
Takes load off radio operator to actually generate and handle the content and moves load to advise the served agency on how to send the content they need.
Radio Operator operates the system:
Puts load to generate and track content on the operator
Reduces training to served agency (training only needs to really be "how to give info to the operator" )
Personally I don't expect being able to train served agencies on to much, I personally anticipate that the operator will be doing most of the content, the advantage is at least now it can be done in text (important for medical as accuracy matters) and be done as a "Send and wait" instead of sitting down and trying to get a clear voice frequency.
How info gets to the operator can very, the served agency may setup an email account internally on their mails system for the operator. May have a desk of computers that allow staff to type up messages and they display to the operator (who can then decide does this go via voice, meshchat, winlink, etc) or maybe its ICS forms on paper, etc. The methods are endless, the point is it gets to the operator and they can get it out to the appropriate location.
A new group can negotiate those methods with their served agency, an existing group likely already has these in place and will continue "as is" I suspect.