The idea behind the development of the AUD₂IT-algorithm was to provide residents a documentation aid, which helps to structure the medical reports without getting lost in unimportant details or losing important information. Therefore, the AUD₂IT-algorithm maps the entire emergency treatment and brings together the data in clusters, which are documented chronologically. A pleasant side effect is, that the AUD₂IT-algorithm can replace or include many of the numerous emergency medical action schemes such as SBAR, SAMPLER or cABCDE, thus only one single action scheme must be learned (2, 3).

The treatment process in a resuscitation room commences well before the patient even arrives. The resuscitation team is actively engaged in preparing for the patient's arrival and the entire process is carefully orchestrated to ensure the best possible outcome. So, there was a need to expand the AUD₂IT-algorithm to include the phase from the alarm to the arrival of the patient in the resuscitation room. The (PR_E-)AUD²IT-algorithm was developed (6). Table 1 compares and describes the two algorithms.

While the (PR_E-)-section represents a chronological period of time in preparation for care for the emergency patient, the period during the AUD²IT-section is more complicated. The sequence of anamnesis, clinical examination, considering a differential diagnosis, technical diagnostics, interpretation and therapy is rather an academic classification then a description of the real workflow. In a real setting, most of these steps take place simultaneously. Therefore, the application of the AUD₂IT-algorithm should also be carried out according to the real processes.

Bernhard et al. say that handover is an important point within an emergency treatment and gives advice, which general conditions should be ensured during the handover-process (5). But there is lack of information about the contents and the structure of the handover. As a result, healthcare professionals may resort to employing pre-existing handover protocols; however, these protocols are frequently incomplete and may not adequately address all necessary actions. That is not necessary as the AUD₂IT-algorithm can be used instead and therewith can replace most of the existing action schemes. The clue is, that on the one hand the AUD₂IT-algorithm can be used as a structure for the entire treatment process and also is entirely used within this process to summarize the existing state of knowledge at each point of a team-timeout (Figure 1). It is not necessary to repeat every information at every time when the team has not changed. It is enough just to summarize changes or new findings since the last AUD₂IT-check.

In this way, the AUD₂IT-algorithm gets a new role and can not only be used for treatment planning and documentation, but also for all handovers.

The “U” changed during the time. While it described in the initial AUD₂IT-algorithm the clinical examination, in (PR_E-)AUD²IT-algorithm it also includes an ecg or sonography (2, 3, 6). This should be critically questioned since these apparatus diagnostic are also the consequence of the anamnesis and clinical examination. In an emergency treatment, several steps take place at the same time, so it would make more sense to assign each person with a different task and thus carry out all measures according to the AUD₂IT-algorithm at the same time.

The treatment documentation should be done according to the AUD₂IT-algorithm by using international standards for interoperability like FHIR or HL7.

Let us discuss two aspects of the nomenclature.

In the original version of the AUD₂IT-algorithm, the ″2″ is subscript to make clear that it stands for two D's. The ″2″ in the initial publication of the (PR_E-)AUD²IT-algorithm is superscript, giving it meaning and suggesting, that the “D” is being squared. We recommend to go back to the original variant with a subscript ″2″, as it is also the case in other algorithms like the CHA₂DS₂-VASc-Score (7).

We would like to propose a recommendation on the use of brackets and hyphen. To do justice to the fact that (PR_E-) describes a chronological process while AUD₂IT should be used repeatedly during an ongoing treatment process, we recommend to put the AUD₂IT in brackets. The underscore and the hyphen both represent a team time out; to avoid confusion, we recommend using in both cases the same special character. Consequently, we recommend to use the notation PR-E-(AUD₂IT) for the complete algorithm.

The PR-E-(AUD₂IT)-algorithm makes it possible to document a treatment process that, in principle, does not have to be limited to the field of emergency medicine. After treatment in the emergency department, often follows a transition to inpatient care. The fact, that the illness occurred acutely, does not play a significant role in the handover and documentation. When the patient moves from the emergency department to another unit, data is also transferred. This often results in interface breaks, which can be countered by a uniform design of the data infrastructure. Why should it not be possible for the documentation of a treatment to be continued in the same way even after the transfer to another unit?

In principle, all inpatient and outpatient treatments at case level could be documented with the AUD₂IT-algorithm. The result would be a clear standardization of data infrastructures, which is for example reflected in uniform treatment reports and user interfaces of IT applications. Further studies should evaluate whether these considerations can also be proven in practice.

Also, in the outpatient treatment the PR-E-(AUD₂IT)-algorithm could be used and further developed. One example could be the preparation and allocation of needed resources at the general practitioner. The algorithm is a standard tool that can be used by medical personnel of any level of training. It gives the user a sense of security in their daily work.