Patent ID: 12217864

DESCRIPTION OF PREFERRED EMBODIMENTS

Referring to the drawings, different examples will now be described in more detail with reference to the attached figures. The thicknesses of lines, layers and/or areas may be exaggerated in the Figures for the illustration.

Additional examples may cover modifications, equivalents and alternatives, which are within the scope of the disclosure. Identical or similar reference numbers pertain in the entire description of the figures to identical or similar elements, which may be implemented in a mutually identical form or in a similar form in a comparison with one another, while they provide the same function or a similar function.

It is apparent that if an element is described as being “connected” or “coupled” to another element, the elements may be connected or coupled directly or via one or more intermediate elements. If two elements A and B are combined with the use of an “or,” this shall be understood to mean that all possible combinations are disclosed, i.e., only A, only B as well as A and B, unless something else is explicitly or implicitly defined. An alternative formulation for the same combinations is “at least one of A and B” or “A and/or B.” The same applies, mutatis mutandis, to combinations of more than two elements.

Exemplary embodiments will be explained in more detail below. A license for using a system function, which is provided by a network component, is shared in this case from a first medical device to a second medical device. The network component, the first medical device and the second medical device are coupled in this case via a network, i.e., these can communicate with one another via the network. Typical networks, which may be configured for use for this purpose, are Internet protocol-based networks, such as LANs (Local Area Networks), WANs (Wide Area Networks), WLANs (Wireless LANs), Internet, Intranet, etc.

FIG.1shows a block diagram of an exemplary embodiment of a process10for a first medical device for the use of a license-based system function of a network component in a network. The process comprises a transmission11of a request for an available license into the network and a reception12of a reply from a second medical device. The reply indicates that a license for the system function is available at the second medical device. The process comprises, moreover, a request13for the available license from the second medical device and a reception14of information on the available license from the second medical device. The process further provides for a use15of the system function with the use of the information on the license from the second medical device.

The medical devices are defined as terminals in this case, which carry out certain functions at a patient or at a hospital bed. These are connected via the network to one another and also to the network component. The network component may be any desired server, access/gateway or network node, which offers the system function, e.g., a service or an access, to the medical devices. The system function is not available freely, but is subject to a permit (license) for their use.

A license is defined, in general, as a permit to use, for example, for a software, for an access or for a function. An example is the permit to use said system function, which is offered by the network component.

A process is shown from the viewpoint of the second medical device inFIG.2.FIG.2shows a block diagram of an exemplary embodiment of a process20for providing a license for a first medical device from a second medical device. The process comprises a reception21of a request for an available license from the first medical device at the second medical device and a transmission of a reply from the second medical device to the first medical device. The reply indicates that the license for the system function is available at the second medical device. As is also shown inFIG.2, a reception23of a request for the available license at the second medical device and a provision24of information on the available license by the second medical device to the first medical device will follow.

FIG.3shows a block diagram of an exemplary embodiment of a process30for a network component for providing a system function for medical devices in a network. The process30provides for a use31of a license for the system function for a first medical device and for a provision32of the system function for the first medical device based on the license. The use31may also comprise in some exemplary embodiments an issuance of the license. It is, however, also possible, in general, that the license was originally issued by a licensing unit, which does not correspond to the network component. The process30comprises, moreover, a reception33of a request for the system function from a second medical device and a reception34of information on the license from the second medical device. The process comprises, furthermore, a provision35of the system function for the second medical device based on the license.

In some exemplary embodiments, the license may be shared again by the first medical device. The process10comprises in this case a reception of a request for an available license for the system function from a third medical device and a transmission of a reply to the third medical device, wherein the reply indicates that the license for the system function is available at the first medical device. The process10further comprises in this case a reception of a request for the available license from the third medical device and a provision of the information on the available license to the third medical device.

FIG.4shows a block diagram of an exemplary embodiment of a device40for a medical device400and a block diagram of an exemplary embodiment of a medical device400. Optional components are indicated by broken lines.FIG.4shows, moreover, a block diagram of an exemplary embodiment of a device50for a network component500and a block diagram of an exemplary embodiment of a network component500.

The device40for the medical device400for using a system function of the network component500in a network600comprises an interface42, which is configured for the communication in the network600. The communication in the network600is indicated by two-ended arrows drawn in broken lines. The device40comprises, moreover, a control module44, which is coupled with the interface42and which is configured for carrying out one of the processes10or20.FIG.4also illustrates an exemplary embodiment of a medical device400with a device40(in a view drawn in broken lines, because it is optional from the viewpoint of the device40).

FIG.4shows, moreover, an exemplary embodiment of a device50for a network component500for providing a system function for medical devices400in a network600. The device50comprises an interface52, which is configured for the communication in the network600. The device50comprises, moreover, a control module54, which is coupled with the interface52, and which is configured for carrying out one of the processes30.FIG.4also illustrates an exemplary embodiment of a network component500with the device50(drawn with broken lines, because it is optional from the viewpoint of the device50).

FIG.4illustrates, moreover, a system700, which may comprise a plurality of medical devices400, and which comprises at least one network component500.

The interfaces42,52may be configured in exemplary embodiments as typical interfaces for communication in networks. For example, these may be configured in exemplary embodiments as corresponding contacts. They may also be configured in exemplary embodiments as separate hardware. They may comprise memories, which store the signals to be transmitted and/or to be received at least temporarily. The interfaces42,52may be configured to receive electrical signals, for example, as a bus interface, as an optical interface, as an Ethernet interface, as a wireless interface, etc. The interfaces42,52may, moreover, also be configured in exemplary embodiments for wireless transmission and comprise a radio front end as well as corresponding antennas. Further, the interfaces42,52may comprise synchronization mechanisms for the one or more types of connection for the synchronization with the respective transmission medium.

The control modules4454may comprise in exemplary embodiments one or more freely selectable controllers, microcontrollers, network processors, processor cores, such as Digital Signal Processor cores (DSPs), programmable hardware components, etc. Exemplary embodiments are not limited to a particular type of processor core. Any desired processor cores or even a plurality of processor cores or microcontrollers are conceivable for implementing a control module44,54. Implementations in an integrated form with other devices are conceivable as well, for example, in a control unit, which additionally also comprises one or more other functions. A control module44,54may be embodied in exemplary embodiments by a processor core, by a computer processor core (CPU=Central Processing Unit), by a graphics processor core (GPU=Graphics Processing Unit), by an application-specific integrated circuit core (ASIC=Application-Specific Integrated Circuit), by an integrated circuit (IC=Integrated Circuit), by a one-chip system core (SOC=System on Chip), by a programmable logic element or by a field-programmable gate array with a microprocessor (FPGA=Field Programmable Gate Array) as the core of the component or of the components.

Accordingly, a licensing of system functions can take place in exemplary embodiments. A possibility of using this system function can thus be created in a distributed system of electromedical devices400and clinical IT systems500. It is potentially unnecessary for all the components to have originated from one manufacturer, and it can thus also be possible that licenses are distributed to third parties, without these having to use the same licensed technology. The above-mentioned medical devices (first medical device and second medical device,FIGS.1and2) may thus originate from different manufacturers.

In some exemplary embodiments, the provision or use of the system function can be terminated or stopped after the license has been shared. The process10will in this case comprise on the side of the sharing medical device a termination of a use of the system function by the sharing medical device after the provision of the information on the available license to another medical device receiving the license. From the viewpoint of the network component500, the process30taking place there comprises, furthermore, a termination of the provision of the system function for the first (sharing) medical device prior to the provision of the system function for the second medical device (medical device receiving the license). Moreover, the process30may comprise a refusal to provide the system function for the second medical device on the side of the network component providing the system function if the checking shows a negative result.

A system700may comprise in exemplary embodiments 1 . . . n (n=positive integer) system function participants, e.g., electromedical devices (medical devices) and/or clinical IT systems (network components). The respective interfaces42,52may be configured for installing a license. The devices40,50may have, moreover, storage possibilities in order to store the installed licenses. The interfaces42,52may, moreover, be configured to authenticate the individual components.

The use15of the system function may comprise a provision of the license for the network component500for checking and activating the system function. A checking of a valid sharing of the license from the first medical device to the second medical device can take place from the viewpoint of the network component500. This may take place, for example, by receiving a confirmation of the sharing from the first medical device.

Another mechanism, which can be used in exemplary embodiments for the mutual authentication and verification of the license, is the use of certificates. The information on the license may be contained in a certificate. For example, a secure communication channel may be established between the individual components. Secure means in this connection that the communication channel is secured by coding. The use of the system function may comprise the establishing of a secured communication channel between the medical device400and the network component500. The establishing of such a secure channel may likewise take place between medical devices for sharing the license. One possibility of achieving this is the use of TLS (Transport Layer Security) with an X.509 certificate, which points to a Trust Root. X.509 is a standard for issuing digital certificates, whose authenticity is guaranteed by a certification unit (Trust Root, trustworthy source). A coded and hence secure communication can be established in this case on the basis of one or more key pairs, a public key and a private key each.

The system shown inFIG.4may then also have one or more system function providers (network components)500, e.g., a clinical IT system, but electromedical devices may offer a system function as well, and they may accordingly be network components500. At least one system function is provided in this case, and a plurality of system functions are preferably provided, which must be activated by a license. Further examples of such a system function are report generation, the sharing of data, and the calculation of clinical parameters or diagnoses. The system function may comprise, for example, the recording of a diagnostic electrocardiogram, ECG.

The devices40,50may comprise in exemplary embodiments corresponding memories for “Trust Root(s)” or certification, as well as the above-described communication interfaces42,52, via which authentication information and licenses can be selected. Moreover, data and/or commands can be received via the communication interfaces42,52from other components or be transmitted to these.

FIG.5shows a sequence diagram in an exemplary embodiment.FIG.5shows two medical devices400aand400b(patient monitors) as well as a network component500(IT component). The medical device400breceives in this exemplary embodiment a license for a system function (diagnostic ECG), which is offered by the IT component500. The medical device400btransmits for this a search request for devices that have a license of this type into the network. The transmission11of the request for the available license into the network comprises in this exemplary embodiment a transmission of a wireless message in the network.

The wireless message is received,21, by the medical device400a, after which this gives a positive reply22(license available) to this. The medical device400bmakes a concrete request13for the available license to the medical device400aupon receiving12the reply (potentially a plurality of replies from the network). This medical device400areceives,23, the request and provides,24, corresponding information on the available license for the medical device400b. Should the license still be needed by the medical device400a, the provision of the license may also be refused to the medical device400b(last step inFIG.5). After reception14of the information on the license, the license is used,15, by the medical device400b. In the exemplary embodiment according toFIG.5, a communication channel is established at first for the request33for the system function “diagnostic ECG” to the network component500and it is checked there. The license information is then selected by the network component from the medical device400b. In case of a valid license, the system function is then provided,35, by the network component.

The license may have been provided before by the network component500to the medical device400a. A certificate may accordingly be provided for the system function participant at a communication interface by the network component500or also by another licensor. Further, corresponding communication partners, which offer, for example, one or more system functions, are provided by the network.

The network component500or another licensor may generate in exemplary embodiments a license for the use of the at least one optional system function including license information. For example, the generated license information comprises a license code, a license goal, etc. The generated license may then be installed in the system function participant (medical device) for the use of the optional system function provided by the system function provider500. A communication can in this case be established between the system function participant400a,400band the system function provider500, and the system function provider500may check authentication information for trustworthiness, for example, by an X.509 certificate chain.

The respective licenses and also communication partners may in this case be authenticated, and their public keys may be checked, for example, by certificates. Depending on the communication sequence, a certificate chain can thus be established, and the authenticity of a key can be checked with a preceding certificate. It is also possible to speak of validation or certification paths in this procedure.

A reading of license information from the system function participant400a,400bcan then be carried out by means of a checked (secure) communication channel by the system function provider. The optional system function of the system function provider can then be activated after successful checking of the read license information. For example, the license information was checked successfully precisely when the read license information matches the optional system function.

A message, which indicates that the license is no longer available at the system function participant, can optionally be received at the network component500in some additional exemplary embodiments. The activation of the system function may optionally be carried out by the system function participant, or an optional activation of the function can take place for system function participants who do not have a license if a certain number of electromedical components have an active license.

For example, 10 devices400are purchased from a manufacturer in another exemplary embodiment, and the manufacturer has also sold the system function provider500. Additional devices400were purchased from third parties and from the first manufacturer. If the number of active licenses exceeds 12, the function is activated for 6 devices from third parties. Licenses can be automatically exchanged between the electromedical devices400in exemplary embodiments. A license may be bound to a certificate and is thus automatically bound to one end point and to one time interval. In some exemplary embodiments, the licenses are not licenses that activate a function on the electromedical device, but they do so at the system function provider. Moreover, a license can only be shared to a communication partner if this is trustworthy. Different types of licenses are, for example, tokens, BoundToEndpoint, Floating, etc.

For example, 10 patient monitors400from company A have a license each at a gateway G500from company A. The gateway G500also allows the export of the data for devices from a third company B in this case.

A patient monitor PM1400ahas a license for the determination of diagnostic ECG. The diagnostic ECG will be determined by a clinical IT component S500. A second patient monitor PM2400bhas at first no license for the determination of diagnostic ECG. Instead of replacing the device400bat the patient, the patient monitor PM2400bsearches for devices, for example, by means of wireless message in the network, which have a license of a defined type, and takes over this floating license in the network. It can then activate the clinical component S500.

A patient monitor PM1400bmay refuse to provide the licenses used for a communication partner, e.g., if this does not correspond to the license goal indicated, cf. last step inFIG.5.

The information can be generated, exchanged and checked independently from a defined license technology due to the certificates. The certificate chain can be checked instead of a proprietary format. A markedly increased failure safety may be achieved due to the elimination of a central component.

Exemplary embodiments may be, for example, a computer program with a program code for carrying out one or more of the above processes, or the exemplary embodiments may refer to these if the computer program is executed on a computer or processor. Steps, operations or processes of different, above-described processes may be carried out by programmed computers or processors. Examples may also cover program storage devices, e.g., digital data storage media, which are machine-, processor- or computer-readable and code machine-executable, processor-executable or computer-executable programs of instructions. The instructions execute some or all of the steps of the above-described processes or cause these to be executed. The program storage devices may comprise or be, e.g., digital memories, magnetic storage media, for example, magnetic disks and magnetic tapes, hard drives or optically readable digital storage media. Additional examples may also cover computers, processors or control units, which are programmed to execute the steps of the above-described processes, or (field)-programmable logic arrays ((F)PLAs=(Field) Programmable Logic Arrays) or (field)-programmable gate arrays ((F)PGA=(Field) Programmable Gate Arrays), which are programmed to execute the steps of the above-described processes.

Functions of different elements shown in the figures as well as the function blocks indicated may be implemented in the form of dedicated hardware, e.g., of “a signal provider,” “of a signal processor unit,” “of a processor,” “of a control,” etc., as well as as hardware capable of executing software in conjunction with corresponding software. In case of provision by a processor, the functions may be provided by an individual dedicated processor, by an individual, jointly used processor or by a plurality of individual processors, some of which or all of which may be used together. However, the term “processor” or “control” is not limited exclusively to hardware exclusively capable of executing software, but it may comprise digital signal processor hardware (DSP hardware; DSP=Digital Signal Processor), network processor, application-specific integrated circuit (ASIC=Application Specific Integrated Circuit), field-programmable logic array (FPGA=Field Programmable Gate Array), read-only memory (ROM=Read Only Memory) for storing software, random excess memory (RAM=Random Access Memory) and nonvolatile storage device (storage). Other hardware, conventional and/or customer-specific, may be included as well.

A block diagram may represent, for example, a general circuit diagram, which implements the principles of the disclosure. Similarly, a flow chart, a state transition diagram, a pseudocode and other similar processes may represent operations or steps, which are represented, for example, essentially in a computer-readable medium and are thus executed by a computer or processor, regardless of whether such a computer or processor is explicitly shown. Processes disclosed in the description or in the patent claims may be implemented by a component, which has means for executing each of the respective steps of these processes.

It is apparent that the disclosure of a plurality of steps, processes, operations or functions disclosed in the description or in the claims shall not be interpreted such that these are located in the defined order, unless this is explicitly or implicitly indicated otherwise, e.g., for technical reasons. Therefore, these are not limited to a defined order by the disclosure of a plurality of steps or functions, unless these steps or functions are not interchangeable for technical reasons. Further, an individual step, function, process or operation may include in some examples a plurality of partial steps, partial functions, partial processes or partial operations and/or may be divided into these. Such partial steps may be included and be a part of the disclosure of this individual step, unless they are explicitly ruled out.

While specific embodiments of the invention have been shown and described in detail to illustrate the application of the principles of the invention, it will be understood that the invention may be embodied otherwise without departing from such principles.

LIST OF REFERENCE NUMBERS

10Process for a first medical device for the use of a license-based system function of a network component in a network11Transmission of a request for an available license into the network12Reception of a reply from a second medical device, wherein the reply indicates that a license for the system function is available at the second medical device13Request for the available license from the second medical device14Reception of information on the available license from the second medical device15Use of the system function with the use of the information on the license from the second medical device20Process for providing a license to a first medical device from a second medical device, wherein the license authorizes the use of a license-based system function for a network component in a network21Reception of a request for an available license from the first medical device at the second medical device22Transmission of a reply from the second medical device to the first medical device, wherein the reply indicates that the license is available for the system function at the second medical device23Reception of a request for the available license at the second medical device24Provision of information on the available license by the second medical device to the first medical device30Process for a network component for providing a system function for medical devices in a network31Use of a license for the system function for a first medical device32Provision of the system function for the first medical device based on the license33Reception of a request for the system function from a second medical device34Reception of information on the license from the second medical device35Provision of the system function for the second medical device based on the license40Device for a medical device for the use of a system function of a network component in a network42Interface44Control module50Device for a network component for the provision of a system function for medical devices in a network52Interface54Control module400Medical device400aMedical device400bMedical device500Network component600network700System