Skip to main content

Suggestion System: Medical Requirements (Level 3)

Level 3 of the suggestion system ensures that the medical care level (doctor, transport capacity, intensive care) exactly matches the specifications of the operation keywords. This stage also operates strictly according to the Difference Principle.

Updated over 2 weeks ago

Core Function: Medical Remaining Requirement Determination

Level 3 calculates the remaining requirement for each medical category (e.g., emergency doctor, ambulance, rescue helicopter). All units already suggested by the Area Responsibility (Level 1) or the Equipment Requirements (Level 2) are offset against these requirements.

The Calculation Logic:

  1. Summation of all requirements from active keywords.

  2. Subtraction of units already committed to the operation.

  3. Subtraction of units already suggested by Levels 1 and 2.

  4. Identification and suggestion of remaining capacities based on distance or the fastest route.


Relevant Configuration Fields (Mapping)

The logic compares specific quantity fields in the keyword with the unit categories.

Reference (IKeyword)

Localization

Target Unit Category (UnitCategory)

DispatchAmountDoctorGround

Amount (Doctor Ground)

Physician

NEF

DispatchAmountHelicopter

Amount (HEMS)

AIR AMB

RTH

DispatchAmountHelicopterICU

Amount (Intensive Care Helo)

AIR ICU AMB

ITH

DispatchAmountAmbulanceRegular

Amount (Ambulance Regular)

AMB Type II, AMB

KTW, MZF

DispatchAmountAmbulanceUrgent

Amount (Ambulance Urgent)

AMB Type I, AMB

RTW, MZF

DispatchAmountAmbulanceDoctor

Amount (Ambulance Doctor)

AMB Physician

NAW

DispatchAmountAmbulanceICU

Amount (Ambulance ICU)

AMB ICU

ITW


Special Logic: The Physician Component

In addition to vehicle categories, the system evaluates the UnitDoctorOption property.

  • Requirement "Amount (Doctor)" (DispatchAmountDoctor): This value requests a medical doctor's qualification, regardless of the vehicle type.

  • Credit: Units configured in the master data with the Doctor Suggestion Option cover this requirement.

  • Substitution: If Area Responsibility (Level 1) has already suggested a rescue helicopter (RTH), Level 3 recognizes that a doctor is already present. An additional emergency doctor fly-car (NEF) will not be suggested in this case, provided only one doctor was requested.


Selection Process

Level 3 iterates through available EMS resources and checks for matches with remaining requirements:

  1. Filtering: Exclusion of all unavailable units (see article "Availability").

  2. Categorization: Matching whether a unit serves one of the open categories (RTW, NEF, RTH, etc.).

  3. Sorting: Prioritization by distance/travel time.

  4. Filling: The system selects units until all DispatchAmount counters of the keywords are at zero or below.

Interaction with Level 1 and 2

Level 3 is highly integrative. It prevents the dispatch of "escort EMS resources" if the tactical units already cover the medical component.

Fire Protection Example: A keyword requests 1x Fire Station (Level 1) and 1x Ambulance (RTW) for crew safety (Level 3). If the Fire Station from Level 1 already includes a vehicle that meets the criteria of an ambulance, Level 3 recognizes this and does not suggest an additional ambulance.


Summary of Priorities

  • Qualification over Type: Ensuring the medical care level takes precedence.

  • Avoidance of Redundancy: EMS resources are only added if the tactical dispatch (Fire/Police) does not contain a sufficient medical component.

  • Geographic Proximity: Within the medically suitable categories, the shortest travel time always decides.

Did this answer your question?