Computer-implemented method for providing personalized healthcare parameters and healthcare management system

Abstract

The present disclosure relates to a computer-implemented method and a healthcare management system for providing personalized healthcare parameters. The method comprises the following: providing a healthcare application (20) and an interface application (25) running in a data processing component having a plurality of data processors; submitting a service request from the healthcare application (20) to the interface application (25) indicating a request for determining a first personalized healthcare parameter, the first personalized healthcare parameter indicating a first healthcare condition of the patient; in response to receiving the service request, generating, by the interface application (25), a first input data request; providing the first input data request to a first service application (26a) from a plurality of service applications, where each of the service applications (26) is configured to determine a respective personalized healthcare parameter for a patient in response to receiving a respective personalized input data, and the first service application (26a) is configured to determine the first personalized healthcare parameter; receiving first input data information in the receiving interface application (25), the first input data information indicating a data specification of first input data required by the first service application (26a) for determining the first personalized healthcare parameter; receiving the first input data information in the healthcare application (20); generating first personalized input data in the healthcare application (20), the first personalized input data being generated from the first input data information; receiving the first personalized healthcare parameter in the healthcare application (20), in response to receiving the first personalized input data in the first service application (26a), determining the first personalized healthcare parameter, such determining comprising processing the first personalized input data; and outputting the first personalized healthcare parameter to a receiving device (27; 27 ') connected to the data processing component (2); 28).

Description

[0001] The present disclosure relates to a computer-implemented method for providing personalized healthcare parameters and a healthcare management system. Background Art

[0002] In recent years, healthcare management for patients has increasingly relied on the integration of personalized healthcare information from different healthcare data sources. Analyzing personalized healthcare data from different sources, such as electronic health records (EHR), helps improve healthcare management for patients. On the other hand, integrating healthcare information from different sources requires reliable and secure processing of healthcare data from different sources to avoid erroneous healthcare parameter determination, which may lead to, for example, incorrect diagnosis or other incorrect actions (such as control of medical devices).

[0003] Document US2021 / 0098133A1 discloses a machine learning system for healthcare applications, which includes: a data acquisition pipeline configured to automatically receive patient data, which includes stored data from an EHR database and real-time data from multiple data sources, including EHR records, claims data, and social determinants of health data; a data processing module configured to clean, extract and process the received patient data; at least one predictive model configured to analyze the cleaned and processed data and determine a risk score for each patient; a configuration file that defines predictive model execution parameters; an adjustment module configured to adjust parameters of the predictive model, including variables, thresholds, and coefficients; a retraining module configured to make additional adjustments to the predictive model to eliminate inherent data bias; and a dashboard and reporting module configured to present risk scores to the patient care team.

[0004] Document WO 2021 / 030637A1 relates to a patient health management platform that accesses the patient's metabolic profile and the biosignals recorded for the patient during the current time period (including sensor data and / or laboratory test data collected for the patient). The platform receives patient data recorded during the current time period, including the food consumed by the patient, the medications taken, and the symptoms experienced. The platform implements a machine learning metabolic model to determine the patient's metabolic state at the end of the current time period by comparing the actual performance of the metabolic state with the prediction of the metabolic state. The performance and prediction are determined based on the recorded biosignals and the recorded patient data, respectively. The platform generates patient-specific treatment recommendations that outline instructions for the patient to improve his or her metabolic state, and provides patient-specific treatment recommendations to the patient device for display to the patient. Summary of the invention

[0005] An object of the present invention is to provide a computer-implemented method for providing personalized healthcare parameters, and a healthcare management system enabling a more reliable and error-free determination of personalized healthcare parameters for a patient, such as a diabetic patient.

[0006] To achieve this object, there is provided a computer implemented method for providing personalized healthcare parameters according to claim 1. Further, there is provided a healthcare management system according to claim 15. Further aspects are disclosed in the dependent claims.

[0007] According to one aspect, a computer-implemented method for providing or determining personalized healthcare parameters includes: providing a healthcare application and an interface application running in a data processing component; submitting a service request from the healthcare application to the interface application indicating a request for determining a first personalized healthcare parameter, the first personalized healthcare parameter indicating a first healthcare condition of a patient; generating a first input data request by the interface application in response to receiving the service request; providing the first input data request to a first service application from a plurality of service applications, wherein each of the service applications is configured to determine a corresponding personalized healthcare parameter for the patient in response to receiving a corresponding personalized input data, and the first service application is configured to determine the first personalized healthcare parameter; receiving first input data information in the receiving interface application, the first input data information indicating a data specification of the first input data required by the first service application for determining the first personalized healthcare parameter; receiving the first input data information in the healthcare application; generating first personalized input data in the healthcare application, the first personalized input data being generated based on the first input data information; receiving the first personalized healthcare parameter in the healthcare application, wherein in response to receiving the first personalized input data in the first service application, determining the first personalized healthcare parameter, such determination comprising processing the first personalized input data; and outputting the first personalized healthcare parameter to a receiving device connected to the data processing component.

[0008] Another aspect relates to a healthcare management system, comprising a data processing component having a plurality of data processors, the healthcare management system being configured to: provide a healthcare application and an interface application running in the data processing component; submit a service request from the healthcare application to the interface application indicating a request for determining a first personalized healthcare parameter, the first personalized healthcare parameter indicating a first healthcare condition of a patient; generate a first input data request by the interface application in response to receiving the service request; provide the first input data request to a first service application from a plurality of service applications, wherein each of the service applications is configured to determine a corresponding personalized healthcare parameter for the patient in response to receiving the corresponding personalized input data, and the first service application Configured to determine the first personalized healthcare parameter; receive first input data information in the receiving interface application, the first input data information indicating a data specification of the first input data required by the first service application for determining the first personalized healthcare parameter; receive the first input data information in the healthcare application; generate first personalized input data in the healthcare application, the first personalized input data being generated based on the first input data information; receive the first personalized healthcare parameter in the healthcare application, wherein in response to receiving the first personalized input data in the first service application, determine the first personalized healthcare parameter, such determination comprising processing the first personalized input data; and output the first personalized healthcare parameter to a receiving device connected to the data processing component.

[0009] The technology proposed for the computer-implemented method and the healthcare management system supports reliable and error-free determination of one or more personalized healthcare parameters that are determined by one or more of the service applications. The process for correctly generating first personalized input data assigned to a patient and providing the first personalized input data that conforms to the first input data information ensures that the first service application used to determine the first personalized healthcare parameter is receiving correct input data. Based on such correct input data that conforms to the first input data information, the input data can be correctly processed by the first service application used to determine the first personalized healthcare parameter. Such reliable and error-free determination of one or more personalized healthcare parameters can be performed even when details about the specific data processing of the first personalized input data by the (one or more) service applications are unknown. For example, even if some / certain algorithms applied by the (one or more) service applications used to determine the first personalized healthcare parameters are unknown, the correct determination of the one or more personalized healthcare parameters can be ensured.

[0010] The data processing component may have one or more data processors. For example, the data processing component has multiple data processors. The first service application may run on a processor(s) different from the processors running the healthcare application and the interface application.

[0011] Collect or collect certain / certain data requirements of the first input data from the first service application. In particular, the first input data request may require the first service application to inform the first input data information. Then, the first data information is received from the first personalized healthcare application in the interface application, and the first input data information is further received from the interface application in the healthcare application. In the case of determining the first personalized healthcare parameter in the healthcare application or by the healthcare application requesting, in response (e.g., in real time), the first input data information is requested, thereby ensuring that at any time the first personalized healthcare parameter / or some other personalized healthcare parameters will be determined by one or more of the service applications, the input data is generated and provided according to the (one or more) input data requirements of the corresponding service application, which can exchange data with the healthcare application and is requested to determine one or more personalized healthcare parameters. For example, if a certain service application has received a certain update, such an update causes the (one or more) requirements of the input data to be received by the service application to change. According to the proposed technology, the current (or updated) (one or more) data requirements will always be requested by and received in the healthcare application for correctly and error-free generation of personalized input data. The input data information will indicate such (one or more) requirements.

[0012] The interface application may also be referred to as a common interface (application) between the healthcare application and the plurality of service applications. The common interface ensures or stipulates that, before actually submitting the input data to the (one or more) service applications, the corresponding input data is submitted to the service application according to the corresponding (one or more) input data requirements indicated by the input data information collected by the healthcare application.

[0013] The generation of the first input data request may further include, in the interface application, determining one or more preselected first service applications from a plurality of service applications, each of the one or more preselected first service applications being configured to determine a first personalized healthcare parameter; and selecting a first service application from the one or more preselected first service applications. Prior to receiving a service request from a healthcare application indicating a request for determining a first personalized healthcare parameter, one or more preselected first service applications may be determined by the interface application, each of such preselected first service applications being configured to determine a first personalized healthcare parameter. A plurality of service applications may be used to determine the first personalized healthcare parameter. Service applications from the plurality of service applications may require different input data specifications. In this example, the interface application proactively collects information about the first service application in advance (before receiving the service request), so that if an actual service request is received in the interface application, the first service application is ready to be selected. The interface application may store information about the one or more preselected first service applications in a local memory accessible by and allocated to the interface application. For example, information about the one or more pre-selected first service applications may be updated by the interface application after a predetermined time limit has elapsed since the one or more pre-selected first service applications were last determined.

[0014] The computer-implemented method may further include determining, by the interface application, one or more preselected first service applications from at least one of: a first plurality of service applications locally accessible by the interface application and in a local database assigned to the interface application; and a second plurality of service applications remotely accessible in a remote database. The plurality of service applications may be provided for local and / or remote access by the interface application. For example, access to the remote database may be provided via the Internet. A service provider may provide a service application homepage that provides the plurality of service applications for use. Other or additional service applications may be accessed by the interface application in a local database assigned to one or more data processors, the interface application itself being run or implemented on the one or more data processors.

[0015] The provider of the healthcare application (and optionally the interface application) may be different from the provider(s) of at least a subset or all of the plurality of service applications. In one example, the provider of the healthcare application (and the interface application) is unaware of the algorithm(s) actually applied by one or more of the service applications to determine the corresponding healthcare parameter(s).

[0016] The submission of the service request may further include: providing service application information with the service request, the service application information indicating the selection of the first service application; and generating a first input data request by the interface application in response to the service application information, and providing the first input data request to the first service application. In the present example, the service request provided from the healthcare application to the interface application indicates the selected first service application to be requested to determine the first personalized healthcare parameter. For example, the healthcare application may have been provided with general information about the service applications available for use or invocation. Based on such information, the service request may be provided to include service application information indicating the selection of the first service application, which may be one service application from a plurality of service applications that are all configured to determine the first personalized healthcare parameter and are "known" to the healthcare application. In response to such a service request including the service application information, the interface application will provide the first input data request to the selected first service application. In the present example, the healthcare application itself at least partially has control over which service application is requested to determine the first personalized healthcare parameter. Alternatively, the healthcare application may simply submit the input request to the interface application (without identifying the preferred or selected service application). In response, the interface application will determine or select the service application that is requested to actually determine the first personalized healthcare parameter.

[0017] The generation of the first personalized input data may further include receiving healthcare data from one or more healthcare data sources in the healthcare application. The healthcare data source may be selected from the group of the following healthcare data sources: an unstructured healthcare database, a clinical healthcare database, and regulated healthcare device data; and the first personalized input data is generated from the received healthcare data. With respect to the unstructured healthcare database, for example, it may provide personalized fitness data of the patient. For example, the clinical healthcare database may provide a personalized electronic health record (EHR). With respect to the regulated healthcare device data, for example, measurement data from a blood glucose meter and / or an insulin pump assigned to the patient may be provided. In one instance, alternatively or in addition, the healthcare application may receive healthcare data not from a database but from some other healthcare data source (such as a personal fitness device that collects personalized fitness data and / or a blood glucose meter that collects measurements of the patient). Therefore, the healthcare data may be received directly from one of such devices in the healthcare application, and / or the healthcare data may be received through one of the healthcare databases after the healthcare data was previously stored in the healthcare database.

[0018] One or more of the healthcare applications may be configured to semantically identify which data or data points are needed from the input data, and semantically collect matching data or data points. Priority may be applied to data for the same input data point from multiple healthcare data sources. Steps for interpolating and / or estimating missing data (points) based on existing information may be applied. For example, a patient's body mass index (BMI) may be determined based on information about the patient's weight and height. Alternatively or in addition, a patient's waist size may be determined based on information about the patient's weight and height.

[0019] When checking whether the received healthcare data complies with the data specification of the first input data of the first service application and determining non-compliance, generating the first personalized input data from the received healthcare data may further include: converting at least a portion of the received healthcare data having or provided with (according to) the source data specification into the first personalized input data having or provided with the data specification of the first input data. Due to receiving the first input data information indicating the data specification of the first input data required by the first service application in the healthcare application (e.g., received from the interface application), the healthcare application may check or determine whether the healthcare data received from the first service application complies with the data specification of the first input data of the first service application. In some cases, the application first data conversion may be applied to convert the received healthcare data provided with or according to the source data specification different from the data specification of the first input data into the first personalized input data that complies with the data specification of the first input data. The source data specification defines the specification about the source data. The source data provided with or according to the source data specification refers to the source data provided to comply with or meet the specification (such as the format of the data). For example, the first data specification of the input data may define or specify the unit of the corresponding (one or more) values ​​of the first input required by the first service application. The first data specification of the input data may define or specify a unit of certain values ​​for some of the healthcare data. If the healthcare data received from the data source does not conform to the unit of such value, a conversion is applied in the healthcare application.

[0020] The generation of the first personalized input data may in particular comprise receiving healthcare data from one or more healthcare data sources and generating the first personalized input data from the received healthcare data, comprising checking whether the received healthcare data complies with data specifications of the first input data of the first service application.

[0021] In a healthcare application, the computer-implemented method may further include: converting a first personalized healthcare parameter having an output data specification into a first personalized healthcare parameter having a first source data specification required by a first healthcare data source from a group of healthcare data sources; and storing the first personalized healthcare parameter having the first source data specification in the first healthcare data source. The first personalized healthcare parameter determined by the first service application may be provided to or returned to one of the healthcare data sources, such that, for example, a current value or an updated value of the first personalized healthcare parameter is stored in the healthcare data source. Such storage may provide for updating an electronic medical record for a patient.

[0022] The submitting of the service request may further include generating the service request in the healthcare application in response to a triggering event detected in the healthcare application. In this example, the service request for determining the first personalized healthcare parameter is initiated after the triggering event has been detected in the healthcare application. Generating the service request in the healthcare application in response to detecting the triggering event may be performed automatically in the healthcare application, for example, in real time in response to detecting the triggering event.

[0023] The (e.g., first) triggering event may indicate a user input received in the healthcare application. For example, the user input may indicate a request to update an electronic health record for a patient regarding a first personalized healthcare parameter. For example, a physician may request determination of the first personalized healthcare parameter for diagnostic reasons. Alternatively or additionally, a device input may be received in the healthcare application (e.g., from a medical device), wherein the device input indicates a request from the medical device to determine the first personalized healthcare parameter, which may then be applied to control the operation of the medical device.

[0024] The (e.g. second) triggering event may indicate a triggering time point. For example, a time limit may be set or predetermined. After the time limit has passed, the trigger point is detected in the healthcare application, thereby initiating the generation of the service request. The time limit may be set or predetermined, for example, by user input.

[0025] The (e.g., third) triggering event may indicate a change in parameter value of a medical parameter applied to determine a previous first personalized healthcare parameter by the first service application, thereby updating the previous first personalized healthcare parameter with the first personalized healthcare parameter. The updating of the previous first personalized healthcare parameter comprises a new calculation or determination of the first personalized healthcare parameter by the first service application. For example, the medical parameter may refer to a patient's blood glucose level, and the blood glucose level has previously been applied as an input parameter for determining the first personalized healthcare parameter. Due to a (currently) detected change in blood glucose level, a new determination of the first personalized healthcare parameter is triggered, such determination of the first personalized healthcare parameter taking into account the different (current) blood glucose level caused by the change. A threshold value for the medical parameter may be predetermined, for example, by user input. The determination of the first personalized healthcare parameter may be triggered only if the medical parameter reaches or exceeds the threshold value. For example, the determination of the first personalized healthcare parameter may be triggered if the medical parameter reaches or exceeds a value change of 10%, preferably a value change of 20%, and more preferably a value change of 30% compared to the value previously determined for the first personalized healthcare parameter.

[0026] The computer-implemented method may further include: receiving first personalized input data by an interface application; verifying by the interface application whether the first personalized input data complies with the first input data information based on the first input data information received in the interface application; and providing the first personalized input data from the interface application to the first service application only if the first personalized input data is verified to comply with the first input data information. In this example, before the first personalized input data is provided by the interface application to the first service application, some checks (e.g., plausibility checks) are performed on whether the first personalized input data received by the interface application from the healthcare application complies with the first input data information. For example, a plausibility check may be provided to provide a check whether the first personalized input data is within (or outside) some value or data range that can be predefined. Such optional measurements or checks further improve the safe and correct use of the first service application for determining the first personalized healthcare parameter.

[0027] The output of the first personalized healthcare parameter may further include receiving the first personalized healthcare parameter by a medical device; and controlling the operation of the medical device according to the first personalized healthcare parameter. For example, the first personalized healthcare parameter may be applied to control at least one of a blood glucose meter, a blood glucose sensor, and an insulin pump. In this or other embodiments, the determination of the first personalized healthcare parameter may be performed or applied for a diabetic patient. With respect to the control of the blood glucose meter, in response to receiving the first personalized healthcare parameter, some measurements for detecting the patient's current blood glucose level may be initiated. In another example, some new or additional analysis of the measurement data indicating the patient's blood glucose level may be performed in response to providing the first personalized healthcare parameter, wherein the first personalized healthcare parameter may exceed a certain threshold for the first personalized healthcare parameter. Due to such threshold exceeding, a new or additional analysis of the measurement data may be initiated. Similarly, in response to providing the first personalized healthcare parameter, detection of current measurement data by a blood glucose sensor and / or administration of an insulin bolus by an insulin pump may be initiated or started.

[0028] The outputting of the first personalized healthcare parameter may further include at least one of the following: displaying the first personalized healthcare parameter on an output display device and printing by an output printer device.

[0029] The plurality of service applications may include a service application configured to determine, for a patient, one or more personalized healthcare parameters selected from the group consisting of: risk prediction, therapy management, and treatment recommendations. With respect to risk prediction, the likelihood of chronic kidney disease may be determined by at least one of the service applications. With respect to therapy management and / or treatment recommendations, one or more personalized healthcare parameters selected from the group consisting of: blood glucose level, insulin dose, carbohydrate intake, recommended time for insulin administration or carbohydrate intake may be determined by the service application(s).

[0030] In response to receiving and / or outputting the first personalized healthcare parameter, a further service request or a second service request may be initiated (such as automatically triggered) in the healthcare application. The further service request indicates an additional request or a second request for determining a second personalized healthcare parameter, which is different from the first personalized healthcare parameter and indicates a second healthcare condition of the patient. The steps performed in response to the further service request will be similar or comparable to the steps performed in response to the first service request. The second service application (which may be different from the first service application) will provide for determining the further personalized healthcare parameter. The second service application will receive the second input data according to the second input data information. For example, if the first personalized healthcare parameter indicates the patient's risk of kidney disease, the risk of liver disease may be determined by the further personalized healthcare parameter. For example, such determination of at least one additional or further personalized healthcare parameter may be triggered in response to the first personalized healthcare parameter reaching or exceeding a certain threshold. For example, if it can be determined that the patient's risk of kidney disease is high, the determination of the risk of liver disease may be initiated in response to such a finding in the healthcare application.

[0031] Embodiments of the computer-implemented methods described above may be provided mutatis mutandis with respect to a healthcare management system. DETAILED DESCRIPTION

[0032] Next, another embodiment is described. Reference is made to the accompanying drawings. In the accompanying drawings, it is shown:

[0033] Figure 1 A schematic diagram of a healthcare management system provided with a data processing component or system having a plurality of data processors, and a software component including a plurality of software applications running on the plurality of data processors;

[0034] Figure 2 a schematic diagram of an arrangement for performing a computer-implemented method for determining or providing personalized healthcare parameters in a healthcare management system; and

[0035] Figure 3 Schematic diagram of a computer-implemented method for determining personalized healthcare parameters.

[0036] Figure 1A schematic diagram of a healthcare management system 1 is shown, which healthcare management system is provided with a data processing component 2 having a plurality of data processors 3, and a software component 4 including a plurality of software applications 5 implemented or running on the plurality of data processors 3. Furthermore, the arrangement provided with the data processing component 2 and the software component 4 is functionally connected to at least one data source or database 6, which is accessible by at least one of the data processing component 2 and the software component 4 and is configured to provide healthcare data for one or more patients. Alternatively, the database 6 may be integrated with the arrangement provided with the data processing component 2 and the software component 4. The hardware and / or software elements or components of the healthcare management system 1 may be provided in one or more computer network systems. The data processors from the plurality of data processors 3 may be located in a network consisting of Figure 1 The dashed lines 4a in the figure schematically indicate different (separate) locations. Similarly, software applications from the plurality of software applications 5 may be run on different (separate) data processors. The data exchange may be performed by wireless and / or wired data transmission.

[0037] Figure 2 A schematic diagram of an arrangement is shown, the arrangement comprising elements or modules provided by, for example, a healthcare management system 1 for performing a computer-implemented method for providing or determining personalized healthcare parameters. In general, Figure 2 The arrangement may be provided based on the healthcare management system 1. On the data processing component 2, at least some of the plurality of software applications 5 are running, wherein each of the applications is configured to provide one or more functions of the healthcare management system 1 applied in the computer-implemented method for determining personalized healthcare.

[0038] refer to Figure 2 , the healthcare application 20 is implemented by one or more of the software applications 5 of the software component 4. The healthcare application 20 is configured to extract healthcare information from the healthcare data and provide insights into the healthcare condition of the patient, for example, to allow a diagnosis based on the healthcare condition. The healthcare application 20 may be a personalized healthcare application assigned to the patient and personalized for the patient. Personalization may be achieved by receiving personalized information (such as the patient's name, birthday, and / or personal healthcare data) in the healthcare application 20 and providing limited access to the personalized healthcare data based only on such personalized information.

[0039] Through the healthcare application 20, a plurality of healthcare data sources or resources 21 may be accessed. The healthcare data source 21 may be implemented by a plurality of databases accessible by the healthcare application 20. A first healthcare data source 21a may be provided as an unstructured healthcare database containing, for example, personalized fitness data collected by a fitness device 22 assigned to or used by a patient. A second healthcare data source 21b provides clinical healthcare data, such as a personalized electronic health record (EHR) received via user input 23. The second healthcare data source 21b may provide healthcare data compliant with the FHIR standard (FIHR - Fast Healthcare Interoperability Resources). FHIR specifications such as HL 7FHIR describe a set of resources and several different frameworks for exchanging data resources between different healthcare related systems.

[0040] according to Figure 2 In the example shown, there is a third healthcare data source 21c that provides regulated healthcare device data, such as measurement data from a medical device 24 (eg, a blood glucose meter and / or an insulin pump assigned to a patient).

[0041] The healthcare application 20 is configured to receive and process healthcare data from one or more of the different healthcare data sources 21. In addition, the healthcare application 20 may be configured to provide healthcare data to the healthcare data sources 21 and provide such healthcare data for storage in the one or more healthcare data sources 21. To perform such data generation for data storage, the healthcare application 20 may be configured to generate healthcare data that conforms to a source data specification that specifies characteristics of data that may be stored in at least one of the healthcare data sources 21a, 21b, 21c.

[0042] according to Figure 2, an interface application 25 is provided, which is configured to exchange electronic data with the healthcare application 20. The interface application 25 can run on the same data processor subset as the healthcare application 20, or on a different data processor subset from the data processing component 2. The interface application 25 provides a common interface between the healthcare application 20 and a plurality of service applications 26. The plurality of service applications 26 can be implemented by one or more of the software applications 5. The one or more software applications that implement the plurality of service applications 26 can be separate from the one or more software applications provided for the healthcare application 20. Each of the service applications 26a, 26b, 26c is configured to determine one or more personalized healthcare parameters indicating the healthcare condition of the patient for whom the input data has been previously collected in response to receiving (e.g., personalized) input data. For example, the plurality of service applications 26 can be configured to determine one or more personalized healthcare parameters for the patient selected from the following group: likelihood of chronic kidney disease, blood glucose level, insulin dose, carbohydrate intake, and recommended time for insulin administration or carbohydrate intake.

[0043] In order to correctly determine the corresponding personalized healthcare parameters, each of the service applications 26a, 26b, 26c from the plurality of service applications 26 will need to receive input data according to a separate input data specification. For example, such input data specification may refer to input data parameters such as name, data type (string, object, array) and / or unit of a certain value (e.g., milliliters, grams, kilograms, etc.). Only if the received input data complies with the input data specification of the corresponding service application from the plurality of service applications 26, such service application will correctly determine one or more personalized healthcare parameters.

[0044] Figure 3 Shown in Figure 2 A schematic diagram of the steps performed in an arrangement of a computer-implemented method for determining personalized healthcare parameters for a patient.

[0045] In step 30, a triggering event is detected in the healthcare application 20. For example, a user input may be received as a triggering event. Alternatively, a certain time limit may have passed to trigger the event. An event trigger refers to a request to determine a first personalized healthcare parameter for a patient. A triggering event such as a user input may indicate personalized patient information (such as name, birthday, and / or personal healthcare data). Alternatively, some personalized code assigned to the patient may be provided together with or in response to a triggering event in the healthcare application 20. For example, a device code assigned to a medical device (such as a blood glucose meter) may indicate the patient, and the medical device is then assigned to the patient.

[0046] In step 31, after the healthcare application 20 has generated the service request in response to detecting the triggering event, a service request indicating a request to determine a first personalized healthcare parameter is submitted from the healthcare application 20 to the interface application 25. The first personalized healthcare parameter to be determined indicates a first healthcare condition of the patient.

[0047] In response to receiving the service request by the interface application 25, a first input data request is generated by the interface application 25 and submitted to the first service application 26a (step 32). The first input data request will require the first service application 26a to inform first input data information indicating data specifications regarding the first input data required to be received by the first service application 26a for determining the first personalized healthcare parameter. According to step 33, the interface application 25 receives data or information indicating the first input data information from the first service application 26a. After receiving the first input data information, the interface application 25 will provide the data or information indicating the first input data information to the healthcare application 20 (step 34).

[0048] In response to receiving the first input data information, the healthcare application 20 will collect personalized health data from one or more healthcare data sources from the plurality of healthcare data sources 21 (steps 35, 36). Based on such collected or collected healthcare data, the healthcare application 20 will generate first personalized input data that conforms to the first input data information. In step 37, such first personalized input data is submitted to the interface application 25.

[0049] Generating the first personalized input data from the received healthcare data may include applying a first transformation of the data specification in the following manner: transforming at least some of the received healthcare data having the source data specification into the first personalized input data having or conforming to the first input data information. As the first input data information is received in the healthcare application 20 (e.g., received from the interface application), the healthcare application 20 may check or determine whether the healthcare data received from the (one or more) data sources 21 conforms to the data information provided for the input data of the first service application 26a. In some cases, the first data transformation may be applied to transform the received healthcare data provided with the data source specification that does not conform to the first input data information into the first input data that conforms to the first input data information. For example, the first input data information may define or specify a unit of a certain value of some of the healthcare data. If the healthcare data received from the (one or more) data sources 21 does not conform to the unit of such value, a transformation regarding the unit of such value is applied in the healthcare application 20.

[0050] The first service application 26a will receive the first personalized input data from the interface application 25 (step 38). After the first service application 26a processes the first personalized input data to determine the first personalized healthcare parameter in step 39, the first service application 26a returns the determined first personalized healthcare parameter to the interface application 25. Next, in step 40, the interface application 25 transmits the first personalized healthcare parameter to the healthcare application 20. The first personalized healthcare parameter will be output by the healthcare application (step 41) to the receiving device that receives the first personalized healthcare parameter.

[0051] For example, the first personalized healthcare parameter may be provided to an output device 27 for printing and / or displaying the first personalized healthcare parameter. Alternatively or in addition, the first personalized healthcare parameter may be provided by the healthcare application 20 to a medical device 28 (such as a blood glucose meter or an insulin pump) assigned to the patient. The operation of such a medical device 28 may be controlled according to or dependent on the first healthcare parameter.

[0052] Optionally, in step 42 , the first healthcare parameter may be stored in one of the healthcare data sources 21 .

Claims

1. A computer-implemented method for providing personalized healthcare parameters, the computer-implemented method comprising: - providing a healthcare application (20) and an interface application (25) running in the data processing component (2); - submitting a service request from the healthcare application (20) to the interface application (25) indicating a request for determining a first personalized healthcare parameter, the first personalized healthcare parameter indicating a first healthcare condition of a patient; - in response to receiving the service request, generating a first input data request by the interface application (25); - providing the first input data request to a first service application from a plurality of service applications (26a), wherein - each of the service applications (26) is configured to determine a respective personalized healthcare parameter for the patient in response to receiving the respective personalized input data, and - said first service application (26a) being configured to determine said first personalized healthcare parameter; wherein the first input data request requires the first service application (26a) to inform first input data information; - receiving, in the interface application (25), from a first personalized healthcare application (26a), the first input data information indicating a data specification of first input data required by the first service application (26a) for determining the first personalized healthcare parameter, wherein the data specification specifies in which / which corresponding value units the first service application (26a) requires the first input; - receiving, in said healthcare application (20), said first input data information from said interface application; - generating first personalized input data in the healthcare application (20), the first personalized input data being generated based on the first input data information, wherein the generating of the first personalized input data comprises receiving healthcare data from one or more healthcare data sources and generating the first personalized input data from the received healthcare data, and the generating of the first personalized input data from the received healthcare data comprises checking whether the received healthcare data complies with the data specification of the first input data of the first service application; - receiving the first personalized healthcare parameter in the healthcare application (20), wherein in response to receiving the first personalized input data in the first service application (26a), determining the first personalized healthcare parameter, such determination comprising processing the first personalized input data; as well as - outputting said first personalized healthcare parameter to a receiving device (27; 28) connected to said data processing component (2).

2. The computer-implemented method of claim 1, wherein said generating of said first input data request further comprises, in said interface application (25), - determining one or more preselected first service applications from the plurality of service applications, each of the one or more preselected first service applications being configured to determine the first personalized healthcare parameter; and - selecting said first service application from said one or more pre-selected first service applications (26a).

3. The computer-implemented method of claim 2, further comprising determining, by the interface application (25), the one or more pre-selected first service applications from at least one of: - a first plurality of service applications locally accessible by the interface application (25) and assigned to a local database of the interface application; and - A second plurality of service applications remotely accessible in a remote database.

4. The computer-implemented method according to at least one of the preceding claims, wherein said submitting of said service request further comprises: - providing service application information together with the service request, the service application information indicating the selection of the first service application (26a); and - In response to the service application information, the first input data request is generated by the interface application (25) and provided to the first service application (26a).

5. The computer-implemented method according to at least one of the preceding claims, wherein said generating of first personalized input data further comprises, in said healthcare application (20), - receiving the healthcare data from one or more healthcare data sources selected from the group of the following healthcare data sources: an unstructured healthcare database, a clinical healthcare database, and regulated healthcare device data.

6. A computer-implemented method according to at least one of the preceding claims, wherein generating first personalized input data from the received healthcare data in a non-compliant manner further comprises converting at least some of the received healthcare data provided with a source data specification into the first personalized input data provided with the data specification of the first input data.

7. The computer-implemented method of claim 5 or 6, further comprising, in the healthcare application (20), - converting the first personalized healthcare parameter having an output data specification into the first personalized healthcare parameter having a first source data specification required by a first healthcare data source from the group of healthcare data sources; and - Storing the first personalized healthcare parameter with the first source data specification in the first healthcare data source.

8. A computer-implemented method according to at least one of the preceding claims, wherein the submission of the service request further comprises generating the service request in the healthcare application (20) in response to a triggering event detected in the healthcare application (20).

9. The computer-implemented method of claim 8, wherein the triggering event indicates a user input received in the healthcare application (20).

10. The computer-implemented method of claim 8 or 9, wherein the triggering event indicates a triggering time point.

11. The computer-implemented method according to at least one of claims 8 to 10, wherein the triggering event indicates a change in parameter value of a medical parameter applied to determine a previous first personalized healthcare parameter by the first service application (26a), thereby updating the previous first personalized healthcare parameter using the first personalized healthcare parameter.

12. The computer-implemented method according to at least one of the preceding claims, further comprising - receiving, by said interface application (25), said first personalized input data; - verifying, by the interface application (25), whether the first personalized input data conforms to the first input data information based on the first input data information received in the interface application (25); as well as - providing the first personalized input data from the interface application (25) to the first service application (26a) only if the first personalized input data is verified to comply with the first input data information.

13. The computer-implemented method according to at least one of the preceding claims, wherein said outputting of said first personalized healthcare parameter further comprises - receiving, by a medical device, said first personalized healthcare parameter; and - controlling the operation of said medical device according to said first personalized healthcare parameter.

14. A computer-implemented method according to at least one of the preceding claims, wherein the plurality of service applications comprises a service application configured to determine, for the patient, one or more personalized healthcare parameters selected from the group consisting of: risk prediction, therapy management, and treatment recommendations.

15. A healthcare management system comprising a data processing component (2), the healthcare management system being configured to - provide a healthcare application (20) and an interface application (25) running in the data processing component (2); - submitting a service request from the healthcare application (20) to the interface application (25) indicating a request for determining a first personalized healthcare parameter, the first personalized healthcare parameter indicating a first healthcare condition of a patient; - in response to receiving the service request, generating a first input data request by the interface application (25); - providing the first input data request to a first service application from a plurality of service applications (26a), wherein - each of the service applications (26) is configured to determine a respective personalized healthcare parameter for the patient in response to receiving the respective personalized input data, and - said first service application (26a) being configured to determine said first personalized healthcare parameter; wherein the first input data request requires the first service application (26a) to inform first input data information; - receiving, in the interface application (25), first input data information from the first personalized healthcare application (26a), the first input data information indicating a data specification of first input data required by the first service application (26a) for determining the first personalized healthcare parameter, wherein the data specification specifies in which / which corresponding value units the first service application (26a) requires the first input; - receiving, in the healthcare application (20), the first input data information from the interface application (25); - generating first personalized input data in the healthcare application (20), the first personalized input data being generated based on the first input data information, wherein the generating of the first personalized input data comprises receiving healthcare data from one or more healthcare data sources and generating the first personalized input data from the received healthcare data, and the generating of the first personalized input data from the received healthcare data comprises checking whether the received healthcare data complies with the data specification of the first input data of the first service application; - receiving the first personalized healthcare parameter in the healthcare application (20), wherein in response to receiving the first personalized input data in the first service application (26a), determining the first personalized healthcare parameter, such determination comprising processing the first personalized input data; as well as - outputting said first personalized healthcare parameter to a receiving device (27; 28) connected to said data processing component (2).

Images