Well, I'm glad that there's been a lot of discussion about the terminology issue, but my point wasn't just about terminology and communications standardization being a problem for the fire service. Without digressing, despite some of the very considerate and well expressed views pointed out by readers in the
Terminology blog I wrote, it is a problem- go back and look at the reports of any disaster that has happened in the last twenty years and you'll see that communications interoperability and terminology has been a consistent problem (the report I'm referring to I'm pretty sure was written by Professor Ben Aguirre from the Disaster Research Center, but I don't have it in front of me and I'll need to go find it - I'll link to it here when I do find it-
EDITOR NOTE: THIS WAS AN INCORRECT REFERENCE; THE REFERENCE IS ACTUALLY FROM THE ARTICLE "
LESSONS WE DON'T LEARN: A STUDY OF THE LESSONS OF DISASTERS, WHY WE...", BY AMY DONAHUE AND ROBERT TUOHY - GO TO THE LINK FOR MORE INFO), my point was actually about just agreement at all.
I'd like to paraphrase something Judge Thomas Kemmerlin, a respected jurist and law professor, said to me once: that standards and laws are like vultures; vultures may be ugly and cumbersome beasts, and we may not like them much, but they have an important job in that they clean up the messes left that otherwise would rot and cause disease and other problems. Likewise, we may not like standards and laws that tell us what to do, but these standards and laws were created to solve problems where people didn't do the right thing, and many would not be necessary if people would just talk to one another and use best practices instead of taking shortcuts and not using up-to-date information and skills.
Standardization is required for a certain number of issues; as a member of several national committees where standardization is always the hot topic for debate, my point is that you don't have to have some unattainable (and unreasonable) standard to make things uniform, but there should at least be a starting point that everyone can agree on that THIS standard defines something. I'm not in favor of standardization because I think we do things right all of the time and everyone else should "listen to me"; I'm in favor of knowing the definition of something and knowing how I can use that resource when I have a problem. Just as if we were working on a car and I said, "hand me a crescent wrench" and you handed me a pipe wrench, I might be able to make that work, but on the other hand, if I'm trying to get into a tight area, there's no way that tool will work.
I'll take something near and dear to my heart: NFPA 1006, as an example. To declare someone a Level 1 Rescue Technician in say, the auto/machinery extrication discipline, shouldn't require someone to have a degree in physics (I realize that's a little over the top, but bear with me). I happen to think that someone with that "title" should at least have things like some HAZMAT Awareness KSAs, fire suppression KSAs, some emergency medical stuff, etc. There ARE those who think that these people should all be at least EMTs but we agreed that this wasn't probably necessary for the minimum standard (and it isn't).
When there is, for some reason, the need for your fire department to cross over the line to visit my department for a major event, when I call for 10 "Level 1 Auto/Machinery Rescue Technicians", I should have a reasonable expectation that they have met a minimum standard. I think it is unreasonable to expect them all to be physics professors. If your department chooses to have physics professors as your minimum qualification, then good for you. But there needs to be a starting point (a REASONABLE starting point) and then we can call apples apples and oranges oranges.
The problem is that there are those out there in standardization land that only agree that it's their way or no way and that everything else is not acceptable. Do I believe that firefighters employed by Hilton Head Island Fire & Rescue should be required as condition of employment to be NREMT Basic or better? Yes, I do. Is that a reasonable expectation for everyone? Well, I personally think it is, but I'm realistic in agreeing that it is not. If I call for a firefighter from your jurisdiction, should I expect them to be NREMT-B or better? No, I should not expect that.
In operating at a few major disasters (and I have), I am always amazed at what comes into a staging area posing as a defined asset. My favorite one is the four guys and a pickup truck with a Hurst tool in back that was being defined as an Urban Search and Rescue Task Force. I saw a team of ten with four dogs saying they were a Task Force as well.
Yes, I am in full agreement that the NIMS initiatives are a strike in the direction of standardization in the emergency setting and yes, even though I'm against them, I think that some reasonable consideration could be applied to keeping some ten codes instead of wholesale elimination (I think everyone can agree 10-4 means "okay"), but the problem isn't just making everyone look and sound alike from a uniformity standpoint, it is more about knowing what to expect from someone who chooses to define their unit, their title, or whatever it is that needs defining, and what they are capable of as well as knowing how best to support that resource in an emergency.
You need to be a member of My Firefighter Nation to add comments!
Join My Firefighter Nation