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

Abstract

A method for generating graphical data of a patient treatment history includes receiving medical data for a patient 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 the medical data during a current patient visit and a previous patient visit. Each graphical element includes a graphical indicator for a diagnosis of a medical condition and at least one graphical sub-element 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 time progression between patient visits in the timeline view.

Description

[0001] Priority Claim and Cross-Reference to Related Applications

[0002] This application claims priority to U.S. Provisional Patent Application No. 63 / 364,517, entitled “SYSTEM AND METHOD FOR ADAPTIVE GENERATION OF GRAPHICAL DATA OF A TREATMENT HISTORY” and filed on May 11, 2022, the entire contents of which are incorporated herein by reference. This application cross-references U.S. Provisional Patent Application No. 63 / 364,518, entitled “SYSTEM AND METHOD FOR ADAPTIVE GENERATION OF GRAPHICAL DATA OF PREDICTED DIAGNOSES” and filed on May 11, 2022, the entire contents of which are incorporated herein by reference. Background Art

[0003] People with diabetes (PwD), and particularly those with type 2 diabetes (T2D), most often receive care from a primary care physician (PCP), such as a general practitioner (GP) or family medicine physician (FM). PCPs are often overwhelmed by patient volume, as they see not only patients with T2DM, but also those with many other chronic conditions. With a typical appointment lasting less than 15 minutes, PCPs experience a significant cognitive burden with regard to disease management and optimal treatment recommendations. These factors contribute to the phenomenon of clinical inertia, which is a delay in appropriately intensifying treatment for better disease management. Clinical inertia, in turn, results in high health economic costs and negatively impacts the quality of life of PwD.

[0004] Therefore, there is a need for clinical decision support (CDS) tools that assist PCPs and other healthcare providers (HCPs) in selecting appropriate treatments for the type 2 diabetes population. When integrated into their clinical workflow, CDS tools that take into account patient characteristics can help HCPs make better personalized treatment decisions, thereby improving clinical, patient-reported, and economic outcomes. Although the medical community has recognized clinical guidelines for diabetes treatment from organizations such as the American Diabetes Association (ADA) and the European Association for the Study of Diabetes (EASD), even these clinical guidelines for treatment transitions in T2D can be difficult for PCPs to follow or apply due to the large amount of patient data. In addition, the potential course of recommended treatments can be complex and constantly changing over several years, which poses further difficulties in the ability to track disease progression and provide proactive 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 burden would be beneficial. Summary of the invention

[0005] The adaptive clinical decision support user interface (UI) enables healthcare providers (HCPs) to provide efficient care journey management for patients with diabetes. The UI contains information graphics for each visit that are dynamically updated with relevant physiological values, which are used to drive the underlying guidance logic to form diagnostic and treatment recommendations. Comorbidities and relevant physiological markers can also be tracked to further adjust care according to recognized guidelines, which may recommend modified treatments, initiate advanced treatment services, or call disease risk progression algorithms directly from the interface. The user interface reduces the cognitive burden of exploring complex treatment pathways based on the current disease state.

[0006] In one embodiment, a method for generating a user interface for a patient's treatment history has been developed. The method includes receiving, with a processor, medical data for a patient, the medical data corresponding to a plurality of patient visits to a healthcare provider, and generating, with the processor, graphical data corresponding to a timeline view of the plurality of patient visits. The generation of 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 in the plurality of patient visits, the first graphical element further including a graphical indicator for a first diagnosis of a first medical condition and at least one graphical sub-element, the at least one graphical sub-element being associated with a physiological parameter selected from the medical data, the physiological parameter being associated with the first diagnosis. The method further includes generating a second graphical element corresponding to a second diagnosis based on the medical data for the patient during a first previous patient visit in the plurality of patient visits, the second graphical element further including a graphical indicator for a second diagnosis of a second medical condition and at least one graphical sub-element, the at least one graphical sub-element being associated with a physiological parameter selected from the medical data, the physiological parameter being associated with the second diagnosis. The method further includes generating a first graphical connector between the second graphical element and the first graphical element, the first graphical connector indicating a temporal progression between the first previous patient visit and the current patient visit in the timeline view.

[0007] In another embodiment, a computing system configured to generate a user interface for a patient's treatment history has been developed. The computing system includes a memory and a processor operably connected to the memory. The memory is configured to store: medical data for the patient, the medical data corresponding to multiple 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, the graphical data further including a first graphical element corresponding to a first diagnosis based on medical data during a current patient visit in the multiple patient visits, the first graphical element further including a graphical indicator for a first diagnosis of a first medical condition and at least one graphical sub-element, the at least one graphical sub-element being associated with a physiological parameter selected from the medical data, 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 medical data for the patient during a first previous patient visit in the plurality of patient visits, the second graphical element further comprising 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 associated with a physiological parameter selected from the medical data, 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 a temporal progression between the first previous patient visit and the current patient visit in the timeline view.

[0008] In another embodiment, a method for generating a user interface for a patient's treatment history has been developed. The method includes receiving, with a processor, medical data for the patient, the medical data corresponding to an initial patient visit to a healthcare provider, and generating, with the processor, graphical data corresponding to a timeline view. The generating of the graphical data further includes generating a first graphical element corresponding to a first diagnosis based on the medical data during the initial patient visit, the first graphical element further 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 associated with a physiological parameter selected from the medical data, the physiological parameter being related to the first diagnosis. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] To facilitate identification of the discussion of any particular element or act, the most significant digit(s) in a reference number refers to the figure number in which the element is first introduced.

[0010] Figure 1 is a schematic diagram of a computer system configured to generate graphical data of a medical timeline for a patient in an adaptive user interface for a healthcare provider.

[0011] Figure 2It is for Figure 1 A block diagram of a method of operation of a system.

[0012] Figure 3 is a depiction of a timeline view combined with graphical data for a patient's treatment history.

[0013] Figure 4 Describes the larger time range in the timeline view Figure 3 A depiction of a timeline view.

[0014] Figure 5 are shifted to depict an earlier time range in the patient's visit history in the timeline view Figure 3 A depiction of a timeline view.

[0015] Figure 6 is a depiction of a simplified timeline view during an initial patient visit. DETAILED DESCRIPTION

[0016] These and other advantages, effects, features and purposes may be better understood from the following description. In the specification, reference is made to the accompanying drawings which form a part hereof and in which are shown by way of illustration and not limitation, embodiments of the inventive concept. Throughout the several views of the drawings, corresponding reference numerals indicate corresponding parts.

[0017] Although the inventive concept is susceptible to various modifications and alternative forms, its exemplary embodiments are shown by way of example in the accompanying drawings and are described in detail herein. However, it should be understood that the description of the following exemplary embodiments is not intended to limit the inventive concept to the specific form disclosed, but on the contrary, it is intended to cover all advantages, effects and features that fall within its essence and scope, as defined by the embodiments described herein and the following embodiments. Therefore, in order to interpret the scope of the inventive concept, reference should be made to the embodiments described herein and the following embodiments. Therefore, it should be noted that the embodiments described herein may have advantages, effects and features that are useful for solving other problems.

[0018] The devices, systems and methods will now be described more fully hereinafter with reference to the accompanying drawings, in which some, but not all, embodiments of the inventive concept are shown. Indeed, these devices, systems and methods may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will satisfy applicable legal requirements.

[0019] Likewise, many modifications and other embodiments of the devices, systems, and methods described herein will occur to those skilled in the art having the benefit of the above description and the teachings presented in the associated drawings. Therefore, it should be understood that the devices, systems, and methods are not limited to the specific embodiments disclosed, and variations and other embodiments are intended to be included within the scope of the embodiments. Although specific terms are employed herein, these terms are used only in a general and descriptive sense and not for purposes of limitation.

[0020] Unless otherwise defined, all scientific and technological terms used herein have the same meaning as commonly understood by those skilled in the art to which the present disclosure belongs. Although methods and materials similar or equivalent to those described herein can be used in the practice or testing of the present method, preferred methods and materials are described herein.

[0021] In addition, referring to an element by the indefinite article "a" or "a kind" does not exclude the possibility of the presence of more than one element, unless the context clearly requires that there is and there is only one element. Therefore, the indefinite article "a" or "a kind" usually means "at least one / kind". Similarly, the terms "have", "comprise" or "include" or any arbitrary grammatical variation thereof are used in a non-exclusive manner. Therefore, these terms can refer to the situation where there are no other features in the entity described in this context except the features introduced by these terms, or the situation where there are one or more other features. For example, expressions such as "A has B", "A contains B" and "A includes B" can refer to the situation where there are no other elements in A except B (i.e., A is only and exclusively composed of B), or the situation where there are one or more other elements in A except B, such as element C, element C and D or even other elements.

[0022] As used herein, the term patient 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 comorbidities associated with diabetes. In specific embodiments described herein, a PwD is a patient of a healthcare provider (HCP), and references to a PwD and a patient are used interchangeably herein. While specific embodiments described herein relate to improving a user interface for a patient's treatment history for an HCP treating a PwD, the systems and methods described herein are not limited to treating a PwD and can be used to implement an improved user interface for treating other diseases and medical conditions, and in particular, chronic medical conditions requiring long-term treatment.

[0023] As used herein, the term "physiological parameter" refers to any quantifiable aspect of PwD physiology measured as part of providing medical data to diagnose a new medical condition or to track the status of a previously diagnosed medical condition. A non-limiting list of physiological parameters of interest in the treatment of diabetes and diabetic comorbidities includes body mass index (BMI), blood pressure (BP), blood glucose, glycosylated hemoglobin (HbA1c), blood ketones, and estimated glomerular filtration rate (eGFR).

[0024] As used herein, the term "medical data" is meant to include 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 ​​for the PwD. Medical diagnostic data optionally includes relevant genetic data, phenotypic data, demographic data, and socioeconomic data related to the PwD. Medical data includes records of previously prescribed medications or other medical treatments prescribed to the PwD during previous patient visits. During the 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 treatments or manually select different courses of action for the PwD.

[0025] As used herein, the term "prescribed treatment" refers to any medical diagnostic test, medical diagnostic or prognostic algorithm, medical procedure, medical therapy, medication, diet and lifestyle modification, or other recommended course of action issued by the HCP to the PwD during the treatment history for the PwD. Specifically, with respect to medications, the term "prescribed" herein encompasses both over-the-counter and prescription medications.

[0026] As used herein, the term "graphics data" refers to any form of encoded data that a computing device uses to generate visually perceptible output using a display device, printer, or other output device, including text, geometric features, pictures, icons, textures, and the like. Graphics data in different forms include both static image data and moving images such as animations and videos. 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 ​​in an image, wherein a display device generates an output image formed by the array of pixel values. Rasterized image data can be compressed using JPEG, PNG, WEBP, or other suitable compression formats for static images, and can also be compressed using 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 encode declarative parameters that describe the shape, color, arrangement, and other details of an image that a computing device processes to reproduce the image, and include Scalable Vector Graphics (SVG), graphics generated from Cascading Style Sheets (CSS) documents, Portable Document Format (PDF), and other suitable vector graphics formats. Procedural graphics data includes data encoded as mandatory command data for a processor to execute to dynamically generate graphics data. Examples of procedural graphics data include encoded command parameters for controlling JavaScript, WebAssembly, WebGL, or other scripting languages ​​to draw graphics as HTML used in publicly available web browsers. <canvas>A portion of an element, or data encoded in Postscript language rendered by a computing device using a Postscript rendering engine. In addition, markup language formats such as Hypertext Markup Language (HTML), Extensible Markup Language (XML) or suitable markup languages ​​can be used to format the arrangement of one or more groups of graphic data forming a graphic element to generate a timeline view and other graphics described herein. In some configurations, a single computing system generates graphic data and performs a process of rendering the graphic data to a display device for human users to view the graphics. As described in further detail below, in other configurations, a first computing system generates graphic data and transmits the graphic data to one or more computing systems, which perform the task of rendering the graphics to one or more display devices so that one or more human users can view the graphics.

[0027] Figure 1 A system 100 is depicted for providing clinical decision support information to a HCP using an adaptive user interface as described herein. The 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.

[0028] Figure 1 The CDS system 102 utilizes one or more computing devices to perform the functions described herein, and the one or more computing devices include those depicted as Figure 1 The CDS processor 104 includes 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. The CDS processor 104 is operably connected to the CDS memory 106 and the network transceiver 116. The CDS memory 106 includes one or more volatile data storage devices such as static and dynamic random access memories (RAMs) and one or more non-volatile data storage devices such as magnetic, solid-state, and optical storage drives. During operation, the CDS processor 104 reads data and writes data to the CDS memory 106 to execute stored program instructions and store data including medical data received from the HCP terminal 126 and the EHR service 118 and generated graphical 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, to transmit and receive EHR data using the EHR service 118, and to transmit graphical data for a timeline view user interface of the PwD's treatment history 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 to transmit graphical data for the PwD's treatment history to the PWD device 136.

[0029] In the CDS system 102, the CDS memory 106 stores CDS software 108, a diagnostic database 110, PwD medical data 112, and graphical data 114. The CDS software 108 includes stored program instructions that the CDS processor 104 executes to perform clinical support functions and generate graphical data corresponding to a timeline view of one or more diagnoses for a PwD and one or more prescribed treatments for treating the PwD in 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 to the CDS system, and to enable the CDS system 102 to transmit the generated graphical data described herein to the HCP terminal 126. The diagnostic database 110 includes a stored set of logical rules that the CDS system 102 uses to generate a diagnosis for the PwD based on the medical data for the PwD. In a specific configuration, the diagnostic database 110 encodes the guidelines from the American Diabetes Association (ADA) diabetes medical care standards. Alternative configurations use different medical guidelines or other algorithms to generate diagnosis and prescribed treatment. Although the CDS system 102 uses the diagnostic database 110 to generate graphical elements that display diagnosis and prescribed treatment in an automated manner during the operation of the system 100, the HCP optionally uses the HCP terminal 126 to overwrite the suggested diagnosis or action plan suggestions. The PwD medical data 112 includes any relevant medical data for the PwD during the current patient visit and historical medical record data including medical data for one or more previous patient visits. The PwD medical data 112 optionally includes the PwD medical data received by the CDS system 102 from the EHR service 118, the PwD medical data has historical medical data stored in the electronic health record for the PwD and data received from external laboratory tests, home diagnostics (such as field and continuous glucose meter devices), and medical data provided to the CDS system 102 by the HCP terminal 126 during the patient visit. In addition, during operation, the CDS system 102 optionally transmits updated medical data for the PwD to the EHR service 118 to reflect updated measurements to physiological parameters, diagnoses, or to record prescribed medications or other medical treatments received by the PwD during the course of treatment. The graphical data 114 includes a graphical representation of a timeline view user interface of a treatment history for the PwD during a series of one or more patient visits based on the PwD medical data 112. For example, the graphical data 114 forms a timeline view that includes graphical elements and sub-elements to depict one or more diagnoses and related physiological parameters for each diagnosis, prescribed treatments, prescribed medications, diagnostic tests, and graphical connectors linking the graphical elements in the timeline view.In some configurations, the graphical 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 for a PwD based on the PwD medical data 112 .

[0030] Figure 1 The EHR service 118 provides medical data for PwDs to the CDS system 102 in the form of EHR. Figure 1 In the exemplary embodiment of , the EHR service is a networked computing service that includes a digital processor 120, a memory 122 that stores EHR data 124 for the PwD. The EHR data 124 is a digital record encoded in a standard format, such as the Fast Healthcare Interoperability Resources (FHIR) format, a version of the Health Level Seven International (HL7) format, or another suitable electronic health record format. Figure 1 In an embodiment of the present invention, 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 a unified system. In an actual embodiment, the EHR data 124 for the PwD may include data received from multiple data sources, including external diagnostic testing services, HCPs operating the HCP terminal 126, the CDS system 102, and EHR data from other HCPs (such as medical specialists treating the PwD for other medical conditions and comorbidities).

[0031] Figure 1 The HCP terminal 126 is a desktop or laptop personal computer (PC), tablet computer, smartphone, or other suitable client computing device of the HCP, which other suitable client computing device includes a terminal processor 128, 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 a timeline view of multiple patient visits for the PwD as the PwD receives treatment in a series of visits with the HCP. In some configurations, the HCP also uses the HCP terminal 126 to communicate with the PWD device 136 between patient visits, or for remote patient visits where the HCP is providing telemedicine services to the PwD. Figure 1 In an embodiment of the present invention, the HCP terminal 126 executes stored program instructions in 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 a web browser software that acts as a client to 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 a display device 134 to generate a visual output of the graphical data 114, which the CDS system 102 generates and transmits to the HCP terminal 126. The display device 134 is, for example, a flat panel display screen or other electronic display device, although 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 enter data and modify the timeline view, as described in further detail below, while in other configurations, the HCP terminal 126 incorporates a combination of a mouse, keyboard, voice input device, or other input device [not shown] for receiving HCP input.

[0032] Figure 1 The PWD device 136 of the PWD is another desktop or laptop PC, a tablet computer, a smart phone, or other suitable client computing device of the PWD, which includes a device processor 138, a device memory 140 storing 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 an on-site or continuous blood glucose meter, a fitness tracking device such as a smart watch, or other medical device. The PWD device 136 is optionally configured to enable the PWD to conduct a telemedicine patient visit with the HCP via the HCP terminal 126 using video conferencing software and other telemedicine software known in the art and not described in further detail herein. In some configurations, the CDS system 102 transmits the generated graphical data of the timeline view user interface for 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 retransmits the graphical data of the timeline view of the PWD's treatment history to the PWD device 136 during the telemedicine patient visit.

[0033] Figure 2 2 is a block diagram of a process 200 for the operation of a CDS system for generating a graphical timeline view user interface of a treatment history and recommended prescribed therapies for a diagnosed condition of a PwD during a series of one or more patient visits. Although the process 200 may be performed at any time, for illustrative purposes, the process 200 is described as occurring during a patient visit to generate a graphical timeline view of a current patient visit and one or more previous patient visits (if such previous patient visits have occurred). Figure 1 The process 200 is described with reference to the system 100 of FIG. 1 , and reference to the process 200 performing a function or action refers to the operation of a processor (such as the CDS processor 104 in the CDS system 102) executing stored program instructions (such as the CDS software 108) to perform the function or action.

[0034] The process 200 begins when the CDS system 102 receives PwD medical data for at least one patient visit (block 202). In the system 100, the processor 104 in the CDS system 102 receives medical data from one or more sources, including but not limited to the EHR service 118, the HCP terminal 126, and the PWD device 136 in some cases. Specifically, the EHR service 118 provides medical data for previous patient visits including previous diagnoses, prescribed medications and medical treatments, a history of physiological parameter data measurements for the PwD, and optionally socioeconomic and demographic data related to the PwD. During the patient visit, the HCP terminal 126 transmits physiological parameters and other medical data to the CDS system 102, optionally 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, the CDS system 102 may receive medical data regarding blood tests or other diagnostic tests received by the PwD at an external diagnostic laboratory prior to the patient visit, either directly from the diagnostic laboratory's computing system, via the EHR service 118, or from the HCP terminal 126. As described above, the CDS system 102 stores the received PwD medical data 112 in the CDS memory 106.

[0035] The process 200 continues when the CDS system 102 identifies the physiological parameters that have the greatest correlation with the diagnosis during each patient visit (block 204). Figure 1 In an embodiment of the present invention, the CDS processor 104 uses the diagnostic database 110 to identify physiological parameters in the PwD medical data 112 that have the greatest correlation with each diagnosis in a series of one or more patient visits. For example, if the patient visit includes a diagnosis that the PwD is both obese and has uncontrolled HbA1c, which indicates the onset of type 2 diabetes, the CDS processor 104 uses the diagnostic database 110 to identify physiological parameters with the highest correlation with these diagnoses, such as the body mass index (BMI) and measured HbA1c level for the PwD that are related to obesity. In many cases, the PwD medical data 112 includes physiological parameters and other information that are not directly related to the diagnosis, and the CDS processor 104 filters such data from the timeline view, although the HCP can of course access the complete PwD medical data 112 via a conventional user interface if desired.

[0036] The process 200 continues when the CDS system 102 generates a graphical element for each patient visit and at least one graphical sub-element for an identified physiological parameter associated with one or more diagnoses in each patient visit (block 206). The graphical element and graphical sub-element provide a graphical indicator of the physiological parameter data that led to the diagnosis and the prescribed treatment. A graphical indicator refers to any type of graphical data in a timeline view that conveys specific information about medical data for a PwD, a prescribed treatment for a PwD, or a recommendation for a prescribed treatment for 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 graphical data for the graphical sub-element within the boundaries of a parent graphical element, or otherwise associates each graphical sub-element with the parent graphical element. The graphical element and sub-element provide a clear indication of the relationship between the graphical element for a patient visit and one or more graphical sub-elements related to the patient visit.

[0037] Figure 3 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, is depicted. In timeline view 300, graphical elements 304 and 316 are implemented as rectangular graphical elements that each include text to provide information related to each patient visit, including a graphical indicator of the patient visit number (e.g., first, second, third, etc.), the current diagnosis, and the current medication or therapy prescribed for the PwD (if any). Figure 3 One example of a timeline view is depicted, with graphical element 304 including a textual graphical indicator indicating that a second PwD was seen and that the PwD was diagnosed as obese with uncontrolled HbA1c. Graphical sub-elements 308a and 308b are depicted as circles subdivided into two semicircular areas, with the top area listing physiological parameters related to diagnosis and treatment, and the bottom area listing quantified values ​​of the physiological parameters. Figure 3 , sub-element 308a depicts HbA1c having a value of 7.1, which is an elevated value supporting a diagnostic prediction that the patient has diabetes. Sub-element 308b depicts a body mass index (BMI) physiological parameter associated with an obesity diagnosis. In some configurations, the graphical data of each physiological parameter graphical sub-element provides the HCP with additional information in addition to the quantitative value of the physiological parameter. For example, in some configurations, the physiological parameter data is displayed using color-coded text or a color-coded graphic in the graphic sub-element to indicate whether the physiological parameter is within or outside of the range for a particular PwD. Using the HbA1c physiological parameter as an example, green may indicate an HbA1c value that is considered normal for a healthy individual, yellow may indicate an elevated HbA1c for non-insulin dependent diabetes, and red may indicate a further elevated HbA1c, which indicates the need for insulin therapy. In some configurations, the graphical sub-element of the physiological parameter also includes an arrow or other graphical indicator showing the trend of the physiological parameter over time since a previous patient visit, such as an upward or downward arrow indicating an upward or downward trend in HbA1c level or a change in another related physiological parameter. In certain configurations, the graphical indicator of the physiological parameter includes a chart, icon, or other non-textual graphical indicator that can be easily interpreted by the HCP to assess the condition of the PwD.

[0038] The timeline view 300 further depicts a second patient visit and a third patient visit graphical element 316 that is spatially offset from the graphical element 304 in the timeline view and that is linked by a first graphical connector 310a / 310b that indicates a temporal progression between the patient visits along the timeline view. Figure 3 , graphical element 316 for the third patient visit represents the current patient visit, while the second patient visit in graphical element 304 represents the most recent previous patient visit, and in some embodiments, the default timeline view depicts the current patient visit and the most recent previous patient visit (where applicable). For treatment histories that include one or more previous patient visits that are not displayed in the default timeline view, timeline view 300 optionally includes a timeline view starting with the earliest displayed patient visit (which is Figure 3 ) to provide additional earlier patient visits present in the treatment history. Graphic element 316 further includes a graphical indication that the PwD is receiving medication therapy and a diagnosis of renal dysfunction, which is a known complication of diabetes. Graphic element 316 further includes graphical sub-elements 318a and 318b. Graphic sub-element 318a indicates an HbA1c value for the patient at the third patient visit, which is the same physiological parameter as sub-element 308a, but has a potentially different value (7.3 vs. 7.1) based on changes in the patient's physiology. Graphic sub-element 318b indicates an estimated glomerular filtration rate (eGFR) value, which is a physiological parameter that is highly correlated with a diagnosis of renal dysfunction. Thus, graphical element 316 includes a graphical sub-element for at least one physiological parameter (eGFR) that is not present in graphical element 304 for the earlier patient visit, and conversely, graphical element 304 includes a graphical sub-element for at least one physiological parameter (BMI) that is not present in graphical element 310.

[0039] As described above, process 200 identifies and generates graphical sub-elements of physiological parameters that are most relevant to the diagnosis in each patient visit, and in some cases, the most relevant physiological parameters selected change based on changes in the underlying condition of the PwD. Thus, process 200 generates an adaptive display of information that emphasizes physiological parameters with the highest relevance during different patient visits in the PwD's medical history, which enables the HCP to evaluate and treat the PwD efficiently and with reduced cognitive load compared to reviewing all physiological parameters for the PwD in a traditional EHR or other health record. For example, Figure 3 Further depicted are non-limiting examples of alternative graphical elements 328 and 338 generated by the CDS system 102 during process 200 based on different potential diagnoses and related physiological parameters for the PwD that may occur for different disease progressions. Graphical element 328 corresponds to a diagnosis that the PwD should begin insulin because the HbA1c value depicted in graphical sub-element 330 has increased significantly from a previous patient visit and the existing metformin prescription is no longer effective. Graphical element 340 corresponds to a diagnosis that the PwD should continue to receive non-insulin medications in response to a slight increase in HbA1c (graphic sub-element 342a) and unchanged BMI (graphic sub-element 342b). Figure 3 Graphical elements 328 and 340 with corresponding graphical sub-elements are depicted in dashed lines because, in this example, only a single displayed graphical element 316 corresponds to the assessed condition of the PwD during the patient visit. In some embodiments, the HCP can modify the diagnosis for the current patient visit via, for example, a drop-down list box or other user interface element to manually select a different diagnosis and treatment option group for the PwD. The CDS system 102 updates the graphical sub-elements as needed to generate graphical data for the most relevant physiological parameters related to the selected diagnosis.

[0040] Reference again Figure 2 During process 200, the CDS processor 104 identifies the prescribed treatments (if any) for the PwD in the PwD medical data 112 (block 208), and generates a graphical element for each prescribed treatment in the timeline view (block 210). 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 medical history for the PwD. Because prescribed treatments are typically issued during a patient visit and subsequently provided to the PwD after the patient visit, the CDS processor 104 generates a timeline view in which the graphical element for the prescribed treatments is located midway between the graphical elements for the patient visits, wherein the graphical connector linking the patient visits is further subdivided into two sub-connectors that also depict the prescribed treatments in the timeline view.

[0041] refer to Figure 3 , a graphical element 312 depicts a previously prescribed treatment, such as a medication prescription for metformin, including a label that the prescribed treatment is a medication and an identifier for the type of medication. In an alternative embodiment, the graphical element for the prescribed medication depicts additional details, such as a dosage level and regimen or other relevant information about the medication. The first graphical connector includes a first sub-connector element 310a that links the graphical element 304 for the previous patient visit to the graphical element 312 for the prescribed treatment, and a second sub-connector element 310b that connects the graphical element 312 for the prescribed treatment to the graphical element 316 for the current patient visit to provide a clear indication in the timeline view 300 of when the prescribed treatment occurred.

[0042] As described herein, during the process 200, the HCP optionally selects to prescribe a treatment that deviates from one or more suggested prescribed treatments provided by the CDS system 102 in the timeline view 300. If the HCP issues another prescribed treatment, the CDS system 102 stores a data identifier in association with the manually selected prescribed treatment to identify that the prescribed treatment was manually selected in the PwD medical data 112. When the CDS system 102 later generates an updated timeline view 300 including the manually selected prescribed treatment, the CDS processor 104 generates a graphical element with a specific graphical indicator that identifies that the HCP manually selected the prescribed treatment instead of selecting from one of the suggested prescribed treatments. For example, the CDS processor 104 generates a graphical element for the prescribed treatment using a specific color or graphical icon to identify that the HCP manually selected the prescribed treatment, while using a different color or other graphical indicator for the graphical element for the prescribed treatment that conforms to the suggestion from the CDS system 102.

[0043] During patient visits, the HCP optionally records clinical notes related to the diagnosis and prescribed treatment. Figure 3 In an embodiment of the graphical element 312, the graphical element 312 includes a graphical sub-element for a clinical note 314, which is depicted as an icon that the HCP can select to display a previously recorded clinical note for a patient visit. The clinical note includes any data recorded by the HCP related to the patient visit and the prescribed medical treatment, such as the reason for prescribing the treatment, reminders for subsequent patient visits. During operation, the HCP optionally selects the graphical sub-element for the clinical note 314 to generate a tooltip or pop-up window displaying the text of the clinical note for review. The HCP can close the tooltip or pop-up window to return to the display of the timeline view 300 to ensure that the HCP can utilize the timeline view 300 with minimal interference.

[0044] Reference again Figure 2 , the process 200 continues when the CDS processor 104 identifies triggers for suggested prescribed treatments (if any) for the PwD based on the physiological data in the PwD medical data 112 for the current patient visit and the criteria in the diagnostic database 110 (block 212). If one or more prescribed treatments are identified, the CDS processor 104 generates a graphical element for triggering each suggested prescribed treatment in the timeline view (block 214). Each trigger graphical element includes a graphical indicator for a suggestion for a prescribed treatment associated with the diagnosis in the first patient visit. In some configurations, more than one trigger is generated if multiple prescribed treatments are applicable to the PwD. The 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 trigger graphical elements for the suggested prescribed therapies enable the HCP to select a prescribed therapy in an efficient manner, although the HCP may decline to select one or more of these triggers, or may choose to prescribe a therapy that is different than the recommendation generated by the 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 for the suggested prescribed therapies, the CDS system 102 stores a record of the selected prescribed therapies in the PwD medical data 112, and optionally transmits the prescribed therapy data to the EHR service 118 to maintain a record of the prescribed therapies.

[0045] refer to Figure 3 , the timeline view 300 includes trigger graphic elements 320 and 322 corresponding to the current patient visit graphic element 316. Graphic element 320 includes a trigger for a change in existing medication therapy, which in this case is a recommendation to stop the existing metformin regimen. Specifically, to identify a trigger for stopping therapy, the CDS processor 104 identifies that therapy is ongoing based on the PwD medical data 112, and identifies a change in therapy based on the diagnosis (which is in Figure 3 ) uses the diagnostic database 110 to identify that stopping the therapy is a recommended treatment option. Graphic element 322 is a trigger for a chronic kidney disease (CKD) detection algorithm or clinical test that provides the HCP with additional information about the diagnosed renal dysfunction. In the timeline view 300, graphic connectors 324 and 326 link the patient visit graphic element 316 to trigger graphic elements 320 and 322, 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 in the graphic element 320 to activate a separate user interface (not shown) for a prescribed drug for the PwD to stop the metformin prescription. Similarly, the HCP selects a hyperlink in the graphic element 322 to open a website or other user interface to command a CKD detection algorithm or clinical test for the PwD. After selecting one or more of the triggers or selecting a prescribed therapy that is different than the suggested prescribed therapy trigger, the HCP optionally enters a clinical note for the patient visit.

[0046] As described above, the CDS system 102 generates graphical data in the timeline view 300 in an adaptive manner based on different potential diagnoses for the PwD. Figure 3 , trigger graphical elements 332 and 338 represent, respectively, for a PwD with a recommendation to start insulin therapy based on the diagnosis of graphical element 328, discontinuing the metformin regimen and triggering an insulin titration protocol. Graphic connectors 334 and 336 connect patient visit graphical element 328 to trigger graphical elements 332 and 338, respectively. Similarly, trigger element 344 indicates a recommendation for treatment with a prescribed SGLT 2 inhibitor, and graphical connector 346 connects patient visit graphical element 340 to trigger graphical element 344. As described above with reference to graphical elements 328 and 340, the CDS processor 104 only generates graphical elements 332 and 338 if the diagnosis matches the diagnosis of uncontrolled HbA1c indicating insulin dependence in graphical element 328, and the CDS processor 104 only generates graphical element 344 if the diagnosis matches the diagnosis of elevated HbA1c controllable by non-insulin medication in graphical element 338.

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

[0048] refer to Figure 3 , timeline graphical element 302 includes a display of the dates during which displayed graphical elements 304 and 316 for patient visits occurred. Figure 3 In the specific example of FIG. 3 , the timeline view 302 depicts the year 2021 in a rectangular area with the abbreviated month names (January, February, March, ...) of 2021 arranged linearly in the timeline. The timeline view 300 aligns the graphical elements of the patient visits with the date of each visit, where graphical element 304 corresponds to the patient visit in March 2021 and graphical element 316 corresponds to the visit in September 2021. The timeline graphical element 302 also highlights the entries for March and September in bold to emphasize the date of each visit. Figure 3 Depicted is a level of precision for the date of each patient visit with year and month for PwDs who have few HCP visits per year. For patients who require more frequent patient visits, the timeline graphical element presents more precise date information including the day and optionally the time of day for each patient visit.

[0049] When the timeline view is generated in block 216 of the process 200, the CDS system 102 transmits the generated graphical data for the timeline view user interface to the client HCP terminal 126 via the network 146 using the CDS processor 104 and the network transceiver 116. The HCP terminal 126 receives the graphical data, and the terminal processor 128 executes the terminal software 132, such as a web browser or other client software, to generate a rendered user interface with a visual depiction of the timeline view using a display device 134 provided in the HCP terminal 126. The HCP interacts with the user interface using the HCP terminal 126, and as described below, the HCP optionally provides input to the HCP terminal to update the timeline user interface, which the CDS system 102 receives via the network 146 and processes to provide an updated set of graphical data for the updated timeline view to the HCP terminal 126. Additionally, in some configurations, the CDS system 102 optionally transmits the generated graphical data for the timeline view user interface to the PWD device 136 for direct display to the PWD using the display device 144. Although for illustrative purposes, the system 100 is embodied as a networked system in which the CDS system 102 is connected to the HCP terminal 126 via the network 146, in another configuration, a single computing system performs the operations of both the CDS system 102 and the HCP terminal 126. In this configuration, a processor in the single computing system generates graphical data corresponding to a timeline view of a patient visit, and operates a display device provided in 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 the HCP terminal 126, which is further reconfigured to host the CDS software 108, the diagnostic database 110, the PwD data 112, and the graphical data 114 in addition to the terminal software 132.

[0050] refer to Figure 2 and Figure 3 , the HCP optionally uses the timeline slider to adjust the timeline view to increase or decrease the time range in the timeline view 300 or to move the time range in the timeline view 300 (block 218). If the CDS system 102 receives input from the HCP terminal 126 to adjust the timeline view, the CDS system 102 generates graphical data for the updated timeline view that depicts the time range specified in the input from the HCP terminal 126 (block 220). Figure 3 As depicted, the timeline graphical element 302 further includes a timeline slider 306. The timeline slider 306 overlays the time range presented in the timeline view 300, which enables the HCP to adjust the timeline view 300 by providing input via the HCP terminal 126. In one mode of operation, the timeline slider 306 receives 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 depicted in the timeline slider 306 to increase or decrease the size of the time range depicted in the timeline view, and Figure 4 The result of this operation is depicted in more detail in FIG. 30. In another operation, the HCP performs a click and drag operation to move the timeline slider 306 to move the time range depicted in the timeline view without increasing or decreasing the size of the time range, and Figure 5 The results of this operation are depicted in greater detail. In one configuration, the HCP adjusts the size of the time range in the timeline view or moves the view similarly based on a calendar date, while 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 depicted in the timeline view adds one or more patient visits to or removes one or more patient visits from the timeline view rather than adding or removing a specific number of months or years to the timeline view, while moving the timeline view updates the display of patient visits by one or more patient visits forward or backward in time rather than moving the timeline view a specific number of months or years.

[0051] Figure 4 An adjusted timeline view 400 is depicted to include a larger time range in response to input from the HCP, which expands the time range depicted in the timeline view during the process 200. Specifically, the timeline view 400 includes input from the HCP. Figure 3 4. The graphical element 300 of the timeline view 300 of the PwD further includes a graphical element 402 corresponding to a first patient visit for the PwD. Similar to graphical elements 304 and 316, graphical element 402 includes a graphical depiction of a diagnosis ("Obesity") for the first patient visit and two graphical sub-elements 404a and 404b depicting HbA1c (404a) and BMI (404b). The graphical connector 348 between graphical elements 402 and 304 indicates the temporal progression from the first patient visit depicted in graphical element 402 to the second patient visit depicted in graphical element 304. The CDS processor 104 generates the graphical data corresponding to the first patient visit in 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. In addition, the CDS processor 104 updates the timeline graphical element 302 to depict the adjusted time range, Figure 4 In the example of , the adjusted time range includes September 2020 to September 2021. Figure 4 In the example of , the timeline graphic element 302 includes identifiers for the years 2020 and 2021, and further includes a simplified detail list of only the months in which the patient visits occurred to provide the HCP with relevant date information for each patient visit. Figure 4 An operation of increasing the time range depicted in the timeline view 400 is depicted, but those skilled in the art will appreciate that similar operations may also decrease the time range depicted in the timeline view.

[0052] Figure 5 An adjusted timeline view 500 is depicted, which the CDS processor 104 generates in response to input from the HCP to move the timeline view to an earlier time range in the treatment history for the PwD. The timeline view 500 includes graphical elements and graphical sub-elements for the first patient visit and the second patient visit depicted above, including the graphical element 402 and graphical sub-elements 404a and 404b for the first patient visit and the graphical element 304 and graphical sub-elements 308a and 308b for the second patient visit. The graphical connector 348 indicates the time progression between the first patient visit and the second patient visit, and the timeline view 302 depicts the adjusted timeline with the overlapped portions being the years 2020 and 2021, with the highlighted months indicating the dates of each patient visit. The timeline view 500 also includes a graphical element 312 corresponding to the prescribed treatment from the second medical visit and graphical subconnectors 310a and 310b indicating additional treatment history in addition to the second patient visit. To generate the timeline view 500, the CDS processor 104 removes the graphical element 316 corresponding to the current patient visit from the timeline view because the current patient visit occurs outside of the earlier time range in the timeline view 500.

[0053] Those skilled in the art will recognize that the processing of steps 206-216 may occur in a different order than described above or may occur concurrently. In addition, the timeline view depicted herein is arranged in a left-to-right format representing earlier to more recent times, but alternative configurations may orient the timeline in a right-to-left format or vertically from top to bottom or bottom to top format. In addition, alternative configurations of process 200 may include different visual formats and arrangements of the graphical elements, graphical sub-elements, and graphical connectors depicted herein.

[0054] Although the process 200 is described in conjunction with a patient treatment history that includes multiple patient visits for illustrative purposes, the CDS system 102 and process 200 also generate a user interface with a simplified timeline view for an initial patient visit, where only a single patient visit is depicted in the timeline view using the same processing steps described above. Figure 6 A timeline view 600 of an initial patient visit for a PwD patient who has been diagnosed with a form of diabetes or is considered at risk for diabetes is depicted. The timeline view 600 includes a graphical element 602 having an indication that the PwD is diagnosed with uncontrolled HbA1c, obese, and having hypertension. The graphical element 602 also includes a graphical sub-element 604a indicating an HbA1c physiological parameter, 604b indicating a BMI physiological parameter, and 604c indicating a blood pressure (BP) physiological parameter associated with the diagnosis for the PwD. The timeline view 600 further includes graphical elements 606 and 610 corresponding to a recommended prescribed treatment trigger for diet and exercise guidance to address elevated blood pressure (graphic element 606) and a recommended prescribed medication for metformin (graphic element 610). Graphic connectors 608 and 612 link the graphical element 602 for the initial patient visit to the graphical elements 606 and 610 for the recommended prescribed treatment, respectively. The timeline view 600 also includes a simplified timeline element 302 that indicates the year and month date of the initial patient visit, but omits a timeline slider control because the patient visit history includes only the initial visit.

[0055] Embodiments described herein enable generation of a timeline view user interface that presents highly relevant diagnoses, physiological parameters, and recommended prescribed treatment options to HCPs. The user interface reduces the cognitive burden on HCPs to achieve more efficient and effective treatment for PwDs and other patients. When integrated into clinical workflows, embodiments described herein can help HCPs make better personalized treatment decisions, thereby improving clinical, patient-reported, and economic outcomes. Specifically, embodiments described herein enable HCPs to work with existing clinical guidelines in an efficient manner to perform a therapy transition for diabetes, because following or applying these guidelines may be cumbersome in the case of a given amount of patient data in prior art systems. In addition, embodiments described herein simplify HCPs' analysis of potential courses of treatment for recommended therapies, which may be complex and evolve over several years, which simplifies the review of PwD treatment histories and tracking the progression of the disease using an adaptive user interface that is customized for each PwD's specific physiological parameters, diagnoses, and prescribed therapies.

[0056] The present disclosure has been described in conjunction with what are believed to be the most practical and preferred embodiments. However, these embodiments have been presented by way of illustration, and are not intended to be limited to the disclosed embodiments. Therefore, those skilled in the art will recognize that the present disclosure encompasses all modifications and alternative arrangements as set forth in the following claims and within the spirit and scope of the present disclosure.< / canvas>

Claims

1. A method for generating a user interface for a patient's treatment history, the method comprising: receiving, with a processor, medical data for the patient, the medical data corresponding to a plurality of patient visits to a health care provider; as well as generating, with the processor, graphical data corresponding to the timeline view of the plurality of patient visits, the generating of the graphical data further comprising: generating a first graphical element corresponding to a first diagnosis based on the medical data during a current patient visit in the plurality of patient visits, the first graphical element further comprising: a graphical indicator of the first diagnosis of a first medical condition; and at least one graphical sub-element, the at least one graphical sub-element being associated with a physiological parameter selected from the medical data, the physiological parameter being related to the first diagnosis; and generating a second graphical element corresponding to a second diagnosis based on the medical data for the patient during a first previous patient visit in the plurality of patient visits, the second graphical element further comprising: a graphical indicator of the second diagnosis for a second medical condition; and at least one graphical sub-element, the at least one graphical sub-element being associated with a physiological parameter selected from the medical data, the physiological parameter being related to the second diagnosis; and A first graphical connector is generated between the second graphical element and the first graphical element, the first graphical connector indicating a temporal progression between the first previous patient visit and the current patient visit in the timeline view.

2. The method of claim 1, generating, using the processor, the graphical data corresponding to the timeline view further comprising: 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 in the plurality of patient visits, the second previous patient visit occurring before the first previous patient visit, the third graphical element further comprising: a graphical indicator of the third diagnosis for a third medical condition; and at least one graphical sub-element, the at least one graphical sub-element being associated with a physiological parameter selected from the medical data, the physiological parameter being related to the third diagnosis; and A second graphical connector is generated between the third graphical element and the second graphical element, the graphical connector indicating a temporal progression between the second previous patient visit and the first previous patient visit in the timeline view.

3. The method of claim 1, generating, using the processor, the graphical data corresponding to the timeline view further comprising: generating graphical data corresponding to a timeline slider in the timeline view; In response to user input of the timeline slider moving to an earlier time range in the timeline view, generating a third graphical element related to a third diagnosis in the medical data during a second previous patient visit in the plurality of patient visits, the second previous patient visit occurring before the first previous patient visit, the third graphical element further comprising: a graphical indicator of the third diagnosis for a third medical condition; and at least one graphical sub-element, the at least one graphical sub-element being associated with a physiological parameter selected from the medical data, the physiological parameter being related to the third diagnosis; generating a second graphical connector between the second graphical element and the third graphical element, the graphical connector indicating a temporal progression between the second previous patient visit and the first previous patient visit in the timeline view; and Responsive to the current patient visit occurring outside the earlier time range in the timeline view, removing the first graphical element from the timeline view.

4. The method of claim 1, generating, using the processor, the graphical data corresponding to the timeline view further comprising: A third graphical element of the timeline is generated, the third graphical element indicating a first date of the first previous patient visit and a second date of the current patient visit.

5. The method of claim 1, generating, using the processor, the graphical data corresponding to the timeline view further comprising: Generating a third graphical element comprising a graphical indicator of a prescription therapy prescribed during the first previous patient visit, wherein the first graphical connector further comprises a first subconnector connecting the second graphical element of the first previous patient visit to the third graphical element and a second subconnector connecting the third graphical element to the first graphical element of the current patient visit to indicate that the patient received the prescribed therapy between the first previous patient visit and the current patient visit in the timeline view.

6. The method according to claim 5, wherein generating the third graphic element using the processor further comprises: The third graphical element is generated including a graphical indicator identifying that the prescribed therapy was manually selected by a healthcare provider.

7. The method according to claim 5, wherein generating the third graphic element using the processor further comprises: The third graphical element is generated to include a graphical sub-element corresponding to a clinical note associated with the prescribed treatment.

8. The method of claim 1, generating, using the processor, the graphical data corresponding to the timeline view further comprising: generating a third graphical element including a graphical indicator of a recommendation for prescribing treatment associated with the first diagnosis; A second graphical connector is generated 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.

9. The method according to claim 1, further comprising: generating, with the processor provided in a server computing system, the graphical data corresponding to the timeline view; as well as The graphical data corresponding to the timeline view is transmitted to a client computing system using the processor and the network transceiver for display using a display device provided in the client computing system.

10. The method according to claim 1, further comprising: generating, with the processor provided in a computing system, the graphical data corresponding to the timeline view; as well as The graphical data corresponding to the timeline view is displayed using a display device provided in the computing system.

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

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

13. The computing system of claim 12, wherein the processor is further configured to: 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 in the plurality of patient visits, the second previous patient visit occurring before the first previous patient visit, the third graphical element further comprising: a graphical indicator of the third diagnosis for a third medical condition; at least one graphical sub-element, the at least one graphical sub-element being associated with a physiological parameter selected from the medical data, the physiological parameter being related to the third diagnosis; and a graphical indicator of a third prescribed treatment for the patient based on the third diagnosis; as well as A second graphical connector is generated between the second graphical element and the third graphical element, the graphical connector indicating a temporal progression between the second previous patient visit and the first previous patient visit in the timeline view.

14. The computing system of claim 12, wherein the processor is further configured to: generating graphical data corresponding to a timeline slider in the timeline view; In response to user input of the timeline slider moving to an earlier time range in the timeline view, generating a third graphical element related to a third diagnosis in the medical data during a second previous patient visit in the plurality of patient visits, the second previous patient visit occurring before the first previous patient visit, the third graphical element further comprising: a graphical indicator of the third diagnosis for a third medical condition; and at least one graphical sub-element, the at least one graphical sub-element being associated with a physiological parameter selected from the medical data, the physiological parameter being related to the third diagnosis; generating a second graphical connector between the second graphical element and the third graphical element, the graphical connector indicating a temporal progression between the second previous patient visit and the first previous patient visit in the timeline view; and Responsive to the current patient visit occurring outside the earlier time range in the timeline view, removing the first graphical element from the timeline view.

15. The computing system of claim 12, wherein the processor is further configured to: A third graphical element of the timeline is generated, the third graphical element indicating a first date of the first previous patient visit and a second date of the current patient visit.

16. The computing system of claim 12, wherein the processor is further configured to: Generating a third graphical element comprising a graphical indicator of a prescription therapy prescribed during the first previous patient visit, wherein the first graphical connector further comprises a first subconnector connecting the second graphical element of the first previous patient visit to the third graphical element and a second subconnector connecting the third graphical element to the first graphical element of the current patient visit to indicate that the patient received the prescribed therapy between the first previous patient visit and the current patient visit in the timeline view.

17. The computing system of claim 16, wherein the processor is further configured to: The third graphical element is generated including a graphical indicator identifying that the prescribed therapy was manually selected by a healthcare provider.

18. The computing system of claim 16, wherein the processor is further configured to: The third graphical element is generated to include a graphical sub-element corresponding to a clinical note associated with the prescribed treatment.

19. The computing system of claim 12, wherein the processor is further configured to: generating a third graphical element including a graphical indicator of a recommendation for prescribing treatment associated with the first diagnosis; A second graphical connector is generated 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.

20. The computing system of claim 12, further comprising: Network transceiver; and The processor is operably connected to the network transceiver and is further configured to: generating, with the processor provided in a server computing system, the graphical data corresponding to the timeline view; as well as The graphical data corresponding to the timeline view is transmitted to a client computing system using the network transceiver for display using a display device provided in the client computing system.

21. The computing system of claim 12, further comprising: Display device; and The processor is operably connected to the display device and is further configured to: The graphical data corresponding to the timeline view is displayed using the display device.

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

23. A method for generating a user interface for a patient's treatment history, the method comprising: receiving, with a processor, medical data for the patient, the medical data corresponding to an initial patient visit with a health care provider; as well as Generating, with the processor, graphical data corresponding to the timeline view, the generating of the graphical data further comprising: generating a first graphical element corresponding to a first diagnosis based on the medical data during the initial patient visit, the first graphical element further comprising: a graphical indicator of the first diagnosis of a first medical condition; and At least one graphical sub-element, the at least one graphical sub-element being associated with a physiological parameter selected from the medical data, the physiological parameter being related to the first diagnosis.

24. The method of claim 23, generating, using the processor, the graphical data corresponding to the timeline view further comprising: generating a second graphical element including a graphical indicator of a recommendation for a prescribed treatment associated with the first prescribed diagnosis; A graphical connector is generated 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.

25. The method of claim 23, generating, using the processor, the graphical data corresponding to the timeline view further comprising: A second graphical element of the timeline is generated, the second graphical element indicating a date of the initial patient visit.

26. The method of claim 23, further comprising: generating, with the processor provided in a server computing system, the graphical data corresponding to the timeline view; as well as The graphical data corresponding to the timeline view is transmitted to a client computing system using the processor and the network transceiver for display using a display device provided in the client computing system.

27. The method of claim 23, further comprising: generating, with the processor provided in a computing system, the graphical data corresponding to the timeline view; as well as The graphical data corresponding to the timeline view is displayed using a display device provided in the computing system.

28. The method of claim 27, wherein the computing system is a healthcare provider's terminal.

Images