Clinical data monitoring
View Patent ↗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.
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.
2. The engine of claim 1 , wherein the selection interface includes at least one of an opt-in and an opt-out choice.
3. The engine of claim 1 , further comprising a periodicity interface through which the user can select periodicity at which at least some of the alerts will be run.
4. The engine of claim 1 , wherein at least one of the filtering and selection interfaces includes a web based interface.
5. The engine of claim 1 , wherein the filtering interface is configured to (1) receive a category selection from a third user, (2) automatically present to the third user a plurality of parameterized values corresponding to the selected category, (3) receive from the third 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 to run against a second database to provide a second set of alerts.
6. The engine of claim 1 , further comprising an additional interface through which the second user can add a new query to the set of queries, and wherein the second user can select the new query as falling within the sub-set of the queries.
7. The engine of claim 1 , wherein the selection interface is customizable by the user.
8. The engine of claim 1 , wherein the first user can add a new query to the set of queries, and second, third and other users can then select the new query as part of their own sets of selected queries.
9. The engine of claim 1 , further comprising a translator that translates elements of the stored queries into a language other than that in which the elements were originally stored.
10. The engine of claim 1 , wherein the filtering interface is configured to receive the category selection as a natural language input from a second user.
11. The engine of claim 1 , wherein the clinical data is derived from medical care facilities located in at least three different countries.
12. The engine of claim 1 , wherein the category is medical specialty.
13. The engine of claim 12 , wherein the plurality of parameterized values includes at least one of general medicine, pediatrics, coronary care, emergency medicine, urology, and obstetrics.
14. The engine of claim 1 , wherein the category is community.
15. The engine of claim 14 , wherein the plurality of parameterized values includes at least one of AIDS and diabetes.