INTEROPERABLE CASE SERIES SYSTEM

• US 20140122121A1
• Filed: 03/08/2013
• Published: 05/01/2014
• Est. Priority Date: 10/31/2012
• Status: Abandoned Application

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: TRIEBEL, William Andrew, BRAUN-BOGHOS, Michael Lawrence
• Application Number:
  US13/790,379
• Publication Number:
  US 20140122121A1
• Time in Patent Office: Days
• US Class Current: 705/3
• 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 integrates a case series repository with one or more software applications. The system receives a case series, where the case series includes one or more adverse event cases, and the system further receives a case revision, where the case revision includes case revision information. The system further stores the case series and the case revision within a case series repository using a case series data model. The system further associates the case revision with the case series using the case series data model. The system further retrieves the case series and the associated case revision using a case series programming interface.

Claims

1. A computer-readable medium having instructions stored thereon that, when executed by a processor, cause the processor to integrate a case series repository with one or more software applications, the integrating comprising:

receiving a case series, 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;

receiving a case revision, wherein the case revision comprises case revision information, and wherein the case revision information comprises at least one change to an adverse event case of the case series;

storing the case series and the case revision within a case series repository using a case series data model, wherein the case series data model defines a format of the case series and the case revision within the case series repository;

associating the case revision with the case series using the case series data model; and

retrieving the case series and the associated case revision using a case series application programming interface, wherein the case series application programming interface defines a format of the case series and the associated case revision for a software application.

2. The computer-readable medium of claim 1, wherein the case series data model comprises a data field that represents one or more case identifiers of the case series, and one or more additional data fields that represent the one or more adverse event cases of the case series, and wherein each case identifier uniquely identifies an adverse event case of the one or more adverse event cases.

3. The computer-readable medium of claim 2, wherein the case series data model comprises one or more additional data fields that represent the case revision information.

4. The computer-readable medium of claim 1, wherein the case revision information comprises timestamp information that identifies the case revision.

5. The computer-readable medium of claim 4, wherein the timestamp information comprises a valid start date and/or time and a valid end date and/or time;

and

wherein the case series data model comprises one or more additional data fields that represent the timestamp information.

6. The computer-readable medium of claim 1, the integrating further comprising:

creating a change log, wherein the change log comprises case series history information, and wherein the case series history information comprises information regarding the history of the case series;

storing the change log within the case series repository using the case series data model, wherein the case series data model defines a format of the change log within the case series repository; and

associating the change log with the case series using the case series data model.

7. The computer-readable medium of claim 1, the integrating further comprising:

creating an annotation, wherein the annotation comprises user-defined information;

storing the annotation within the case series repository using the case series data model; and

associating the annotation with the case revision using the case series data model.

8. The computer-readable medium of claim 1, the integrating further comprising:

creating a folder, wherein the folder comprises a logical organization of the case series, and one or more additional case series;

storing the folder within the case series repository using the case series data model; and

associating the case series with the folder using the case series data model.

9. The computer-readable medium of claim 1, wherein the case series comprises one of:

a named case series;

an active user case series;

a single-use case series;

or a case hit list.

10. The computer-readable medium of claim 1, wherein the case series comprises one of:

an event series;

or a product series.

11. The 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.

12. The computer-readable medium of claim 1, wherein the case series comprises a plurality of case revisions.

13. A computer-implemented method for integrating a case series repository with one or more software applications, the computer-implemented method comprising:

receiving a case series, 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;

receiving a case revision, wherein the case revision comprises case revision information, and wherein the case revision information comprises at least one change to an adverse event case of the case series;

storing the case series and the case revision within a case series repository using a case series data model, wherein the case series data model defines a format of the case series and the case revision within the case series repository;

associating the case revision with the case series using the case series data model; and

retrieving the case series and the associated case revision using a case series application programming interface, wherein the case series application programming interface defines a format of the case series and the associated case revision for a software application.

14. The computer-implemented method of claim 13, wherein the case series data model comprises a data field that represents one or more case identifiers of the case series, and one or more additional data fields that represent the one or more adverse event cases of the case series, and wherein each case identifier uniquely identifies an adverse event case of the one or more adverse event cases.

15. The computer-implemented method of claim 14 wherein the case series data model comprises one or more additional data fields that represent the case revision information.

16. The computer-implemented method of claim 13, wherein the case revision information comprises timestamp information that identifies the case revision.

17. The computer-implemented method of claim 16, wherein the timestamp information comprises a valid start date and/or time and a valid end date and/or time;

and

wherein the case series data model comprises one or more additional data fields that represent the timestamp information.

18. A system for integrating a case series repository with one or more software applications, the system comprising:

a processor;

a memory configured to store one or more instructions;

a case series reception module configured to receive a case series, 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;

a case revision reception module configured to receive a case revision, wherein the case revision comprises case revision information, and wherein the case revision information comprises at least one change to an adverse event case of the case series;

a storage module configured to store the case series and the case revision within a case series repository using a case series data model, wherein the case series data model defines a format of the case series and the case revision within the case series repository;

an association module configured to associate the case revision with the case series using the case series data model; and

a retrieval module configured to retrieve the case series and the associated case revision using a case series application programming interface, wherein the case series application programming interface defines a format of the case series and the associated case revision for a software application.

19. The system of claim 18, wherein the case series data model comprises a data field that represents one or more case identifiers of the case series, and one or more additional data fields that represent the one or more adverse event cases of the case series, and wherein each case identifier uniquely identifies an adverse event case of the one or more adverse event cases.

20. The system of claim 19 wherein the case series data model comprises one or more additional data fields that represent the case revision information.

21. The system of claim 18, wherein the case revision information comprises timestamp information that identifies the case revision.

22. The system of claim 21, wherein the timestamp information comprises a valid start date and/or time and a valid end date and/or time;

and

wherein the case series data model comprises one or more additional data fields that represent the timestamp information.