## 3 Proposed Supervision System and Method for Process Modeling
### Definition of SCVAD Processes
#### 3.2.1 Method for Structuring Processes of the SCVAD  
The digital integration of the DAV, patient, and medical team entities requires the development of applications that provide information through the sending of structured events, using application programming interfaces (APIs) and services compatible with EDA, in a publish-subscribe model [46, 47]. Through the APIs, communication occurs via the exchange of events or messages, where entities can publish events ('send messages') and others can subscribe to topics to receive these messages. Considering that each entity has autonomous and dynamic behavior, depending on the operational context, it is necessary to highlight the unique characteristics and specific requirements of each one. 1. The 'VAD', the patient, and the medical team have telemetry resources to enable communication among the entities via an onboard control system or through mobile devices. 2. The 'patient' has physiological control and regulation mechanisms to maintain homeostasis. Figure 7: Event-oriented structure model of the SCVAD for digitizing patient care processes. 3. The'medical team' has the necessary expertise to monitor the patient's progress and conduct appropriate therapeutic interventions, particularly regarding the occurrence of AEs and the complications they may cause. In this way, it becomes evident that an inherent complexity is associated with the dynamic interaction possibilities among the VAD, patient, and medical team. If reductionist techniques that do not address this dynamic reality are applied, the patient's health status may be compromised, potentially leading to a life-threatening condition. The model illustrated in Figure 8 was proposed to structure the processes of the SCVAD, delineating different operational contexts of the entities and their interactions. Sets A, B, and C are designated to represent the operational domains of each entity. The numbered regions from 1 to 7 are detailed. The red-highlighted numbering indicates the regions where the context of AEs applies, according to the proposal of this work. The following describes the seven regions with distinct semantics:  
* Region 1: Each element in this region of set A represents processes associated with the VAD in the context of its local control system, including the device for processing embedded control algorithms, sensing devices, actuators, and integration with supervisory systems. Therefore, the concept of AEs does not apply in this region, as events may occur that are associated with potential failures of various natures. * Region 2: Each element in this region of set B represents physiological processes inherent to the behavior of the patient's cardiovascular system. It is precisely in this context that AEs may occur, and it is essential to note that AEs occurring in this region are not necessarily related to the other entities. * Region 3: Each element in this region of set C represents issues with the medical team unrelated to the patient; therefore, the concept of AEs does not apply here. * Region 4: Each element in this intersection region between A and C, without the patient, corresponds to processes involving the proper selection of a VAD for a specific patient profile, as well as the setup of operating conditions according to this profile. Therefore, the concept of AEs does not apply in this context, as the patient is absent. Figure 8: The model for structuring SCVAD processes is represented. Note: The red numbering highlights areas susceptible to AEs (5, 6, and 7), while the black numbering identifies areas unrelated to AEs (1, 2, 3, and 4). * Region 5: Each element in this intersection between A and B, without the medical Team, corresponds to processes involving direct interactions between the patient and their VAD, where the concept of AEs applies.