Method for processing medical data sets by edge applications based on cloud-based applications

Abstract

The present disclosure relates to a method for processing a medical data set by an edge application based on a cloud-based application. A computer-implemented method for processing a medical data set at a processing system through at least one edge application, wherein the method includes the following steps: first receiving a medical data set from a medical system, wherein the medical system and the processing system are part of a local network. wherein the method also includes the step of initializing at least one edge application based on the cloud-based application, wherein the cloud-based application is stored in a cloud system, the cloud system is separate from the local network, wherein the edge application is a software application executed by the processing system. wherein the method also includes the step of processing the medical data set by at least one edge application, thereby generating a processed medical data set. wherein the method also includes the step of providing the processed medical data set.

Description

Technical Field

[0001] The present invention describes a method and an apparatus for processing a medical data set at a processing system by at least one edge application, wherein the processing system is part of a local network. Background Art

[0002] Several cloud-based applications are available for different use cases. For example, a cloud-based application can be used to process data according to a specific use case. Such data can be acquired by a system that is part of a local network of an institution, such as a hospital or a doctor's office. In order to process data using a cloud-based application, the data must be transferred from the local network to the cloud-based application. Since such a cloud-based application is executed in a cloud system, the data to be processed must be transferred to the cloud system.

[0003] Depending on the size of the data to be processed, the transfer process will take some time and bandwidth resources, and a stable connection between the local network and the cloud system is necessary.

[0004] Furthermore, if data is transferred from a local network to a cloud system, data protection guidelines must be considered depending on the type and content of the data transferred to the cloud system. This is particularly important for medical data. The data protection guidelines for transferring medical data are strict, and some data is not allowed to leave the local network.

[0005] Therefore, in order to reduce processing time of data and / or ensure compliance with data protection regulations, in some cases it is more convenient to process the data locally at the institution in a processing system of the local network.

[0006] However, such cloud-based applications are typically external, incompatible applications that cannot be easily implemented into the processing systems of an organization's local network. Summary of the invention

[0007] An object of the present invention is to provide a method for processing a medical data set by an edge application, wherein the edge application is based on a cloud-based application and is executed by a processing system.

[0008] This object is achieved by a method, a processing system, a computer program product and a computer-readable storage medium according to the independent claims. Advantageous features and further developments are listed in the dependent claims and the following description.

[0009] In the following, the solution according to the invention is described with respect to the claimed processing system and with respect to the claimed method. Features, advantages or alternative embodiments herein may be assigned to other claimed objects and vice versa. In other words, the claims directed to the processing system may be improved with features described or claimed in the context of the method. In this case, the functional features of the method are embodied by the target unit of the processing system.

[0010] In a first aspect, the present invention relates to a computer-implemented method for processing a medical data set at a processing system by at least one edge application. The method comprises the steps of first receiving a medical data set from a medical system, wherein the medical system and the processing system are part of a local network. The method further comprises the steps of initializing at least one edge application according to a cloud-based application, wherein the cloud-based application is stored in a cloud system that is separate from the local network, and wherein the edge application is a software application executed by the processing system. The method further comprises the steps of processing the medical data set by at least one edge application, thereby generating a processed medical data set. The method further comprises the step of providing the processed medical data set. In particular, providing the processed medical data set may comprise storing, transmitting and / or displaying the medical data set.

[0011] In particular, the processing system is part of or a component of a local network. In particular, the local network is located at an institution such as a hospital or a doctor's office, in other words, the local network is formed by data processing software and / or hardware at the institution. In particular, the local network is an independent system. In particular, medical data sets leaving the network must be pre-processed in accordance with data protection guidelines, for example, they must be anonymized or pseudonymized. In particular, medical data sets to be processed at the processing system are not allowed to leave the local network of the institution at all.

[0012] In particular, the processing system is separate from the cloud system. In particular, the cloud system is hosted by a server that is not located at the organization hosting the processing system. In particular, the processing system and the cloud system are spatially separate. In particular, separation also means that the cloud system cannot directly access data stored or processed by the processing system. The cloud system can only access such data with special authorization and / or if the data is actively sent to the cloud system, wherein data protection guidelines must be observed. In particular, the cloud system is not part of the independent processing system and vice versa.

[0013] Edge applications are software applications executed by a processing system. In particular, medical data sets processed by edge applications are processed at a local network. In other words, processing medical data sets by edge applications implies that the medical data sets are processed locally and do not need to leave the institution and / or local processing system for processing. Edge applications are based on cloud-based applications. In other words, edge applications exist that can be used to process medical data sets in the same manner as edge applications. The difference between edge applications and cloud-based applications is that edge applications process medical data sets locally at a processing system, while cloud-based applications process medical data sets in a cloud system. In particular, edge applications as well as cloud-based applications can be external applications. In other words, edge applications and cloud-based applications can originate from another party other than the processing system itself.

[0014] In particular, the edge application is compiled and / or interpreted according to the cloud-based application and based on the public source code. In particular, the source code for the edge application and the source code for the cloud-based application can be the same in more than 50% of their parts, in particular, they can be the same in more than 75% of their parts, in particular, they can be the same in more than 90% of their parts, and in particular, they can be the same in all cases where external libraries used by the edge application and / or the cloud-based application are not taken into account. In particular, if the edge application and the cloud-based application are compiled software applications, different compiler options or different compilers can be used to compile both for different processing structures. In particular, the edge application and the cloud-based application can be linked to different (shared or static) libraries, or can interact with different external systems based on a public API (abbreviation for "application programming interface").

[0015] In the first step of receiving a medical data set, data to be processed by the edge application is received from the medical system by the processing system. The medical data set may include image data and / or electronic patient records and / or laboratory diagnostic information and / or information about a patient's pre-existing diseases, etc. These are different types of medical data sets. The medical data set may be related to the patient. In particular, the medical data set may be acquired during an examination of the patient and / or may describe medical facts about the patient, etc. The medical system may, for example, include an imaging system (e.g., an X-ray device, a computer tomography device, a magnetic resonance device, a positron emission tomography device, a single photon emission computer tomography device, etc.) and / or a laboratory diagnostic device and / or a picture archiving and communication system (abbreviation: PACS) and / or a radiology information system (abbreviation: RIS) and / or a hospital information system (abbreviation: HIS). Such a system may be referred to as a sub-medical system of the medical system. In other words, the medical system may include equipment and / or IT systems of an institution. In particular, the medical system may include a plurality of different sub-medical systems. In particular, the medical system is part of a local network, similar to the processing system. In particular, data (respectively medical data sets) within the local network can be transmitted between systems such as processing systems and / or medical systems of the local network. In particular, for transmitting data (respectively medical data sets) between systems of the local network, it is not necessary to pre-process the data (respectively medical data sets) in accordance with data protection guidelines.

[0016] In the step of initializing at least one edge application, the edge application is initialized at the processing system. In particular, before the edge application is initialized at the processing system, the edge application is provided to the processing system by the cloud system. In this step, the edge application is initialized locally at the processing system so that the medical data set can be processed locally by the edge application at the local processing system. Therefore, there is no need to transfer the medical data set to the cloud system for processing by the edge application. As mentioned above, the edge application is developed (correspondingly constructed) based on existing cloud-based applications. In other words, the edge application is based on the corresponding cloud-based application. In particular, the step of initializing the edge application must be applied at least once for a single edge application. After initializing at least one edge application at the processing system, it can be used to process the medical data set. In other words, if at least one edge application has been initialized previously, it may not be necessary to perform the initialization step again. In other words, the step of initializing at least one edge application is an optional step. In particular, the step of initializing at least one edge application can be alternatively performed before performing the step of receiving the first medical data set.

[0017] In the step of processing a medical data set, the medical data set is processed by at least one edge application. In particular, the processing depends on at least one edge application and the medical data set that should be processed. Processing a medical data set may, for example, include: pattern recognition and / or image / contrast enhancement and / or masking image data and / or highlighting suspicious findings and / or clustering techniques and / or applying machine learning algorithms and / or applying artificial intelligence algorithms and / or searching for comparable medical data sets in PACS, RIS or HIS and / or creating automatic diagnosis, etc. In the step of processing a medical data set, a processed medical data set is generated. In particular, the processed medical data set is the result after edge applications are performed on the medical data set. The processed medical data set may be the same type as the medical data set, for example, if the medical data set is a medical image, the processed medical data set may be a segmented medical image. Alternatively, the processed medical data set may be another type other than a medical data set, for example, if the medical data set is a medical image, the processed medical data set may be the probability of the presence of a certain structure in the medical image.

[0018] In the step of providing a processed medical data set, a processed medical data set is provided. In particular, providing a processed medical data set may include storing the processed medical data set. The processed medical data set may be stored in a PACS and / or a RIS and / or a HIS in particular. In particular, providing a processed medical data set may include sending the processed medical data set to a PACS and / or a RIS and / or a HIS and / or a sub-medical system. In particular, the medical data set may be provided to a user. The user may be, for example, a medical staff and / or a patient. The medical staff may be, for example, a doctor and / or a nurse, etc. The processed medical data set may be provided to the user in particular via a PACS and / or a RIS and / or a HIS. In this case, in the step of providing a processed medical data set, the processed medical data set is loaded (respectively downloaded) into a PACS and / or a RIS and / or a HIS. In particular, the processed medical data set may be provided to the user via a medical system. In particular, the processed medical data set may be provided to the user via a sub-medical system. In particular, the sub-medical system for providing the processed medical data set may be different from the sub-medical system from which the medical data set is received in the first step of receiving the medical data set. In particular, the user may be informed when the processed medical data set is available, for example in a PACS and / or a RIS and / or a HIS. In particular, the user may be informed via an email and / or via a pop-up window or the like.

[0019] The inventors recognize that edge applications can be initialized at a processing system corresponding to (correspondingly based on) a cloud-based application. In particular, the inventors recognize that, by this method, medical data sets can be processed locally. This helps to comply with data protection guidelines. Additionally, time is saved because there is no need to transfer data to an external cloud server. In addition, it is not necessary to provide a stable connection between the local network and the cloud server. In particular, the inventors recognize that the correspondence between edge applications and cloud-based applications allows the application to be centrally maintained. In particular, medical data sets can be processed in the same way by different applications. Therefore, users can choose the most appropriate way to process medical data sets: locally at the processing system or in the cloud system. In particular, with regard to medical data, it is important that even if one of the processed medical data sets has been processed in the local processing system and the other of the processed medical data sets has been processed in the cloud system, the two processed medical data sets are comparable. This ensures the diagnostic criteria of the medical data sets.

[0020] According to another aspect of the present invention, at least one edge application is based on an image of at least one edge application.

[0021] In particular, the edge application is published as an image of the edge application within the cloud system. In other words, the image of the edge application is provided by the cloud system. In particular, the image of at least one edge application can be published on a cloud repository. In particular, the image of the edge application includes all the information required to install and / or execute the edge application on the processing system. In particular, the image of at least one edge application can be provided via an executable file that can be downloaded from the cloud system. In particular, the image of the edge application can be downloaded from the cloud system. In other words, the edge application can be downloaded from the cloud system. In particular, the edge application can be downloaded to the processing system of the local network. In particular, the image of the edge application can include source code. In particular, in this case, the source code must be compiled at the processing system. Alternatively, the image of the edge application may include the bytecode of the edge application. The bytecode may be compiled in time at the processing system when executing the edge application, or the bytecode may be interpreted by the interpreter of the processing system. Alternatively, the image of the edge application includes compiled machine code that can be directly executed by the processing system after downloading the image.

[0022] The inventors have recognized that providing at least one edge application as an image that can be downloaded and installed by a processing system is the most efficient approach.

[0023] According to another aspect of the present invention, the step of initializing at least one edge application includes the steps of first downloading an image of at least one edge application stored in a cloud system, and installing the image of at least one edge application in a processing system.

[0024] In particular, in the first step of downloading the image of at least one edge application, all information required to install and execute the edge application at the processing system is downloaded. This information is provided via the image of the edge application. In particular, the processing system can automatically download the image of at least one edge application. In particular, this automatic download can be controlled by a specific license stored in the processing system. In particular, the specific license can relate to a specific edge application. The specific license can be checked by the cloud system before downloading at least one edge application (correspondingly at least one edge application image). In other words, if a specific license according to at least one edge application is available at the processing system, the image of at least one edge application can be automatically downloaded. In particular, the specific license can be purchased (respectively acquired) and owned by the user. In other words, the user must purchase or acquire a specific license according to at least one edge application to obtain permission for downloading at least one edge application to the processing system. In particular, the specific license must be purchased once to initialize at least one edge application once at the processing system. In particular, the specific license includes a file stored at the processing system and / or the cloud system. In particular, the specific license may include a key stored at the processing system and / or the cloud system. In particular, the specific license can be used to check the identity of the processing system. In particular, specific permissions are maintained in the cloud system and / or the processing system. In particular, the image of the edge application is securely stored in the cloud system, in particular in a cloud repository of the cloud system. Access to the processing system is strictly controlled by checking the specific permissions of the processing system in order to download the image of the edge application. After initialization, at least one edge application can be executed several times.

[0025] In particular, in the step of installing the image of at least one edge application, the image of the at least one edge application is configured so that the edge application can be executed at the processing system. If necessary, the image of the edge application can be compiled so that the edge application can be executed at the processing system. In particular, if the image is provided by an executable file, in order to install the image of the at least one edge application, the executable file is executed. In particular, the edge application can be executed several times for multiple medical data after installation.

[0026] The inventors have recognized that by providing edge applications via a cloud system, it is easy to initialize edge applications within a processing system. In particular, access to images of edge applications is provided via the cloud system, and no additional installation media such as a USB stick or hard disk is required for installing / initializing edge applications. In particular, the inventors have recognized that updates of edge applications can be provided via the cloud system. Furthermore, the inventors have recognized that by publishing images via a cloud system, it is possible for multiple different processing systems that are part of different local networks to access the images and can download the images according to specific permissions.

[0027] According to another aspect of the present invention, a plurality of edge applications can be executed by a processing system. The method further comprises the step of secondly receiving, by the processing system, associated data, wherein the associated data is related to a medical data set. The method additionally comprises the step of selecting, by the processing system, at least one edge application from the plurality of edge applications based on the associated information. The method further comprises the step of transmitting the medical data set to the at least one edge application.

[0028] In particular, as described above, all edge applications in the plurality of edge applications are initialized at the processing system. In particular, each edge application can be dedicated to processing a medical data set in a specific manner. In particular, each edge application can be dedicated to a specific type of medical data set.

[0029] In the second step of receiving associated data, the associated data is received by the processing system. The associated data is related to the medical data set received in the step of first receiving the medical data set by the processing system. The associated data includes information on how the medical data set should be processed. In particular, the associated data includes information on which edge application among multiple edge applications should process the medical data set. In particular, the associated information may include more than one edge application that should be applied / executed to process the medical data set. In particular, the associated data includes a link to at least one edge application that should be used to process the medical data set. In particular, the link may include information on how data can be sent to at least one edge application at the processing system. Alternatively, the associated data may include the name of at least one edge application. Through a virtual dictionary, the name can be linked to at least one edge application itself. The virtual dictionary can be stored and provided by the processing system. The name can be the full name, acronym, abbreviation, etc. of at least one edge application. Alternatively, the edge application that should be used to execute the medical data set can be indirectly inferred from the associated data. For example, the associated data may include information such as which device has been used to acquire the medical data set or which body region is imaged in the medical data set. This information can be used to infer the most suitable edge application or edge applications for processing medical data sets. In particular, edge applications can be selected through rule-based programming.

[0030] The associated data may in particular be provided by the medical system (respectively by the sub-medical system). Alternatively, the associated data may be provided manually by user input. In particular, the associated data may be part of a medical dataset. For example, if the medical dataset is medical image data, the associated data may be a DICOM (acronym for “Digital Imaging and Communications in Medicine”) header.

[0031] The associated data may be created automatically. In this case, the associated data is created, for example, based on the type of medical data set and / or the type of examination from which the medical data set was obtained. Alternatively or additionally, the associated data may be created and / or manipulated and / or adapted manually. In particular, the associated data may be created, manipulated and / or adapted by a user. In particular, the associated data may be provided by a medical system.

[0032] In particular, the associated data may define one or more edge applications for processing the medical dataset.

[0033] In the step of selecting, at least one edge application is selected based on the associated data. In particular, information provided by the associated data is read out. The information is used to select at least one edge application that should be applied / executed to process the medical data set.

[0034] In the step of transmitting the medical data set, the medical data set is transmitted to the edge application selected in the previous step of selecting at least one edge application. Depending on the associated information, the medical data set can be transmitted to more than one edge application. In particular, since all edge applications are part of the local network, there is no need to consider data protection guidelines when transmitting the medical data set.

[0035] The inventors have realized that the processing of medical data sets can be controlled by associated information. In particular, the inventors have realized that the workflow can be accelerated by providing and / or processing automatically created associated data. Furthermore, the inventors have realized that, alternatively or additionally, associated data can be manually created, adapted and / or manipulated. This enables a user to process a medical data set in a personalized manner depending on the patient or examination, etc., to which the medical data set belongs.

[0036] According to another aspect of the present invention, the associated information includes processing information whether the medical data set should be processed using a cloud-based application or using an edge application based on the cloud-based application.

[0037] As described above, each edge application is based on a cloud-based application. In particular, the edge application and the corresponding cloud-based application process the medical data set in the same way, but in order to process the medical data set using the cloud-based application, the medical data set must be transmitted to the cloud system. In particular, the coordinator can control the data transmission based on the processing information of the associated data.

[0038] In particular, the processing information provided by the associated data may define whether the medical data set should be processed by an edge application within the processing system or by a corresponding cloud-based application within the cloud system.

[0039] The processing information may be set, for example, by a user. The user may decide, based on available time and resources and the medical data set to be processed, whether the data should be processed locally by an edge application or in the cloud by a cloud-based application. Alternatively or additionally, the processing information may be automatically set based on rules set by the user. Alternatively, these rules may be set by a provider of the processing system.

[0040] Alternatively, the processing information may be automatically determined based on the type of medical dataset. If the medical dataset includes, for example, electronic patient records, the data may be too sensitive to be sent to a cloud system. Therefore, it may be more convenient to use edge applications to process such data. In contrast, if the medical dataset includes medical images that can be easily anonymized, it may be advisable to use a cloud-based application to process the data in a cloud system, as this makes it easier to enforce data protection guidelines.

[0041] Alternatively or additionally, the processing information in the associated data may be set according to the size of the medical data set. If the medical data set is large, it may take too long to upload the entire medical data set to the cloud system. In this case, it may be more convenient for the edge application to process the data locally. If the medical data set is small enough, it may be recommended to use a cloud-based application to process the data. The threshold for defining what data of what size may be processed by the edge application and which is the corresponding cloud-based application depends, for example, on the bandwidth of the connection between the processing system and the cloud system. The threshold may be set manually or automatically.

[0042] Alternatively or additionally, the processing information may be determined based on the results and parameters of previous processing of other medical data sets. In particular, the parameter may be the processing time of the previous processing of the other medical data sets. Based on the processing time of the previously processed medical data sets, the processing information may be determined. It may be determined which type of medical data sets take longer to be processed by a cloud-based application and which type of medical data sets take longer to be processed by an edge application. This may also be determined based on the size of the medical data sets. The determination may be performed by a machine learning algorithm or an artificial intelligence algorithm.

[0043] The inventors recognized that in some cases it is more convenient to process the medical data set locally using at least one edge application, and in other cases it is more convenient to process the medical data set using a corresponding cloud application. They recognized that a type of switch can be installed by providing processing information to a coordinator via associated data.

[0044] According to another aspect of the present invention, the steps of first receiving a medical data set, second receiving associated data, selecting at least one edge application, transmitting the medical data set to at least one edge application, and providing a processed medical data set are supervised by a coordinator based on associated data, wherein the coordinator is a software application executed by a processing system.

[0045] In particular, the coordinator is a software application that controls the above-mentioned steps: first receiving a medical data set, second receiving associated data, selecting at least one edge application, transmitting the medical data set to at least one edge application, and providing a processed medical data set. In particular, when a medical data set is received by a processing system, the coordinator is informed. In particular, when an associated data set is received by a processing system, the coordinator is informed. In particular, the coordinator is informed about the information included by the associated data. In particular, the coordinator performs the selection of at least one edge application by informing at least one edge application that there is a medical data set that should be processed by the at least one edge application. In other words, the coordinator activates at least one edge application according to the associated information. In particular, this activation of at least one edge application by the coordinator results in the transmission of the medical data set to at least one edge application and the processing of the medical data set by at least one edge application. In particular, when the step of processing the medical data set by at least one edge application is completed, the coordinator is informed. In particular, the coordinator can initiate the step of providing the processed medical data set after completing the step of processing the medical data set. In particular, the coordinator can supervise how the processed medical data set is provided to the user. In particular, the coordinator may provide a path where the processed medical data set should be stored to provide it to the user. In particular, the coordinator may initiate loading of the processed medical data set into a PACS and / or RIS and / or HIS of the local network.

[0046] In particular, the coordinator includes at least one agent. In particular, the agent included by the coordinator can be designed as an interface between a medical system and at least one edge application. In particular, the agent included by the coordinator can be designed as an interface between at least one edge application and a system designed to provide processed medical data sets to users. Such a system can be, for example, a PACS and / or a RIS and / or a HIS, etc. In particular, the coordinator can include several additional agents. These agents are designed to connect at least two systems of a local network to each other. The connection includes, for example, at least one of activation, data upload, data download, data exchange, notification, etc.

[0047] The inventors have realized that the systems of the local network can be connected via a central supervisory unit, a coordinator. The inventors have realized that it is more efficient to integrate at least one edge application into the local network like this. The inventors have realized that a central supervisory unit such as a coordinator helps to keep an overview of the individual processes executed by the processing system. In particular, the inventors have realized that this simplifies the maintenance of the processing system.

[0048] According to another possible aspect of the invention, the coordinator is designed to communicate with a cloud system.

[0049] In particular, the coordinator comprises a proxy, which serves as an interface between the processing system and the cloud system. In particular, the interface can be used, for example, to download an image of at least one edge application to the processing system. In particular, the interface can prevent an impermissible exchange of data between the cloud system and the processing system. In particular, the interface can ensure that only data that complies with data protection guidelines can be transmitted to the cloud system.

[0050] The inventors have realized that the communication between the cloud system and the processing system can be controlled (respectively supervised) by a coordinator. In particular, the inventors have realized that maintenance of the processing system is simpler if the agent for communicating with the cloud system is also hosted by the coordinator, because this provides an overall overview of all interfaces (respectively agents) of the processing system.

[0051] According to another aspect of the present invention, the step of selecting at least one edge application and / or the step of providing processed medical data includes the following steps: notifying at least one edge application or coordinator through an event service, wherein the event service is a first container plug-in executed by the processing system.

[0052] A general description of the plugin architecture is provided by document EP 3 451 341 A1. A container plugin is designed to run an application / software application. The container plugin includes all necessary packages / software required for running the plugin's application. In particular, the application executed by the container plugin is independent of the system executing the container plugin. In particular, such a container plugin can be packaged in the form of a "docker image" and can be hosted via the software application "Docker".

[0053] In particular, instead of including an agent between the medical system and at least one edge application, the coordinator may include at least an agent that serves as an interface between the medical system and the event service. In particular, the at least one edge application may communicate directly with the event service. In particular, the event service may be informed / notified by the coordinator based on the associated information that the event service should activate at least one edge application. In other words, the event service informs the at least one edge application that there is a medical data set that should be processed by the at least one edge application. This is done in the step of notifying the at least one edge application.

[0054] In the step of providing the processed medical data set, the event service is informed / notified by at least one edge application that the processed medical data set is available. The edge service informs the coordinator via a further agent. This is done in the step of notifying the coordinator. After being notified by the event service, the coordinator initializes, for example, to download the processed medical data set to the institution's PACS and / or RIS and / or HIS, etc. In particular, the event service can provide information on how to download the processed medical data set to the coordinator. This information can originate from the coordinator itself, associated data and / or further configuration data of the processing system.

[0055] The inventors recognize that in order to communicate with the edge applications, the coordinator must include only two agents. In particular, it is not necessary for the coordinator to include an agent for each edge application in multiple edge applications. The inventors recognize that this simplifies the creation, maintenance, and hosting of the coordinator. The inventors recognize that the event service can be designed so that each edge application in multiple edge applications can communicate directly with the event service.

[0056] According to another aspect of the invention, the first step of receiving a medical data set and providing a processed medical data set comprises the step of uploading the medical data set and / or the processed medical data set to an upload service, whereby the upload service is a second container plugin executable by the processing system and the upload service stores the medical data set and / or the processed medical data set.

[0057] In particular, the upload service is a container plugin as described above with respect to the event service.

[0058] In a first step of receiving a medical data set, the coordinator uploads the medical data set to an upload service via an agent. Alternatively, the coordinator supervises the uploading of the medical data set from the medical system to the upload service. The medical data set is stored in the upload service. In the step of providing a processed medical data set, the processed medical data set is uploaded to the upload service from at least one edge application. Therefore, the coordinator does not have to include an agent for direct communication between the medical system and the edge application. The coordinator must include at least one agent for communicating with the upload service. The processed medical data set can be downloaded from the upload service to any local system, such as PACS and / or RIS and / or HIS, etc. This is supervised by the coordinator. In particular, the event service can provide information on how and / or where the processed medical data set is downloaded from the upload service to the coordinator.

[0059] The inventors have realized that the medical data set and the processed medical data set can be stored by an upload service as a second container plug-in. This allows for centralized data management. Furthermore, the inventors have realized that the coordinator does not need an agent for each edge application. Instead, it is sufficient if the coordinator at least includes an agent for communicating with the upload service.

[0060] According to another aspect of the present invention, the step of transmitting the medical dataset to at least one edge application comprises the following step: at least one edge application downloads the medical dataset stored in the upload service via the download service. Thus, the download service is a third container plug-in executed by the processing system.

[0061] In particular, the download service is a container plugin as described above with respect to the event service.

[0062] In particular, the data stored in the upload service is provided to at least one edge application via the download service. The at least one edge application is activated, informed, and notified by the event service accordingly: there is a medical data set in the upload service that should be processed by at least one edge application. The medical data set can be accessed by at least one edge application via the download service. Therefore, the download service has an interface with the at least one edge application and the upload service, which is designed to transfer the medical data set from the upload service to the at least one edge application.

[0063] The inventors have realized that the provision of the medical data set to at least one edge application can be controlled by a further container plugin, a so-called download service. In particular, this simplifies the maintenance of the entire processing system.

[0064] According to another aspect of the invention, the configuration of the processing system and / or the image of at least one edge application is stored in the cloud system, in particular in a configuration service in the cloud system.

[0065] In particular, the configuration of the processing system may include details about the local network. In particular, such details may include information about the system in the local network and / or information about the coordinator of the processing system and / or information about data protection guidelines related to the medical data set processed in the local network, etc. In particular, the configuration may include information about specific permissions (specific permissions stored in the cloud system and / or the processing system respectively owned by the user of the processing system). In particular, the configuration may include at least one parameter that can be defined for at least one edge application. In other words, the parameter can describe how to process the medical data set using at least one edge application and / or can improve the processing of the medical data set by at least one edge application. In particular, the configuration may include information about how the processed medical data set should be downloaded to provide the processed medical data set. In particular, if the medical data set and / or the processed medical data set is DICOM image data, the configuration may include automatic routing rules defined for the DICOM image data. In particular, the operating aspects of the processing system may be included through the configuration. In particular, the configuration may include information about which edge application should be used to process a specific type of medical data set. In particular, the configuration may include rules for which edge application should be used to process a medical dataset, depending on the type of the medical dataset or the device with which the medical dataset has been acquired, etc.

[0066] In particular, an image of each of the plurality of edge applications initialized at the processing system may be stored by the configuration service. In particular, in the event of a system crash of the processing system, the edge application may be reinitialized again at the processing system without interacting with the cloud system. In particular, the edge application may be reinitialized without providing a specific permission again.

[0067] In particular, data defining the processing system can be stored in the configuration service. In particular, all data that cannot be protected due to data protection guidelines can be stored in the configuration service.

[0068] In particular, the coordinator may communicate with the configuration service. In particular, the coordinator may communicate with the configuration service via a proxy (respectively via an interface).

[0069] In particular, multiple configuration services may be executed by the cloud system, whereby each configuration service may communicate with coordinators of different processing systems of different local networks.

[0070] The inventors have recognized that storing at least the configuration of the processing system within a configuration service facilitates reinstalling and / or reinitializing the processing system after a crash. In particular, the inventors have recognized that storing the configuration data in an independent system such as a cloud system is helpful.

[0071] According to another aspect of the present invention, at least one edge application is downloadable from the cloud system. Thus, the configuration service provides updates of the at least one edge application.

[0072] In particular, when an update of at least one edge application (respectively one edge application) of a plurality of edge applications initialized at the processing system is provided by the cloud system, the configuration service is informed. In particular, the configuration service initializes the download of the update to the processing system where the update can be installed. Alternatively, the update is provided to the configuration service. In this case, the update is sent directly to the processing system by the configuration service.

[0073] In particular, all communications, data exchanges, etc. between the processing systems and the configuration services are supervised by the coordinator.

[0074] The inventors have recognized that the configuration service can be used as an instance of a cloud system that provides useful information from the cloud system to the processing system. In particular, the inventors have recognized that the configuration service can select such updates for edge applications initialized at the processing system. In other words, the inventors have recognized that the configuration service can be used as a filter to filter such information of the cloud system that is of interest to the processing system.

[0075] According to another aspect of the invention, a backup of the processing system and / or at least one edge application is stored in a configuration service.

[0076] In other words, an image of the entire processing system can be stored in the configuration service of the cloud system. In particular, the backup can be an image of the processing system. In the event that the processing system crashes in the local network, the image can be downloaded to the local network. After installing the image of the processing system, it is the same as before the crash.

[0077] Alternatively or additionally, an image of at least one edge application may be stored in the configuration system. If only at least one edge application of the processing system crashes, it may be reinitialized by downloading at least one edge application from the configuration service. In particular, the image of at least one edge application may include user-specific parameter settings defined for a particular processing system. These settings may be defined by a user of the processing system.

[0078] The inventors have recognized that for maintenance of the processing system, it is helpful to have a backup of the system in an independent system such as a cloud system. The inventors have recognized that the image typically does not include patient specific data that must be protected by data protection guidelines. The inventors have recognized that in the event that the image includes data that must be protected by data protection guidelines, such data can be anonymized or pseudonymized. The inventors have recognized that it is helpful to store images of initialized edge applications in a configuration service. Since parameter settings can be added to these images, these images can be personalized. The inventors have recognized that this simplifies resetting the processing system after a crash.

[0079] According to another aspect of the invention, the medical dataset comprises medical image data, wherein processing the medical dataset comprises in particular pattern recognition and / or image registration and / or image enhancement and / or masking.

[0080] In particular, the medical image data may be acquired, for example, using an X-ray device, a computer tomography device, a magnetic resonance device, a positron emission tomography device, a single photon emission computer tomography device, etc. In particular, such medical image data may depict a body region of a patient. In particular, such medical image data may be provided according to the DICOM (acronym for “Digital Imaging and Communications in Medicine”) standard.

[0081] In particular, processing the medical image data may include pattern recognition. In pattern recognition, suspicious structures within the medical image data are detected. Such suspicious structures may be, for example, tumor structures or abnormalities. In particular, pattern recognition helps to find suspicious structures in the medical image data. In particular, pattern recognition may be performed by a trained algorithm such as deep learning or machine learning or artificial intelligence. Alternatively, pattern recognition may be performed by an untrained algorithm.

[0082] Alternatively or additionally, processing the medical image data may include image registration. In particular, during image registration, two medical image data that primarily depict the same body region may be registered so that the two medical image data match as closely as possible. In other words, the medical image data may be superimposed by image registration so that the depicted body regions superimpose as closely as possible.

[0083] Alternatively or additionally, processing the medical image data may include image enhancement. In particular, image enhancement may include reducing artifacts and / or sharpening contours and / or enhancing contrast, etc. In particular, image enhancement may include methods for improving image quality. In particular, details and / or structures in the medical image data that may be important to a user may be enhanced by image enhancement.

[0084] Alternatively or additionally, processing the medical image data may include masking the medical image data. In particular, structures that are not important to the user may be masked during processing. Such masking may be performed by a trained algorithm. Alternatively, masking may be performed by an untrained algorithm, such as by thresholding and / or edge detection.

[0085] In particular, these possibilities for processing medical data sets can be provided by one edge application. Alternatively, these possibilities can be provided by a combination of more than one edge application.

[0086] The inventors have recognized that in particular medical image data can be processed by the methods described above. The inventors have recognized that cloud-based applications can be used to process medical image data. They have recognized that it is helpful to integrate edge applications based on such cloud applications in a local processing system to process medical image data. In particular, they have recognized that medical image data can be avoided from leaving the local network by processing it using edge applications.

[0087] In a second aspect, the present invention relates to a processing system for processing a medical data set at the processing system by at least one edge application. The processing system comprises an interface and a computing unit. The interface is configured to first receive a medical data set from a medical system, wherein the medical system and the processing system are part of a local network. The interface and / or the computing unit are configured to initialize at least one edge application according to a cloud-based application, wherein the cloud-based application is stored in a cloud system that is separate from the local network, and wherein the edge application is a software application executed by the processing system. The computing unit is also configured to process the medical data set by at least one edge application, thereby generating a processed medical data set. The interface is also configured to provide the processed medical data set.

[0088] In particular, the processing system may be configured to perform the previously described method for processing a medical data set at the processing system by at least one edge application. The processing system is configured to perform the method and aspects thereof by configuring the interface and the computing unit to perform corresponding method steps. In particular, the interface may include one or more sub-interfaces. In particular, the computing unit may include one or more computing sub-units.

[0089] According to another aspect of the present invention, the processing system includes: an event service as a first container plug-in, an upload service as a second container plug-in, and / or a download service as a third container plug-in.

[0090] In a third aspect, the invention relates to a computer program product having a computer program and a computer readable medium. An implementation based mainly on software has the advantage that even previously used processing systems can be easily upgraded by software updates to work in the described manner. In addition to the computer program, such a computer program product may optionally include additional components such as documentation and / or further components, and hardware components such as, for example, a hardware key (dongle, etc.) to use the software.

[0091] In another aspect, the invention relates to a computer program product comprising program elements which are directly loadable into a storage unit of a first providing system and which, when executed by a processing system, cause the processing system to perform a method according to the claimed method and aspects thereof.

[0092] In a fourth aspect, the invention relates to a computer-readable storage medium comprising program elements readable and executable by a processing system to perform the claimed method and aspects thereof when the program elements are executed by the processing system. BRIEF DESCRIPTION OF THE DRAWINGS

[0093] Other objects and features of the present invention will become apparent from the following detailed description considered in conjunction with the accompanying drawings. It should be understood, however, that the drawings are designed for illustration purposes only and not as a definition of the limits of the present invention.

[0094] Figure 1 A schematic flow chart of a first embodiment of a method for processing a medical data set at a processing system by at least one edge application is shown,

[0095] Figure 2 shows a schematic flow chart of a second embodiment of a method for processing a medical data set at a processing system by at least one edge application,

[0096] Figure 3 shows a schematic flow chart of a third embodiment of a method for processing a medical data set at a processing system by at least one edge application,

[0097] Figure 4 shows a schematic flow chart of a fourth embodiment of a method for processing a medical data set at a processing system by at least one edge application,

[0098] Figure 5 shows a schematic flow chart of a fifth embodiment of a method for processing a medical data set at a processing system by at least one edge application,

[0099] Figure 6A schematic flow chart of an embodiment of systems and components involved in a method for processing a medical data set at a processing system by at least one edge application is shown,

[0100] Figure 7 A processing system is shown. DETAILED DESCRIPTION

[0101] Figure 1 A schematic flow chart of a first specific embodiment of a method for processing a medical data set at a processing system PSYS by means of at least one edge application EAPP is shown.

[0102] The first step of this embodiment is a step of first receiving a REC-1 medical data set from a medical system MSYS by a processing system PSYS. In a first embodiment, the medical data set includes medical image data of a patient. Alternatively or additionally, the medical data set may include electronic patient records and / or laboratory diagnostic information and / or information about a patient's pre-existing disease, etc. Typically, the medical data set may include data of a patient. In particular, the medical data set may include data of a patient acquired during an examination of the patient. Alternatively or additionally, the medical data set may include general information about the patient or information about a previous disease. In a first embodiment, the medical system MSYS includes an imaging system (e.g., an X-ray device, a computer tomography device, a magnetic resonance device, a positron emission tomography device, a single photon emission computer tomography device, etc.). Alternatively or additionally, the medical system may include a laboratory diagnostic device, a picture archiving and communication system (abbreviation: PACS), a radiology information system (abbreviation: RIS) and / or a hospital information system (abbreviation: HIS). In particular, the medical system MSYS may include a plurality of different sub-medical systems Sub-MSYS01, Sub-MSYS02, Sub-MSYS03, Sub-MSYS04, Sub-MSYS05, Sub-MSYS06, Sub-MSYS07, Sub-MSYS08. In particular, each sub-medical system Sub-MSYS01, ..., Sub-MSYS08 may be one of the systems listed above. In particular, one of the sub-medical systems Sub-MSYS01, ..., Sub-MSYS08 provides a medical data set to the processing system PSYS. The medical system MSYS and the processing system PSYS are part of a local network NETW.

[0103] The step of initializing INI for at least one cloud application does not have to be performed for each medical data set received, but in this embodiment, if at least one edge application EAPP is not yet available at the processing system PSYS, the step of initializing INI is performed. In other words, the step of initializing INI for at least one edge application EAPP is an optional step. In an alternative embodiment, the step of initializing INI for at least one edge application EAPP can be performed before the step of receiving the first REC-1 medical data set is performed. At least one edge application is designed to process PROC medical data sets. In particular, at least one edge application EAPP is a software application executed by the processing system PSYS. In particular, at least one edge application EAPP can be an external, incompatible application. This means that at least one edge application EAPP is provided by a different party from the processing system PSYS itself. At least one edge application EAPP is based on a cloud-based application CAPP. This means that at least one edge application EAPP and the corresponding cloud-based application CAPP process medical data sets in the same way. Thus, at least one edge application EAPP is executed at the processing system PSYS. In contrast, the corresponding cloud-based application CAPP is executed by the cloud system CSYS. The cloud system CSYS and the processing system PSYS are separated from each other. This means that data transfer between the two systems is possible only with a specific approval. For example, such an approval is given for initializing at least one edge application EAPP from the cloud system CSYS. Furthermore, separation can also mean that the server for hosting the processing system PSYS is spatially located separately from the server for hosting the cloud system CSYS. In the step of initializing at least one edge application EAPP INI, at least one edge application EAPP is initialized at the processing system PSYS so that the at least one edge application EAPP can be executed to process the medical data set.

[0104] In the next step of processing the PROC medical data set, the medical data set is processed by the edge application EAPP. Thus, a processed medical data set is generated. In other words, the processed medical data set is the result of processing the medical data set PROC using at least one edge application EAPP. How to process the medical data set depends on the at least one edge application EAPP executed to process the medical data set. On the other hand, how to process the medical data set depends on the type of the medical data set. In this first embodiment, the type of the medical data set is image data. Alternatively or additionally, the type of the medical data set can be text data, structured data such as DICOM, data of electronic patient records, etc. In the case where the medical data set includes medical image data, processing the medical data set PROC may include, for example, pattern recognition and / or image enhancement and / or image registration (registration) and / or masking (masking), etc. In the case where the medical data set includes text data, processing the medical data set PROC may, for example, include ontology (ontology) and / or text recognition, etc.

[0105] In the step of providing PROV, the processed medical data set is provided to the user. The user may be, for example, a doctor and / or a nurse and / or any other medical staff, and / or even the patient himself. In particular, providing the PROV medical data set may be done via the medical system MSYS. In particular, the processed medical data set may be provided to the user via the sub-medical systems Sub-MSYS01, ..., Sub-MSYS08. The sub-medical systems Sub-MSYS01, ..., Sub-MSYS08 for providing the PROV processed medical data set to the user may be different from or the same as the sub-medical systems Sub-MSYS01, ..., Sub-MSYS08 from which the medical data set is received in the first step of receiving the REC-1 medical data set.

[0106] Figure 2 A schematic flow chart of a second specific embodiment of a method for processing a medical data set at a processing system PSYS by means of at least one edge application EAPP is shown.

[0107] The following steps are as follows Figure 1 The method is performed as described and may include all advantageous features described therein: first receiving a REC-1 medical data set, processing a PROC medical data set and providing a PROV processed medical data set.

[0108] In this embodiment, the optional step of causing at least one edge application to initialize INI includes two steps.

[0109] The first step includes first downloading DOWN-1 an image I-EAPP of at least one edge application EAPP from the cloud system CSYS to the processing system PSYS. The image I-EAPP of at least one edge application EAPP can be, for example, an executable (".exe") file that can be executed at the processing system. In particular, at least one edge application EAPP is built within the cloud system CSYS. The image I-EAPP is published within the cloud system CSYS. If a specific license according to at least one edge application EAPP is provided by the processing system PSYS, the image ImEdgeSys can be downloaded from the cloud system CSYS to the processing system PSYS. By providing the image I-EAPP via the cloud system CSYS, the image I-EAPP can be downloaded by multiple different processing systems PSYS that are part of multiple different local networks NETW. If each local network NETW belongs to another institution such as a clinic, a doctor's office, etc., multiple institutions can access the image I-EAPP. This is much easier than publishing the image I-EAPP via storage media such as hard disks, USB drives, etc.

[0110] In a second step of installing INSTALL of the image I-EAPP of at least one edge application EAPP on the processing system PSYS, the at least one edge application EAPP is installed so that the at least one edge application EAPP can be executed by the processing system PSYS and can be used to process the medical data set. In particular, the image I-EAPP is compiled so that the edge application is executable at the processing system. If the image I-EAPP is provided as an executable file, the file is executed.

[0111] Figure 3 A schematic flow chart of a third specific embodiment of a method for processing a medical data set at a processing system PSYS by means of at least one edge application EAPP is shown.

[0112] As per Figure 1 The following steps are performed as described: first receiving a REC-1 medical data set, causing at least one edge application to initialize INI, processing a PROC medical data set, and providing a PROV processed medical data set. In an alternative embodiment, according to Figure 2 , the step of initializing at least one edge application INI may include the following two steps: first downloading DOWN-1 an image I-EAPP of at least one edge application EAPP; and installing the INSTALL image I-EAPP.

[0113] In particular, multiple edge applications EAPP can be executed by the processing system PSYS. In particular, the number of executable edge applications EAPP depends on a specific license, which is provided by the local network NETW (corresponding to the processing system PSYS) and serves as permission to download the corresponding edge application EAPP from the cloud system CSYS.

[0114] In the second step of receiving REC-2, the associated data is received by the processing system PSYS. In an alternative embodiment, the step of receiving the second REC-2 associated data can be performed before the step of receiving the first REC-1 medical data set. The associated data includes information about which edge application EAPP of multiple edge applications EAPP the medical data set should be processed by. The associated data can also be provided by the medical system MSYS (correspondingly by the sub-medical system Sub-MSYS01, ..., Sub-MSYS08). Alternatively, the associated data can be manually provided by user input. In an alternative embodiment, the associated data can also include processing information. The processing information determines whether the medical data set should be processed by at least one edge application EAPP as described above and which is defined by the associated data, or whether it should be processed by the corresponding cloud-based application CAPP in the cloud system CSYS. The processing information can be manually determined by the user. Alternatively, the processing information can be determined based on the type of medical data set or the size of the medical data set. If the medical data set includes sensitive data, it is more advantageous to process the medical data set locally using at least one edge application EAPP without loading it into the cloud system CSYS. If the medical data set is large, loading it into the cloud system CSYS may take too long and it may also be preferred to process it locally. A threshold in this regard may be set manually or automatically depending on the bandwidth of the connection between the processing system PSYS and the cloud system CSYS.

[0115] In the step of selecting SEL at least one edge application EAPP according to the associated data, at least one edge application EAPP is selected that should be used to process the medical data set.

[0116] Depending on this selection, in the step of transmitting the TRANS medical data set, the medical data set is transmitted to at least one edge application EAPP.

[0117] The steps of first receiving REC-1 a medical data set, second receiving REC-2 associated information, selecting SEL at least one edge application EAPP according to the associated information, transmitting TRANS the medical data set to at least one edge application EAPP and providing PROV a processed medical data set are supervised by the coordinator ORCH. The coordinator ORCH is designed to control these steps and processes. In particular, the coordinator ORCH comprises at least one agent, which is necessary to realize the communication and / or data exchange between the individual components of the processing system PSYS and between the processing system PSYS and the cloud system CSYS. Figure 6 Possible components of a processing system are schematically depicted and described in FIG.

[0118] Figure 4 A schematic flow chart of a fourth specific embodiment of a method for processing a medical data set at a processing system PSYS by means of at least one edge application EAPP is shown.

[0119] Usually according to Figure 1 The following steps are performed as described: first receiving a REC-1 medical data set, causing at least one edge application to initialize INI, processing a PROC medical data set, and providing a PROV processed medical data set. In an alternative embodiment, according to Figure 2 , the step of initializing at least one edge application INI may include the following two steps: first downloading DOWN-1 at least one edge application EAPP image I-EAPP; and installing INSTALL image I-EAPP. Figure 3 The following steps are performed as described: second receiving data associated with REC-2, selecting SEL at least one edge application EAPP, and transmitting TRANS the medical data set to at least one edge application EAPP.

[0120] The step of selecting SEL at least one edge application EAPP and providing PROV a processed medical data set includes the following steps: the event service ES notifies NTF-1, NTF-2 at least one edge application EAPP or the coordinator ORCH according to the associated data. The event service ES is a container plugin. The event service ES is designed to communicate with the coordinator ORCH via the proxies PROXY01, PROXY02, PROXY03, PROXY04, and PROXY05 of the coordinator ORCH. In addition, the event service ES is designed to communicate with at least one edge application EAPP. In an advantageous embodiment, the event service ES is designed to communicate with all edge applications EAPP in a plurality of edge applications EAPP that can be executed by the processing system PSYS.

[0121] In the step of selecting SEL at least one edge application EAPP, the coordinator ORCH informs the event service ES which edge application EAPP should be used to process the medical data set based on the associated data. Alternatively, the coordinator ORCH transmits the associated data to the event service ES, and the event service ES reads out which edge application EAPP should be executed from the associated data. The event service ES notifies, respectively informs, and respectively activates at least one edge application EAPP based on the associated data. In other words, the event service ES informs at least one edge application EAPP that there is an available medical data set that should be processed. Notifying at least one edge application EAPP is given in the step of notifying NTF-1 at least one edge application.

[0122] In the step of providing PROV the processed medical data set, the event service ES informs the coordinator ORCH that the processed medical data set is available in the step of notifying the NTF-2 coordinator ORCH. Therefore, the coordinator ORCH can initiate, for example, downloading the processed medical data set to the medical system MSYS, respectively to the sub-medical systems Sub-MSYS01, ..., Sub-MSYS08. For this purpose, the event service ES is informed by at least one edge application EAPP or by the upload service US described below that the processed medical data set is available.

[0123] As such, it is not necessary that the coordinator ORCH is designed to communicate with all edge applications EAPP. Since edge applications EAPP may be external, incompatible applications, several different interfaces (respectively proxies PROXY01, ..., PROXY05) may be required to communicate with all edge applications EAPP.

[0124] In this embodiment, the step of first receiving the REC-1 medical data set and providing the PROV processed medical data set comprises the step of uploading the medical data set, the processed medical data set UP-1, UP-2 to the upload service US, respectively. The upload service US is a second container plugin executed by the processing system PSYS. The upload service US is designed to store the medical data set and / or the processed medical data set.

[0125] In a first step of receiving a REC-1 medical dataset, in a step of uploading a UP-1 medical dataset, the medical dataset is uploaded from the medical system MSYS to the upload service US via the coordinator ORCH. Therefore, the coordinator ORCH comprises agents Prox01, ..., Prox05 to communicate with the medical system MSYS and with the upload service US and / or to exchange data between them. In an alternative embodiment, the coordinator ORCH only supervises the transmission of the medical dataset from the medical system MSYS to the upload service US. The medical dataset is stored in the upload service US.

[0126] In the step of providing the PROV processed medical data set, in the step of uploading the UP-2 processed medical data set, the processed medical data set is transmitted from the at least one edge application EAPP to the upload service US. The processed medical set is stored in the upload service US. The upload service US may inform the event service ES that the processed medical data set is available. The event service ES then notifies the coordinator ORCH that the processed medical data set is available. The steps of uploading the UP-2 processed medical data set and notifying the NTF-2 coordinator ORCH through the event service ES included in the step of providing the PROV processed medical data set may be performed in any order.

[0127] In this embodiment, the step of transmitting TRANS the medical data set to at least one edge application EAPP comprises the following steps: second downloading DOWN-2 the medical data set stored in the upload service US via the download service DS. The download service DS is a third container plugin executed by the processing system PSYS. In other words, the download service DS transmits the medical data set to be processed to at least one edge application EAPP. The at least one edge application EAPP has been notified by the event service ES that there is an available medical data set, which should be processed by at least one edge application.

[0128] Figure 5 A schematic flow chart of a fifth specific embodiment of a method for processing a medical data set at a processing system PSYS by means of at least one edge application EAPP is shown.

[0129] Usually according to Figure 1 The following steps are performed as described: first receiving a REC-1 medical data set, causing at least one edge application to initialize INI, processing a PROC medical data set, and providing a PROV processed medical data set. In an alternative embodiment, according to Figure 2 , the step of initializing at least one edge application INI may include the following two steps: first downloading DOWN-1 at least one edge application EAPP image I-EAPP; and installing INSTALL image I-EAPP. Figure 3 The following steps are performed as described: second receiving data associated with REC-2, selecting SEL at least one edge application EAPP, and transmitting TRANS the medical data set to at least one edge application EAPP.

[0130] according to Figure 4 The following steps are performed according to the description: notifying at least one edge application EAPP and / or coordinator ORCH of NTF-1, NTF-2 through the event service ES, uploading the medical data set and / or processed medical data set UP-1, UP-2 to the upload service US, and downloading the DOWN-2 medical data set for the second time via the download service DS.

[0131] In this embodiment, the step of the second reception REC-2 also includes the step of uploading the associated data UP' to the upload service US. The step of uploading the associated data UP' is performed in the same manner as the step of uploading the UP medical data set and / or the processed medical data set. In this embodiment, the associated data is also stored in the upload service US. This is particularly important if the associated information includes additional information on how to process the medical data set. Such information may be important for at least one edge application EAPP. In this case, it is advantageous to upload the associated data to the upload service US so that at least one edge application EAPP can access the associated data via the download service DS. In this embodiment, the download service DS is also designed to download the associated data from the upload service US to at least one edge application EAPP.

[0132] Figure 6 A schematic diagram of an embodiment of systems and components involved in a method for processing a medical data set at a processing system PSYS by means of at least one edge application EAPP is shown.

[0133] The local network NETW includes a medical system MSYS and a processing system PSYS.

[0134] The medical system MSYS includes a plurality of sub-medical systems Sub-MSYS01, ..., Sub-MSYS08. Such sub-medical systems Sub-MSYS01, ..., Sub-MSYS08 may be, for example, imaging systems, PACS, RIS, HIS, personal computers in a local network, etc. The number of sub-medical systems Sub-MSYS01, ..., Sub-MSYS08 is not fixed. In a preferred embodiment, the medical system MSYS includes at least one sub-medical system Sub-MSYS01, ..., Sub-MSYS08.

[0135] The processing system PSYS includes a coordinator ORCH, at least one edge application EAPP, an event service ES, an upload service US and a download service DS. Thus, the coordinator ORCH includes a plurality of agents Prox01, ..., Prox05. The number of agents is not fixed. The coordinator ORCH serves as a communication interface and supervisor. The communication structure and / or the data exchange structure are visualized by arrows between the system and the components. The coordinator ORCH can communicate and exchange data with the medical system MSYS. In addition, the coordinator ORCH can communicate and / or exchange data with the event service ES and the upload service US, which are part of the processing system PSYS. In addition, the coordinator ORCH can communicate and / or exchange data with the cloud system CSYS.

[0136] The cloud system CSYS comprises a configuration service CS, at least one cloud-based application CAPP corresponding to at least one edge application EAPP, and at least an image I-EAPP of the at least one edge application EAPP.

[0137] The configuration service CS is designed to store configuration data of the processing system PSYS and / or at least one edge application EAPP. In addition, the configuration service CS can be designed to provide updates for at least one edge application EAPP, wherein the updates are published within the cloud system CSYS. Furthermore, in some embodiments, the configuration service CS is designed to store backups, correspondingly storing images of the processing system PSYS. Furthermore, the backup may include initialized edge applications EAPP of the processing system PSYS. Furthermore, the backup may include parameter settings of at least one edge application EAPP. In the event of a crash, the entire processing system PSYS including the corresponding edge application EAPP can be reinstalled without having to provide specific permissions again, first download DOWN-1, and install the INSTALL edge application EAPP.

[0138] The cloud-based application CAPP can also be executed to process the medical data set. For this purpose, the medical data set must be transferred to the cloud system CSYS. This can be done via the coordinator ORCH as indicated by the arrow. For this purpose, the coordinator ORCH must be informed that the medical data set should be processed by the cloud-based application CAPP. This can be done by manual input by the user, or the information can be provided by the associated data as processing information. The processing information can be determined manually by the user, or it can be determined automatically based on the details of the connection between the cloud system CSYS and the processing system PSYS.

[0139] An image I-EAPP of at least one edge application EAPP may be downloaded for initializing the at least one edge application EAPP INI at the processing system PSYS.

[0140] The interactions between the coordinator ORCH, at least one edge application EAPP, the event service ES, the upload service US and the download service DS are indicated by arrows. Further explanation of these interactions is given in accordance with Figure 4 and Figure 5 is given in the description.

[0141] For a detailed description of the individual steps, see Figures 1 to 5 .

[0142] Figure 7 A processing system PSYS is shown. The shown processing system PSYS is configured to perform the method according to the invention for processing a medical data set by at least one edge application. The processing system PSYS comprises an interface PSYS.IF, a calculation unit PSYS.CU and a storage unit PSYS.MU.

[0143] The processing system PSYS can be, in particular, a computer, a microcontroller or an integrated circuit. Alternatively, the processing system PSYS can be a real network or a virtual network of computers (the technical term for a real network is a "cluster" and the technical term for a virtual network is a "cloud"). The processing system PSYS can also be designed as a virtual system executed on a computer, a real network of computers or a virtual network of computers (the technical term is "virtualization").

[0144] The interface PSYS.IF can be a hardware interface or a software interface (e.g. a PCI bus, USB or FireWire). The computing unit PSYS.CU can have hardware elements or software elements, such as a microprocessor or a so-called FPGA (short for "field programmable gate array"). The memory unit PSYS.MU can be implemented as a non-permanent working memory (random access memory, RAM for short) or as a permanent mass storage device (hard disk, USB stick, SD card, solid state disk).

[0145] The interface PSYS.IF can in particular comprise a plurality of sub-interfaces for carrying out different steps of the respective method. In other words, the interface PSYS.IF can also be understood as a plurality of interfaces PSYS.IF. The computing unit PSYS.CU can in particular comprise a plurality of sub-computing units for carrying out different steps of the respective method. In other words, the computing unit PSYS.CU can also be understood as a plurality of computing units PSYS.CU.

[0146] Whether or not explicitly described, individual embodiments or individual aspects and features thereof may be combined or exchanged with one another without limiting or expanding the scope of the described invention, provided that such combination or exchange makes sense and is in the sense of the invention. Where applicable, the advantages described with respect to one embodiment of the invention also benefit other embodiments of the invention.

Claims

1. A computer-implemented method for processing a medical data set, in, The method comprises the following steps: - first receiving (REC-1) a medical data set from a medical system (MSYS), wherein the medical system (MSYS) is part of a local network (NETW), - accessing a cloud system (CSYS) comprising an image of at least one edge application (EAPP), said at least one edge application (EAPP) corresponding to a cloud-based application (CAPP) stored in said cloud system (CSYS); - downloading and installing an image of the at least one edge application (EAPP) from the cloud system (CSYS) on the processing system (PSYS) of the local network (NETW) to initialize the at least one edge application (EAPP) on the processing system (PSYS) of the local network (NETW), wherein the cloud system (CSYS) is separated from the local network (NETW), wherein the edge application (EAPP) is a software application executed by the processing system (PSYS), - determining whether the medical data set is to be processed by the at least one edge application (EAPP) or by the cloud-based application (CAPP); - processing (PROC) the medical dataset by at least one of the at least one edge application (EAPP) and the cloud-based application (CAPP) by inputting the medical dataset into the at least one edge application (EAPP) or the cloud-based application (CAPP), Thus generating a processed medical dataset, wherein the at least one edge application (EAPP) and the cloud-based application (CAPP) are configured to process the medical dataset in the same manner, - PROVing said processed medical dataset.

2. The method according to claim 1, in, A plurality of edge applications (EAPP) can be executed by the processing system (PSYS), The following steps are also included: - a second reception (REC-2) by said processing system (PSYS) of associated data, said associated data being related to said medical data set, - selecting (SEL), by said processing system (PSYS), said at least one edge application (EAPP) from said plurality of edge applications (EAPP) based on said associated data, - transmitting (TRANS) the medical data set to the at least one edge application (EAPP).

3. The method according to claim 2, in, The associated data includes processing information whether the medical data set should be processed using the cloud-based application (CAPP) or using the edge application (EAPP) in accordance with the cloud-based application (CAPP).

4. The method according to claim 2 or 3, in, The steps of first receiving (REC-1), second receiving (REC-2), selecting (SEL), transmitting (TRANS) and providing (PROV) are supervised by a coordinator (ORCH) according to the associated data, Therein, the coordinator (ORCH) is a software application executed by the processing system (PSYS).

5. The method according to claim 4, in, The step of selecting (SEL) the at least one edge application (EAPP) and / or the step of providing (PROV) the processed medical data set comprises the following steps: - notifying (NTF-1, NTF-2) said at least one edge application (EAPP) and / or said coordinator (ORCH) via an event service (ES), Therein, the event service (ES) is a first container plug-in executed by the processing system (PSYS).

6. The method according to claim 3 or 5, in, The first receiving (REC-1) and providing (PROV) step comprises the following steps: - uploading (UP-1, UP-2) said medical data set and / or said processed medical data set to an upload service (US), wherein the upload service (US) is a second container plug-in executable by the processing system (PSYS), The upload service (US) stores the medical dataset and / or the processed medical dataset.

7. The method according to claim 6, in, The TRANS step includes the following steps: - a second downloading (DOWN-2) of a medical dataset stored in said upload service (US) by said at least one edge application (EAPP) via a download service (DS), Wherein, the download service (DS) is a third container plug-in executed by the processing system (PSYS).

8. The method according to one of claims 1 to 3, 5 and 7, in, An image (I-EAPP) of the at least one edge application (EAPP) and / or a configuration of the processing system (PSYS) are stored in the cloud system (CSYS).

9. The method according to claim 8, in, An image (I-EAPP) of the at least one edge application (EAPP) and / or a configuration of the processing system (PSYS) is stored in a configuration service (CS) within the cloud system (CSYS).

10. The method according to claim 9, in, The at least one edge application (EAPP) is downloadable from the cloud system (CSYS), Wherein, the configuration service (CS) provides updates for the at least one edge application (EAPP).

11. The method according to claim 9, in, A backup of said at least one edge application (EAPP) and / or said processing system (PSYS) is stored in said configuration service (CS).

12. The method according to one of claims 1 to 3, 5, 7, 9, 10 and 11, in, The medical data set includes medical image data.

13. The method according to claim 12, in, Processing (PROC) the medical dataset comprises pattern recognition and / or image registration and / or image enhancement and / or masking.

14. A processing system (PSYS) for processing a medical data set, in, The processing system (PSYS) comprises an interface (PSYS.IF) and a computing unit (PSYS.CU), - wherein the interface (PSYS.IF) is configured for first receiving (REC-1) a medical data set from a medical system (MSYS), wherein the medical system (MSYS) is part of a local network (NETW), - wherein the interface (PSYS.IF) and / or the computing unit (PSYS.CU) are configured for accessing a cloud system (CSYS) comprising an image of at least one edge application (EAPP), the at least one edge application (EAPP) corresponding to a cloud-based application (CAPP) stored in the cloud system (CSYS); - wherein the interface (PSYS.IF) and / or the computing unit (PSYS.CU) are configured to download and install an image of the at least one edge application (EAPP) from the cloud system (CSYS) on the processing system (PSYS) of the local network (NETW) to initialize the at least one edge application (EAPP) on the processing system (PSYS) of the local network (NETW), wherein the cloud system (CSYS) is separated from the local network (NETW), wherein the edge application (EAPP) is a software application executed by the processing system (PSYS), wherein the computing unit (PSYS.CU) is configured to determine whether the medical data set is to be processed by the at least one edge application (EAPP) or by the cloud-based application (CAPP); - wherein the computing unit (PSYS.CU) is further configured for processing (PROC) the medical data set by at least one of the at least one edge application (EAPP) and the cloud-based application (CAPP) by inputting the medical data set to the at least one edge application (EAPP) or the cloud-based application (CAPP), Thus generating a processed medical dataset, wherein the at least one edge application (EAPP) and the cloud-based application (CAPP) are configured to process the medical dataset in the same manner, - wherein said interface (PSYS.IF) is further configured for providing (PROV) said processed medical data set.

15. The processing system (PSYS) according to claim 14, in, The processing system (PSYS) comprises: an event service (ES) as a first container plug-in, an upload service (US) as a second container plug-in and / or a download service (DS) as a third container plug-in.

16. A computer program product comprising a program element which can be directly loaded into a storage unit of a processing system (PSYS) and which, when executed by the processing system (PSYS), causes the processing system (PSYS) to perform a method according to any one of claims 1 to 13.

17. A computer-readable storage medium comprising program elements that can be read and executed by a processing system (PSYS) to perform the method of one of claims 1 to 13 when said program elements are executed by said processing system (PSYS).

Images