System and method for adaptive generation of graphical data of treatment history

Abstract

A method for generating graphical data of a patient's treatment history includes receiving a patient's medical data corresponding to a patient visit to a healthcare provider and generating graphical data corresponding to a timeline view of the patient visit. The generated graphical data includes first and second graphical elements corresponding to first and second diagnoses based on medical data during the current patient visit and previous patient visits. Each graphical element includes a graphical indicator of a diagnosis regarding a medical condition and at least one graphical sub-element, and the at least one graphical sub-element is related to a physiological parameter selected from the medical data and related to the diagnosis. The method includes generating a first graphical connector between the second graphical element and the first graphical element to indicate the passage of time between patient visits in the timeline view.

Description

Technical Field

[0001] Priority Claim and Cross - Reference to Related Applications This application claims the benefit of priority of U.S. Provisional Patent Application No. 63 / 364,517, filed on May 11, 2022, entitled "SYSTEM AND METHOD FOR ADAPTIVE GENERATION OF GRAPHICAL DATA OF A TREATMENT HISTORY", the entire content of which is incorporated herein by reference. This application cross - references U.S. Provisional Patent Application No. 63 / 364,518, filed on May 11, 2022, entitled "SYSTEM AND METHOD FOR ADAPTIVE GENERATION OF GRAPHICAL DATA OF PREDICTED DIAGNOSES", the entire content of which is incorporated herein by reference.

Background Art

[0002] Patients with diabetes (PwD), particularly those with type 2 diabetes (T2D), generally receive treatment from primary care physicians (PCPs) such as general practitioners (GPs) or family physicians (FMs). Since PCPs diagnose not only T2DM patients but also patients with many other chronic conditions, they are often overwhelmed due to the large number of patients. With typical appointment times of less than 15 minutes, there is a significant cognitive load on PCPs regarding disease management and optimal treatment recommendations. These factors lead to a phenomenon called clinical inertia, which is the delay caused when strengthening appropriate treatment for better disease management. Clinical inertia, in turn, leads to an increase in the medical - economic costs and a decrease in the quality of life of PwD.

[0003] Therefore, there is a need for clinical decision support (CDS) tools that assist primary care physicians (PCPs) and other healthcare providers (HCPs) in selecting appropriate treatment options for people with type 2 diabetes. When integrated within the clinical workflow, CDS tools that consider patient characteristics can help HCPs make better individualized treatment decisions that improve clinical, patient-reported, and economic outcomes. In the medical field, clinical guidelines for the treatment of diabetes from organizations such as the American Diabetes Association (ADA) and the European Association for the Study of Diabetes (EASD) are recognized, but even these clinical guidelines for treatment transitions in type 2 diabetes (T2D) can be cumbersome for PCPs to follow or apply considering the volume of patient data. Additionally, potential recommended treatment regimens are complex and can evolve over the years, presenting further difficulties in tracking disease progression and providing preventive disease management. Therefore, improvements in systems and methods for providing clinical information and CDS to PCPs and other HCPs in an efficient manner that reduces cognitive load would be beneficial.

Summary of the Invention

[0004] An adaptive clinical decision support user interface (UI) enables healthcare providers (HCPs) to efficiently manage the care process for diabetic patients. The UI includes information graphics for each visit that are dynamically updated with relevant physiological values used to drive underlying guidance logic for forming diagnosis and treatment recommendations. Comorbidities and related physiological markers can be tracked to further tailor care in light of allowable guidelines where modified treatments may be recommended, advanced treatment services initiated, or disease risk progression algorithms directly invoked from the interface. The UI reduces the cognitive load in navigating complex treatment pathways based on the current disease state.

[0005] In one embodiment, a method for generating a user interface of a patient's treatment history has been developed. The method includes receiving, using a processor, medical data of a patient, where the medical data corresponds to multiple patient visits to a healthcare provider, and generating, using the processor, graphical data corresponding to a timeline view of the multiple patient visits. Generating the graphical data further includes generating a first graphical element corresponding to a first diagnosis based on the medical data during a current patient visit among the multiple patient visits, the first graphical element further including a graphical indicator of the first diagnosis for the first medical condition and at least one graphical sub-element, where at least one graphical sub-element is related to a physiological parameter selected from the medical data and the physiological parameter is related to the first diagnosis. The method further includes generating a second graphical element corresponding to a second diagnosis based on the medical data of the patient during a first previous patient visit among the multiple patient visits, the second graphical element further including a graphical indicator of the second diagnosis for the second medical condition and at least one graphical sub-element, where at least one graphical sub-element is related to a physiological parameter selected from the medical data and the physiological parameter is related to the second diagnosis. The method further includes generating a first graphical connector between the second graphical element and the first graphical element, where the first graphical connector indicates the progression of time between the first previous patient visit and the current patient visit in the timeline view.

[0006] In another embodiment, a computing system configured to generate a user interface of a patient's treatment history was developed. The computing system includes a memory and a processor operably connected to the memory. The memory is configured to store a patient's medical data, and the medical data corresponds to a plurality of patient visits to a healthcare provider and stored program instructions. The processor is configured to execute the stored program instructions to generate graphical data corresponding to a timeline view. The processor is further configured to generate graphical data further including a first graphical element corresponding to a first diagnosis based on the medical data during the current patient visit among the plurality of patient visits, the first graphical element further including a graphical indicator of the first diagnosis for the first medical condition and at least one graphical sub-element, the at least one graphical sub-element being related to a physiological parameter selected from the medical data, and the physiological parameter being related to the first diagnosis. The processor is further configured to generate a second graphical element corresponding to a second diagnosis based on the patient's medical data during a first previous patient visit among the plurality of patient visits, the second graphical element further including a graphical indicator of the second diagnosis for the second medical condition and at least one graphical sub-element, the at least one graphical sub-element being related to a physiological parameter selected from the medical data, and the physiological parameter being related to the second diagnosis. The processor is further configured to generate a first graphical connector between the second graphical element and the first graphical element, the first graphical connector indicating the passage of time between the first previous patient visit and the current patient visit in the timeline view.

[0007] In another embodiment, a method for generating a user interface of a patient's treatment history has been developed. The method includes receiving, using a processor, medical data of a patient, where the medical data corresponds to a first patient visit to a medical provider, and generating, using the processor, graphical data corresponding to a timeline view. The generation of the graphical data further includes generating a first graphical element corresponding to a first diagnosis based on the medical data during the first patient visit, where the first graphical element further includes a graphical indicator of the first diagnosis for a first medical condition and at least one graphical sub-element, and at least one graphical sub-element is related to a physiological parameter selected from the medical data, and the physiological parameter is related to the first diagnosis.

Brief Description of the Drawings

[0008] To easily identify the description of any particular element or act, the most significant digit of the reference number refers to the figure number in which the element is first introduced.

[0009]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Modes for Carrying Out the Invention

[0010] These and other advantages, effects, features, and purposes will be better understood from the following description. In the description, reference is made to the accompanying drawings which form a part hereof and in which embodiments of the concepts of the present invention are shown by way of illustration and not limitation. Corresponding reference numerals indicate corresponding parts throughout several views of the drawings.

[0011] The concepts of the present invention can accept various modified forms and alternative forms, but its exemplary embodiments are shown by way of example in the drawings and described in detail herein. However, the following description of the exemplary embodiments does not limit the concepts of the present invention to the specific forms disclosed, but rather, the intention is to cover all advantages, effects, and features that fall within the spirit and scope defined by the embodiments described herein and the following embodiments. Therefore, the embodiments described herein and the following embodiments should be referred to in order to interpret the scope of the concepts of the present invention. It should be noted that the embodiments described herein may have advantages, effects, and features useful in solving other problems.

[0012] With reference now to the accompanying drawings, in which some but not all embodiments of the concepts of the present invention are shown, apparatuses, systems, and methods are described more fully hereinafter. In fact, the apparatuses, systems, and methods may be embodied in many different forms and should not be construed as limited to the embodiments described herein. Rather, these embodiments are provided so that this disclosure will satisfy applicable legal requirements.

[0013] Similarly, many modifications and other embodiments of the devices, systems, and methods described herein will come to mind to those skilled in the art to which this disclosure pertains, having the benefit of the teachings presented in the foregoing description and the associated drawings. Accordingly, it is to be understood that the devices, systems, and methods are not limited to the specific embodiments disclosed, and that modifications and other embodiments are intended to be included within the scope of the embodiments. Although specific terms are used herein, they are used in a generic and descriptive sense only and not for purposes of limitation.

[0014] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains. Any methods and materials similar or equivalent to those described herein can be used in the practice or testing of the methods, but the preferred methods and materials are described herein.

[0015] Moreover, references to an element by the indefinite article "a" or "an" do not exclude the possibility of there being more than one element, unless the context clearly requires that there be only one element. Thus, the indefinite article "a" or "an" typically means "at least one." Similarly, the terms "having," "comprising," or "including," or any grammatical variations thereof, are used in a non-exclusive manner. Thus, these terms can refer to both situations where there are no additional features in the entity described in this context in addition to the features introduced by these terms, and situations where there are one or more additional features. For example, the expressions "A has B," "A comprises B," and "A includes B" can all refer to situations where, in addition to B, there are no other elements in A (i.e., situations where A consists solely and exclusively of B), or to situations where, in addition to B, there are one or more additional elements such as element C, elements C and D, or further elements.

[0016] As used herein, the term "person with diabetes" (PwD) refers to a patient diagnosed with, or at risk of being diagnosed with, one or more forms of diabetes, including prediabetes, type 1 diabetes, type 2 diabetes, gestational diabetes, and one or more co-existing diseases associated with diabetes. In certain embodiments described herein, the PwD is a patient of a healthcare provider (HCP), and references to the PwD and the patient are used interchangeably herein. Certain embodiments described herein are directed to improving a user interface for a patient treatment history for an HCP treating a PwD, but the systems and methods described herein are not limited to the treatment of PwDs and can be used to implement an improved user interface for the treatment of other diseases and conditions, particularly chronic conditions that require long-term treatment.

[0017] As used herein, the term "physiological parameter" refers to any quantifiable aspect of the physiological function of a PwD that is measured as part of providing medical data for diagnosing a new condition or tracking the status of a previously diagnosed condition. A non-limiting list of physiological parameters important in the treatment of diabetes and diabetes co-existing diseases includes body mass index (BMI), blood pressure (BP), blood glucose, glycosylated hemoglobin (HbA1c), blood ketones, and estimated glomerular filtration rate (eGFR).

[0018] As used herein, the term "medical data" refers to both medical diagnostic data and medical treatment data. Medical diagnostic data includes identification of previous diagnoses, diagnostic test results, and records of previous and current physiological parameter values of the PwD. Medical diagnostic data optionally includes related genetic data, phenotypic data, demographic data, and socioeconomic data regarding the PwD. Medical treatment data includes records of previously prescribed medications or other medical treatments prescribed to the PwD during previous patient visits. During a current patient visit, the clinical decision support system is configured to generate one or more prescribed treatments for the PwD based on the medical data, and the HCP can adopt the prescribed treatment or manually select a different course of action for the PwD.

[0019] As used herein, the term "prescribed treatment" refers to any medical diagnostic test, medical diagnosis or prognostic algorithm, medical procedure, medical therapy, drug therapy, dietary therapy and lifestyle modification, or other recommended course of action that an HCP issues to a PwD during the PwD's treatment history. In particular, with respect to drugs, the term "prescribed" herein encompasses both over-the-counter drugs and prescription drugs.

[0020] As used herein, the term "graphics data" refers to any form of encoded data that a computing device uses to generate a visually perceivable output, including text, geometry, photographs, icons, textures, etc., using a display device, printer, or other output device. The various forms of graphics data include both still image data and moving image data such as animation and video. Examples of graphics data include rasterized image data, vector graphics data, procedural graphics data, and combinations thereof. Examples of rasterized image data include graphics data that encodes an array of pixel values within an image, and the display device generates an output image formed from the array of pixel values. Rasterized image data can be compressed using JPEG, PNG, WEBP, or other suitable compression formats for still images, and video compression codecs such as h.264, h.265, VP9, AV1, or other suitable compression formats for video or animation. Examples of vector graphics include graphics data that encodes declarative parameters that describe the shape, color, placement, and other details of an image that a computing device processes to reproduce the image. Examples of vector graphics include scalable vector graphics (SVG), graphics generated from a cascading style sheet (CSS) document, portable document format (PDF), and other suitable vector graphics formats. Procedural graphics data includes data encoded as imperative command data that a processor executes to dynamically generate graphics data. Examples of procedural graphics data include JavaScript, WebAssembly, WebGL, or HTML used in publicly available web browsers <canvas>Encoded command parameters for controlling another scripting language for drawing graphics as part of an element, or data encoded in a PostScript language that a computing device renders using a PostScript rendering engine are included. Further, one or more graphical datasets forming graphical elements are formatted using a markup language format such as Hypertext Markup Language (HTML), Extensible Markup Language (XML), or a suitable markup language to generate the timeline views and other graphics described herein. In some configurations, a single computing system generates graphics data and a human user performs a process of rendering the graphics data to a display device for viewing the graphics. As described in further detail below, in other configurations, a first computing system generates graphics data and transmits the graphics data to one or more computing systems that perform a task of rendering the graphics to one or more display devices so that one or more human users can view the graphics.

[0021] Figure 1 shows a system 100 for providing clinical decision support information to an HCP using the adaptive user interface described herein. System 100 includes a clinical decision support (CDS) system 102, an electronic health record (EHR) service 118, an HCP terminal 126, and an optional PwD device 136. The CDS system 102, the electronic health record (EHR) service 118, the HCP terminal 126, and the PWD device 136 are communicatively connected via a network 146.

[0022] The CDS system 102 of FIG. 1 utilizes one or more computing devices including one or more central processing units (CPUs), graphics processing units (GPUs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), other digital logic devices, or combinations thereof, shown as the CDS processor 104 of FIG. 1, to perform the functions described herein. The CDS processor 104 is operably connected to a CDS memory 106 and a network transceiver 116. The CDS memory 106 includes one or more volatile data storage devices such as static and dynamic random access memories (RAM), and one or more non-volatile data storage devices such as magnetic storage devices, solid state storage devices, and optical storage devices. During operation, the CDS processor 104 reads and writes data to the CDS memory 106, executes stored program instructions, and stores data including medical data received from the HCP terminal 126 and the EHR service 118 and generated graphics data. The CDS processor 104 operates the network transceiver 116, which is a wired or wireless network interface controller that transmits and receives data via the network 146, to receive medical data and other commands from the HCP terminal 126, transmit and receive EHR data with the EHR service 118, and transmit graphical data of the timeline view user interface of the treatment history of the PwD to the HCP terminal 126. In some configurations, the CDS processor 104 also operates the network transceiver 116 to receive medical data directly from the PWD device 136 and transmit graphical data of the treatment history of the PwD to the PWD device 136.

[0023] In the CDS system 102, the CDS memory 106 stores the CDS SOFTWARE 108, the diagnostic database 110, the PwD medical data 112, and the graphics data 114. The CDS SOFTWARE 108 includes stored program instructions that are executed by the CDS processor 104 to perform clinical support functions and generate graphical data corresponding to a timeline view of one or more prescribed treatments for treating the PwD over one or more diagnoses and a series of patient visits. The CDS SOFTWARE 108 also implements one or more network interfaces, such as a web server or other network server, to enable the HCP terminal 126 to access the CDS system 102 and send commands, and to enable the CDS system 102 to send the generated graphical data described herein to the HCP terminal 126. The diagnostic database 110 includes a set of stored logical rules that the CDS system 102 uses to generate a diagnosis of the PwD based on the medical data of the PwD. In one particular configuration, the diagnostic database 110 encodes guidelines from the American Diabetes Association (ADA) {1>Standards of Medical Care in Diabetes<1}. Alternative configurations use different medical guidelines or other algorithms to generate diagnoses and prescribed treatments. The CDS system 102 uses the diagnostic database 110 to generate graphical elements that automatically display diagnoses and prescribed treatments during operation of the system 100, although the HCP may optionally use the HCP terminal 126 to override the proposed diagnosis or course of action recommendations. The PwD medical data 112 includes both any relevant medical data of the PwD during the current patient visit and past medical record data including medical data from one or more previous patient visits. The PwD medical data 112 optionally includes PwD medical data received by the CDS system 102 from the EHR service 118, which includes not only past medical data stored in the electronic health record of the PwD, but also data received from tests at external laboratories, home diagnostics such as spot and continuous glucose meter devices, and medical data provided by the HCP to the CDS system 102 via the HCP terminal 126 during the patient visit.Furthermore, during operation, the CDS system 102 optionally transmits updated medical data of the PwD to the EHR service 118 to reflect the updated measurements in physiological parameters, diagnosis, or record the prescription drugs or other medical treatments the PwD receives during the treatment process. The graphics data 114 includes a graphical representation of a timeline view of the treatment history of the PwD over a series of one or more patient visits based on the PwD medical data 112. For example, the graphics data 114 includes graphical elements and sub-elements that show one or more diagnoses and associated physiological parameters of each diagnosis, prescribed treatments, prescription drugs, diagnostic tests, as well as graphical connectors that link the graphical elements within the timeline view to form a timeline view. In some configurations, the graphics data 114 further includes stored text, icons, geometric templates, and other visually perceptible data used by the CDS system 102 to adaptively generate a timeline view of the PwD based on the PwD medical data 112.

[0024] The EHR service 118 in FIG. 1 provides the medical data of the PwD to the CDS system 102 in the form of an EHR. In the exemplary embodiment of FIG. 1, the EHR service is a network computing service that includes a digital processor 120 and a memory 122 that stores the EHR data 124 of the PwD. The EHR data 124 is a digital record encoded in a standard format such as the Fast Healthcare Interoperability Resource (FHIR) format, a version of the Health Level Seven International (HL7) format, or another suitable electronic health record format. In the embodiment of FIG. 1, the EHR service 118 operates independently of the CDS system 102, but in an alternative configuration, the EHR service 118 and the CDS system 102 may be implemented as an integrated system. In an actual embodiment, the EHR data 124 of the PwD may include data received from a plurality of data sources including an external diagnostic test service, an HCP operating the HCP terminal 126, the CDS system 102, and EHR data from other HCPs such as medical experts treating the PwD for other medical conditions and co-morbidities.

[0025] The HCP terminal 126 in FIG. 1 is a desktop or laptop personal computer (PC), tablet, smartphone, or other suitable client computing device of the HCP that includes a terminal processor 128, a memory 130, and a display device 134. The HCP uses the HCP terminal 126 to provide medical data to the CDS system 102 and optionally the EHR service 118, and to receive and display graphical data corresponding to the timeline view of multiple patient visits of the PwD when the PwD undergoes treatment by the HCP over a series of visits. In some configurations, the HCP also uses the HCP terminal 126 to communicate with the PWD device 136 between patient visits, or to conduct remote patient visits in situations where the HCP provides telemedicine services to the PwD. In the embodiment of FIG. 1, the HCP terminal 126 executes stored program instructions within the terminal software 132 stored in the HCP terminal memory 130 to enable the HCP terminal 126 to communicate with the CDS service 102. In one configuration, the terminal software 132 includes an operating system and web browser software that functions as a client for one or more web services provided by the CDS system 102, but in an alternative configuration, the terminal software 132 is another client software program. During operation, the terminal processor 128 executes the terminal software 132 and operates the display device 134 to generate a visual output of the graphics data 114 generated by the CDS system 102 and transmitted to the HCP terminal 126. The display device 134 is, for example, a flat panel display screen or other electronic display device, but in some configurations, a printer may reproduce the graphical display of the timeline view on paper or other print media. In some configurations, the display device 134 incorporates a touch screen interface to enable the HCP to input data and modify the timeline view, as will be described in more detail below, but in other configurations, the HCP terminal 126 incorporates a combination of a mouse, keyboard, voice input device, or other input device (not shown) to receive HCP input.

[0026] The PWD device 136 in FIG. 1 is another desktop or laptop PC, tablet, smartphone, or other suitable client computing device of the PwD that includes a device processor 138, a device memory 140 that stores PwD device software 142, and a device display 144. In some configurations, the PWD device 136 receives physiological parameter data from a monitoring device such as a spot or continuous blood glucose meter, a health tracking device such as a smartwatch, or other medical device. The PWD device 136 is optionally configured to use video conferencing software and other telemedicine software known in the art and not described in further detail herein so that the PwD can conduct a telemedicine patient visit with the HCP via the HCP terminal 126. In some configurations, the CDS system 102 transmits generated graphics data for a timeline view user interface of the PwD's treatment history to the PWD device 136 for display using the display device 144 via the network 146. In another configuration, the HCP terminal 126 re-transmits the graphics data of the timeline view of the PwD's treatment history to the PWD device 136 during a telemedicine patient visit.

[0027] FIG. 2 is a block diagram of a process 200 of the operation of a CDS system for generating a graphical timeline view user interface of the diagnosed symptoms and recommended prescribed treatments of a PwD over a series of one or more patient visits. Process 200 is executable at any time, but for illustrative purposes, process 200 is described as occurring during a patient visit to generate a graphical timeline view of the current patient visit and, if any, one or more previous patient visits. Process 200 is described in relation to the system 100 of FIG. 1, and references to process 200 performing a function or action refer to the action of a processor, such as the CDS processor 104 within the CDS system 102, executing stored program instructions, such as CDS software 108, to perform the function or action.

[0028] Process 200 begins when CDS system 102 receives PwD medical data for at least one patient visit (block 202). In system 100, the processor 104 of CDS system 102 receives medical data from one or more sources including, but not limited to, EHR service 118, HCP terminal 126, and optionally PWD device 136. In particular, EHR service 118 provides medical data for previous patient visits, including previous diagnoses, prescription medications and medical treatments, a history of PwD physiological parameter data measurements, and optionally socioeconomic and demographic data regarding the PwD. During a patient visit, HCP terminal 126 optionally transmits physiological parameters and other medical data to CDS system 102 based on manual input from the HCP, automatically uploaded physiological parameters generated by a medical testing device such as a blood glucose meter, or both. Additionally, CDS system 102 may receive medical data regarding blood tests or other diagnostic tests that the PwD receives at an external diagnostic laboratory prior to a patient visit directly from the diagnostic laboratory's computing system, via EHR service 118, or from HCP terminal 126. As described above, CDS system 102 stores the received PwD medical data 112 in CDS memory 106.

[0029] Process 200 continues such that the CDS system 102 identifies the most relevant physiological parameters for diagnosis during each patient visit (block 204). In the embodiment of FIG. 1, the CDS processor 104 uses the diagnostic database 110 to identify the physiological parameters within the PwD medical data 112 that are most relevant to each diagnosis in a series of one or more patient visits. For example, if a patient visit includes a diagnosis that the PwD is obese and has an uncontrolled HbA1c indicating the onset of type 2 diabetes, the CDS processor 104 uses the diagnostic database 110 to identify the most relevant physiological parameters for these diagnoses, such as the body mass index (BMI) related to obesity and the HbA1c level measured for the PwD. Often, the PwD medical data 112 includes physiological parameters and other information not directly related to the diagnosis, and the CDS processor 104 filters these data from the timeline view, although the HCP can, of course, access the complete PwD medical data 112 via the conventional user interface as needed.

[0030] Process 200 continues such that CDS system 102 generates graphical elements for each patient visit and at least one graphical sub - element for identified physiological parameters related to one or more diagnoses in each patient visit (block 206). The graphical elements and graphical sub - elements provide graphical indicators of physiological parameter data leading to diagnoses and prescribed treatments. A graphical indicator refers to any type of graphical data in a timeline view that conveys specific information about the medical data of a PwD, the prescribed treatment of a PwD, or the recommendations for the prescribed treatment of a PwD. A graphical sub - element is a type of graphical element that is subordinate to another graphical element in a timeline view, and the CDS system 102 generates the graphical data of the graphical sub - element within the boundaries of the parent graphical element or otherwise associates each graphical sub - element with the parent graphical element. The graphical elements and sub - elements clearly show the relationship between the graphical elements of a patient visit and one or more graphical sub - elements related to the patient visit.

[0031] Figure 3 shows an example of a timeline view 300 rendered from graphical data generated during process 200, including graphical elements and graphical sub-elements for each patient visit. In the timeline view 300, graphical elements 304 and 316 are embodied as rectangular graphical elements, and each graphical element includes text providing information related to each patient visit, including the number of patient visits (e.g., first, second, third, etc.), the current diagnosis, and, if any, graphical indicators of the current drug therapy or treatment prescribed to the PwD. Figure 3 shows an example of a timeline view, where graphical element 304 includes a text graphical indicator indicating the second PwD visit and that the PwD is diagnosed with uncontrolled HbA1c and obesity. Graphical sub-elements 308a and 308b are shown as circles subdivided into two semi-circular regions having an upper region listing physiological parameters related to the diagnosis and treatment and a lower region listing the quantified values of the physiological parameters. In Figure 3, sub-element 308a indicates an HbA1c value of 7.1, which is a high value supporting the diagnosis prediction that the patient has diabetes. Sub-element 308b indicates the body mass index (BMI) physiological parameter related to the diagnosis of obesity. In some configurations, the graphical data of the graphical sub-elements for each physiological parameter provides additional information to the HCP beyond the quantitative value of the physiological parameter. For example, in some configurations, the physiological parameter data is displayed using color-coded text or color-coded graphics within the graphical sub-element to indicate whether the physiological parameter is within range or out of range for a particular PwD. Using the HbA1c physiological parameter as an example, green can indicate an HbA1c value considered normal for a healthy individual, yellow can indicate an elevated HbA1c for a non-insulin-dependent diabetic patient, and red can indicate a further elevated HbA1c indicating the need for insulin treatment.In some configurations, the graphical sub-elements of the physiological parameters also include arrows or other graphical indicators that display the trend of physiological parameters over time from previous patient visits, such as upward or downward arrows indicating an upward or downward trend in HbA1c levels or a change in another relevant physiological parameter. In some configurations, the graphical indicators of the physiological parameters include graphs, icons, or other non-text graphical indicators that can be easily interpreted by the HCP to evaluate the symptoms of the PwD.

[0032] The timeline view 300 further shows a second patient visit and graphical elements 316 of a third patient visit that are spatially offset from the graphical elements 304 of the timeline view, and the two elements are linked by a first graphical connector 310a / 310b that indicates the passage of time between patient visits along the timeline view. In FIG. 3, the graphical elements 316 of the third patient visit represent the current patient visit, the second patient visit of the graphical elements 304 represents the most recent previous patient visit, and in some embodiments, the default timeline view shows the current patient visit and the most recent previous patient visit when applicable. For treatment histories that include one or more previous patient visits not shown in the default timeline view, the timeline view 300 optionally includes a graphical connector 348 that extends from the earliest displayed patient visit, which is graphical element 304 in the example of FIG. 3, graphically indicating that there are earlier patient visits in the treatment history. The graphical elements 316 further include a graphical representation that the PwD is receiving drug therapy and diagnosis for renal dysfunction, a known co-morbidity of diabetes. The graphical elements 316 further include graphical sub-elements 318a and 318b. The graphical sub-element 318a indicates the patient's HbA1c value at the third patient visit, which is the same physiological parameter as sub-element 308a but may be a different value (7.3 vs. 7.1) based on changes in the patient's physiological function. The graphical sub-element 318b indicates the estimated glomerular filtration rate (eGFR) value, a physiological parameter highly relevant to the renal dysfunction diagnosis. Thus, the graphical elements 316 include graphical sub-elements of at least one physiological parameter (eGFR) that do not exist in the graphical elements 304 for previous patient visits, and conversely, the graphical elements 304 include graphical sub-elements of at least one physiological parameter (BMI) that do not exist in the graphical elements 316.

[0033] As described above, process 200 identifies and generates graphical sub-elements of physiological parameters most relevant to the diagnosis at each patient visit, and in some cases, the most relevant selected physiological parameters change based on changes in the underlying disease of the PwD. Therefore, process 200 generates an adaptive display of information highlighting the most relevant physiological parameters during different patient visits in the PwD's medical history, whereby the HCP can efficiently and with reduced cognitive load evaluate and treat the PwD compared to reviewing all of the PwD's physiological parameters in a conventional EHR or other health record. For example, FIG. 3 further shows non-limiting examples of alternative graphical elements 328 and 338 that the CDS system 102 generates during process 200 based on different potential diagnoses and related physiological parameters for PwDs that can occur for different disease progressions. Graphical element 328 corresponds to the diagnosis that the PwD should initiate insulin because the HbA1c value shown in graphical sub-element 330 has substantially increased from a previous patient visit and the existing prescription of metformin is no longer effective. Graphical element 340 corresponds to the diagnosis that the PwD should continue non-insulin drug therapy in response to a slight increase in HbA1c (graphical sub-element 342a) and no change in BMI (graphical sub-element 342b). FIG. 3 shows, in this example, that only a single displayed graphical element 316 corresponds to the evaluated symptoms of the PwD during the patient visit, so graphical elements 328 and 340 with corresponding graphical sub-elements are shown in dashed lines. In some embodiments, the HCP can change the diagnosis for the current patient visit and manually select a set of different diagnosis and treatment options for the PwD, for example, via a drop-down list box or other user interface element. The CDS system 102 updates the graphical sub-elements as needed to generate graphical data of the most relevant physiological parameters related to the selected diagnosis.

[0034] Referring back to FIG. 2, during process 200, the CDS processor 104 identifies (block 208) any prescribed treatments for the PwD in the PwD medical data 112 and generates (block 210) graphical elements for each prescribed treatment in the timeline view. In the processing of blocks 208 and 210, the prescribed treatments refer to previously prescribed treatments recorded in the PwD medical data 112 as part of the PwD's medical history. Prescribed treatments are typically issued during a patient visit and then provided to the PwD after the patient visit, so the CDS processor 104 generates a timeline view where the graphical elements for the prescribed treatments are positioned at intermediate positions among the graphical elements of the patient visits, and the graphical connectors linking the patient visits are further subdivided into two sub-connectors that similarly show the prescribed treatments in the timeline view.

[0035] Referring to FIG. 3, the graphical element 312 indicates a previously prescribed treatment such as a drug prescription for metformin, including a label that the prescribed treatment is a drug and an identifier of the drug type. In an alternative embodiment, the graphical element for the prescription drug indicates additional details such as dosage levels and dosing schedules, or other relevant information about the drug. The first graphical connector includes a first sub-connector element 310a that links the graphical element 304 of the previous patient visit to the graphical element 312 of the prescribed treatment, and a second sub-connector element 310b that connects the graphical element 312 of the prescribed treatment to the graphical element 316 of the current patient visit, providing a clear indication in the timeline view 300 of when the prescribed treatment was performed.

[0036] As described herein, during process 200, the HCP optionally chooses to prescribe a treatment that deviates from one or more of the recommended prescribed treatments provided by the CDS system 102 in the timeline view 300. If the HCP issues a different prescribed treatment, the CDS system 102 stores in the PwD medical data 112 a data identifier associated with the manually selected prescribed treatment to identify that the prescribed treatment was manually selected. When the CDS system 102 later generates an updated timeline view 300 that includes the manually selected prescribed treatment, the CDS processor 104 generates a graphical element having a specific graphical indicator that identifies that the HCP selected a manually prescribed treatment rather than one of the recommended prescribed treatments. For example, the CDS processor 104 generates a graphical element of the prescribed treatment using a specific color or graphical icon to identify that the HCP manually selected the prescribed treatment, while the graphical elements of the prescribed treatments that comply with the recommendations from the CDS system 102 use a different color or other graphical indicator.

[0037] During a patient visit, the HCP optionally records clinical notes related to the diagnosis and prescribed treatment. In the embodiment of FIG. 3, the graphical element 312 includes a graphical sub-element for the clinical note 314, which is shown as an icon that the HCP can select to display previously recorded clinical notes for the patient visit. The clinical note includes any data that the HCP records in connection with the patient visit and prescribed medical treatment, such as the rationale for prescribing the treatment, reminders for follow-up patient visits, etc. In operation, the HCP optionally selects the graphical sub-element of the clinical note 314 to generate a tooltip or pop-up window that displays the text of the clinical note for review. The HCP can close the tooltip or pop-up window and return to the display of the timeline view 300, minimizing distractions and enabling the HCP to reliably utilize the timeline view 300.

[0038] Referring again to FIG. 2, process 200 continues such that CDS processor 104 identifies the trigger if there is a prescribed treatment recommended for the PwD based on the physiological data within the PwD medical data 112 and the criteria of the diagnostic database 110 for the current patient visit (block 212). If one or more prescribed treatments are identified, CDS processor 104 generates a graphical element for each recommended prescribed treatment trigger in the timeline view (block 214). The graphical element for each trigger includes a graphical indicator of the recommendation for the prescribed treatment related to the diagnosis in the first patient visit. In some configurations, if multiple prescribed treatments are applicable to the PwD, two or more triggers are generated. CDS processor 104 also generates a graphical connector between the graphical element for the current patient visit and the corresponding graphical element for the trigger. The graphical element of the recommended prescribed treatment trigger enables the HCP to select the prescribed treatment in an efficient manner, although the HCP may reject selecting one or more of the triggers, or may choose to prescribe a treatment different from the recommendation generated by CDS system 102 based on the PwD medical data 112 and the diagnostic database 110. If the HCP selects one or more of the triggers of the recommended prescribed treatment, CDS system 102 stores a record of the selected prescribed treatment in the PwD medical data 112 and optionally transmits the prescribed treatment data to the EHR service 118 to maintain a record of the prescribed treatment.

[0039] Referring to FIG. 3, the timeline view 300 includes graphical elements 320 and 322 of triggers corresponding to the graphical elements 316 of the current patient visit. The graphical element 320 includes a trigger for a change in an existing medication treatment, in this case, a recommendation to discontinue the existing metformin dosing plan. In particular, to identify the trigger to discontinue the treatment, the CDS processor 104 uses the diagnostic database 110 to identify that the treatment is effective based on the PwD medical data 112 and that it is a treatment option recommended to discontinue the treatment based on the diagnosis of renal dysfunction in the example of FIG. 3. The graphical element 322 is a trigger for a chronic kidney disease (CKD) detection algorithm or a clinical trial that provides additional information regarding the diagnosed renal dysfunction to the HCP. In the timeline view 300, the graphical connectors 324 and 326 link the graphical element 316 of the patient visit to the graphical elements 320 and 322 of the triggers, respectively. During operation, the HCP uses the HCP terminal 126 to select a hyperlink or other graphical user interface control element on the trigger element to select the trigger element. For example, the HCP selects a hyperlink within the graphical element 320 to activate a separate user interface (not shown) for the PwD's prescription medications to discontinue the metformin prescription. Similarly, the HCP selects a hyperlink within the graphical element 322 to open a website or other user interface to order the PwD's CKD detection algorithm or clinical trial. Optionally, the HCP may enter a clinical note regarding the patient visit after selecting one or more of the triggers or after selecting a prescribed treatment different from the recommended prescribed treatment trigger.

[0040] As described above, the CDS system 102 adaptively generates the graphical data of the timeline view 300 based on different potential diagnoses of PwD. In FIG. 3, the graphical elements 332 and 338 of the trigger respectively represent the suspension of the metformin dosing plan and the trigger of the insulin titration protocol for PwD for whom it is recommended to start insulin treatment based on the diagnosis of the graphical element 328. The graphical connectors 334 and 336 connect the graphical element 328 of the patient visit to the graphical elements 332 and 338 of the trigger respectively. Similarly, the trigger element 344 indicates the recommendation for the prescribed treatment of the SGLT2 inhibitor, and the graphical connector 346 connects the graphical element 340 of the patient visit to the graphical element 344 of the trigger. As described above with reference to the graphical elements 328 and 340, the CDS processor 104 generates the graphical elements 332 and 338 only when the diagnosis matches the diagnosis that the HbA1c indicating insulin dependence of the graphical element 328 is not controlled, and the CDS processor 104 generates the graphical element 344 only when the diagnosis matches the diagnosis of an increase in HbA1c that can be controlled by drugs other than insulin of the graphical element 338.

[0041] Referring again to FIG. 2, the process 200 continues such that the CDS processor 104 generates a timeline view including the graphical elements and connectors described above with reference to the processing of blocks 206-214 (block 216). In addition to including the arrangement of the previously generated graphical elements, the timeline view generates one or more graphical elements indicating the time range during which patient visits and prescribed treatments are performed. The timeline view further includes a timeline slider that enables the HCP to both adjust the size of the time range depicted in the timeline view and move the time range depicted in the timeline view forward and backward in time.

[0042] Referring to FIG. 3, the graphical element 302 of the timeline includes a display of the dates on which the graphical elements 304 and 316 displayed for the patient visits occurred. In the specific example of FIG. 3, the timeline view 302 represents the year 2021 in a rectangular area where the abbreviated month names (January, February, March...) of 2021 are linearly arranged on the timeline. The timeline view 300 aligns the graphical elements of the patient visits with the dates of each patient visit, where the graphical element 304 corresponds to a patient visit in March 2021 and the graphical element 316 corresponds to a visit in September 2021. The graphical element 302 of the timeline also highlights the entries for March and September in bold font to emphasize the dates of each visit. FIG. 3 shows the level of accuracy of the date of each patient visit, along with the year and month, for PwDs who visit the HCP only a few times a year. For patients who require more frequent patient visits, the graphical elements of the timeline present more accurate date information including the day, and optionally the time, of each patient visit.

[0043] When a timeline view is generated at block 216 of process 200, CDS system 102 uses CDS processor 104 and network transceiver 116 to transmit graphical data for the generated timeline view user interface to client HCP terminal 126 via network 146. HCP terminal 126 receives the graphical data, and terminal processor 128 executes terminal software 132 such as a web browser or other client software to generate a rendered user interface that includes a visual depiction of the timeline view using display device 134 provided on HCP terminal 126. The HCP interacts with the user interface using HCP terminal 126, and as described below, the HCP optionally provides input to the HCP terminal to update the timeline user interface, and CDS system 102 receives this via network 146 and the process provides an updated graphical data set for the updated timeline view to HCP terminal 126. Further, in some configurations, CDS system 102 optionally transmits the generated graphical data for the timeline view user interface to PWD device 136 for direct display on the PwD using display device 144. System 100 is embodied, for purposes of illustration, as a network system in which CDS system 102 is connected to HCP terminal 126 via network 146, but in another configuration, a single computing system executes the operations of both CDS system 102 and HCP terminal 126. In this configuration, a processor of the single computing system generates graphical data corresponding to the timeline view of the patient visit and operates a display device provided on the single computing system to display the graphical data corresponding to the timeline view of the patient visit. In one configuration, the single computing system is an HCP terminal 126 that is further reconfigured to host CDS software 108, diagnostic database 110, PwD data 112, and graphics data 114 in addition to terminal software 132.

[0044] Referring to FIGS. 2 and 3, the HCP may optionally use the timeline slider to increase or decrease the time range of the timeline view 300 or adjust the timeline view to move the time range of the timeline view 300 (block 218). If the CDS system 102 receives an input from the HCP terminal 126 to adjust the timeline view, the CDS system 102 generates graphics data of an updated timeline view indicating the time range specified by the input from the HCP terminal 126 (block 220). As shown in FIG. 3, the graphical elements 302 of the timeline further include a timeline slider 306. The timeline slider 306 covers the time range presented in the timeline view 300, whereby the HCP can adjust the timeline view 300 by providing an input via the HCP terminal 126. In one mode of operation, the timeline slider 306 receives an input to adjust the size of the timeline slider to increase or decrease the size of the time range depicted in the timeline view 300. For example, in one operation, the HCP clicks or drags one of the end arrows shown on the timeline slider 306 to increase or decrease the size of the time range shown in the timeline view, and FIG. 4 shows the result of this operation in more detail. In another operation, the HCP moves the timeline slider 306 by performing a click-and-drag operation to move the time range shown in the timeline view without increasing or decreasing the size of the time range, and FIG. 5 shows the result of this operation in more detail. In one configuration, the HCP adjusts the size of the time range of the timeline view or moves the time range of the view based on the date of the calendar, and in another configuration, the time increment for each adjustment is based on a series of patient visits stored in the PwD medical data 112.In a configuration that uses patient visits as a basis for adjusting the timeline view, changing the size of the time range shown in the timeline view involves adding or removing one or more patient visits to the timeline view instead of adding or removing a specific number of months or years to the timeline view. On the other hand, moving the timeline view involves updating the display of patient visits by one or more patient visits forward or backward in time instead of moving the timeline view by a specific number of months or years.

[0045] Figure 4 shows an adjusted timeline view 400 that includes a larger time range in response to an input from an HCP that expands the time range shown in the timeline view during process 200. In particular, timeline view 400 includes graphical elements from timeline view 300 of FIG. 3 and further includes a graphical element 402 corresponding to a first patient visit of the PwD. Similar to graphical elements 304 and 316, graphical element 402 includes a graphical depiction of the diagnosis of the first patient visit ("obesity") and two graphical sub-elements 404a and 404b showing HbA1c (404a) and BMI (404b). A graphical connector 348 between graphical elements 402 and 304 shows the progression of time from the first patient visit shown in graphical element 402 to the second patient visit shown in graphical element 304. The CDS processor 104 generates graphical data corresponding to the first patient visit of graphical element 402, graphical sub-elements 404a and 404b, and graphical connector 348 based on the PwD medical data 112 and the diagnostic database 110 in the same manner as described above with reference to the processing of blocks 206-210. Further, the CDS processor 104 updates the graphical element 302 of the timeline to show an adjusted time range that includes September 2020 to September 2021 in the example of FIG. 4. In the example of FIG. 4, the graphical element 302 of the timeline includes identifiers for 2020 and 2021 and further includes a reduced list of only the months in which patient visits were made to provide the HCP with relevant date information for each patient visit. Although FIG. 4 shows an operation to increase the time range shown in timeline view 400, those skilled in the art will understand that a similar operation can also decrease the time range shown in the timeline view as well.

[0046] FIG. 5 shows an adjusted timeline view 500 generated by the CDS processor 104 in response to an input from the HCP, which moves the timeline view to an earlier time range of the treatment history of the PwD. The timeline view 500 includes the graphical elements 402 for the first patient visit, as well as the graphical sub-elements 404a and 404b, and the graphical elements 304 and the graphical sub-elements 308a and 308b for the second patient visit, including the graphical elements and graphical sub-elements for the first and second patient visits shown above. The graphical connector 348 indicates the progression of time between the first patient visit and the second patient visit, and the timeline view 302 shows that the adjusted timeline overlaps with parts of 2020 and 2021, and the highlighted months indicate the dates of each patient visit. The timeline view 500 also includes the graphical element 312 corresponding to the treatment prescribed at the second medical visit, and the graphical sub-connectors 310a and 310b showing additional treatment history after the second patient visit. To generate the timeline view 500, since the current patient visit is being performed outside the earlier time range of the timeline view 500, the CDS processor 104 deletes the graphical element 316 corresponding to the current patient visit from the timeline view.

[0047] One skilled in the art will recognize that the processing of steps 206-216 may be performed in a different order than described above, or simultaneously. Further, although the timeline views shown herein are arranged in a left-to-right format representing earlier times to more recent times, alternative configurations can orient the timeline in a right-to-left format, or in a vertical top-to-bottom or bottom-to-top format. Additionally, alternative configurations of the process 200 can include different visual formats and arrangements of the graphical elements, graphical sub-elements, and graphical connectors shown herein.

[0048] Process 200 is described in the context of a patient treatment history that includes multiple patient visits for convenience of explanation, but the CDS system 102 and process 200 also generate a user interface having a simplified timeline view for the first patient visit in which only a single patient visit is shown in the timeline view using the same processing steps described above. FIG. 6 shows a timeline view 600 of the first patient visit of a PwD patient diagnosed with or at risk of diabetes. The timeline view 600 includes a graphical element 602 having a display of the diagnosis of the PwD as having uncontrolled HbA1c, being obese, and having hypertension. The graphical element 602 also includes a graphical sub-element 604a showing the HbA1c physiological parameter related to the diagnosis of the PwD, a graphical sub-element 604b showing the BMI physiological parameter, and a graphical sub-element 604c showing the blood pressure (BP) physiological parameter. The timeline view 600 further includes graphical elements 606 and 610 corresponding to a recommended prescribed treatment trigger (graphical element 606) for diet therapy and exercise guidance to address the elevated blood pressure and a recommended prescription drug (graphical element 610) for metformin. Graphical connectors 608 and 612 link the graphical element 602 for the first patient visit to the graphical elements 606 and 610 for the recommended prescribed treatments, respectively. The timeline view 600 shows the date of the first patient visit and also includes a simplified timeline element 302 with the timeline slider control omitted since the patient visit history includes only the first visit.

[0049] The embodiments described herein enable the generation of a timeline view user interface that presents relevant diagnoses, physiological parameters, and recommended prescribed treatment options to an HCP. The user interface reduces the cognitive burden on the HCP and enables more efficient and effective treatment of PwDs and other patients. When integrated within a clinical workflow, the embodiments described herein can assist HCPs in making better personalized treatment decisions that improve clinical, patient-reported, and economic outcomes. In particular, the embodiments described herein enable HCPs to collaborate with existing clinical guidelines for treatment transitions in diabetes in an efficient manner, which can be cumbersome to follow or apply considering the amount of patient data in prior art systems. Additionally, the embodiments described herein simplify the analysis by HCPs of potentially recommended treatment regimens that can be complex and evolve over several years, and simplify the review of a PwD's treatment history and tracking of disease progression using an adaptive user interface customized to the specific physiological parameters, diagnoses, and prescribed treatments of each PwD.

[0050] This disclosure is described in relation to what is considered to be the most practical and preferred embodiments. However, these embodiments are presented by way of example and are not intended to be limiting of the disclosed embodiments. Accordingly, those skilled in the art will understand that this disclosure encompasses all modifications and alternative configurations that are within the spirit and scope of this disclosure and are described in the following claims.< / canvas>

Claims

1. A method for generating a user interface for a patient's treatment history, comprising: Receiving, using a processor, the medical data of the patient, wherein the medical data corresponds to a plurality of patient visits to a healthcare provider; Generating, using the processor, graphical data corresponding to a timeline view of the plurality of patient visits; wherein generating the graphical data comprises: Generating a first graphical element corresponding to a first diagnosis based on the medical data during a current patient visit among the plurality of patient visits, the first graphical element comprising: A graphical indicator of the first diagnosis for a first medical condition, and Further comprising at least one graphical sub-element, the at least one graphical sub-element being related to a physiological parameter selected from the medical data, the physiological parameter being related to the first diagnosis; Generating a second graphical element corresponding to a second diagnosis based on the medical data of the patient during a first previous patient visit among the plurality of patient visits, the second graphical element comprising: A graphical indicator of the second diagnosis for a second medical condition, and Further comprising at least one graphical sub-element, the at least one graphical sub-element being related to a physiological parameter selected from the medical data, the physiological parameter being related to the second diagnosis; Generating a first graphical connector between the second graphical element and the first graphical element, the first graphical connector indicating the progression of time between the first previous patient visit and the current patient visit in the timeline view; The method further comprising:

2. Wherein generating, using the processor, the graphical data corresponding to the timeline view comprises: Generating graphical data corresponding to a timeline slider in the timeline view. In response to user input to the timeline slider that expands the time range depicted in the timeline view, generating a third graphical element related to a third diagnosis in the medical data during a second previous patient visit that occurred before the first previous patient visit among the plurality of patient visits, wherein the third graphical element is a graphical indicator of the third diagnosis for a third medical condition, and further comprising at least one graphical sub-element, the at least one graphical sub-element being related to a physiological parameter selected from the medical data, the physiological parameter being related to the third diagnosis, generating the third graphical element; generating a second graphical connector between the third graphical element and the second graphical element, the graphical connector indicating the passage of time between the second previous patient visit and the first previous patient visit in the timeline view, generating the second graphical connector; The method according to claim 1, further comprising. **Claim 3** Using the processor, generating the graphical data corresponding to the timeline view is generating graphical data corresponding to a timeline slider in the timeline view; In response to user input to the timeline slider that moves to an earlier time range of the timeline view, generating a third graphical element related to a third diagnosis in the medical data during a second previous patient visit that occurred before the first previous patient visit among the plurality of patient visits, wherein the third graphical element is a graphical indicator of the third diagnosis for a third medical condition, and further comprising at least one graphical sub-element, the at least one graphical sub-element being related to a physiological parameter selected from the medical data, the physiological parameter being related to the third diagnosis, generating the third graphical element; Generating a second graphical connector between the second graphical element and the third graphical element, wherein the graphical connector indicates the passage of time between the second previous patient visit and the first previous patient visit in the timeline view, generating a second graphical connector; Removing the first graphical element from the timeline view in response to the current patient visit being performed outside the earlier time range of the timeline view; The method according to claim 1, further comprising.

4. Using the processor to generate the graphical data corresponding to the timeline view is Generating a third graphical element of a timeline indicating a first date of the first previous patient visit and a second date of the current patient visit; The method according to claim 1, further comprising.

5. Using the processor to generate the graphical data corresponding to the timeline view is Further comprising generating a third graphical element including a graphical indicator of a prescribed treatment prescribed during the first previous patient visit, wherein the first graphical connector is configured to indicate that the patient has received the prescribed treatment between the first previous patient visit and the current patient visit in the timeline view, and further comprising a first sub-connector connecting the second graphical element of the first previous patient visit to the third graphical element, and a second sub-connector connecting the third graphical element to the first graphical element of the current patient visit; The method according to claim 1.

6. Using the processor to generate the third graphical element is Generating the third graphical element including a graphical indicator identifying that the prescribed treatment was manually selected by a healthcare provider; The method according to claim 5, further comprising.

7. Using the processor to generate the third graphical element is Generating the third graphical element including a graphical sub-element corresponding to a clinical note associated with the prescribed treatment; The method according to claim 5, further comprising.

8. Using the processor to generate the graphical data corresponding to the timeline view, generating a third graphical element including a graphical indicator of a recommended treatment for the prescribed treatment related to the first diagnosis; further including generating a second graphical connector between the first graphical element and the third graphical element, the second graphical connector indicating that the recommendation for the prescribed treatment is related to the first diagnosis; The method according to claim 1.

9. Using the processor provided in the server computing system to generate the graphical data corresponding to the timeline view; using the processor and the network transceiver to transmit the graphical data corresponding to the timeline view to the client computing system for display using a display device provided in the client computing system; The method according to claim 1, further comprising.

10. Using the processor provided in the computing system to generate the graphical data corresponding to the timeline view; displaying the graphical data corresponding to the timeline view using a display device provided in the computing system; The method according to claim 1, further comprising.

11. The method according to claim 10, wherein the computing system is a terminal of a healthcare provider.

12. A computing system configured to generate a user interface for a patient's treatment history, the medical data of the patient corresponding to a plurality of patient visits to a healthcare provider, and stored program instructions, a memory configured to store; a processor operably connected to the memory; comprising, the processor executing the stored program instructions to be configured to generate graphical data corresponding to a timeline view, the graphical data being a first graphical element corresponding to a first diagnosis based on the medical data during the current patient visit among the plurality of patient visits, the first graphical element being a graphical indicator of the first diagnosis for the first medical condition, and further comprising at least one graphical sub - element, wherein the at least one graphical sub - element is related to a physiological parameter selected from the medical data, and the physiological parameter is related to the first diagnosis, a first graphical element, and a second graphical element corresponding to a second diagnosis based on the medical data of the patient during a first previous patient visit among the plurality of patient visits, wherein the second graphical element is a graphical indicator of the second diagnosis for a second medical condition, and further comprising at least one graphical sub - element, wherein the at least one graphical sub - element is related to a physiological parameter selected from the medical data, and the physiological parameter is related to the second diagnosis, a second graphical element, and a first graphical connector between the second graphical element and the first graphical element, the first graphical connector indicating the progression of time between the first previous patient visit and the current patient visit in the timeline view, a first graphical connector, and a computing system further comprising.

13. The processor is generating graphical data corresponding to a timeline slider of the timeline view, in response to user input to the timeline slider that expands the time range depicted in the timeline view, generating a third graphical element related to a third diagnosis in the medical data during a second previous patient visit that occurred before the first previous patient visit among the plurality of patient visits, wherein the third graphical element is a graphical indicator of the third diagnosis for a third medical condition, and at least one graphical sub - element, wherein the at least one graphical sub - element is related to a physiological parameter selected from the medical data, and the physiological parameter is related to the third diagnosis, at least one graphical sub - element, and generating a third graphical element further comprising a graphical indicator of a third prescribed treatment for the patient based on the third diagnosis, and Generating a second graphical connector between the second graphical element and the third graphical element, the graphical connector indicating the passage of time between the second previous patient visit and the first previous patient visit in the timeline view, generating a second graphical connector The computing system according to claim 12, further configured to perform. **Claim 14** The processor is Generating graphical data corresponding to a timeline slider of the timeline view, In response to user input to the timeline slider to move to an earlier time range of the timeline view, generating a third graphical element related to a third diagnosis in the medical data during a second previous patient visit that occurred before the first previous patient visit among the plurality of patient visits, the third graphical element being A graphical indicator of the third diagnosis for the third medical condition, and Further including at least one graphical sub-element, the at least one graphical sub-element being related to a physiological parameter selected from the medical data, the physiological parameter being related to the third diagnosis, generating a third graphical element Generating a second graphical connector between the second graphical element and the third graphical element, the graphical connector indicating the passage of time between the second previous patient visit and the first previous patient visit in the timeline view, generating a second graphical connector, and, Removing the first graphical element from the timeline view in response to the current patient visit being performed outside the earlier time range of the timeline view The computing system according to claim 12, further configured to perform. **Claim 15** The processor is The computing system according to claim 12, further configured to generate a third graphical element of a timeline indicating a first date of the first previous patient visit and a second date of the current patient visit. **Claim 16** The processor is Further configured to generate a third graphical element including a graphical indicator of the prescribed treatment prescribed during the previous patient visit of the first, wherein the first graphical connector is configured to indicate that the patient has received the prescribed treatment between the previous patient visit of the first and the current patient visit of the timeline view. A first sub-connector connecting the second graphical element of the previous patient visit of the first to the third graphical element, and a second sub-connector connecting the third graphical element to the first graphical element of the current patient visit. The computing system according to claim 12, further comprising:

17. The processor is Generating the third graphical element including a graphical indicator identifying that the prescribed treatment was manually selected by a healthcare provider The computing system according to claim 16, further configured as follows.

18. The processor is Generating the third graphical element including a graphical sub-element corresponding to a clinical memo associated with the prescribed treatment The computing system according to claim 16, further configured as follows.

19. The processor is Generating a third graphical element including a graphical indicator of a recommendation for a prescribed treatment related to the first diagnosis, Generating a second graphical connector between the first graphical element and the third graphical element, wherein the second graphical connector indicates that the recommendation for the prescribed treatment is related to the first diagnosis. Generating a second graphical connector The computing system according to claim 12, further configured to perform the above.

20. Further comprising a network transceiver, The processor is operably connected to the network transceiver, Generating the graphical data corresponding to the timeline view using the processor provided in the server computing system, and To display using a display device provided in a client computing system, the network transceiver is used to transmit the graphical data corresponding to the timeline view to the client computing system. The computing system according to claim 12, further configured to perform the above.

21. Further comprising a display device, The processor is operably connected to the display device, The graphical data corresponding to the timeline view is displayed on the display device, The computing system according to claim 12, further configured as above.

22. The computing system according to claim 21, wherein the computing system is a terminal of a healthcare provider.

23. A method for generating a user interface for a patient's treatment history, comprising: Receiving, using a processor, the medical data of the patient, wherein the medical data corresponds to the first patient visit to a healthcare provider; Generating, using the processor, graphical data corresponding to a timeline view, wherein generating the graphical data includes: Generating a first graphical element corresponding to a first diagnosis based on the medical data during the first patient visit, the first graphical element including: A graphical indicator of the first diagnosis for a first medical condition, and At least one graphical sub-element, the at least one graphical sub-element being related to a physiological parameter selected from the medical data, the physiological parameter being related to the first diagnosis.

24. Generating, using the processor, the graphical data corresponding to the timeline view includes: Generating a second graphical element including a graphical indicator of a recommendation for a prescribed treatment related to a first prescribed diagnosis; Further comprising generating a graphical connector between the first graphical element and the second graphical element, the graphical connector indicating that the recommendation for the prescribed treatment is related to the first diagnosis. The method according to claim 23.

25. Generating, using the processor, the graphical data corresponding to the timeline view, Generating a second graphical element of a timeline indicating the date of the first patient visit, The method according to claim 23, further comprising. **Claim 26** Generating, using the processor provided in the server computing system, the graphical data corresponding to the timeline view; Transmitting, using the processor and the network transceiver, the graphical data corresponding to the timeline view to the client computing system for display using a display device provided in the client computing system; The method according to claim 23, further comprising. **Claim 27** Generating, using the processor provided in the computing system, the graphical data corresponding to the timeline view; Displaying, using a display device provided in the computing system, the graphical data corresponding to the timeline view; The method according to claim 23, further comprising. **Claim 28** The method according to claim 27, wherein the computing system is a terminal of a healthcare provider.

Images