# US 2017/0255697 A1 · Patient-centric modeling of patient data > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2017/0255697 A1 - Document ID: US20170255697A1 - Status: Published application - Kind: A1 - Application number: 15/604,537 - Filed: 2017-05-24 - Published: 2017-09-07 - Earliest claimed: 2017-05-24 - Assignees: Curesoft, Inc. - Applicants: Curesoft, Inc. - Inventors: Michael MORRIS; Daniel FOBES - Web page: https://patentgrep.com/patent/US20170255697A1 ## CPC - G16H 10/60: for patient-specific data, e.g. for electronic patient records - G16H: HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA ## Abstract Exemplary methods, apparatuses, and systems generate and maintain patient-specific models of patient data to assist in monitoring a patient's unique health conditions, and to provide more informative analyses of patient data and the relationships between elements of patient data. When a patient modeling server receives patient data from an external device, the patient modeling server determines whether values for elements of patient data satisfy individualized ranges for the elements of patient data, specific to the patient. In response to this determination, the patient modeling server can transmit notification and/or alert messages, and modify the individualized ranges for the elements of patient data. The patient modeling server also determines relationships between elements of patient data, based on analyses performed on the elements of patient data, to generate patient-specific models. ## Claims ### Claim 1 A computer-implemented method, comprising: generating an ontological data structure having a first plurality of nodes, each of the first plurality of nodes associated with an element of patient data for a patient, the data structure maintaining relationships between the nodes and values for the elements of patient data represented by the nodes; determining an individualized range of values for an element of patient data represented by a node within the first plurality of nodes based on a history of values for the patient; receiving an input from an external device; determining, based on the external device or content of the received input, the received input includes a value for the element of patient data represented by the node within the first plurality of nodes; comparing the value from the received input with a threshold value, the threshold value based on the individualized range of values; registering an occurrence of an event in response to determining the received input fails to satisfy the threshold value; transmitting a notification message indicating the occurrence of the detected event; and modifying the individualized range for the node based on the received input. ### Claim 2 (depends on 1) The computer-implemented method of claim 1, wherein determining the received input includes the value for the element of patient data represented by the node within the first plurality of nodes comprises: identifying an attribute identifier associated with the value in the received input; and mapping the received input to the node within the first plurality of nodes identified by the attribute identifier. ### Claim 3 (depends on 1) The computer-implemented method of claim 1, wherein determining the received input fails to satisfy the threshold value comprises: determining that the received input is not within the individualized range of values for the element of patient data represented by the node. ### Claim 4 (depends on 1) The computer-implemented method of claim 1, wherein determining the received input fails to satisfy the threshold value comprises: determining that the received input is not within the individualized range of values for the element of patient data represented by the node and is not within a standard range of values for the element of patient data represented by the node, the standard range of values determined based on averaging values for a pool of patients with the condition. ### Claim 5 (depends on 1) The computer-implemented method of claim 1, further comprising: receiving a second input, the received second input including a second value for a second element of patient data represented by a second node within the first plurality of nodes, the second node having a relationship with the node; determining the received second input indicates a change in the second value for the second element of patient data represented by the second node; and associating the change in the second value with the occurrence of the event. ### Claim 6 (depends on 1) The computer-implemented method of claim 1, further comprising: receiving a request to access the ontological data structure, the request including a user identifier, the user identifier linked to a filtered view of the ontological data structure, the filtered view based on a condition associated with a patient represented by the ontological data structure; identifying a subset of the ontological data structure based on the filtered view; and modifying a graphical depiction of the ontological data structure to display the identified subset of the ontological data structure in response to the request. ### Claim 7 (depends on 6) The computer-implemented method of claim 6, further comprising: determining that the element of patient data represented by the node has a relationship with a second element of patient data represented by a second node in response to determining that a change in the value for the element of patient data represented by the node corresponds to a change in a value for the second element of patient data represented by the second node; creating the relationship between the node and the second node in the ontological data structure; and modifying the subset of the ontological data structure to include the second node. ### Claim 8 (depends on 7) The computer implemented method of claim 7, wherein the node represents an immunotherapy treatment applied to the patient, and the second node represents a test result of the patient. ### Claim 9 (depends on 1) The computer-implemented method of claim 1, further comprising retrieving a second ontological data structure for a second patient, the second patient having the condition; determining the second ontological data structure includes a relationship in addition to the relationships of the ontological data structure, the relationship associated with an additional input; transmitting a request for the additional input based on the relationship; and modifying the ontological data structure to include the relationship. ### Claim 10 (depends on 1) The computer implemented method of claim 1, wherein the element of patient data represented by the node is one of: a physical attribute of the patient, a test result of the patient, a measured data of the patient, and/or a treatment applied to the patient. ### Claim 11 A non-transitory computer-readable medium storing instructions, which when executed by a processing device, cause the processing device to perform a method comprising: generating an ontological data structure having a first plurality of nodes, each of the first plurality of nodes associated with an element of patient data for a patient, the data structure maintaining relationships between the nodes and values for the elements of patient data represented by the nodes; determining an individualized range of values for an element of patient data represented by a node within the first plurality of nodes based on a history of values for the patient; receiving an input from an external device; determining, based on the external device or content of the received input, the received input includes a value for the element of patient data represented by the node within the first plurality of nodes; comparing the value from the received input with a threshold value, the threshold value based on the individualized range of values; registering an occurrence of an event in response to determining the received input fails to satisfy the threshold value; transmitting a notification message indicating the occurrence of the detected event; and modifying the individualized range for the node based on the received input. ### Claim 12 (depends on 11) The non-transitory computer-readable medium of claim 11, wherein determining the received input includes the value for the element of patient data represented by the node within the first plurality of nodes comprises: identifying an attribute identifier associated with the value in the received input; and mapping the received input to the node within the first plurality of nodes identified by the attribute identifier. ### Claim 13 (depends on 11) The non-transitory computer-readable medium of claim 11, wherein determining the received input fails to satisfy the threshold value comprises: determining that the received input is not within the individualized range of values for the element of patient data represented by the node. ### Claim 14 (depends on 11) The non-transitory computer-readable medium of claim 11, wherein determining the received input fails to satisfy the threshold value comprises: determining that the received input is not within the individualized range of values for the element of patient data represented by the node and is not within a standard range of values for the element of patient data represented by the node, the standard range of values determined based on averaging values for a pool of patients with the condition. ### Claim 15 (depends on 11) The non-transitory computer-readable medium of claim 11, further comprising: receiving a second input, the received second input including a second value for a second element of patient data represented by a second node within the first plurality of nodes, the second node having a relationship with the node; determining the received second input indicates a change in the second value for the second element of patient data represented by the second node; and associating the change in the second value with the occurrence of the event. ### Claim 16 (depends on 11) The non-transitory computer-readable medium of claim 11, further comprising: receiving a request to access the ontological data structure, the request including a user identifier, the user identifier linked to a filtered view of the ontological data structure, the filtered view based on a condition associated with a patient represented by the ontological data structure; identifying a subset of the ontological data structure based on the filtered view; and modifying a graphical depiction of the ontological data structure to display the identified subset of the ontological data structure in response to the request. ### Claim 17 (depends on 16) The non-transitory computer-readable medium of claim 16, further comprising: determining that the element of patient data represented by the node has a relationship with a second element of patient data represented by a second node in response to determining that a change in the value for the element of patient data represented by the node corresponds to a change in a value for the second element of patient data represented by the second node; creating the relationship between the node and the second node in the ontological data structure; and modifying the subset of the ontological data structure to include the second node. ### Claim 18 (depends on 17) The non-transitory computer-readable medium of claim 17, wherein the node represents an immunotherapy treatment applied to the patient, and the second node represents a test result of the patient. ### Claim 19 (depends on 11) The non-transitory computer-readable medium of claim 11, further comprising: retrieving a second ontological data structure for a second patient, the second patient having the condition; determining the second ontological data structure includes a relationship in addition to the relationships of the ontological data structure, the relationship associated with an additional input; transmitting a request for the additional input based on the relationship; and modifying the ontological data structure to include the relationship. ### Claim 20 An apparatus comprising: a processing device; and a memory coupled to the processing device, the memory storing instructions which, when executed by the processing device, cause the apparatus to: generate an ontological data structure having a first plurality of nodes, each of the first plurality of nodes associated with an element of patient data for a patient, the data structure maintaining relationships between the nodes and values for the elements of patient data represented by the nodes; determine an individualized range of values for an element of patient data represented by a node within the first plurality of nodes based on a history of values for the patient; receive an input from an external device; determine, based on the external device or content of the received input, the received input includes a value for the element of patient data represented by the node within the first plurality of nodes; compare the value from the received input with a threshold value, the threshold value based on the individualized range of values; register an occurrence of an event in response to determining the received input fails to satisfy the threshold value; transmit a notification message indicating the occurrence of the detected event; and modify the individualized range for the node based on the received input.