Source: https://patents.google.com/patent/US8856172B2/en
Timestamp: 2018-06-21 02:30:51
Document Index: 166484777

Matched Legal Cases: ['Application No. 03372021', 'Application No. 03372021', 'Application No. 03772021', 'Application No. 03772021', 'Application No. 12153336', 'Application No. 03772021', 'Application No. 2003259281', 'Application No. 0078', 'Application No. 166', 'Application No. 03372021', 'Application No. 03372021', 'Application No. 12153336', 'Application No. 03772021', 'Application No. 03772021']

US8856172B2 - Method and system of unifying data - Google Patents
US8856172B2
US8856172B2 US13523402 US201213523402A US8856172B2 US 8856172 B2 US8856172 B2 US 8856172B2 US 13523402 US13523402 US 13523402 US 201213523402 A US201213523402 A US 201213523402A US 8856172 B2 US8856172 B2 US 8856172B2
US20130073590A1 (en )
1. A system for unifying data, comprising:
a plurality of separate data sources, each data source having a respective data access mechanism for facilitating querying thereof, each data source having stored thereon data for a particular clinical trials patient, and the plurality of data sources comprising (a) an electronic data capture (“EDC”) data source having EDC study data stored thereon, including EDC study data for the particular clinical trials patient, and (b) a patient diary data source having patient diary data stored thereon, including patient diary data for the particular clinical trials patient;
a first complex query calling a plurality of the data source query function calls, including, in response to a user query about the particular clinical trials patient, calling a query of the EDC data source for EDC study data for the particular clinical trials patient and a query of the patient diary data source for patient diary data for the particular clinical trials patient; wherein the first complex query does not identify any data source to query;
wherein, in response to the first complex query, EDC study data for the particular clinical trials patient is retrieved from the EDC data source and patient diary data for the particular clinical trials patient is retrieved from the patient diary data source to populate at least one result set;
a second complex query, in response to a user passing dimension instance parameters in the form of a list of a plurality of clinical trials patients, calls a first query of a first data source for patient characteristics data for a first clinical trials patient, calls a second query of a second data source for patient characteristics data for a second clinical trials patient, and calls a third query of a third data source for patient characteristics data for a third clinical trials patient;
wherein the second complex query does not identify any data source to query; and wherein, in response to the second complex query, patient characteristics data for the first clinical trials patient is retrieved from the first data source, patient characteristics data for the second clinical trials patient is retrieved from the second data source, and patient characteristics data for the third clinical trials patient is retrieved from the third data source to populate at least one result set.
2. The system of claim 1, wherein the first complex query comprises a clinical trials patient quality of life complex query.
wherein the first complex query calls, in response to the user query about the particular clinical trials patient, a data query of the other data source for other data about the particular clinical trials patient; and
wherein, in response to the first complex query, EDC study data for the particular clinical trials patient is retrieved from the EDC data source, patient diary data for the particular clinical trials patient is retrieved from the patient diary data source, and other data for the particular clinical trials patient is retrieved from the other data source to populate at least one result set.
the first data source is a study database;
the second data source is a first EDC study database; and
the third data source is a second EDC study database.
5. The system of claim 1, wherein the first complex query calls, in response to the user query about the particular clinical trials patient:
wherein, in response to the first complex query, patient pain level data for the particular clinical trials patient is retrieved from the patient diary data source, EDC medication data for the particular clinical trials patient is retrieved from the EDC data source, and other patient diary data for the particular clinical trials patient is retrieved from the patient diary data source to populate at least one result set.
wherein the first complex query further calls, in response to the user query about the particular clinical trials patient, a query of the other data source for other patient data about the particular clinical trials patient; and
wherein, in response to the first complex query, patient pain level data for the particular clinical trials patient is retrieved from the patient diary data source, EDC medication data for the particular clinical trials patient is retrieved from the EDC data source, other patient diary data for the particular clinical trials patient is retrieved from the patient diary data source, and other data for the particular clinical trials patient is retrieved from the other data source to populate at least one result set.
a first plurality of nodes storing information defining a corresponding plurality of business context dimensions for the industry, including clinical study, clinical trial site, and clinical trial patient dimensions, each node of the first plurality of nodes representing an industry business context dimension, with one node of the first plurality of nodes for each dimension, and wherein the first plurality of nodes includes a clinical study node, a clinical trial site node, and a clinical trial patient node; and
wherein, in response to the first complex query, the system uses the first plurality of nodes and the mapping data to retrieve EDC study data for the particular clinical trials patient from the EDC data source and retrieve patient diary data for the particular clinical trials patient from the patient diary data source to populate at least one result set.
8. The system of claim 7, wherein the industry business context dimensions include clinical trial sponsor, clinical study, clinical trial site, clinical trial patient, and clinical trial visit dimensions and further wherein the first plurality of nodes includes a clinical trial sponsor node, a clinical study node, a clinical trial site node, a clinical trial patient node, and a clinical trial visit node.
10. The system of claim 7, wherein the mapping data comprises a second plurality of nodes for mapping the first plurality of nodes to the plurality of data sources on a dimension by dimension basis, each node of the second plurality of nodes representing a data source specific dimension of at least one of the data sources,
(b) each data source instance represented within the plurality of data sources, with the second plurality of nodes mapped to the first plurality of nodes based on corresponding business context dimensions, each node of the second plurality of nodes storing information defining at least one business context dimension instance from the plurality of data sources, each business context dimension instance relating to an instance of stored data within the corresponding data source instance associated with the corresponding business context dimension; and
wherein, in response to the first complex query, the system uses the first plurality of nodes and the second plurality of nodes to retrieve EDC study data for the particular clinical trials patient from the EDC data source and retrieve patient diary data for the particular clinical trials patient from the patient diary data source to populate at least one result set.
11. A system for unifying data, comprising:
a plurality of separate data sources, each data source having a respective data access mechanism for facilitating querying thereof, each data source having stored thereon data for a particular clinical trials patient, and the plurality of data sources comprising (a) an electronic data capture (“EDC”) data source having EDC study data and EDC medication data stored thereon, including EDC study data and EDC medication data for the particular clinical trials patient, (b) a patient diary data source having patient diary data and patient pain level data stored thereon, including patient diary data and patient pain level data for the particular clinical trials patient, and (c) another data source having other data stored thereon, including other data for the particular clinical trials patient;
a first complex query calling a plurality of the data source query function calls, including, in response to a user query about the particular clinical trials patient, calling:
(e) a query of the other data source for other patient data about the particular clinical trials patient; wherein, in response to the complex query, patient pain level data for the particular clinical trials patient is retrieved from the patient diary data source, EDC medication data for the particular clinical trials patient is retrieved from the EDC data source, EDC study data for the particular clinical trials patient is retrieved from the EDC data source, other patient diary data for the particular clinical trials patient is retrieved from the patient diary data source, and other data for the particular clinical trials patient is retrieved from the other data source to populate at least one result set;
wherein the first complex query does not identify any data source to query; a second complex query, in response to a user passing dimension instance parameters in the form of a list of a plurality of clinical trials patients, calls a first query of a first data source for patient characteristics data for a first clinical trials patient, calls a second query of a second data source for patient characteristics data for a second clinical trials patient, and calls a third query of a third data source for patient characteristics data for a third clinical trials patient;
wherein the second complex query does not identify any data source to query; and
wherein, in response to the second complex query, patient characteristics data for the first clinical trials patient is retrieved from the first data source, patient characteristics data for the second clinical trials patient is retrieved from the second data source, and patient characteristics data for the third clinical trials patient is retrieved from the third data source to populate at least one result set;
wherein the second plurality of nodes store information relating data stored within the plurality of data sources to at least a portion of the plurality of business context dimensions for at least one of (a) each data source type represented within the plurality of data sources, and
wherein, in response to the at least one first complex query, the system uses the first plurality of nodes and the second plurality of nodes to retrieve patient pain level data for the particular clinical trials patient from the patient diary data source, EDC medication data for the particular clinical trials patient from the EDC data source, EDC study data for the particular clinical trials patient from the EDC data source, other patient diary data for the particular clinical trials patient from the patient diary data source, and other data for the particular clinical trials patient from the other data source to populate at least one result set.
13. A system for unifying data relating to an industry having a plurality of industry business context dimensions which define logical groupings of data related to the industry, the system comprising:
data storage space associated with the one or more computer systems for storing data suitable for processing by at least one of the one or more computers;
a first complex query calling a plurality of data source query function calls, including, in response to a user query about a particular clinical trials patient as a dimension instance of the clinical trials patient industry business context dimension, a query of an electronic data capture (“EDC”) data source having EDC study data stored thereon, including EDC study data for the particular clinical trials patient;
wherein the first complex query does not identify any data source to query, the first complex query calling the plurality of data source query function calls to perform the querying of the at least two data sources for the data relating to the dimension instance, wherein the data relating to the dimension instance is retrieved from each of the at least two data sources, including EDC data for the dimension instance being retrieved from the EDC data source, to populate at least one result set object;
a second complex query, in response to a user passing dimension instance parameters in the form of a list of a plurality of clinical trials patients, calls a first query of a first data source for patient characteristics data for a first dimension instance, calls a second query of a second data source for patient characteristics data for a second dimension instance, and calls a third query of a third data source for patient characteristics data for a third dimension instance;
wherein, in response to the second complex query, patient characteristics data for the first dimension instance is retrieved from the first data source, patient characteristics data for the second dimension instance is retrieved from the second data source, and patient characteristics data for the third dimension instance is retrieved from the third data source to populate at least one result set object.
14. The system of claim 13, wherein the first complex query calls, in response to the user query about a particular clinical trials patient:
15. The system of claim 13 wherein the first complex query comprises a clinical trials patient quality of life complex query.
17. The system of claim 13, wherein the first complex query calls, in response to the user query about a particular clinical trials patient:
18. The system of claim 17 wherein the industry business context dimensions include clinical trial sponsor, clinical study, clinical trial site, clinical trial patient, and clinical trial visit dimensions and further wherein the first plurality of nodes includes a clinical trial sponsor node, a clinical study node, a clinical trial site node, a clinical trial patient node, and a clinical trial visit node.
US20130073590A1 true US20130073590A1 (en) 2013-03-21
US8856172B2 true US8856172B2 (en) 2014-10-07
CA2493269A1 (en) 2002-07-26 2004-02-05 Datatrak International, Inc. Method and system of unifying data
WO2004012057A2 (en) 2002-07-26 2004-02-05 Datatrak International Method and system of unifying data
RU2333530C2 (en) 2002-07-26 2008-09-10 Дэйтатрек Интернэшнл Method and system for data unification
"IBM Life Sciences Solutions: Turning Data into Discovery with DiscoveryLink" Mar. 2002.
Advisory Action mailed Jun. 4, 2012, for related Reexamination Control No. 90/011,985.
Amendment in Response to Reexamination Non-Final Office Action filed Feb. 16, 2012, in response to Non-Final Office Action dated Dec. 16, 2011, for related Reexamination Control No. 90/011,985.
Amendment to Claims filed Jul. 26, 2012, for EP Application No. 03372021.6.
Annevelink, et al., "Heterogenous Database Integration in a Physician Workstation", pp. 368-372, Proceedings of the Annual Symposium on Computer Application in Medical Care, 1992.
Billhardt, H., et al., A New Method for Unifying Heterogeneous Databases, Second International Symposium Medical Data Analysis Proceedings, Jose Crespo, et al. eds., Springer-Verlag Berlin Heidelberg, New York, 54-61 (2001).
Communication for EP Application No. 03372021.6 dated Oct. 16, 2007.
Communication from EP Application No. 03772021 dated Jan. 22, 2010.
Communication from European Application No. 03772021.6 dated Dec. 10, 2010.
De Smedt et al., "A Physician's Workstation as an Application of Object-Oriented Database Technology in Healthcare", pp. 234-252, Lecture Notes in Computer Science, vol. 819, 1994.
European Search Report dated Feb. 1, 2013, for related European Patent Application No. 12153336.8.
Ex Parte Reexamination Interview Summary dated Feb. 14, 2012, for related Reexamination Control No. 90/011,985.
Examination Report dated Feb. 5, 2013, for related European Patent Application No. 03772021.6.
Examiner's First Report for Australian Patent Application No. 2003259281 dated Jan. 8, 2009.
Executed Declaration of Christopher Lee Wilke filed Feb. 16, 2012, in response to Non-Final Office Action dated Dec. 16, 2011, for related Reexamination Control No. 90/011,985.
Final Office Action filed Apr. 6, 2012, in response to Non-Final Office Action dated Dec. 16, 2011, for related Reexamination Control No. 90/011,985.
IBM DiscoveryLink product information, Apr. 12, 2004.
International Search Report for International Patent Application No. PCT/US03/23656 dated Jan. 14, 2004.
JP Office Action dated Apr. 27, 2009 from 2004-524998.
Marks, C, Extensible Multi-Agent System for Heterogeneous Database Association Rule Mining and Unification, (unpublished M.S. thesis, Air Force Institute of Technology Air University) (on file with the Air Force Institute of Technology Air University), 1-91 (Mar. 1999).
Marrs, K., et al., Unifying Heterogeneous Distributed Clinical Data in a Relational Database, Proceedings of the Symposium on Computer Applications in Medical Care, C. Safran, ed., McGraw-Hill, New York, 644-648 (1994).
Non-Final Office Action dated Dec. 16, 2011, for related U.S. Reexamination Control No. 90/011,985.
Notice of Allowance from U.S. Appl. No. 10/628,884 dated Aug. 13, 2007.
Notice of Allowance from U.S. Appl. No. 10/628,884 dated Aug. 8, 2008.
Office action from Indian Application No. 0078/CHENP/2005 dated Mar. 13, 2006.
Office action from Israeli Application No. 166,517 dated Mar. 24, 2009.
Office action from U.S. Appl. No. 10/628,884 dated Mar. 25, 2008.
Office action from U.S. Appl. No. 10/628,884 dated Oct. 31, 2006.
Order Granting Request for Ex Parte Reexamination dated Dec. 16, 2011, for related U.S. Reexamination Control No. 90/011,985.
Paepcke, A., An Object-Oriented View Onto Public, Heterogeneous Text Databases, Proceedings of the 9th International Conference on Data Engineering, 484-493 (1993).
Patent Board Decision dated Mar. 4, 2014, for related Reexamination Control No. 90/011,985.
Patent Owner's Statement of the Substance of the Interview filed Mar. 14, 2012, for related Reexamination Control No. 90/011,985.
Ram, S., etal., A Unifying Semantic Model for Accessing Multiple Heterogeneous Databases in a Manufacturing Environment, Interoperability in Multidatabase Systems, 212-215 (1991).
Record of Oral Hearing dated Jan. 28, 2014, for related Reexamination Control No. 90/011,985.
Request for Ex Parte Reexamination for related U.S. Patent No. 7,464,087 and accompanying attachments submitted to the U.S. Patent Office on Oct. 28, 2011, 176 pgs.
Response After Final filed May 7, 2012, in response to Final Office Action mailed Apr. 6, 2012, for related Reexamination Control No. 90/011,985.
Response filed Dec. 21, 2007, in response to Communication for EP Application No. 03372021.6 dated Oct. 16, 2007.
Response filed Nov. 17, 2010, in response to Communication for EP Application No. 03372021.6 dated Jan. 22, 2010.
Response from U.S. Appl. No. 10/628,884 dated Apr. 2, 2007.
Response from U.S. Appl. No. 10/628,884 dated Jun. 23, 2008.
Response to European Search Report filed Sep. 6, 2013, for related European Patent Application No. 12153336.8.
Response to Examination Report filed Aug. 15, 2013, for related European Patent Application No. 03772021.6.
Russian Office Action from 2005105305 dated Jul. 10, 2007.
Sheth, A., et al., Federated Database Systems for Managing Distributed, Heterogeneous, and Autonomous Databases, ACM Computing Surveys, 22(3): 183-236 (1990).
Smith, J.M., et al., Multibase-integrating heterogeneous distributed database systems, National Computer Conference, 487-499 (1981).
Sujansky, W., A Formal Model for Bridging Heterogeneous Relational Databases in Clinical Medicine, (Ph.D. dissertation, Stanford University), 1-302 (Jan. 1996).
Sujansky, W., Heterogeneous Database Intergration in Biomedicine, Journal of Biomedical Informatics, 34(4): 285-298 (2001).
Supplementary European Search Report for European Patent Application No. 03772021.6 dated Sep. 27, 2007.
Tang et al., "Physicians' Workstations: Integrated Information Management for Clinicians," Proc Annu Symp Comput Appl Med Care, at 569-573 (1991).
Templeton, M., et al., InterViso: Dealing with the Complexity of Federated Database Access, VLDB Journal, 4: 287-317 (1995).
van Wingerde, F.J., et al., Using HL7 and the World Wide Web for Unifying Patient Data from Remote Databases, Proc AMIA Annu Fall Symp., 643-647 (1996).
Young et al., "An Open System Architecture for Development of a Physician's Workstation," Proc Annu Symp Comput Appl Med Care, at 491-495 (1991).