COMPUTER IMPLEMENTED METHOD FOR PROVIDING INDIVIDUALIZED HEALTHCARE PARAMETERS AND HEALTHCARE MANAGEMENT SYSTEM - Patent application
Patent Information
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- F HOFFMANN LA ROCHE & CO AG
- Filing Date
- 2023-05-26
- Publication Date
- 2026-06-02
Smart Images
Figure 00000000_0000_ABST
Abstract
Description
[Technical field]
[0001] The present disclosure relates to a computer-implemented method for providing individualized healthcare parameters and a healthcare management system. [Background technology]
[0002] In recent years, healthcare management for patients has become increasingly dependent on the integration of personalized healthcare information obtained from different healthcare data sources. Performing an analysis of personalized healthcare data from different sources, such as electronic health records (EHRs), helps to improve the healthcare management of patients. Meanwhile, integrating healthcare information obtained from different sources requires reliable and secure processing of healthcare data from different sources, for example, to avoid determining erroneous healthcare parameters, which may cause incorrect diagnosis or other incorrect actions, such as controlling medical devices.
[0003] The document of the US Patent Application Publication No. 2021 / 0098133 specification discloses a machine learning system for healthcare applications comprising a data ingestion pipeline configured to automatically receive patient data including stored data from an EHR database and real-time data from multiple data sources, the data 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 defining predictive model execution parameters, a tuning module configured to tune parameters of the predictive model including variables, thresholds, and coefficients; a retraining module configured to make further tuning of the predictive model to remove inherent data bias; and a dashboard and reporting module configured to present the risk score to the patient's care team.
[0004] Document WO 2021 / 030637 refers to a patient health management platform that accesses biosignals recorded for a patient in a current period, including the patient's metabolic profile and sensor data and / or laboratory test data collected about the patient. The platform receives the patient data recorded for the current period, including foods consumed, medicines taken, and symptoms experienced by the patient. The platform implements a machine-learned metabolic model to determine the patient's metabolic state at the end of the current period by comparing a true representation of the metabolic state with a prediction of the metabolic state. The display and prediction are determined based on the recorded biosignals and the recorded patient data, respectively. The platform generates a patient-specific treatment recommendation outlining instructions for the patient to improve their metabolic state and provides the patient-specific treatment recommendation to the patient's device for display to the patient. Summary of the Invention
[0005] It is an object to provide a computer-implemented method for providing individualized healthcare parameters and a healthcare management system that assists in more reliable and error-free determination of individualized healthcare parameters for patients, such as diabetic patients.
[0006] To solve this object, a computer implemented method for providing personalized healthcare parameters is provided as claimed in claim 1. Furthermore, a healthcare management system is provided as claimed in claim 15. Further aspects are disclosed in the dependent claims.
[0007] According to an aspect, a computer-implemented method for providing or determining personalized healthcare parameters, the method includes providing a healthcare application and an interface application executing on a data processing component; transmitting a service request from the healthcare application to the interface application indicating a request to determine a first personalized healthcare parameter, the first personalized healthcare parameter indicating a first healthcare condition of the 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 of a plurality of service applications, each of the service applications configured to determine a respective personalized healthcare parameter for the patient in response to receiving the respective personalized input data, the first service application configured to determine the first personalized healthcare parameter. providing, receiving first input data information in the interface application, the first input data information indicating a data standard of the first input data required by the first service application to determine the first personalized healthcare parameter; receiving, receiving the first input data information in the healthcare application; generating first personalized input data in the healthcare application, the first personalized input data generated in accordance with the first input data information; generating, receiving the first personalized healthcare parameter in the healthcare application, the first personalized healthcare parameter determined in response to receiving the first personalized input data in the first service application, the first personalized healthcare parameter being determined including processing the first personalized input data; receiving, 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 including: providing a healthcare application and an interface application executing on the data processing component; transmitting a service request from the healthcare application to the interface application indicating a request to determine 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 of the plurality of service applications, each of the service applications configured to determine a respective personalized healthcare parameter for the patient in response to receiving the respective personalized input data; receiving first input data information at an interface application, the first input data format information indicating a data standard of the first input data required by the first service application for determining a first personalized healthcare parameter; receiving the first input data information at the healthcare application; generating first personalized input data at the healthcare application, the first personalized input data being generated in accordance with the first input data information; receiving the first personalized healthcare parameter at the healthcare application, the first personalized healthcare parameter being determined in response to receiving the first personalized input data at the first service application, wherein such determining includes processing the first personalized input data; receiving; outputting the first personalized healthcare parameter to a receiving device coupled to the data processing component;The method is configured to:
[0009] The computer-implemented method and the technique proposed for the healthcare management system aid in reliable and error-free determination of one or more individualized healthcare parameters determined by one or more service applications. The process for correctly generating first individualized input data assigned to a patient and providing such first individualized input data conforming to the first input data information ensures that the first service application applied to determine the first individualized healthcare parameter receives correct input data. Based on such correct input data that matches the first input data information, the input data can be correctly processed by the first service application to determine the first individualized healthcare parameter. Such reliable and error-free determination of one or more individualized healthcare parameters can be made even when details regarding the specific data processing of the first individualized input data by the service application are not known. For example, correct determination of one or more individualized healthcare parameters is guaranteed even when some algorithms applied by the service application to determine the respective healthcare parameter are not known.
[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 different from the processor on which the healthcare application and the interface application run.
[0011] Some data requirements for the first input data are collected or gathered from the first service application. In particular, the first input data request may request the first service application to inform about the first input data information. The first data information is then 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. When the determination of the first personalized healthcare parameter is requested in or by the healthcare application, the first input data information is requested to respond, for example in real time, so that whenever the first personalized healthcare parameter / or any other personalized healthcare parameter is determined by one or more service applications, data can be exchanged with the healthcare application, ensuring that the input data is generated and correctly provided according to the input data requirements of the respective service application requested to determine one or more personalized healthcare parameters. For example, if some service applications receive some updates, and such updates cause changes in requirements for input data received by the service applications, the proposed technology ensures that current (or updated) data requirements for input data are always required by and received at the healthcare applications to correctly and correctly generate personalized input data. The input data information indicates such requirements.
[0012] The interface application may also be referred to as a generic interface (application) between the healthcare application and multiple service applications. The generic interface ensures or provides that each input data is sent to the service application according to the respective input data requirements indicated by the input data information collected by the healthcare application before actually sending the input data to the service application.
[0013] Generating the first input data request may further include determining, in the interface application, one or more preselected first service applications of 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 the first service application from the one or more preselected first service applications. The one or more preselected first service applications may be determined by the interface application before receiving a service request indicating a request to determine the first personalized healthcare parameter from the healthcare application, each of such preselected first service applications being configured to determine the first personalized healthcare parameter. A plurality of service applications may be available for determining the first personalized healthcare parameter. Service applications of the plurality of service applications may require different input data standards. In this example, the interface application proactively gathers information about the first service application in advance (before receiving the service request) and is therefore ready to select the first service application when the actual service request is received at the interface application. The interface application may store information about the one or more preselected first service applications in a local memory accessible by the interface application and allocated to the interface application. The information about the one or more preselected first service applications may be updated by the interface application, for example, after a predetermined time limit has elapsed since the one or more preselected 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 in a local database locally accessible by the interface application and 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 access by the interface application locally and / or remotely. For example, access to the remote database may be provided via the Internet. A service provider may provide a service application home page offering the plurality of service applications for use. Other or additional service applications may be accessible by the interface application in a local database assigned to the one or more data processors on which the interface application itself executes or is implemented.
[0015] The provider of the healthcare application (and optionally the interface application) may be different from the provider of at least a subset or all of the service applications. In one example, the provider of the healthcare application (and the interface application) does not know which algorithms are actually applied by one or more service applications to determine the respective healthcare parameters.
[0016] Transmitting the service request may further include providing service application information together with the service request, the service application information indicating a 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 this example, the service request provided from the healthcare application to the interface application indicates a selected first service application to be requested to determine the first personalized healthcare parameter. For example, the healthcare application may be provided with general information about service applications available for use or calling. Based on such information, the service request may be provided to include service application information indicating a selection of a first service application, which may be one of a plurality of service applications that all determine the first personalized healthcare parameter and that the healthcare application is configured to "know". In response to such type of service request including the service application information, the interface application provides the first input data request to the selected first service application. In this example, the healthcare application itself has at least partial control over which service application is requested to determine the first personalized healthcare parameter. Alternatively, the healthcare application may simply send an input request to the interface application (without identifying a preferred or selected service application). In response, the interface application determines or selects the service application required to actually determine the first personalized healthcare parameter.
[0017] The generation of the first individualized input data may further include receiving, at the healthcare application, healthcare data from one or more healthcare data sources. The healthcare data source may be selected from the following group of healthcare data sources: unstructured healthcare database, clinical healthcare database, and regulated healthcare device data, and generate the first individualized input data from the received healthcare data. With respect to the unstructured healthcare database, for example, it may provide the patient's individualized fitness data. The clinical healthcare database may provide, for example, an individualized electronic health record (EHR). With respect to the regulated healthcare device data, for example, it may provide measurement data from a blood glucose meter and / or an insulin pump assigned to the patient. In an example, alternatively or additionally, the healthcare application may receive the healthcare data not from a database, but from some other healthcare data source, such as a personal fitness device that collects the individualized fitness data, and / or a blood glucose meter that collects the patient's measurement data. Thus, the healthcare data may be received directly at the healthcare application from one of such devices and / or via one of the healthcare databases, after previously storing the healthcare data in such database.
[0018] One or more of the healthcare applications may be configured to semantically recognize which data or data points are needed from the input data and semantically collect matching data or data points. Prioritization may be applied to data of the same input data point from multiple healthcare data sources. Interpolation and / or estimation of missing data (points) from existing information may be applied. For example, a patient's Body Mass Index (BMI) may be determined from information about the patient's weight and height. Alternatively or additionally, a waist size may be determined for a patient from information about the patient's weight and height.
[0019] When checking whether the received healthcare data complies or does not comply with the data standard of the first input data of the first service application, generating the first individualized input data from the received healthcare data may further include converting at least a portion of the received healthcare data that provided or is provided in (according to) the source data standard into the first individualized input data that provided or is provided in the source data standard. To receive the first input data information indicating the data standard of the first input data required by the first service application (e.g., from an interface application) of the healthcare application, the healthcare application can check or determine whether the healthcare data received from the data source complies with the data standard of the first input data of the first service application. In some cases, the first data conversion may be applied to convert the healthcare data that is provided in or received in accordance with a source data standard different from the data standard of the first input data into the first individualized input data that complies with the data standard of the first input data. The source data standard defines the standard of the source data. Providing source data with or in accordance with a source data standard refers to providing source data that matches or meets such a standard, such as the format of data. For example, the first data standard of the input data may define or specify a unit of value in which the first input should be received by the first service application. The first data standard of the input data may define or specify some particular unit of value for some of the healthcare data. If the healthcare data received from the data source does not conform to such unit of value, a conversion is applied in the healthcare application.
[0020] Generating the first individualized input data may particularly include receiving healthcare data from one or more healthcare data sources and generating the first individualized input data from the received healthcare data, where the generating includes checking whether the received healthcare data complies with a data standard of the first input data of the first service application.
[0021] The computer-implemented method may further include, in the healthcare application, converting the first individualized healthcare parameter having the output data standard into a first individualized healthcare parameter having a first source data standard required by a first healthcare data source from the group of healthcare data sources, and storing the first individualized healthcare parameter having the first source data standard in the first healthcare data source. The first individualized healthcare parameter determined by the first service application may be provided or returned to one of the healthcare data sources, thereby, for example, storing a current or updated value of the first individualized healthcare parameter in the healthcare data source. Such storage may result in updating the patient's electronic health record.
[0022] Sending the service request may further include generating a service request in the healthcare application in response to a trigger event detected in the healthcare application. In this example, the service request for determining the first individualized healthcare parameter is initiated after the trigger event is detected in the healthcare application. The generation of the service request in the healthcare application in response to the detection of the trigger event may be performed automatically in the healthcare application, for example, in real time in response to the detection of the trigger event.
[0023] The (e.g., first) trigger event may indicate a user input received at the healthcare application. For example, the user input may indicate a request to update the patient's electronic health record with respect to the first personalized healthcare parameter. For example, a doctor may request the determination of the first personalized healthcare parameter for diagnostic reasons. Alternatively or additionally, device inputs may be received at the healthcare application, for example from some medical devices, the device inputs indicating a request from the medical devices to determine the first personalized healthcare parameter that can be applied to control the operation of the medical devices.
[0024] The (e.g., second) trigger event may indicate a trigger time point. For example, a time limit may be set or predetermined. After the time limit has elapsed, the trigger point is detected in the healthcare application, thereby initiating the generation of a service request. The time limit may be set or predetermined by, for example, a user input.
[0025] The (e.g. third) triggering event may indicate a parameter value change of the medical parameter applied by the first service application to determine the previous first personalized healthcare parameter, thereby updating the previous first personalized healthcare parameter with the first personalized healthcare parameter. The update of the previous first personalized healthcare parameter includes a new calculation or determination of the first personalized healthcare parameter by the first service application. For example, the medical parameter may refer to the blood glucose value of the patient, the blood glucose value having been previously applied as an input parameter for determining the first personalized healthcare parameter. Due to a (currently) detected change in the blood glucose value, a new determination of the first personalized healthcare parameter is triggered, and such determination of the first personalized healthcare parameter takes into account the different (current) blood glucose value caused by the change. A threshold value may be pre-determined for the medical parameter, for example by a user input. The determination of the first personalized healthcare parameter may be triggered only if the medical parameter reaches or exceeds a threshold value. For example, determining a first individualized healthcare parameter may be triggered when the medical parameter reaches or exceeds a 10% value change, preferably a 20% value change, more preferably a 30% value change compared to a value previously determined for the first individualized healthcare parameter.
[0026] The computer-implemented method may further include receiving the first personalized input data by the interface application, verifying whether the first personalized input data conforms to the first input data information by the interface application based on the first input data information received at the interface application, and providing the first personalized input data from the interface application to the first service application only if it is verified that the first personalized input data conforms to the first input data information. In this example, before providing the first personalized input data by the interface application to the first service application, there is some check (e.g., validity check) on whether the first personalized input data received by the interface application from the healthcare application conforms to the first input data information. For example, the validity check may be provided on checking whether the first personalized input data is within (or outside) some value or data range that may be predefined. Any such measurement or check further improves the safe and accurate use of the first service application to determine the first personalized healthcare parameter.
[0027] Outputting the first personalized healthcare parameter may further include receiving the first personalized healthcare parameter by the 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 embodiment or other embodiments, determining the first personalized healthcare parameter may be performed or applied to a diabetic patient. With respect to controlling the blood glucose meter, in response to receiving the first personalized healthcare parameter, some measurement may be initiated to detect the patient's current blood glucose level. In another example, in response to providing the first personalized healthcare parameter, some new or additional analysis of the measurement data indicative of the patient's blood glucose level may be performed, and the first personalized healthcare parameter may exceed some threshold value of the first personalized healthcare parameter. Such exceeding of the threshold value may trigger a new or additional analysis of the measurement data. Similarly, detection of the current measurement data by the blood glucose sensor and / or insulin bolus administration by the insulin pump may be initiated or initiated in response to providing the first personalized healthcare parameter.
[0028] Outputting the first individualized healthcare parameter may further include at least one of displaying on an output display device and printing by an output printer device, the first individualized healthcare parameter.
[0029] The plurality of service applications may include a service application configured to determine, for the patient, one or more personalized healthcare parameters selected from the following groups: risk prediction, treatment management, and treatment recommendation. With regard to risk prediction, a likelihood of chronic kidney disease may be determined by at least one of the service applications. With regard to treatment management and / or treatment recommendation, one or more personalized healthcare parameters selected from the following groups: blood glucose level, insulin dose, carbohydrate intake, recommended time for insulin administration or carbohydrate intake may be determined by the service application.
[0030] In response to receiving and / or outputting the first individualized healthcare parameter, a further or second service request may be initiated, such as automatically triggered, in the healthcare application. The further service request indicates a further or second request for determining a second individualized healthcare parameter, the second individualized healthcare parameter being different from the first individualized healthcare parameter and indicating a second healthcare condition of the patient. The steps performed in response to the further service request are similar or equivalent to the steps performed in response to the first service request. A second service application (which may be different from the first service application) provides for determining the further individualized healthcare parameter. The second service application receives the second input data according to the second input data information. For example, if the first individualized healthcare parameter indicates the patient's risk of renal disease, the risk of liver disease may be determined by the further individualized healthcare parameter. Such determination of at least one additional or further individualized healthcare parameter may be triggered, for example, in response to the first individualized healthcare parameter reaching or exceeding a certain threshold value. For example, if the risk of kidney disease may be determined to be high for a patient, a determination of the risk of liver disease may be initiated in response to such a finding in a healthcare application.
[0031] With respect to the healthcare management system, the embodiments described above with respect to the computer implemented method may be provided mutatis mutandis.
[0032] Description of Further Embodiments Further embodiments are described below. Reference is made to the figures. [Brief description of the drawings]
[0033] [Figure 1] 1 is a schematic representation of a healthcare management system comprising a data processing entity or system having a plurality of data processors and a software component comprising a plurality of software applications executing on the plurality of data processors. [Diagram 2] 1 illustrates a schematic representation of an arrangement for performing a computer-implemented method for determining or providing individualized healthcare parameters in a healthcare management system. [Diagram 3] 1 is a schematic representation of a computer-implemented method for determining individualized healthcare parameters. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0034] FIG. 1 shows a schematic representation of a healthcare management system 1 providing a data processing component 2 having a plurality of data processors 3 and a software component 4 comprising a plurality of software applications 5 implemented or executed on the plurality of data processors 3. Furthermore, the arrangement providing the data processing component 2 and the software component 4 is functionally connected to at least one data source or database 6 accessible by at least one of the data processing component 2 and the software component 4 and configured to provide healthcare data to one or more patients. Alternatively, the database 6 may be integrated with the arrangement providing 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 different (separate) locations, which are diagrammatically indicated by the dashed line 4a in FIG. 1. Similarly, the software applications from the plurality of software applications 5 may be executed on different (separate) data processors. The exchange of data may be performed by wireless and / or wired data transmission.
[0035] Fig. 2 shows a schematic representation of an arrangement including elements or modules provided, for example, by a healthcare management system 1, for performing a computer-implemented method for providing or determining individualized healthcare parameters. In general, the arrangement of Fig. 2 may be provided on the basis of the healthcare management system 1. At least some of a plurality of software applications 5 are running in the data processing component 2, each application configured to provide one or more functions of the healthcare management system 1 that are applied in the computer-implemented method for determining individualized healthcare parameters.
[0036] 2, the healthcare application 20 is implemented by one or more of the software applications 5 of the software components 4. The healthcare application 20 is configured to extract healthcare information from the healthcare data and provide insight into the healthcare status of the patient, for example to enable a diagnosis based on the healthcare status. The healthcare application 20 may be a personalized healthcare application that is assigned and personalized to the patient. The personalization may be performed by receiving personal information such as the patient's name, date of birth, and / or personal medical data in the healthcare application 20 and providing limited access to personalized healthcare data based only on such personal information.
[0037] A number of healthcare data sources or resources 21 are accessible by the healthcare application 20. The healthcare data sources 21 may be implemented by a number of databases accessible by the healthcare application 20. The first healthcare data source 21a may be provided as an unstructured healthcare database, for example, including personalized fitness data collected by a fitness device 22 assigned to or used by the patient. The second healthcare data source 21b provides clinical healthcare data, such as personalized electronic health records (EHRs) received via user input 23. The second healthcare data source 21b may provide healthcare data that conforms to the FHIR standard (FIHR-Fast Healthcare Interoperability Resources). The FHIR standard, such as HL7FHIR, describes a set of resources and several different frameworks for exchanging data resources between different healthcare-related systems.
[0038] According to the example shown in FIG. 2, there is a third healthcare data source 21c that provides regulated healthcare device data, for example measurement data from a medical device 24, such as a blood glucose meter and / or an insulin pump, assigned to the patient.
[0039] The healthcare application 20 is configured to receive and process healthcare data from one or more of the different healthcare data sources 21. The healthcare application 20 may also be configured to provide healthcare data to the healthcare data sources 21 and provide such healthcare data for storage in one or more of the healthcare data sources 21. To perform such data generation for storage of data, the healthcare application 20 may be configured to generate healthcare data that conforms to a source data standard that specifies characteristics of data storable in at least one of the healthcare data sources 21a, 21b, 21c.
[0040] According to Fig. 2, an interface application 25 is provided that is configured to exchange electronic data with the healthcare application 20. The interface application 25 may be running on the same subset of data processors as the healthcare application 20 or on a different subset of data processors than the data processing component 2. The interface application 25 provides a generic interface between the healthcare application 20 and a number of service applications 26. The number of service applications 26 may be implemented by one or more software applications 5. The one or more software applications implementing the number of service applications 26 may be separate from the one or more software applications providing the healthcare application 20. Each of the service applications 26a, 26b, 26c is configured to determine, in response to receiving (e.g., personalized) input data, one or more personalized healthcare parameters indicative of a healthcare status of the patient for which the input data was previously collected. For example, the number of service applications 26 may be configured to determine one or more personalized healthcare parameters for the patient selected from the following group: a likelihood of chronic kidney disease, a blood glucose level, a dose of insulin, a carbohydrate intake, and a recommended time for administration of insulin or carbohydrate intake.
[0041] To correctly determine a respective individualized healthcare parameter, each of the service applications 26a, 26b, 26c of the plurality of service applications 26 requires receiving input data according to a respective input data standard. Such input data standard may refer to input data parameters such as, for example, a name, a type of data (string, object, array), and / or a unit of some value (e.g., milliliters, grams, kilograms, ...). Each service application of the plurality of service applications 26 correctly determines one or more individualized healthcare parameters only if the received input data complies with the input data standard of such service application.
[0042] FIG. 3 shows a schematic diagram of steps performed in a computer-implemented method for determining individualized healthcare parameters for a patient in the arrangement of FIG.
[0043] In step 30, a trigger event is detected in the healthcare application 20. For example, a user input may be received as the trigger event. Alternatively, some time limit may have elapsed to trigger the event. The event trigger refers to a request to determine a first personalized healthcare parameter of the patient. The trigger event, such as a user input, may indicate personalized patient information, such as name, date of birth, and / or personal medical data. Alternatively, some personalized code assigned to the patient may be provided along with or in response to the trigger event of the healthcare application 20. For example, a device code assigned to a medical device, such as a blood glucose meter, which is sequentially assigned to the patient, may indicate the patient.
[0044] In step 31, after a service request is generated by the healthcare application 20 in response to detecting the trigger event, a service request indicating a request to determine a first personalized healthcare parameter is sent from the healthcare application 20 to the interface application 25. The first personalized healthcare parameter to be determined is indicative of a first healthcare condition of the patient.
[0045] 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 sent to the first service application 26a (step 32). The first input data request requests the first service application 26a to inform about first input data information indicating a data standard for the first input data that needs to be received by the first service application 26a to determine the first personalized healthcare parameter. According to step 33, the interface application 25 receives data or information indicative of the first input data information from the first service application 26a. After receiving the first input data information, the interface application 25 provides data or information indicative of the first input data information to the healthcare application 20 (step 34).
[0046] In response to receiving the first input data information, the healthcare application 20 collects 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 aggregated healthcare data, the healthcare application 20 generates first personalized input data conforming to the first input data information. Such first personalized input data is transmitted to the interface application 25 in step 37.
[0047] Generating the first individualized input data from the received healthcare data may include applying a first transformation of the data standard by transforming at least a portion of the received healthcare data having a source data standard into first individualized input data having or consistent with the first input data information. By receiving the first input data information in the healthcare application 20 (e.g., from an interface application), the healthcare application 20 can check or determine whether the healthcare data received from the data source 21 complies with the data information provided in the input data of the first service application 26a. In some cases, a first data transformation may be applied to transform the received healthcare data provided in a data source standard that does not comply with the first input data information into first input data that complies with the first input data information. For example, the first input data information may define or specify some particular unit of value for a portion of the healthcare data. If the healthcare data received from the data source 21 does not comply with such unit of value, a transformation is applied in the healthcare application 20 with respect to such unit of value.
[0048] The first service application 26a receives the first personalized input data from the interface application 25 (step 38). After processing the first personalized input data by the first service application 26a 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. Then, in step 40, the interface application 25 transmits the first personalized healthcare parameter to the healthcare application 20. The first personalized healthcare parameter is output by the healthcare application to a receiving device that receives the first personalized healthcare parameter (step 41).
[0049] 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 additionally, the first personalized healthcare parameter may be provided by the healthcare application 20 to a medical device 28 assigned to the patient, such as a blood glucose meter or insulin pump. Operation of such medical device 28 may be controlled according to or in response to the first healthcare parameter.
[0050] Optionally, the first healthcare parameter may be stored in one of the healthcare data sources 21 at step 42 .
Claims
1. A computer implementation method for providing personalized healthcare parameters, To provide a healthcare application (20) and an interface application (25) executed by a data processing component (2), Sending a service request from the healthcare application (20) to the interface application (25) indicating a request to determine a first personalized healthcare parameter, wherein the first personalized healthcare parameter indicates a first healthcare state of the patient. In response to receiving the aforementioned service request, the interface application (25) generates a first input data request. Providing the first input data request to the first service application (26a) among multiple service applications, Each of the service applications (26) is configured to determine individualized healthcare parameters for a patient in response to receiving individualized input data for that patient. The first service application (26a) is configured to determine the first personalized healthcare parameters, The first input data request requests the first service application (26a) to notify and provide the first input data information. The interface application (25) receives first input data information from the first service application (26a), wherein the first input data information indicates a data specification for first input data requested by the first service application (26a) to determine first individualized healthcare parameters, and the data specification specifies the units of each value in which the first input data is requested by the first service application (26a). The first input data information is received in the healthcare application (20) from the interface application. Generating first personalized input data in the healthcare application (20), wherein the first personalized input data is generated according to the first input data information, and the generation of the first personalized input data includes receiving healthcare data from one or more healthcare data sources and generating the first personalized input data from the received healthcare data, wherein the generation includes checking whether the received healthcare data conforms to the data standard of the first input data of the first service application. Receiving the first personalized healthcare parameter in the healthcare application (20), wherein the first personalized healthcare parameter is determined in response to receiving the first personalized input data in the first service application (26a), and such determination includes receiving and processing the first personalized input data. The first individualized healthcare parameter is output to the receiving devices (27, 28) connected to the data processing component (2). Computer implementation methods, including those mentioned above.
2. Generating the first input data request is performed in the interface application (25), Determining one or more pre-selected first service applications from the plurality of service applications, wherein each of the one or more pre-selected first service applications is configured to determine the first personalized healthcare parameter, and The computer implementation method according to claim 1, further comprising selecting the first service application (26a) from the one or more pre-selected first service applications.
3. The interface application (25) The interface application (25) provides local access to a first set of service applications of the local database assigned to the interface application (25), and A second set of multiple service applications that can be remotely accessed via a remote database. The computer implementation method according to claim 2, further comprising determining one or more pre-selected first service applications from at least one of the following.
4. Sending the aforementioned service request The service application information is provided along with the service request, and the service application information indicates the selection of the first service application (26a), and The computer implementation method according to claim 1 or 2, further comprising generating the first input data request by the interface application (25) in response to the service application information and providing the first input data request to the first service application (26a).
5. The generation of the first individualized input data is performed in the healthcare application (20) as follows: The computer implementation method according to claim 1 or 2, further comprising receiving the healthcare data from one or more healthcare data sources selected from the following group of healthcare data sources: unstructured healthcare databases, clinical healthcare databases, and regulated healthcare device data.
6. The computer implementation method according to claim 1 or 2, wherein, in the event of non-compliance, the generation of the first personalized input data from the received healthcare data further comprises converting at least a portion of the received healthcare data provided in the source data standard into the first personalized input data provided in the first input data data standard.
7. In the aforementioned healthcare application (20), Converting the first individualized healthcare parameter having an output data standard to the first individualized healthcare parameter having a first source data standard required by the first healthcare data source from the group of healthcare data sources, and The computer implementation method according to claim 5, further comprising storing the first individualized healthcare parameters having the first source data standard in the first healthcare data source.
8. The computer implementation method according to claim 1 or 2, further comprising sending the service request in the healthcare application (20) in response to a trigger event detected by the healthcare application (20).
9. The computer implementation method according to claim 8, wherein the trigger event indicates user input received by the healthcare application (20).
10. The computer implementation method according to claim 8, wherein the trigger event indicates the trigger time.
11. The computer implementation method according to claim 8, wherein the trigger event indicates a change in the parameter value of a medical parameter applied by the first service application (26a) to determine a previous first personalized healthcare parameter, thereby updating the previous first personalized healthcare parameter with the first personalized healthcare parameter.
12. The interface application (25) receives the first individualized input data, Based on the first input data information received by the interface application (25), it is confirmed whether the first individualized input data conforms to the first input data information provided by the interface application (25), and The computer implementation method according to claim 1 or 2, further comprising providing the first individualized input data from the interface application (25) to the first service application (26a) only when it has been confirmed that the first individualized input data conforms to the first individualized input data information.
13. Outputting the first personalized healthcare parameter means The medical device receives the first personalized healthcare parameter, and The computer implementation method according to claim 1 or 2, further comprising controlling the operation of the medical device according to the first personalized healthcare parameters.
14. The computer implementation method according to claim 1 or 2, wherein the plurality of service applications include a service application configured to determine one or more personalized healthcare parameters selected from the following groups for the patient: risk prediction, treatment management, and treatment recommendations.
15. A healthcare management system comprising a data processing component (2), wherein the healthcare management system is To provide a healthcare application (20) and an interface application (25) executed by the data processing component (2), Sending a service request from the healthcare application (20) to the interface application (25) indicating a request to determine a first personalized healthcare parameter, wherein the first personalized healthcare parameter indicates a first healthcare state of the patient. In response to receiving the aforementioned service request, the interface application (25) generates a first input data request. Providing the first input data request to the first service application (26a) among multiple service applications, Each of the service applications (26) is configured to determine individualized healthcare parameters for a patient in response to receiving individualized input data for that patient. The first service application (26a) is configured to determine the first personalized healthcare parameters, The first input data request requests the first service application (26a) to notify and provide the first input data information. The interface application (25) receives first input data information from the first service application (26a), wherein the first input data information indicates a data specification for first input data requested by the first service application (26a) to determine the first personalized healthcare parameters, and the data specification specifies the units of each value in which the first input data is requested by the first service application (26a). The first input data information is received in the healthcare application (20) from the interface application (25). Generating first personalized input data in the healthcare application (20), wherein the first personalized input data is generated according to the first input data information, and the generation of the first personalized input data includes receiving healthcare data from one or more healthcare data sources and generating the first personalized input data from the received healthcare data, wherein the generation includes checking whether the received healthcare data conforms to the data standard of the first input data of the first service application. Receiving the first personalized healthcare parameter in the healthcare application (20), wherein the first personalized healthcare parameter is determined in response to receiving the first personalized input data in the first service application (26a), and such determination includes receiving and processing the first personalized input data. A healthcare management system configured to output the first individualized healthcare parameters to receiving devices (27, 28) connected to the data processing component (2).