ID:

AIXM-407

target version:

AIXM 5.2

version:

1.0

last updated:

11 APR 2019

status:

APPROVED


Description

Add a new code list value MEDEVAC to the CodeFlightStatusBaseType.

Rationale for change

See https://aixmccb.atlassian.net/browse/AIXM-330

The AirportHeliport element in AIXM 5.1.1 does not have the ability to identify whether an airport/heliport can be used for medical evacuations. Because this is referring to a life-critical situation, a flight with this status may be prioritized by air traffic control. In addition, a need for coding the MEDEVAC value has been identified in the Digital NOTAM scenarios. New usage conditions based on the type of flight, such as needed for medical evacuation, should be supported in FlightCharacteristic.

Impact assessment

[FWD_MAP_1:1] Data mapping is possible and no data loss occurs when data is exchanged from a system (A) that uses AIXM 5.1.1 for output towards a system (B) that uses AIXM 5.2 for input.

[BWD_MAP_1:1] Data mapping is possible and no data loss occurs when data is exchanged from a system (B) that uses AIXM 5.2 for output towards a system (A) that uses AIXM 5.1.1 for input.

Change Proposal details

In the UML model, add the following code to CodeFlightStatusBaseType:

  • MEDEVAC = “Life-critical medical flight”.

Mapping AIXM 5.1.1 to AIXM 5.2 (forward)

[MAPC-01] The following data conversion algorithm is proposed:

  • For each FlightCharacteristic.status that has the value ”OTHER:MEDEVAC”:
    • replace the value with “MEDEVAC”

Mapping AIXM 5.2 to AIXM 5.1.1 (backward)

[MAPC-01] The following data conversion algorithm is proposed:

  • For each FlightCharacteristic.status that has the value “MEDEVAC”:
    • replace the value with “OTHER:MEDEVAC”


Mapping example

Mapping example to be added...


(Note: for mapping test data see: https://github.com/aixm/mapping_52_511/tree/master/AIXM-xxx

AIXM 5.2AIXM 5.1(.1)
  ...





...



  • No labels