After an Ad Hoc incident has been recorded and the player has received an official diagnosis, the next step is to document the medical incident in detail in SAP Sports One. An ad hoc incident is intended as a quick way to mark a player as temporarily unavailable when the exact nature of the injury is not yet known. In contrast, a fully detailed injury record contains complete medical information and supports structured medical management and reporting.
Note
In the following lesson, we will look at how to fully create and document a medical incident directly in SAP Sports One. Of course, you can also update the previously created ad hoc incident and add additional information to it.
To create a new medical incident for a player, please access the Player’s Profile. In the player’s profile, navigate to the Health section. In this section, you can enter relevant health information about current medical events, treatments, medications, medical history, and medical attachments.

In the Current Medical Events section, you get a comprehensive overview of all existing medical events for the player. This includes all medical events that are still open, meaning the return date has not yet been reached. From here, you can also add new medical events. To do so, click Add Medical Event in the top-right corner.

When creating a new medical event, you can differentiate between an Injury, Sickness, and Preventive Action. As an example in this course, we will focus on creating an injury. You will see that, similar to SAP Player Fitness, the web version of SAP Sports One also allows you to mark an injury as ad hoc. Start by entering the basic injury information, such as the start date and the estimated return date. The estimated return date is not the same as the end date of the injury. Therefore, the medical event remains open until the end date has been maintained later on.
Moreover, compared to the previously created ad hoc injury, you can now select an injury from your predefined medical injury catalog. Most commonly, the OSICS injury catalog is used for the classification of medical events in professional sports. By maintaining these catalogs, you establish a structured foundation for accurate diagnosis and documentation, which in turn enables consistent reporting and analysis at later stages of the process.
To create and make adjustments to the catalogs in SAP Sports One, you need, for example, the role of Administrator or Physiotherapist and the corresponding permissions at Medical Data → Catalogs and Parameters. An overview of all SAP Sports One user roles and permissions is available on the SAP Help Portal (User Roles | SAP Help Portal). If you need additional information or support with adjusting your catalogs, please contact your respective SAP representative.
Note
Once a catalog entry has been used in a medical incident, it cannot be deleted. However, it can be set as inactive if necessary. This ensures that historical data remains intact while still allowing updates for future use.
In addition, you can also set a status for the medical event. From ad hoc injuries, you are already familiar with the Exempted status. Here, you can define additional statuses depending on the incident. For example, in the case of a sickness, a player may be available for rehab training but not for full team training on the pitch. Please note that medical event statuses for a player will be explained in more detail later in this course as part of the Return-to-Play process.
Finally, you also have the option to inform coaches and physiotherapists about this medical event. If you select these options, they will receive a message in the medical and coaching communication rooms on their mobile devices, informing them that the player has experienced a medical event. This is useful, for example, to let coaches know that a player is unavailable for training or to share relevant medical information among physiotherapists. For more information about communication rooms in SAP Sports One, please refer to our other learning course: Configuring Communication Rooms.




