Point-in-time query system

• US 9,147,040 B2
• Filed: 06/21/2013
• Issued: 09/29/2015
• Est. Priority Date: 10/31/2012
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Aggarwal, Amit, Triebel, William Andrew, Singhal, Puneet
• Primary Examiner(s): Rostami, Mohammad S
• Application Number:
  US13/923,483
• Publication Number:
  US 20140122523A1
• Time in Patent Office: 830 Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/245 Query processing
• CPC Class Codes: G06F 16/24573 using data annotations, e.g. user-defined metadata
• CPC Class Codes: G16H 10/20 for electronic clinical trials or questionnaires
• CPC Class Codes: G16H 10/60 for patient-specific data, e.g. for electronic patient records
• CPC Class Codes: G16H 50/70 for mining of medical data, e.g. analysing previous cases of other patients
• CPC Class Codes: G16H 70/40 relating to drugs, e.g. their side effects or intended usage

Abstract

A system is provided that implements a point-in-time query. The system selects a point-in-time query type from one or more point-in-time query types. The system further retrieves metadata that includes structured query language information based on the selected point-in-time query type. The system further creates a point-in-time query for a data source based on the retrieved metadata, where the point-in-time query is a query that is based on a date and/or time. The system further compiles the point-in-time query. The system further executes the point-in-time query on the data source; where the executing of the point-in-time query creates a case series.

Claims

1. A non-transitory computer-readable medium having instructions stored thereon that, when executed by a processor, cause the processor to implement a point-in-time query, the implementing comprising:

receiving a selection of a point-in-time query type, from one or more point-in-time query types, from a user;

retrieving metadata, from a repository, that comprises structured query language information based on the selected point-in-time query type;

creating a point-in-time query for a drug safety database based on the retrieved metadata and a date, the drug safety database including a plurality of adverse event records, each adverse event record including an effective end date indicating when a subsequent revision of the adverse event record was stored in the drug safety database, a patient identifier and drug safety data associated with a patient, the point-in-time query including a comparison of the date with the adverse event record effective end date;

compiling the point-in-time query to create a compiled point-in-time query; and

executing the compiled point-in-time query on the drug safety database to create a case series.

2. The non-transitory computer-readable medium of claim 1, the implementing further comprising:

receiving a selection of the date from the user,

wherein each adverse event record includes an effective start date indicating when the adverse event record was stored in the drug safety database, and

wherein the point-in-time query further includes a comparison of the date with the adverse event record effective start date.

3. The non-transitory computer-readable medium of claim 1, the implementing further comprising:

creating a user-defined point-in-time query type;

creating metadata, associated with the user-defined point-in-time query type, including structured query language information; and

storing the created metadata in the repository.

4. The non-transitory computer-readable medium of claim 1, wherein the one or more point-in-time query types comprises at least one of:

a system-defined point-in-time query type;

or

a user-defined point-in-time query type.

5. The non-transitory computer-readable medium of claim 4, wherein the system-defined point-in-time query type is one of:

a current data query type;

a last-locked-revision-as-of-a-point-in-time query type;

a last-locked-revision-for-a-version-in-a-period query type;

an at-submission query type;

an at-lock query type;

or

a historical data query type.

6. The non-transitory computer-readable medium of claim 1, the implementing further comprising storing the point-in-time query within a query repository.

7. The non-transitory computer-readable medium of claim 6, the implementing further comprising:

modifying at least one of a point-in-time query type associated with the stored point-in-time query, or a date associated with the stored point-in-time query;

compiling the modified point-in-time query; and

executing the compiled modified point-in-time query.

8. The non-transitory computer-readable medium of claim 1, the implementing further comprising storing the case series in a case series repository.

9. The non-transitory computer-readable medium of claim 1, wherein the case series comprises one or more adverse event cases, and wherein each adverse event case comprises a data record that represents an adverse event.

10. The non-transitory computer-readable medium of claim 1, wherein the case series comprises one or more reports or patient identifiers that are related to the safety of one or more drugs.

11. A computer-implemented method for implementing a point-in-time query, the computer-implemented method comprising:

receiving a selection of a point-in-time query type, from one or more point-in-time query types, from a user;

retrieving metadata, from a repository, that comprises structured query language information based on the selected point-in-time query type;

creating a point-in-time query for a drug safety database based on the retrieved metadata and a date, the drug safety database including a plurality of adverse event records, each adverse event record including an effective end date indicating when a subsequent revision of the adverse event record was stored in the drug safety database, a patient identifier and drug safety data associated with a patient, the point-in-time query including a comparison of the date with the adverse event record effective end date;

compiling the point-in-time query to create a compiled point-in-time query; and

executing the compiled point-in-time query on the drug safety database to create a case series.

12. The computer-implemented method of claim 11, further comprising:

receiving a selection of the date from the user,

wherein each adverse event record includes an effective start date indicating when the adverse event record was stored in the drug safety database, and

wherein the point-in-time query further includes a comparison of the date with the adverse event record effective start date.

13. The computer-implemented method of claim 11, further comprising:

creating a user-defined point-in-time query type;

creating metadata, associated with the user-defined point-in-time query type, including structured query language information; and

storing the created metadata in the repository.

14. The computer-implemented method of claim 11, further comprising storing the point-in-time query within a query repository.

15. The computer-implemented method of claim 14, further comprising:

modifying at least one of a point-in-time query type associated with the stored point-in-time query, or a date associated with the stored point-in-time query;

compiling the modified point-in-time query; and

executing the compiled modified point-in-time query.

16. A system for implementing a point-in-time query, the system comprising:

a processor;

a memory configured to store one or more instructions;

a point-in-time query type selection module configured to receive a selection of a point-in-time query type, from one or more point-in-time query types, from a user;

a metadata retrieval module configured to retrieve metadata, from a repository, that comprises structured query language information based on the selected point-in-time query type;

a point-in-time query creation module configured to create a point-in-time query for a drug safety database based on the retrieved metadata and a date, the drug safety database including a plurality of adverse event records, each adverse event record including an effective end date indicating when a subsequent revision of the adverse event record was stored in the drug safety database, a patient identifier and drug safety data associated with a patient, the point-in-time query including a comparison of the date with the adverse event record effective end date;

a point-in-time query compilation module configured to compile the point-in-time query to create a compiled point-in-time query; and

a point-in-time query execution module configured to execute the compiled point-in-time query on the drug safety database to create a case series.

17. The system of claim 16, further comprising:

a date/time selection module configured to receive a selection of the date from the user,

wherein each adverse event record includes an effective start date indicating when the adverse event record was stored in the drug safety database, and

wherein the point-in-time query further includes a comparison of the date with the adverse event record effective start date.

18. The system of claim 16, further comprising:

a point-in-time query type creation module configured to create a user-defined point-in-time query type;

a metadata creation module configured to create metadata, associated with the user-defined point-in-time query type, including structured query language information; and

a metadata storage module configured to store the created metadata in the repository.

19. The system of claim 16, further comprising a point-in-time query storage module configured to store the point-in-time query within a query repository.

20. The system of claim 19, further comprising:

a point-in-time query modification module configured to modify at least one of a point-in-time query type associated with the stored point-in-time query, or a date associated with the stored point-in-time query,

wherein the point-in-time query compilation module is further configured to compile the modified point-in-time query, and

wherein the point-in-time query execution module is further configured to execute the compiled modified point-in-time query.