Protocopedia - Recent changes [en]

IMS

Jonesk — Fri, 03 Apr 2026 15:39:28 GMT

← Older revision		Revision as of 15:39, 3 April 2026
(One intermediate revision by the same user not shown)
Line 40:		Line 40:
	\|January 1, 2026		\|January 1, 2026
	\|}		\|}

			== Section 2 - Operations ==


			== Section 3 - Special Hazards Operations ==


			== Section 4 - Safety ==


			== Section 5 - Fire Cause Investigation ==


			== Forms / Checklists ==

1.3 Area Command

Jonesk — Fri, 03 Apr 2026 12:13:26 GMT

← Older revision		Revision as of 12:13, 3 April 2026
(2 intermediate revisions by the same user not shown)
Line 8:		Line 8:
	Multiple simultaneous alarms with implementation of the Incident Management System in the same geographical area. The complexity and span or control of an incident warrants. Critical lifesaving or property values are at risk, and incidents are utilizing limited resources. The incidents will continue into the next operational period.		Multiple simultaneous alarms with implementation of the Incident Management System in the same geographical area. The complexity and span or control of an incident warrants. Critical lifesaving or property values are at risk, and incidents are utilizing limited resources. The incidents will continue into the next operational period.

	<div style="margin-left: 2em;">'''Location:''' Area Command Post</div>		<div style="margin-left: 2em;">'''Location:''' Area Command Post
			</div>

	<div style="margin-left: 2em;">'''Recommended Staffing:''' Most qualified in management of large complex incidents with respect to their functional areas</div>		<div style="margin-left: 2em;">'''Recommended Staffing:''' Most qualified in management of large complex incidents with respect to their functional areas
			</div>

	<div style="margin-left: 2em;">'''Reports To:''' Agency Administrations</div>		<div style="margin-left: 2em;">'''Reports To:''' Agency Administrations
			</div>

	==== Procedure ====		==== Procedure ====

IMS

Jonesk — Fri, 03 Apr 2026 12:07:11 GMT

← Older revision		Revision as of 12:07, 3 April 2026
Line 24:		Line 24:
	\|1.3		\|1.3
	\|[[1.3 Area Command\|Area Command]]		\|[[1.3 Area Command\|Area Command]]
	\|~~January1~~, 2017		\|January 1, 2017
	\|		\|
	\|January 1, 2026		\|January 1, 2026
Line 30:		Line 30:
	\|1.4		\|1.4
	\|[[1.4 Unified Command\|Unified Command]]		\|[[1.4 Unified Command\|Unified Command]]
	\|~~January1~~, 2017		\|January 1, 2017
			\|
			\|January 1, 2026
			\|-
			\|1.5
			\|[[1.5 Incident Commander\|Incident Commander]]
			\|January 1, 2017
	\|		\|
	\|January 1, 2026		\|January 1, 2026
	\|}		\|}

1.5 Incident Commander

Jonesk — Fri, 03 Apr 2026 12:06:53 GMT

Created page with "==== Purpose ==== The Incident Commander (IC) provides comprehensive leadership and management to the response effort. The position is the focal point of all facets of the operation consistent with the Incident Management System. ==== Responsibilities ==== The IC is ultimately responsible for all incident response activities including development and implementation of an Incident Action Plan (IAP) plan to stabilize the incident, make decisions and issue orders for effi..."

New page

==== Purpose ====
The Incident Commander (IC) provides comprehensive leadership and management to the response effort. The position is the focal point of all facets of the operation consistent with the Incident Management System.

==== Responsibilities ====
The IC is ultimately responsible for all incident response activities including development and implementation of an Incident Action Plan (IAP) plan to stabilize the incident, make decisions and issue orders for efficient and effective utilization of resources. The IC must process information and cues obtained through radio transmissions, face to face reports, and observations from a variety of sources and relay and receive same from Section Chiefs and Command Staff operating within their span of control. '''It is recognized that the IC may not have knowledge of unique or specialized operations (i.e. confined space, hazmat, etc.) and thus may utilize group or division leaders who are technical specialists to aid in command and control of the incident.''' '''It is therefore imperative that their role be confined to managing the alarm and resources required.'''

==== Activation ====
Any situation requiring four or more units where, in the judgment of the on-scene ranking officer, the Incident Management System (IMS) should be implemented for concerns of safety for personnel, management of resources, and scene control.

<div style="margin-left: 2em;">'''Location:''' On Scene at Command Post</div>

<div style="margin-left: 2em;">'''Recommended Staffing:''' First arriving Fire Department officer until relieved by higher authority</div>

<div style="margin-left: 2em;">'''Reports To:''' Final Authority</div>

==== Procedure ====

* Arrive on the scene and establish or assume command; obtain incident briefing previous IC.
* If not previously established, identify command name (“4th Avenue Command”), report command post location and establish A (Alpha) side.
* Assess the incident situation and conduct an initial strategy briefing with the current operation command personnel.
* Activate the elements of the IMS appropriate for management of the incident.
* Brief Command Staff and primary Section Chiefs.
* Participate in the preparation and authorize the implementation of an (the) Incident Action Plan (IAP).
* Determine conditions and needs to make informed command decisions and transmit incident objectives to command staff.
* Coordinate primary IC Staff activities.
* Manage overall incident operations and resource utilization.
* Approve requests for and utilization of additional resources.
* Authorize release of information to the media.
* Ensure the incident status form (worksheet) or command board is utilized and completed. Ensure that proper forms are available and utilized by section and group leaders.
* Obtain briefings from Section Chiefs, Command Staff, and agency representatives on incident management issues and/or concerns.
* Obtain information on environmental issues and/or concerns.
* Review the progress of the incident and direct organizational efforts towards higher priority tasks.
* Ensure that safety procedures are utilized and followed by all personnel.
* Approve plan for demobilization of resources and return to normal operating status.
* Prepare a final incident summary for media briefing, reports, etc.
[[IMS|back to IMS]]

Incident Management System Organization

Jonesk — Fri, 03 Apr 2026 11:52:58 GMT

← Older revision		Revision as of 11:52, 3 April 2026
(One intermediate revision by the same user not shown)
Line 21:		Line 21:
	** Liaison Officer		** Liaison Officer
	** Incident Command Aide		** Incident Command Aide
			[[IMS\|back to IMS]]

IMS

Jonesk — Fri, 03 Apr 2026 11:50:27 GMT

← Older revision		Revision as of 11:50, 3 April 2026
Line 24:		Line 24:
	\|1.3		\|1.3
	\|[[1.3 Area Command\|Area Command]]		\|[[1.3 Area Command\|Area Command]]
			\|January1, 2017
			\|
			\|January 1, 2026
			\|-
			\|1.4
			\|[[1.4 Unified Command\|Unified Command]]
	\|January1, 2017		\|January1, 2017
	\|		\|
	\|January 1, 2026		\|January 1, 2026
	\|}		\|}

1.4 Unified Command

Jonesk — Fri, 03 Apr 2026 11:50:11 GMT

Created page with "==== Purpose ==== A Unified Command links the responding organizations to the incident and provides a forum for these agencies to make consensus decisions. The Unified Command establishes a common set of incident objectives and strategies while Incident Commanders continue to carry out their respective agency’s jurisdictional responsibilities. ==== Responsibilities ==== The overall management of an incident. The Unified Command will develop overall objectives and stra..."

New page

==== Purpose ====
A Unified Command links the responding organizations to the incident and provides a forum for these agencies to make consensus decisions. The Unified Command establishes a common set of incident objectives and strategies while Incident Commanders continue to carry out their respective agency’s jurisdictional responsibilities.

==== Responsibilities ====
The overall management of an incident. The Unified Command will develop overall objectives and strategies. The Unified Command will have ultimate approval of all resources. Unified Command is intended to be a ‘decision by committee’. If a decision cannot be agreed on by the Unified Command, the Unified Command member with the most jurisdictional responsibility will be deferred to for the final decision.

Unified commands with routine agencies such as law enforcement, other fire departments, and management teams from private entities shall be established using a streamline process to prevent delays in operations activities with the goal of hazard mitigation.

==== Activation ====
When an incident affects the jurisdictional or statutory responsibility of more than one agency. The incident is multijurisdictional and without a common system or organizational framework.

<div style="margin-left: 2em;">'''Location:''' Incident Command Post</div>

<div style="margin-left: 2em;">'''Recommended Staffing:''' Top management personnel from Agencies having Jurisdiction (AHJ). Non-government responders and private industries when an incident affects their facilities.</div>

<div style="margin-left: 2em;">'''Reports To:''' Authority having Jurisdiction (AHJ)</div>

==== Procedure ====

* Agreement by Authority having Jurisdiction for a Unified Command to be established.
* Selection of members to the command determined by specifics of the incident.
* Establish a Unified Command and obtain an incident briefing from the previous Incident Commander.
* Establish a Unified Command Post that is Co-Located with all Unified Command Personnel; consider use of Mobile Command Vehicles.
* If needed, fill the Command staff positions. There should be only one Operations Section Chief to oversee Branch directors from each discipline.
* Assess the incident situation and conduct a strategy meeting with members of the Unified Command.
* Prepare one set of Incident Objectives based off of all unified discipline strategies.
* Brief the Command Staff and primary Section Chiefs.
* Prepare and approve an Incident Action Plan.
* Determine needs to make informed command decisions and relate these needs to the command staff.
* Manage overall incident operations.
* Consider a joint staging area for incident resources.
* Coordinate primary staff activities.
* Approve requests for and utilization of extended resources.
* Authorize release of information to the media. Establish a Joint Information Center (JIC) for PIOs and Media if size of incident warrants.
* Ensure the incident status form (worksheet) or command board is utilized and completed. Ensure that proper forms are available and utilized by section group leaders.
* Obtain briefing from Section Chiefs, Command Staff and agency representatives on management concerns.
* Obtain information on environmental concerns.
* Review the progress of the incident and channel organizational efforts towards highest priority tasks.
* Ensure that safety procedures and disciplines are practiced and maintained by all personnel.
* Approve plan for demobilization and return to normal operating status.
* Prepare final incident summary for media briefing, reports, etc.
[[IMS|back to IMS]]

1.3 Area Command

Jonesk — Fri, 03 Apr 2026 11:36:35 GMT

← Older revision		Revision as of 11:36, 3 April 2026
Line 39:		Line 39:
	* Maintain log of major actions/decisions.		* Maintain log of major actions/decisions.
	* Prepare a final incident summary.		* Prepare a final incident summary.
			[[IMS\|back to IMS]]

IMS

Jonesk — Fri, 03 Apr 2026 11:35:24 GMT

Section 1 - Command Operations

← Older revision		Revision as of 11:35, 3 April 2026
Line 22:		Line 22:
	\|January 1, 2026		\|January 1, 2026
	\|-		\|-
			\|1.3
			\|[[1.3 Area Command\|Area Command]]
			\|January1, 2017
	\|		\|
	\|		\|January 1, 2026
	\|
	\|
	\|
	\|}		\|}

1.3 Area Command

Jonesk — Fri, 03 Apr 2026 11:35:13 GMT

Created page with "==== Purpose ==== Oversee the management of incident(s), focusing on strategic assistance, direction, and resolving competition for resources. This position does not supersede any Incident Commanders or Unified Commands but supports and provides strategic direction. ==== Responsibilities ==== The overall direction and setting of priorities for Incident Management Teams (IMTs) assigned to incidents in close proximity or large complex incidents. This includes ensuring tha..."

New page

==== Purpose ====
Oversee the management of incident(s), focusing on strategic assistance, direction, and resolving competition for resources. This position does not supersede any Incident Commanders or Unified Commands but supports and provides strategic direction.

==== Responsibilities ====
The overall direction and setting of priorities for Incident Management Teams (IMTs) assigned to incidents in close proximity or large complex incidents. This includes ensuring that conflicts are resolved, that incident objectives are established, and that strategies are selected for the use of critical resources. The Area Commander has the responsibility to coordinate with local, state, federal, and volunteer assisting and/or cooperating organizations.

==== Activation ====
Multiple simultaneous alarms with implementation of the Incident Management System in the same geographical area. The complexity and span or control of an incident warrants. Critical lifesaving or property values are at risk, and incidents are utilizing limited resources. The incidents will continue into the next operational period.

<div style="margin-left: 2em;">'''Location:''' Area Command Post</div>

<div style="margin-left: 2em;">'''Recommended Staffing:''' Most qualified in management of large complex incidents with respect to their functional areas</div>

<div style="margin-left: 2em;">'''Reports To:''' Agency Administrations</div>

==== Procedure ====

* Arrive in area and establish Area Command.

* Establish appropriate location for the Area Command facilities, consider Mobile Command Center Vehicle.
* Notify the Incident Commanders covered by the Area Command.
* Activate the elements of the area command needed to manage the incident(s) via Branch Commanders. (Planning, Logistics, Aviation, Tech Specialists, etc.)
* Review objectives and strategies for each incident, including expectations of Agency Administrators, concerns, or restraints.
* Assess the incident situation; establish priorities and objectives for the overall command.
* If operating as a Unified Area Command, develop working agreement for how Area Commanders will function together.
* Determine and assign an appropriate Area Command team. A small team is more manageable.
* Identify and allocate critical resources to best meet the needs of Area Command.
* Consider establishing an Area Command Staging Area / Mobilization Center to pool resources prior to allocation to area incidents or individual staging areas.
* Obtain incident briefing and IAP’s from Incident Commanders (as appropriate).
* Assess incident situations prior to strategy meeting.
* Brief the Area Command Staff and IMT, if established.
* Determine need for an assigned Technical Specialists to support Area Command.
* Participate in the preparation and authorize the implementation of the Incident Action Plan (IAP).
* Develop an operating guide for the Area Command staff.
* Prepare for additional operational cycles.
* Establish PIO or, if needed, Joint Information Center (JIC).
* Review the progress of the incident and channel organizational efforts towards highest priority tasks.
* Approve overall plan for demobilization and return to normal operating status.
* Maintain log of major actions/decisions.
* Prepare a final incident summary.

1.2 Organization / Command Structure

Jonesk — Fri, 03 Apr 2026 11:13:39 GMT

← Older revision		Revision as of 11:13, 3 April 2026
(One intermediate revision by the same user not shown)
Line 1:		Line 1:
	[[File:1.2 Regular Response.png\|center\|640x640px]]		[[File:1.2 Regular Response.png\|center\|640x640px]]

			=== <div style="text-align: center;">Expanding or Moderate Structure Fire, HazMat Incident, or EMS Response</div> <div style="text-align: center;">(to include multiple alarm responses)</div> ===
			[[File:1 2 Exanding Struture Fire.png\|center]]


	[[File:~~1 2 Exanding Struture Fire~~.png\|center]]		=== <div style="text-align: center;">Major Inciddent</div> ===
			[[File:Major Incident.png\|center]][[IMS\|back to IMS]]

File:Major Incident.png

Jonesk — Fri, 03 Apr 2026 11:01:03 GMT

Jonesk uploaded File:Major Incident.png

New page

Major Incident

IMS

Jonesk — Wed, 01 Apr 2026 20:46:03 GMT

← Older revision		Revision as of 20:46, 1 April 2026
Line 17:		Line 17:
	\|-		\|-
	\|1.2		\|1.2
	\|[[Organization / Command Structure]]		\|[[1.2 Organization / Command Structure\|Organization / Command Structure]]
	\|January 1, 2017		\|January 1, 2017
	\|		\|

1.2 Organization / Command Structure

Jonesk — Wed, 01 Apr 2026 20:34:42 GMT

Created page with "center|640x640px center"

New page

[[File:1.2 Regular Response.png|center|640x640px]]

[[File:1 2 Exanding Struture Fire.png|center]]

File:1 2 Exanding Struture Fire.png

Jonesk — Wed, 01 Apr 2026 20:33:40 GMT

Jonesk uploaded File:1 2 Exanding Struture Fire.png

New page

Expanded

File:1.2 Regular Response.png

Jonesk — Wed, 01 Apr 2026 20:31:08 GMT

Jonesk uploaded File:1.2 Regular Response.png

New page

Small Structure Fire, HazMat Incident, or EMS Response. First Alarm Units

Incident Management System Organization

Jonesk — Wed, 01 Apr 2026 20:28:10 GMT

← Older revision	Revision as of 20:28, 1 April 2026
(2 intermediate revisions by the same user not shown)
(No difference)

IMS

Jonesk — Wed, 01 Apr 2026 20:25:42 GMT

← Older revision		Revision as of 20:25, 1 April 2026
(3 intermediate revisions by the same user not shown)
Line 1:		Line 1:
			[[Main Page\|Protocols]]

			== Section 1 - Command Operations ==
	{\| class="wikitable"		{\| class="wikitable"
	\|+		\|+
Line 13:		Line 16:
	\|January 1, 2026		\|January 1, 2026
	\|-		\|-
			\|1.2
			\|[[Organization / Command Structure]]
			\|January 1, 2017
	\|		\|
	\|		\|January 1, 2026
	\|
	\|
	\|
	\|-		\|-
	\|		\|

Main Page

Jonesk — Wed, 01 Apr 2026 20:20:47 GMT

@@ Line 1: / Line 1: @@
-==EMS TABLE OF CONTENTS==
+==TABLE OF CONTENTS==
 [[Medical Director Authorization]]
@@ Line 7: / Line 9: @@
 ===Section 1 - Administrative Policies===
 {| class="wikitable"
 |-
@@ Line 681: / Line 681: @@
 [[IMS]]

IMS

Jonesk — Wed, 01 Apr 2026 20:18:22 GMT

← Older revision		Revision as of 20:18, 1 April 2026
Line 8:		Line 8:
	\|-		\|-
	\|1.1		\|1.1
	\|Incident Management System Organization		\|[[Incident Management System Organization]]
	\|January 1, 2017		\|January 1, 2017
	\|January 1, 2026		\|January 1, 2026

Main Page

Jonesk — Wed, 01 Apr 2026 20:17:53 GMT

← Older revision		Revision as of 20:17, 1 April 2026
Line 679:		Line 679:

	[https://forms.gle/XA7uhzLGYbwqBHTZ9 Link to MD Meeting Sign In]		[https://forms.gle/XA7uhzLGYbwqBHTZ9 Link to MD Meeting Sign In]

			[[IMS]]

	==IMS TABLE OF CONTENTS==		==IMS TABLE OF CONTENTS==
Line 693:		Line 695:
	\|-		\|-
	\|1.2		\|1.2
	\|Organization / Command Structure		\|[[Organization / Command Structure]]
	\|		\|
	\|-		\|-

IMS

Jonesk — Wed, 01 Apr 2026 20:17:43 GMT

Created page with "{| class="wikitable" |+ !Section !Description !Issue Date !Revision Date !Effective Date |- |1.1 |Incident Management System Organization |January 1, 2017 |January 1, 2026 |January 1, 2026 |- | | | | | |- | | | | | |}"

New page

{| class="wikitable"
|+
!Section
!Description
!Issue Date
!Revision Date
!Effective Date
|-
|1.1
|Incident Management System Organization
|January 1, 2017
|January 1, 2026
|January 1, 2026
|-
|
|
|
|
|
|-
|
|
|
|
|
|}

Main Page

Jonesk — Tue, 31 Mar 2026 15:01:00 GMT

Section 1 - Command Operations

← Older revision		Revision as of 15:01, 31 March 2026
Line 689:		Line 689:
	\|-		\|-
	\|1.1		\|1.1
	\|Incident Management System Organization		\|[[Incident Management System Organization]]
	\|		\|
	\|-		\|-

Incident Management System Organization

Jonesk — Tue, 31 Mar 2026 14:59:34 GMT

Created page with "== 1.1 Incident Management System Organization == === Purpose === The organizational structure outline in this plan has been derived from the '''National Interagency Incident Management System (NIMS)'''. '''NIMS''' is utilized by the Federal Government and is recognized and recommended by the Florida Fire Chiefs’ Association as the standard Incident Command System. In addition, certain portions of this manual have been adapted from Firescope, Phoenix Fireground Comman..."

New page

== 1.1 Incident Management System Organization ==

=== Purpose ===
The organizational structure outline in this plan has been derived from the '''National Interagency Incident Management System (NIMS)'''. '''NIMS''' is utilized by the Federal Government and is recognized and recommended by the Florida Fire Chiefs’ Association as the standard Incident Command System. In addition, certain portions of this manual have been adapted from Firescope, Phoenix Fireground Command System, Florida Incident Field Operations Guide, and the National Fire Service Incident Management System Consortium.

=== General ===
Under the Incident Management System, (IMS), the ultimate control and direction of all emergency response falls under a single individual, the Incident Commander, except where a Unified Command or Area Command is established. Incident Command is responsible for the overall incident response effort and the implementation of the appropriate portions of this plan. This command system is quite flexible in that the incident commander can activate, consolidate, or delete various positions depending on the needs of the incident. Although this structure is designed for full or partial implementation, it is important that all position roles are reviewed to ensure vital functions are not overlooked.

=== NIMS ===

* It is recommended that the person ultimately taking command at an incident be a chief officer or other qualified individual, highly trained and skilled in the Incident Management System. The Incident Management System is not rank structured but can be filled from whatever positions are best suited for the needs of the individual department.
* The degree of plan implementation will again depend upon the nature and magnitude of the incident. The following pages outline the roles and responsibilities of the various areas of the command structure.
* The IMS organizational structure develops in a modular fashion based on the kind and size of an incident. The organization’s staff builds from the top down with the responsibility and performance placed initially with the Incident Commander. As the need exists, four separate sections can be deployed, each with several units that may be established. The General Staff positions are:
** Operations
** Planning
** Logistics
** Administration (Finance)
* In addition to these four sections, Command Staff may include the following:
** Safety Officer
** Public Information Officer (PIO)
** Liaison Officer
** Incident Command Aide

Main Page

Jonesk — Tue, 31 Mar 2026 14:52:21 GMT

Section 1 - Command Operations

@@ Line 1: / Line 1: @@
-==TABLE OF CONTENTS==
+==EMS TABLE OF CONTENTS==
 [[Medical Director Authorization]]
@@ Line 679: / Line 679: @@
 [https://forms.gle/XA7uhzLGYbwqBHTZ9 Link to MD Meeting Sign In]

Analgesia and Sedation

Jonesk — Mon, 30 Mar 2026 17:45:01 GMT

2.04 ANALGESIA/SEDATION

← Older revision		Revision as of 17:45, 30 March 2026
Line 33:		Line 33:
	* [[Versed\|MIDAZOLAM (VERSED)]] 2 - 10 mg IV or IN, titrated to effect		* [[Versed\|MIDAZOLAM (VERSED)]] 2 - 10 mg IV or IN, titrated to effect
	* [[Valium\|DIAZEPAM (VALIUM)]] 2 - 20 mg SLOW IVP titrated to effect		* [[Valium\|DIAZEPAM (VALIUM)]] 2 - 20 mg SLOW IVP titrated to effect
	* [[Ketamine\|KETAMINE (KETALAR)]] 0.5 mg/kg IVP or IN titrated to effect OR 1-2 mg/kg IM x 1 dose - Remember that Ketamine is not reversible and may mask changes in patient condition.		* [[Ketamine\|KETAMINE (KETALAR)]] 0.5 mg/kg IVP or IN, titrated to effect OR 1-2 mg/kg IM x 1 dose - Remember that Ketamine is not reversible and may mask changes in patient condition.
	'''[[Cold Emergencies\|FROST BITE]]:'''		'''[[Cold Emergencies\|FROST BITE]]:'''
	* [[Nitrous_Oxide\|NITROUS OXIDE]] self administered, as needed for pain		* [[Nitrous_Oxide\|NITROUS OXIDE]] self administered, as needed for pain
Line 42:		Line 42:
	* [[Versed\|MIDAZOLAM (VERSED)]] 2 - 10 mg IV, IO or IN, titrated to effect		* [[Versed\|MIDAZOLAM (VERSED)]] 2 - 10 mg IV, IO or IN, titrated to effect
	* [[Valium\|DIAZEPAM (VALIUM)]] 2 - 20 mg SLOW IVP titrated to effect		* [[Valium\|DIAZEPAM (VALIUM)]] 2 - 20 mg SLOW IVP titrated to effect
	* [[Ketamine\|KETAMINE (KETALAR)]] 0.5 mg/kg IVP or IN ~~every 20 seconds~~ titrated to effect OR 1-2 mg/kg IM x 1 dose - Remember that Ketamine is not reversible and may mask changes in patient condition.		* [[Ketamine\|KETAMINE (KETALAR)]] 0.5 mg/kg IVP or IN, titrated to effect OR 1-2 mg/kg IM x 1 dose - Remember that Ketamine is not reversible and may mask changes in patient condition.
	'''FLANK PAIN/[[Suspected Kidney Stone\|SUSPECTED KIDNEY STONES]]:'''		'''FLANK PAIN/[[Suspected Kidney Stone\|SUSPECTED KIDNEY STONES]]:'''
	* TORADOL (KETOROLAC) 15mg – 30mg IV depending on hydration status		* TORADOL (KETOROLAC) 15mg – 30mg IV depending on hydration status

Drug Assisted Intubation

Jonesk — Fri, 27 Mar 2026 12:49:40 GMT

Paralytics if needed:

← Older revision		Revision as of 12:49, 27 March 2026
(One intermediate revision by the same user not shown)
Line 21:		Line 21:
	*Administer [[Morphine_Sulfate\|MORPHINE]]: Adult 2-20mg		*Administer [[Morphine_Sulfate\|MORPHINE]]: Adult 2-20mg

			==== Paralytics if needed: ====
			*<s>If intubation is unsuccessful due to the patient being clinched, strong gag reflex, or seizure, consider Succinylcholine: Adult 1.5mg/kg. Pediatric 2mg/kg.</s>
	====Paralytics if needed:====		*<s>Do not administer to patients with Hx of HYPERKALEMIA, RHABDOMYOLYSIS, Severe Burns and Malignant hyperthermia. (i.e. peaked T waves, kidney insufficiency, renal failure, acidosis, crush injuries.)</s>
	*If intubation is unsuccessful due to the patient being clinched, strong gag reflex, or seizure, consider Succinylcholine: Adult 1.5mg/kg. Pediatric 2mg/kg.		*<s>If ventricular dysrhythmias are present after medication administration, consider Calcium Chloride.</s>
	*Do not administer to patients with Hx of HYPERKALEMIA, RHABDOMYOLYSIS, Severe Burns and Malignant hyperthermia. (i.e. peaked T waves, kidney insufficiency, renal failure, acidosis, crush injuries.)
	*If ventricular dysrhythmias are present after medication administration, consider Calcium Chloride.

	====Placement and proof:====		====Placement and proof:====
Line 42:		Line 40:

	====Remember to titrate to effect all medications administered====		====Remember to titrate to effect all medications administered====


	====ONCE THE DECISION IS MADE TO PERFORM (DAI), THE LEAD PARAMEDIC MUST CONSIDER THE FOLLOWING:====		====ONCE THE DECISION IS MADE TO PERFORM (DAI), THE LEAD PARAMEDIC MUST CONSIDER THE FOLLOWING:====
	*2 PERSON BVM.		*2 PERSON BVM.

Main Page

Jonesk — Fri, 27 Mar 2026 11:19:08 GMT

Removed Link to Code Cool Protocol

← Older revision		Revision as of 11:19, 27 March 2026
(One intermediate revision by the same user not shown)
Line 75:		Line 75:
	\|\|2.03 \|\|[[Rapid Trauma Assessment, Focused History and Physical Exam]]\|\|Sept-15		\|\|2.03 \|\|[[Rapid Trauma Assessment, Focused History and Physical Exam]]\|\|Sept-15
	\|-		\|-
	\|\|2.04\|\|[[Analgesia and Sedation]]\|\|~~December~~-20		\|\|2.04\|\|[[Analgesia and Sedation]]\|\|March-26
	\|-		\|-
	\|\|2.05\|\|[[Drug Assisted Intubation]]\|\|December-16		\|\|2.05\|\|[[Drug Assisted Intubation]]\|\|December-16
Line 131:		Line 131:
	\|4.11\|\|[[Acute Cardiogenic Pulmonary Edema Pneumonia]]\|\|March-09		\|4.11\|\|[[Acute Cardiogenic Pulmonary Edema Pneumonia]]\|\|March-09
	\|-		\|-
	\|4.12\|\|[[Code Cool Post ROSC Induced Hypothermia]]\|\|March-09		\|4.12\|\|<s>Code Cool Post ROSC Induced Hypothermia</s> REMOVED\|\|March-26
	\|-		\|-
	\|4.13\|\|[[Adult Immediate Post-Cardiac Arrest Care]]\|\|April-12		\|4.13\|\|[[Adult Immediate Post-Cardiac Arrest Care]]\|\|April-12

Analgesia and Sedation

Jonesk — Thu, 26 Mar 2026 19:52:18 GMT

2.04 ANALGESIA/SEDATION

← Older revision		Revision as of 19:52, 26 March 2026
Line 33:		Line 33:
	* [[Versed\|MIDAZOLAM (VERSED)]] 2 - 10 mg IV or IN, titrated to effect		* [[Versed\|MIDAZOLAM (VERSED)]] 2 - 10 mg IV or IN, titrated to effect
	* [[Valium\|DIAZEPAM (VALIUM)]] 2 - 20 mg SLOW IVP titrated to effect		* [[Valium\|DIAZEPAM (VALIUM)]] 2 - 20 mg SLOW IVP titrated to effect
	* [[Ketamine\|KETAMINE (KETALAR)]] 0.5 mg/kg IVP or IN ~~every 20 seconds~~ titrated to effect OR 1-2 mg/kg IM x 1 dose - Remember that Ketamine is not reversible and may mask changes in patient condition.		* [[Ketamine\|KETAMINE (KETALAR)]] 0.5 mg/kg IVP or IN titrated to effect OR 1-2 mg/kg IM x 1 dose - Remember that Ketamine is not reversible and may mask changes in patient condition.
	'''[[Cold Emergencies\|FROST BITE]]:'''		'''[[Cold Emergencies\|FROST BITE]]:'''
	* [[Nitrous_Oxide\|NITROUS OXIDE]] self administered, as needed for pain		* [[Nitrous_Oxide\|NITROUS OXIDE]] self administered, as needed for pain

Pulseless Electrical Activity (PEA)

Jonesk — Wed, 25 Mar 2026 16:19:40 GMT

Pharmacologic Therapy:

← Older revision		Revision as of 16:19, 25 March 2026
Line 62:		Line 62:

	====Cases of suspected bradycardia, relative bradycardia or vagally stimulated such as patients found in the restroom.====		====Cases of suspected bradycardia, relative bradycardia or vagally stimulated such as patients found in the restroom.====
	* First, [[Atropine\|ATROPINE]] 0.5 -1.0 mg rapid ~~IVP~~. Repeat every 3 - 5 minutes up to a total of 0.04 mg/kg or approximately 3 mg		* First, [[Atropine\|ATROPINE]] 0.5 -1.0 mg rapid IV / IO. Repeat every 3 - 5 minutes up to a total of 0.04 mg/kg or approximately 3 mg
	* Apply TCP, set at maximum Milliamp. If pulse generated, decrease dosage to setting which still maintains a palpable pulse. If unsuccessful, reattempt capture every 3 - 5 minutes as above		* Apply TCP, set at maximum Milliamp. If pulse generated, decrease dosage to setting which still maintains a palpable pulse. If unsuccessful, reattempt capture every 3 - 5 minutes as above
	* [[Epinephrine\|EPINEPHRINE 1:10,000]] 1 mg IVP or IO Repeat EPINEPHRINE every 3 - 5 minutes of continued arrest		* [[Epinephrine\|EPINEPHRINE 1:10,000]] 1 mg IVP or IO Repeat EPINEPHRINE every 3 - 5 minutes of continued arrest

Scope of Practice

Treloars — Thu, 12 Mar 2026 16:04:04 GMT

1.20 SCOPE OF PRACTICE

← Older revision		Revision as of 16:04, 12 March 2026
Line 96:		Line 96:
	\| 15 \|\| Cricothyrotomy (Needle or Surgical) \|\| \|\| X		\| 15 \|\| Cricothyrotomy (Needle or Surgical) \|\| \|\| X
	\|-		\|-
	\| 16 \|\| Supraglottic Airway ~~(King LTS-D Tube)~~ \|\| X\|\| X		\| 16 \|\| Supraglottic Airway \|\| X\|\| X
	\|-		\|-
	\| 17 \|\| Ventilator Management - 16 y/o or older \|\| \|\| X		\| 17 \|\| Ventilator Management - 16 y/o or older \|\| \|\| X

← Older revision		Revision as of 17:45, 30 March 2026
Line 33:		Line 33:
	* [[Versed\|MIDAZOLAM (VERSED)]] 2 - 10 mg IV or IN, titrated to effect		* [[Versed\|MIDAZOLAM (VERSED)]] 2 - 10 mg IV or IN, titrated to effect
	* [[Valium\|DIAZEPAM (VALIUM)]] 2 - 20 mg SLOW IVP titrated to effect		* [[Valium\|DIAZEPAM (VALIUM)]] 2 - 20 mg SLOW IVP titrated to effect
	* [[Ketamine\|KETAMINE (KETALAR)]] 0.5 mg/kg IVP or IN titrated to effect OR 1-2 mg/kg IM x 1 dose - Remember that Ketamine is not reversible and may mask changes in patient condition.		* [[Ketamine\|KETAMINE (KETALAR)]] 0.5 mg/kg IVP or IN, titrated to effect OR 1-2 mg/kg IM x 1 dose - Remember that Ketamine is not reversible and may mask changes in patient condition.
	'''[[Cold Emergencies\|FROST BITE]]:'''		'''[[Cold Emergencies\|FROST BITE]]:'''
	* [[Nitrous_Oxide\|NITROUS OXIDE]] self administered, as needed for pain		* [[Nitrous_Oxide\|NITROUS OXIDE]] self administered, as needed for pain
Line 42:		Line 42:
	* [[Versed\|MIDAZOLAM (VERSED)]] 2 - 10 mg IV, IO or IN, titrated to effect		* [[Versed\|MIDAZOLAM (VERSED)]] 2 - 10 mg IV, IO or IN, titrated to effect
	* [[Valium\|DIAZEPAM (VALIUM)]] 2 - 20 mg SLOW IVP titrated to effect		* [[Valium\|DIAZEPAM (VALIUM)]] 2 - 20 mg SLOW IVP titrated to effect
	* [[Ketamine\|KETAMINE (KETALAR)]] 0.5 mg/kg IVP or IN ~~every 20 seconds~~ titrated to effect OR 1-2 mg/kg IM x 1 dose - Remember that Ketamine is not reversible and may mask changes in patient condition.		* [[Ketamine\|KETAMINE (KETALAR)]] 0.5 mg/kg IVP or IN, titrated to effect OR 1-2 mg/kg IM x 1 dose - Remember that Ketamine is not reversible and may mask changes in patient condition.
	'''FLANK PAIN/[[Suspected Kidney Stone\|SUSPECTED KIDNEY STONES]]:'''		'''FLANK PAIN/[[Suspected Kidney Stone\|SUSPECTED KIDNEY STONES]]:'''
	* TORADOL (KETOROLAC) 15mg – 30mg IV depending on hydration status		* TORADOL (KETOROLAC) 15mg – 30mg IV depending on hydration status

← Older revision		Revision as of 19:52, 26 March 2026
Line 33:		Line 33:
	* [[Versed\|MIDAZOLAM (VERSED)]] 2 - 10 mg IV or IN, titrated to effect		* [[Versed\|MIDAZOLAM (VERSED)]] 2 - 10 mg IV or IN, titrated to effect
	* [[Valium\|DIAZEPAM (VALIUM)]] 2 - 20 mg SLOW IVP titrated to effect		* [[Valium\|DIAZEPAM (VALIUM)]] 2 - 20 mg SLOW IVP titrated to effect
	* [[Ketamine\|KETAMINE (KETALAR)]] 0.5 mg/kg IVP or IN ~~every 20 seconds~~ titrated to effect OR 1-2 mg/kg IM x 1 dose - Remember that Ketamine is not reversible and may mask changes in patient condition.		* [[Ketamine\|KETAMINE (KETALAR)]] 0.5 mg/kg IVP or IN titrated to effect OR 1-2 mg/kg IM x 1 dose - Remember that Ketamine is not reversible and may mask changes in patient condition.
	'''[[Cold Emergencies\|FROST BITE]]:'''		'''[[Cold Emergencies\|FROST BITE]]:'''
	* [[Nitrous_Oxide\|NITROUS OXIDE]] self administered, as needed for pain		* [[Nitrous_Oxide\|NITROUS OXIDE]] self administered, as needed for pain