Computer implementation method
By establishing a secure communication channel between the host device and the algorithm service, transmitting and processing health care data, the problem of lack of security measures for local host medical algorithm equipment in the networked service environment is solved, and the networked service environment is realized. The effect of safely processing sensitive data.
Patent Information
- Application Number
- CN202410713911.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2023-06-05
- Filing Date
- 2024-06-04
- Publication Date
- 2024-12-06
AI Technical Summary
Existing localhost-only medical algorithm devices lack security measures when integrated into networked service environments, cannot effectively protect sensitive personal data, and cannot provide network service functions such as user concepts, access permissions, and audit trails.
By establishing a secure communication channel between the host device and the algorithm service, transmitting and processing health care data, ensuring the confidentiality and authenticity of the data during transmission, and using the TLS protocol for encryption, ensuring the security of the data during transmission.
It realizes the secure processing of sensitive medical data in a networked service environment, provides the same security as the local host environment, ensures the confidentiality and authenticity of the data during transmission, and meets the security requirements in the network service environment.
Smart Images

Figure CN119089457A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to a computer-implemented method, a host device, an algorithm service, and an algorithm service. Background Art
[0002] When medical algorithm devices are developed, this is often done in the form of localhost-only applications to increase process efficiency. They are also often based on sufficiently complete architectural patterns to implement the medical algorithm device (and therefore provide results), but without implementing any security measures to protect the sensitive personal data processed and without implementing any service functions (such as audit trails).
[0003] This minimal complete architectural pattern allows for efficient development of medical algorithm devices, as all instances reusing the same architectural pattern result in very similar localhost-only systems. This allows for efficient and simplified threading models, risk assessments, and penetration testing on all medical algorithm devices developed using the same pattern.
[0004] However, on the other hand, it is desirable to integrate medical algorithm devices into a networked service environment, providing healthcare providers with remote access to a cloud-based catalog of medical algorithm devices that can be remotely executed in the context of a patient's medical treatment, as well as providing service functions such as user concepts, access rights and audit trails.
[0005] The inventors then recognized a problem: how can a medical algorithm device, which is developed, threat modeled, risk assessed, and penetration tested as a local host-only application, be securely integrated into a networked service environment and does not implement any security measures to protect the sensitive personal data processed. In addition, they recognized that the network service environment should be able to declare that the security provided to the exchanged sensitive personal data is equivalent to the security provided by the local host environment for which the medical algorithm device was developed and in which the medical algorithm device was thread modeled, risk assessed, and penetration tested.
[0006] The present disclosure is made in view of the above considerations. Summary of the invention
[0007] In a first aspect, embodiments of the present invention provide a computer-implemented method for transmitting healthcare data between a host device and an algorithm service, the host device residing in a first computer network and the algorithm service residing in a second computer network different from the first computer network, the method comprising the steps of:
[0008] (a) Establish a secure communication channel between the host device and the algorithm service;
[0009] (b) Transmitted from the host device to the algorithm service via a secure communication channel:
[0010] identification of an algorithm to be applied to the healthcare data held by the host device, and
[0011] healthcare data to which the identified algorithm is to be applied; and
[0012] (c) receiving at the algorithm service an identification of the algorithm and the health care data;
[0013] (d) applying the identified algorithm to the healthcare data to obtain results; and
[0014] (e) transmitting the results of applying the identified algorithm to the healthcare data from the algorithm service to the host via the secure communication channel.
[0015] This approach allows the development of medical algorithms as local host-only applications with minimal complete architectural patterns and without the need to implement any security measures to protect sensitive healthcare data. This makes the development of medical algorithm devices efficient and secure when processing sensitive medical data.
[0016] The first computer network and the second computer network may each include one or more firewalls, or be separated by one or more firewalls. The or each firewall may control the ingress and egress of data in the respective computer networks. The first computer network may have a security configuration that is different from the second computer network and / or controlled by a different entity than the second computer network. For example, the first computer network may be defined or reside in a first control domain, and the second computer network may be defined or reside in a second control domain.
[0017] The host device may be a computer, a smartphone, a tablet, or other personal computing device. The algorithm service may be a computer, a server, a collection of computers, a collection of servers, a cloud computing environment, and / or a virtualized machine implemented on any of them. The algorithm service may be considered as software, a set of software running on a computing device, and / or implemented as one or more containers in a cloud computing environment. It may be that the host device does not apply the algorithm to the healthcare data. That is, the algorithm determined in step (b) can only be applied by the algorithm service (which may be a different entity from the host device). The algorithm service may include one or more instances, such as one or more cloud instances, to apply the algorithm in parallel.
[0018] The algorithms provided by the algorithm service may include a step-by-step process or set of instructions designed to solve a specific problem or perform a specific task. They are a finite sequence of well-defined, explicit instructions that are executed in a specific order to achieve a desired result. For example, an algorithm provided by the algorithm service may receive patient data related to cardiovascular health as healthcare data. The algorithm may perform one or more steps on the healthcare data, or perform one or more steps using the healthcare data, and provide an indication of the risk of myocardial infarction as a result.
[0019] The identification of the algorithm may be, for example, a label identifying a particular algorithm or class of algorithms to be applied to the healthcare data.The host device may maintain a list of algorithms provided by the algorithm service, which may be provided to the host device by the algorithm service.
[0020] The identification of the algorithm and the transmission of the healthcare data may occur simultaneously, or sequentially in either order.
[0021] The healthcare data may include, for example, physiological data associated with the patient, analytical test results associated with the patient, metadata associated with the patient (e.g., "smoker"), and / or metadata associated with one or more tests performed on the patient or a sample from the patient. The healthcare data may be stored locally on the host device or may be retrieved based on instructions from a user of the host device. When retrieval is indicated, the healthcare data may be stored, for example, on a laboratory information system (LIS) or a healthcare information system (HIS). The LIS or HIS may contain or be linked to the databases mentioned below.
[0022] The method may further include transmitting GUI instructions from the algorithm service to the host device, the GUI instructions causing a graphical user interface to be generated when executed by the host device, the GUI instructions being selected by the algorithm service based on the algorithm identified by the host device. The GUI instructions may include an HTML document for presentation by a browser connected to or hosted on the host device. In some examples, the algorithm service initiates an instance of an algorithm identified by the host device, and the initiated algorithm provides the algorithm service with GUI instructions for forwarding to the host device. The algorithm service may add some additional instructions, such as a header, to the GUI instructions after receiving from the algorithm and before transmitting to the host device.
[0023] The method may further include establishing a second secure communication channel between the host device and the database, and transmitting an identification of the patient and one or more data field identifiers from the host device to the database through the second secure channel, the database returning a patient-specific value for the or each data field identifier, wherein the patient-specific value is included in or forms the healthcare data transmitted from the host device to the algorithm service. TLS may be used to establish the second secure communication channel. Establishing the second secure communication channel may include the host device verifying the identity of the database. Establishing the second secure communication channel may include the host device and the database each encrypting messages to be sent between each other. In addition, TLS may be used to establish a secure communication channel between the host device and the algorithm service.
[0024] The method may further include the following step between steps (c) and (d): transmitting a confirmation instruction from the algorithm service to the host device, the confirmation instruction indicating which algorithm is to be applied to what healthcare data. Step (b) may further include transmitting a pre-fill request, the pre-fill request causing the algorithm service to return a pre-filled GUI, the GUI being pre-filled with healthcare data, the identified algorithm being to be applied to the healthcare data, the algorithm service transmitting the confirmation instruction in response to receiving the pre-fill request. The confirmation instruction may include a confirmation GUI instruction, the confirmation GUI instruction causing a pre-filled graphical user interface showing the provided healthcare data and the algorithm to be applied to be generated. The method may further include receiving one or more change requests related to the pre-filled graphical user interface at the host device, and transmitting these change requests to the algorithm service. For example, the GUI may include one or more input fields for receiving change requests. The algorithm service may then implement the one or more changes and send back to the host device a modified confirmation GUI instruction reflecting the one or more changes. The method may further include receiving an acceptance of the pre-filled graphical user interface on the host device and sending it to the algorithm service. The algorithm service may then apply the algorithm specified in the pre-filled graphical user interface.
[0025] The method may further include transmitting an execution request from the host device to the algorithm service, the execution request causing the algorithm service to apply the identified algorithm to the healthcare data, the algorithm service performing steps (d) and (e) in response to receiving the execution request. In some examples, the execution request includes an identification of the algorithm to be applied and the healthcare data, the identified algorithm to be applied to the healthcare data. In some examples, the execution request references an existing pending request in the algorithm service (the algorithm service already retains a previously transmitted identification of the algorithm and the healthcare data).
[0026] The method may further include the step of converting the results of applying the algorithm to the healthcare data before transmitting the results to the host device and / or the step of converting the healthcare data before transmitting the healthcare data to the algorithm service. For example, the healthcare data may be converted from one digital format to another digital format.
[0027] The algorithm service may include an API, and the host device includes an edge module, the API and the edge module communicating securely via a secure communication channel. The algorithm service may include an algorithm module or an algorithm device that may be connected to the API via an unsecure channel and / or located within a second computer network (or may actually be connected to the API via a secure channel if desired). The algorithm module or device may implement a medical algorithm as it performs calculations on healthcare data to obtain a result. The host device may include an interface module that is connected to the edge module via an unsecure channel and / or located in a first computer network. The interface module may be a browser or other interface through which a clinician interacts with the host device.
[0028] Establishing the secure communication channel may include the host device verifying the identity of the algorithm service. In some examples, establishing the secure communication channel may also include the algorithm service verifying the identity of the host device. Establishing the secure communication channel may include the host device and the algorithm service each encrypting messages sent between each other. This may include, for example, the host device and the algorithm service agreeing on a set of keys to be used to encrypt and decrypt messages sent between each other.
[0029] Establishing a secure channel of communication may include implementing a Transport Layer Security protocol TLS, wherein the host device assumes the role of a TLS client and the algorithm service assumes the role of a TLS server.
[0030] In a second aspect, an embodiment of the present invention provides a host device, the host device comprising one or more processors, a memory and a network interface, the memory containing machine executable instructions, the machine executable instructions when executed on the processor causing:
[0031] (a) the network interface establishes a secure communication channel between a host device and an algorithm service, the host device resides in a first computer network, and the algorithm service resides in a second computer network different from the first computer network;
[0032] (b) The host device transmits to the algorithm service via a secure communication channel:
[0033] identification of an algorithm to be applied to the healthcare data held by the host device, and
[0034] healthcare data to which the identified algorithm is to be applied; and
[0035] (c) The host device receives, from the algorithm service via the secure communication channel, the results of applying the identified algorithm to the healthcare data.
[0036] These instructions may further cause the host device to: receive GUI instructions from the algorithm service, which, when executed by the processor, cause a graphical user interface to be generated. The GUI instructions may be selected by the algorithm service based on an algorithm identified by the host device. The GUI instructions may include an HTML document for presentation in a browser connected to or hosted by the host device. In some examples, the algorithm service may have initiated an instance of the algorithm identified by the host device, and the initiated algorithm may have provided the algorithm service with GUI instructions for forwarding to the host device. The algorithm service may have added some additional instructions to the GUI instructions after receiving from the algorithm and before transmitting to the host device. These steps may be prompted by, for example, a request from a third-party device (such as an algorithm service) (which then causes steps (a)-(c) to be performed).
[0037] These instructions may further cause the network interface to establish a second secure communication channel between the host device and the database, and transmit an identification of the patient and one or more data field identifiers from the host device to the database through the second secure channel, whereupon the host device receives a patient-specific value for the or each data field identifier from the database, wherein the patient-specific value is included in or forms the healthcare data transmitted from the host device to the algorithm service.
[0038] The instructions may further cause the host device to receive a confirmation instruction from the algorithm service indicating which algorithm is to be applied to what healthcare data. Step (b) may further include transmitting a pre-fill request, the pre-fill request causing the algorithm service to return a pre-filled GUI, the GUI being pre-filled with the healthcare data to which the identified algorithm is to be applied, the algorithm service transmitting the confirmation instruction in response to receiving the pre-fill request. The confirmation instruction may include a confirmation GUI instruction causing a pre-filled graphical user interface to be generated showing the provided healthcare data and the algorithm to be applied. The host device may then receive one or more change requests associated with the pre-filled graphical user interface and transmit these change requests to the algorithm service.
[0039] The instructions may further cause the host device to transmit an execution request from the host device to the algorithm service, the execution request causing the algorithm service to apply the identified algorithm to the healthcare data. In some examples, the execution request includes an identification of the algorithm to be applied and the healthcare data, the identified algorithm to be applied to the healthcare data. In some examples, the execution request references an existing pending request in the algorithm service (the algorithm service already retains a previously transmitted identification of the algorithm and the healthcare data).
[0040] The instructions may further cause the host device to transform the healthcare data before transmitting it to the algorithm service. For example, the healthcare data may be transformed from one digital format to another digital format.
[0041] The host device may include an edge module configured to securely communicate with the API of the algorithm service via a secure communication channel. The host device may include an interface module configured to connect to the edge module via an unsecure channel and / or be located in the first computer network. The interface module may be a browser or other interface through which a clinician interacts with the host device.
[0042] Establishing the secure communication channel may include the host device verifying the identity of the algorithm service. In some examples, establishing the secure communication channel may also include the algorithm service verifying the identity of the host device. Establishing the secure communication channel may include the host device and the algorithm service each encrypting messages sent between each other. This may include, for example, the host device and the algorithm service agreeing on a set of keys to be used to encrypt and decrypt messages sent between each other.
[0043] Establishing a secure channel of communication may include implementing a Transport Layer Security protocol TLS, wherein the host device assumes the role of a TLS client and the algorithm service assumes the role of a TLS server.
[0044] In a third aspect, an embodiment of the present invention provides an algorithm service, the algorithm service comprising one or more processors, a memory and a network interface, the memory containing machine executable instructions, the machine executable instructions when executed on the processor causing:
[0045] (a) the network interface establishes a secure communication channel between the algorithm service and the host device, the host device resides in a first computer network, and the algorithm service resides in a second computer network different from the first computer network;
[0046] (b) The algorithm service is received from the host device via a secure communication channel:
[0047] identification of an algorithm to be applied to the healthcare data held by the host device; and
[0048] Healthcare data, the algorithm is to be applied to healthcare data;
[0049] (c) the algorithm service applies the identified algorithm to the healthcare data to obtain an outcome; and
[0050] (e) The algorithm service transmits the results of applying the identified algorithm to the healthcare data to the host device via the secure communication channel.
[0051] These instructions may further cause the algorithm service to transmit GUI instructions from the algorithm service to the host device, which GUI instructions, when executed by the host device, cause a graphical user interface to be generated, the GUI instructions being selected by the algorithm service based on the algorithm identified by the host device. The GUI instructions may include an HTML document for presentation by a browser connected to or hosted on the host device. In some examples, the algorithm service initiates an instance of an algorithm identified by the host device, and the initiated algorithm provides GUI instructions to the algorithm service for onward transmission to the host device. The algorithm service may add some additional instructions to the GUI instructions after receiving them from the algorithm and before transmitting them to the host device. These steps may be prompted, for example, by a request from a third-party device (such as a host device) (which then causes steps (a)-e) to be performed).
[0052] The instructions may further cause the algorithm service to transmit a confirmation instruction from the algorithm service to the host device between steps (b) and (c), the confirmation instruction indicating which algorithm is to be applied to what healthcare data. Step (b) may further include transmitting a pre-fill request, the pre-fill request causing the algorithm service to return a pre-filled GUI, the GUI being pre-filled with the healthcare data to which the identified algorithm is to be applied, the algorithm service transmitting the confirmation instruction in response to receiving the pre-fill request. The confirmation instruction may include a confirmation GUI instruction causing a pre-filled graphical user interface to be generated showing the provided healthcare data and the algorithm to be applied.
[0053] The instructions may further cause the algorithm service to perform steps (c) and (e) in response to receiving an execution request from the host device (the execution request causing the algorithm service to apply the identified algorithm to the healthcare data). In some examples, the execution request includes an identification of the algorithm to be applied and the healthcare data, the identified algorithm to be applied to the healthcare data. In some examples, the execution request references an existing pending request in the algorithm service (the algorithm service already retains a previously transmitted identification of the algorithm and the healthcare data).
[0054] The instructions may further cause the algorithm service to transform the results of applying the algorithm to the healthcare data before transmitting it to the host device.
[0055] The algorithm service may include an API that is configurable to securely communicate with an edge module of a host device via a secure communication channel. The algorithm service may include an algorithm module or algorithm device that is connected to the API via an unsecure channel and / or is located within a second computer network. The algorithm module or device may implement a medical algorithm as it performs calculations on healthcare data to obtain a result.
[0056] Establishing the secure communication channel may include the host device verifying the identity of the algorithm service. In some examples, establishing the secure communication channel may also include the algorithm service verifying the identity of the host device. Establishing the secure communication channel may include the host device and the algorithm service each encrypting messages sent between each other. This may include, for example, the host device and the algorithm service agreeing on a set of keys to be used to encrypt and decrypt messages sent between each other.
[0057] Establishing a secure channel of communication may include implementing a Transport Layer Security protocol TLS, wherein the host device assumes the role of a TLS client and the algorithm service assumes the role of a TLS server.
[0058] In a fourth aspect, an embodiment of the present invention provides an edge module for a host device, wherein the edge module is configured as follows:
[0059] (a) establishing a secure communication channel between an edge module and an algorithm service, the edge module residing in a first computer network, and the algorithm service residing in a second computer network different from the first computer network;
[0060] (b) receiving, from the interface module, an identification of an algorithm to be applied to the healthcare data stored by the host device;
[0061] (c) transmit to the algorithm service via a secure communication channel:
[0062] identification of an algorithm to be applied to the healthcare data held by the host device, and
[0063] healthcare data to which the identified algorithm is to be applied; and
[0064] (d) receiving, from the algorithm service via the secure communication channel, the results of applying the identified algorithm to the healthcare data.
[0065] The edge module may be configured to receive GUI instructions from the algorithm service, which, when executed by the processor, causes a graphical user interface to be generated. The GUI instructions may have been selected by the algorithm service based on the algorithm identified by the interface module. The GUI instructions may include an HTML document for presentation in a browser connected to or hosted by a host device. In some examples, the algorithm service may have initiated an instance of the algorithm identified by the interface module, and the initiated algorithm may have provided the algorithm service with GUI instructions for forwarding to the host device. The algorithm service may have added some additional instructions to the GUI instructions after receiving from the algorithm and before transmitting to the host device.
[0066] The edge module can be configured to establish a second secure communication channel between the edge module and the database, and transmit an identification of the patient and one or more data field identifiers from the edge module to the database through the second secure channel, and then the edge module receives a patient-specific value for the data field identifier or each data field identifier from the database, wherein the patient-specific value is included in or forms the healthcare data transmitted from the edge module to the algorithm service. The second secure communication channel can have any one or any combination of the properties or characteristics of the secure communication channel between the host device and the algorithm service. For example, the second secure communication channel can verify the identity of the database, and / or encrypt data transmitted between the edge module and the database.
[0067] The edge module may be configured to receive a confirmation instruction from the algorithm service, the confirmation instruction indicating which algorithm is to be applied to what healthcare data. Step (c) may further include transmitting a pre-fill request, the pre-fill request causing the algorithm service to return a pre-filled GUI, the GUI being pre-filled with the healthcare data to which the identified algorithm is to be applied, the algorithm service transmitting the confirmation instruction in response to receiving the pre-fill request. The confirmation instruction may include a confirmation GUI instruction causing a pre-filled graphical user interface to be generated showing the provided healthcare data and the algorithm to be applied. The edge module may then receive one or more change requests related to the pre-filled graphical user interface from the interface module, and transmit these change requests to the algorithm service.
[0068] The edge module can be configured to transmit an execution request to the algorithm service, the execution request causing the algorithm service to apply the identified algorithm to the healthcare data. In some examples, the execution request includes an identification of the algorithm to be applied and the healthcare data, the identified algorithm to be applied to the healthcare data. In some examples, the execution request references an existing pending request in the algorithm service (the algorithm service already retains the previously transmitted identification of the algorithm and the healthcare data).
[0069] The edge module can be configured to transform the healthcare data before transmitting it to the algorithm service. For example, the healthcare data can be converted from one digital format to another digital format.
[0070] The edge module may form part of a host device (eg the host device of the second aspect), or may be a separate unit connected to the host device via a network.
[0071] Establishing the secure communication channel may include the edge module verifying the identity of the algorithm service. In some examples, establishing the secure communication channel may also include the algorithm service verifying the identity of the edge module. Establishing the secure communication channel may include the edge module and the algorithm service each encrypting messages sent between each other. This may include, for example, the edge module and the algorithm service agreeing on a set of keys to be used to encrypt and decrypt messages sent between each other.
[0072] Establishing a secure communication channel may include implementing a transport layer security protocol TLS, wherein the edge module assumes the role of a TLS client and the algorithm service assumes the role of a TLS server.
[0073] In a fifth aspect, an embodiment of the present invention provides a system comprising a host device of the second aspect and an algorithm service of the third aspect connected via a network.
[0074] The present invention includes any combination of described aspects and preferred features unless such a combination is expressly impermissible or explicitly avoided.
[0075] Another aspect of the present invention provides: a computer program comprising code, which, when executed on a computer, causes the computer to perform the method of the first aspect or the portion of the method of the first aspect corresponding to one or both of a host device and an algorithm service; a computer-readable medium storing a computer program, which comprises code, which, when executed on a computer, causes the computer to perform the method of the first aspect or the portion of the method of the first aspect corresponding to one or both of a host device and an algorithm service; and a computer system programmed to perform the method of the first aspect or the portion of the method of the first aspect corresponding to one or both of a host device and an algorithm service. BRIEF DESCRIPTION OF THE DRAWINGS
[0076] Figure 1 is a schematic diagram of the system;
[0077] Figure 2 is a flow chart of the method; and
[0078] Figure 3 It is a network diagram. DETAILED DESCRIPTION
[0079] Aspects and embodiments of the present invention will now be discussed with reference to the accompanying drawings. Other aspects and embodiments will be apparent to those skilled in the art.
[0080] Figure 1 is a schematic diagram of a system 100. The system includes a host device 102 and an algorithm service 112. The host device includes an interface module (which may be referred to as a third-party agent) 106, such as a web browser or terminal for a clinician to interact with the host device and therefore the edge module and on the algorithm service. The host device also includes an edge module 104, which communicates with the interface module via a first insecure channel 108. The edge module 104 also communicates with an API 114 of the algorithm service via a first secure channel 110. The API of the algorithm service communicates with one or more algorithm devices 116 via a second insecure channel 118. In this example, the edge module 104 also communicates with an IT service 120 including a database 124. The communication is conducted via a second secure channel 122.
[0081] During operation, the interface module provides in message 1 an identification of an algorithm to be applied to certain healthcare data (algorithm ID), as well as the healthcare data itself or an identification of a patient (patient ID). In the latter example, the patient ID is then sent to the IT service over the second secure communication channel 122 in message 2 along with one or more data field identifiers. For example, message 2 may specify the patient ID and also request their blood glucose concentration and weight (as two data field identifiers). The IT service may then retrieve the values corresponding to those data fields (values) for that patient from its database and return them to the edge module in message 3.
[0082] The edge module then transmits the algorithm ID, value, and operation field containing the request to pre-populate the GUI to the API 114 through the first secure channel 110. In the example where message 1 contains the healthcare data itself, messages 2 and 3 are omitted, so the edge module only forwards the content of message 1 to the API along with the operation field containing the pre-populated request.
[0083] The API sends a message 5 containing the GETUI instruction and the received values to the algorithm device 116 corresponding to the algorithm device identified by the algorithm ID in message 4 via a second insecure channel 118. In some examples, these values will be converted at some stage in the processing, such as by an interface module, an edge module, or indeed by the API at this stage (for example, by converting from one digital format to another). In this case, the values are represented as f(value), where f is a function that converts the values. The algorithm device then replies with a message 6UI(f(value)) containing a GUI instruction, such as an HTML document, which indicates: the values it has received and the algorithm it intends to apply to these values. The message is forwarded by the API to the edge module 104 as message 7 via the first secure channel 110, and the message is then forwarded to the interface module 106 as message 8.
[0084] The clinician can then approve the application of the algorithm via the interface module 106, or submit any change or update requests (e.g., a new algorithm to be applied, or a change to healthcare data). Message 9 is sent to the edge module 104, again containing in this example an algorithm ID and a value (which can be a transformed value, an original value, or a modification of an initial value or a transformed value in response to a change request from a user), which the edge module understands as a protocol for applying the algorithm to the data described in the UI(f(value) message. The edge module then transmits message 10 to the API via a first secure communication channel 110, the message including a request for the algorithm device to apply the algorithm to these values. In this example, message 10 includes the algorithm ID, the value, and an operation field containing a request to execute the algorithm.
[0085] In some examples, the algorithm service 112 may store the values originally transmitted in message 4, so the clinician may include one or more changes or update requests to those values when approving or requesting execution of the algorithm in message 10. In other examples, the algorithm service does not store the values, so upon receiving message 10, the algorithm device will execute using the values and algorithm ID received in message 10, regardless of the values or algorithm ID received in message 4.
[0086] When message 10 is received by API 114, it transmits message 11 to algorithm device 116, requesting that the algorithm be applied to the healthcare data. In this example, message 11 contains a POST request with encapsulated values. Algorithm device 116 then applies the algorithm to the healthcare data and provides the results in message 12. In this example, the results are provided in the form of an HTML document, giving GUI instructions (UI(res)) for displaying the results. This is forwarded from the API to edge module 104 as message 13, and from the edge module to interface module 106 as message 14.
[0087] From the healthcare provider's perspective, the interface module still resides within a local host environment that the healthcare provider will maintain control of. In addition, the algorithm device does not reside within the same network environment as the healthcare provider's interface module, but rather resides in its own environment that is connected to the local host environment via the technical network and the first secure communication channel.
[0088] Thus, the interface module 106 now interacts with the edge module 104 residing within the same local host environment, rather than directly interacting with the algorithm device 116. The edge module is responsible for interacting with a healthcare provider database (e.g., a database 124 provided by an IT service 120) in order to retrieve medically relevant data related to patients who are under the healthcare provider's treatment and the entire algorithm device being triggered in the context of the patient's treatment. The healthcare provider database DB resides in an IT environment (IT service 120) that is different from the local host environment in which the interface module and the edge module reside. The IT environment and the local host environment are connected via a technical network and a second secure communication channel. The edge module interacts with an API residing in the algorithm service environment in order to request execution of the algorithm device and retrieve algorithm result values. The algorithm service environment in which the API resides is different from the local host environment and is connected via a technical network and a first secure communication channel as described above. The API interacts with the algorithm device in order to programmatically execute the algorithm contained within the algorithm device and retrieve the algorithm result value.
[0089] In this example, in the context of a healthcare provider treating a patient identified by a patient identifier ID, and where the healthcare provider needs an algorithm (e.g., a medical algorithm) identified by an algorithm identifier algorithm ID in order to make an informed medical decision, the complete calculation of the algorithm value consists of two round trips in the networked service environment discussed in detail above.
[0090] for Figure 1 The networked service environment shown provides for the use of secure communication channels across a technical network connecting a healthcare provider local host environment and a healthcare provider IT environment, and across a technical network connecting a healthcare provider local host environment and an algorithm service environment.
[0091] A secure channel is one that provides both confidentiality and authenticity for data exchanged across the channel. If a channel provides confidentiality for data exchanged across the channel, then only a well-defined set of participants who have access to the data can access the data exchanged across such a channel. If a channel provides authenticity for data exchanged through the channel, then the recipient of data exchanged across such a channel can unambiguously determine the origin of the received data.
[0092] For the secure channel between the healthcare provider local host environment and the healthcare provider IT environment, it is specified that the secure channel needs to provide confidentiality for the data exchanged in both directions. It is also specified that the secure channel needs to provide authenticity for at least the data sent from the healthcare provider IT environment to the healthcare provider local host environment, so that the edge module can clearly determine the source of the received medical-related algorithm input value (the value in message 3) as the database DB within the healthcare provider IT environment.
[0093] For the secure channel between the healthcare provider local host and the algorithm service environment, it is specified that the secure channel needs to provide confidentiality for the data exchanged in both directions. It is also specified that the secure channel needs to provide authenticity for at least the data sent from the service environment to the healthcare provider local host environment so that the edge module can clearly determine the source of the retrieved user interface UI, which is filled with a set of regulatory-compliant medical-related algorithm input values (f(values)) or filled with algorithm result values.
[0094] In one implementation of the first channel and / or secure channel of communication, Transport Layer Security (TLS) version 1.3 (or version 1.2) is used. If TLS is used to build the second secure channel, the healthcare provider local host environment will assume the role of a TLS client, with the healthcare provider IT environment assuming the role of a TLS server. If TLS is used to build the first secure channel, the healthcare provider local host environment will assume the role of a TLS client, with the service environment assuming the role of a TLS server.
[0095] TLS as a cryptographic protocol is a protocol within which the TLS server is always authenticated as part of the initial TLS handshake protocol (TLS server authentication is typically achieved by employing an X.509 server certificate), and in which the TLS client and TLS server agree on a shared master secret. This can be done by encrypting a client-generated pre-master secret using RSA (Rivest-Shamir-Adleman) or using ECDHE or DHE key exchange (Elliptic Curve Diffie-Hellman Key Exchange or Diffie-Hellman Key Exchange). The protocol also requires that the master secret be expanded into multiple sets of encryption keys (by using a pseudo-random function PRF in the case of TLS1.2, or by using HKDF in the case of TLS1.3). Application data is exchanged between the TLS client and the TLS server, and confidentiality is provided by employing an encryption cipher such as AES, Advanced Encryption Standard, or ChaCha20 to encrypt the application data using a key derived from the master secret. Authenticity is provided for application data exchanged between a TLS client and a TLS server by employing a keyed-hashed message authentication code (HMAC) in the case of TLS 1.2, or an encrypted Authenticated Encryption with Associated Data (AEAD) cipher in the case of TLS 1.3, where for both HMAC or AEAD a cryptographic key derived from a master secret is used.
[0096] Alternative cryptographic protocols may be chosen as long as they provide the same security guarantees for the constructed channel.
[0097] When the above security measures are implemented in a networked service environment, the security of the algorithmic devices used in such a networked service environment is equivalent to the security of the algorithmic devices used in an environment limited to local hosts.
[0098] The concept of security in the context of using algorithmic devices includes the following four requirements. First, medical-related algorithm input values need to be kept confidential in three environments: the source environment of the medical-related algorithm input values, the usage environment of the medical-related algorithm input values, and the receiver environment of the medical-related algorithm input values. Second, the algorithm result value needs to be kept confidential in two environments: the source environment of the algorithm result value and the receiver environment of the algorithm result value. Third, the receiver of the algorithm result value must be able to clearly determine the source of the medical-related algorithm input value used to calculate the received algorithm result value. Fourth, the receiver of the algorithm result value must be able to clearly determine the source of the received algorithm result value.
[0099] Under the assumption of an uncompromised local host environment, according to the four requirements specified above, the use of the algorithm device in such an uncompromised local host environment can be considered safe. First, the medical-related algorithm input value is confidential for the above three environments. Since all three environments are the same healthcare provider local host environment and are assumed to be an uncompromised healthcare provider local host environment, the medical-related algorithm input value is confidential for the healthcare provider local host environment. Secondly, the algorithm result value is confidential for the above two environments. Since the two environments are the same healthcare provider local host environment and are assumed to be an uncompromised healthcare provider local host environment, the algorithm result value is confidential for the healthcare provider local host environment. Third, the receiver of the algorithm result value of the interface module within the healthcare provider local host environment can clearly determine the source of the medical-related algorithm input value, because the source of the medical-related algorithm input value is the same interface module within the healthcare provider local host environment. Fourth, the receiver of the algorithm result value of the interface module residing in the healthcare provider local host environment can clearly determine the source of the received algorithm result value, because the source of the received algorithm result value is the same medical algorithm device residing in the healthcare provider local host environment.
[0100] Implementing the prescribed security measures in a networked service environment, according to the following four requirements specified above, the use of algorithm devices in a networked service environment that implements the prescribed security measures is visible and safe. First, the medical-related algorithm input value is confidential to three environments: the source environment of the medical-related algorithm input value, i.e., the healthcare provider IT environment; the use environment of the medical-related algorithm input value, i.e., the service environment; and the receiver environment of the medical-related algorithm input value, i.e., the healthcare provider local host environment. This is because the networked service environment uses a secure channel across the technical network to connect the source environment of the medical-related algorithm input value with the receiver environment of the medical-related algorithm input value, and because the networked service environment uses a secure channel across the technical network to connect the receiver environment of the medical-related algorithm input value with the use environment of the medical-related algorithm input value. If the security channel used has the prescribed security quality, the medical-related algorithm input value is confidential to the three environments specified in the first security requirement. Secondly, the algorithm result value is confidential to two environments: the source environment of the algorithm result value, i.e., the service environment; and the receiver environment of the algorithm result value, i.e., the healthcare provider local host environment. This is because the networked service environment uses a secure channel across the technical network to connect the source environment of the algorithm result value with the receiver environment of the algorithm result value. If the security channel used has the specified security quality, the algorithm result value is confidential for the two environments specified in the second security requirement. Third, the receiver of the algorithm result value of the interface module residing in the local host environment of the healthcare provider can clearly determine the source of the medical-related algorithm input value, that is, the database DB residing in the IT environment of the healthcare provider. This is because the networked service environment uses a secure channel across the technology network to connect the source environment of the medical-related algorithm input value with the receiver environment of the algorithm result value. If the security channel used has the specified security quality, the receiver of the algorithm result value can clearly determine the source of the medical-related algorithm input value. Fourth, the receiver of the algorithm result value (the receiver is the interface module residing in the local host environment of the healthcare provider) can clearly determine the source of the received algorithm result value (the source is the medical algorithm device residing in the service environment). This is because the networked service environment uses a secure channel across the technology network to connect the receiver environment of the algorithm result value with the source environment of the received algorithm result value. If the security channel used has the specified security quality, the receiver of the algorithm result value can clearly determine the source of the received algorithm result value.
[0101] Figure 2is a flow chart of method 200. In a first step S102, a secure communication channel is established between a host device and an algorithm service. Next, in step S104, the host device transmits (i) an identification of an algorithm; and (ii) healthcare data, the identified algorithm to be applied to the algorithm service via the established secure communication channel with respect to the healthcare data. The algorithm service then receives the transmitted data in step S106. Then, in step S108, the algorithm service causes the identified algorithm to be applied to the healthcare data. In step S110, the result of step S108 is transmitted to the host device via the established secure communication channel.
[0102] Figure 3 304. A host device 302 of the type previously discussed is connected to an edge module 304, for example by virtue of being located on the same machine (virtual or physical) or via a network connection. The edge module 304 is connected to a wide area network (e.g., the Internet) 306. In this example, the edge module 304 is also connected to an IT service 308 via a network connection in a manner that does not operate via the wide area network 306. However, in some examples, indicated by the dashed line, the IT service 308 can be connected to the wide area network and thereby connected to the edge module 304.
[0103] Algorithm services 312 of the type previously discussed are connected to API 310, for example by virtue of being located on the same machine (virtual or physical) or via a network connection. API 310 is connected to wide area network 306. In this way, API 310 and edge module 304 are able to communicate, establish a secure communication channel, and exchange data.
[0104] The systems and methods of the above-described embodiments may be implemented in a computer system (particularly in computer hardware or computer software) as well as in the described structural components and user interactions.
[0105] The term "computer system" includes hardware, software and data storage devices for implementing the system or performing the method according to the above-mentioned embodiments. For example, a computer system may include a central processing unit (CPU), an input device, an output device and a data storage device. The computer system may have a monitor to provide a visual output display. The data storage device may include RAM, a disk drive or other computer-readable media. The computer system may include multiple computing devices connected by a network and capable of communicating with each other on the network.
[0106] The method of the above-mentioned embodiment may be provided as a computer program or as a computer program product or a computer-readable medium carrying a computer program, and the computer program is arranged to execute the above-mentioned method when being executed on a computer.
[0107] The term "computer-readable medium" includes, but is not limited to, any non-transitory medium or media that can be directly read and accessed by a computer or computer system. The media may include, but is not limited to, magnetic storage media, such as floppy disks, hard disk storage media, and magnetic tapes; optical storage media, such as compact disks or CD-OMs; electronic storage media, such as memory, including RAM, ROM, and flash memory; and hybrids and combinations of the above, such as magnetic / optical storage media.
[0108] Although the present disclosure has been described in conjunction with the above exemplary embodiments, many equivalent modifications and variations will be apparent to those skilled in the art when the present disclosure is given. Therefore, the above exemplary embodiments of the present disclosure are considered to be illustrative rather than restrictive. Various changes may be made to the described embodiments without departing from the spirit and scope of the present disclosure.
[0109] Specifically, although the methods of the above embodiments are described as being implemented on the systems of the described embodiments, the methods and systems of the present disclosure need not be implemented in conjunction with each other, but may be implemented on alternative systems or using alternative methods, respectively.
[0110] The features disclosed in the specification, or in the following claims, or in the drawings, in terms of the manner of expressing or implementing the disclosed functions in their specific forms, or in terms of the methods or processes for obtaining the disclosed results, may be appropriately used alone in their various forms, or in any combination to implement the present disclosure.
[0111] Although the present disclosure has been described in conjunction with the above exemplary embodiments, many equivalent modifications and variations will be apparent to those skilled in the art when the present disclosure is given. Therefore, the above exemplary embodiments of the present disclosure are considered to be illustrative rather than restrictive. Various changes may be made to the described embodiments without departing from the spirit and scope of the present disclosure.
[0112] For the avoidance of any doubt, any theoretical explanations provided herein are intended to improve the reader's understanding. The inventors do not wish to be bound by any of these theoretical explanations.
[0113] Any section headings used herein are for organizational purposes only and are not to be construed as limiting the subject matter described.
[0114] Throughout the specification, including the following claims, unless the context requires otherwise, the words "comprise" and "include" and variations such as "comprises and comprising" and "including", will be understood to imply the inclusion of stated integers or steps or groups of integers or steps but not the exclusion of any other integers or steps or groups of integers or steps.
[0115] It must be noted that, as used in this specification and the appended claims, the singular forms "a", "an", and "the" include plural referents unless the context clearly dictates otherwise. Ranges may be expressed herein as from "about" one particular value and / or to "about" another particular value. When such a range is expressed, another embodiment includes from the one particular value and / or to the other particular value. Similarly, when values are expressed as approximations, by use of the antecedent "about", it will be understood that the particular value forms another embodiment. The term "about" in relation to a numerical value is optional and means, for example, + / - 10%.
Claims
1. A computer-implemented method for transmitting healthcare data between a host device and an algorithm service, the host device residing in a first computer network and the algorithm service residing in a second computer network different from the first computer network, the method comprising the steps of: (a) establishing a secure communication channel between the host device and the algorithm service; (b) transmitting from the host device to the algorithm service via the secure communication channel: identification of an algorithm to be applied to the healthcare data held by the host device, and the healthcare data, the identified algorithm to be applied to the healthcare data; as well as (c) receiving, at the algorithm service, the identification of the algorithm and the healthcare data; (d) applying the identified algorithm to the healthcare data to obtain a result; and (e) transmitting the results of applying the identified algorithm to the healthcare data from the algorithm service to a host via the secure communication channel.
2. A computer-implemented method according to claim 1, wherein the method further includes transmitting GUI instructions from the algorithm service to the host device, wherein the GUI instructions, when executed by the host device, cause generation of a graphical user interface, and the GUI instructions are selected by the algorithm service based on the algorithm identified by the host device.
3. A computer-implemented method according to claim 1 or claim 2, the method further comprising establishing a second secure communication channel between the host device and the database, and transmitting an identification of the patient and one or more data field identifiers from the host device to the database through the second secure channel, the database returning a patient-specific value for the data field identifier or each data field identifier, wherein the patient-specific value is included in the healthcare data transmitted from the host device to the algorithm service or forms the healthcare data transmitted from the host device to the algorithm service.
4. The computer-implemented method of claim 3, wherein establishing the second secure communication channel comprises one or both of the following: The host device verifies the identity of the database; and / or The host device and the database each encrypt messages to be sent between each other.
5. A computer-implemented method according to any of the preceding claims, further comprising the following step between steps (c) and (d): transmitting a confirmation instruction from the algorithm service to the host device, the confirmation instruction indicating which algorithm is to be applied to what healthcare data.
6. The computer-implemented method of claim 5, wherein the confirmation instructions include confirmation GUI instructions that cause generation of a pre-populated graphical user interface showing the provided healthcare data and the algorithm to be applied.
7. The computer-implemented method of claim 6, wherein the method further comprises receiving, at the host device, one or more change requests related to the pre-populated graphical user interface and transmitting the change requests to the algorithm service.
8. A computer-implemented method according to any of the preceding claims, further comprising the step of converting the result of applying the algorithm to the healthcare data before transmitting the result to the host device and / or the step of converting the healthcare data before transmitting the healthcare data to the algorithm service.
9. The computer-implemented method of any one of the preceding claims, the algorithm service comprising an API, and the host device comprising an edge module, the API and the edge module communicating securely via the secure communication channel.
10. The computer-implemented method of any preceding claim, wherein establishing the secure communication channel comprises the host device authenticating the identity of the algorithm service.
11. The computer-implemented method of any one of the preceding claims, wherein establishing the secure communication channel comprises the host device and the algorithm service each encrypting messages to be sent between each other.
12. A host device comprising one or more processors, a memory and a network interface, the memory containing machine executable instructions that when executed on the processor cause: (a) the network interface establishes a secure communication channel between the host device and the algorithm service, the host device resides in a first computer network, and the algorithm service resides in a second computer network different from the first computer network; (b) the host device transmits to the algorithm service via the secure communication channel: identification of an algorithm to be applied to the healthcare data held by the host device, and the healthcare data to which the identified algorithm is to be applied; and (c) The host device receives, from the algorithm service via the secure communication channel, results of applying the identified algorithm to the healthcare data.
13. An algorithm service comprising one or more processors, a memory and a network interface, the memory containing machine executable instructions which, when executed on the processor, cause: (a) the network interface establishes a secure communication channel between the algorithm service and a host device, the host device resides in a first computer network, and the algorithm service resides in a second computer network different from the first computer network; (b) the algorithm service receives from the host device via the secure communication channel: identification of an algorithm to be applied to the healthcare data held by the host device, and the healthcare data to which the algorithm is to be applied; (c) the algorithm service applies the identified algorithm to the healthcare data to obtain a result; and (e) The algorithm service transmits the results of applying the identified algorithm to the healthcare data to the host device via the secure communication channel.
14. An edge module for a host device, the edge module being configured as: (a) establishing a secure communication channel between the edge module and the algorithm service, the edge module residing in a first computer network, and the algorithm service residing in a second computer network different from the first computer network; (b) receiving from an interface module an identification of an algorithm to be applied to healthcare data stored by the host device or received from the interface module; (c) transmitting to the algorithm service via the secure communication channel: identification of the algorithm to be applied to the healthcare data stored by the host device, and the healthcare data to which the identified algorithm is to be applied; and (d) receiving, from the algorithm service via the secure communication channel, results of applying the identified algorithm to the healthcare data.
15. A system comprising: a host device residing within the first computer network, and an algorithm service residing in a second computer network different from said first computer network; The host device and / or the algorithm service is configured to: establishing a secure communication channel between the host device and the algorithm service; The host device is configured to: Transmitting to the algorithm service via the secure communication channel: identification of an algorithm to be applied to the healthcare data held by the host device, and the healthcare data, the identified algorithm to be applied to the healthcare data; The algorithm service is configured to apply the identified algorithm to the healthcare data to obtain a result; as well as The results of applying the identified algorithm to the healthcare data are transmitted to the host device via the secure communication channel.
