Clinical data monitoring
First Claim
1. A data correlation engine that uses a computer to run a set of queries against a database that electronically stores clinical data, comprising:
- a stored set of queries that had been previously created by a first user and run against the database, wherein each individual query within the set is associated with a first parameterized value corresponding to a first category and a second parameterized value corresponding to a second category;
a filtering interface configured to (1) receive a category selection from a second user, (2) automatically present to the second user a plurality of parameterized values corresponding to the selected category, (3) receive from the second user a selection of a parameterized value from the plurality of parameterized values, and (4) retrieve a non-trivial proper sub-set of the queries based on the selected category and the selected parameterized value;
a query selection interface through which the second user can select one or more queries from the retrieved sub-set of queries to be automatically run against the database according to a periodicity schedule to provide a set of exceptional case alerts;
a presentation interface through which the second user can select a presentation aspect of how at least one of the exceptional case alerts will be presented to the second user; and
a correlation module configured to (1) run the selected one or more queries against the database to produce a first value, (2) perform a comparison operation between the produced first value and a second pre-determined value to generate a difference value, and (3) present an exceptional case alert to the second user according to the selected presentation aspect only when the difference value indicates are exceptional case.
9 Assignments
0 Petitions
Accused Products
Abstract
Data is combined from multiple independent data stores, and is then queried using a data correlation engine. Contemplated engines preferably keep track of previously run correlations, and then makes those correlations available to clinicians for their own use. For example, a preferred system might provide a listing of correlations run by other clinicians in a particular medical specialty, or a particular community, whether geographic or otherwise. In another example, a preferred system might provide a listing of correlations sorted by popularity, so that the most frequently accessed correlations appear near the top of the list. In any case a clinician could simply view the list, and check off which correlations he/she would like to have run for his/her practice, or practice community.
16 Citations
15 Claims
-
1. A data correlation engine that uses a computer to run a set of queries against a database that electronically stores clinical data, comprising:
-
a stored set of queries that had been previously created by a first user and run against the database, wherein each individual query within the set is associated with a first parameterized value corresponding to a first category and a second parameterized value corresponding to a second category; a filtering interface configured to (1) receive a category selection from a second user, (2) automatically present to the second user a plurality of parameterized values corresponding to the selected category, (3) receive from the second user a selection of a parameterized value from the plurality of parameterized values, and (4) retrieve a non-trivial proper sub-set of the queries based on the selected category and the selected parameterized value; a query selection interface through which the second user can select one or more queries from the retrieved sub-set of queries to be automatically run against the database according to a periodicity schedule to provide a set of exceptional case alerts; a presentation interface through which the second user can select a presentation aspect of how at least one of the exceptional case alerts will be presented to the second user; and a correlation module configured to (1) run the selected one or more queries against the database to produce a first value, (2) perform a comparison operation between the produced first value and a second pre-determined value to generate a difference value, and (3) present an exceptional case alert to the second user according to the selected presentation aspect only when the difference value indicates are exceptional case. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15)
-
Specification