System for Adaptively Querying a Data Storage Repository

• US 20080222121A1
• Filed: 06/01/2007
• Published: 09/11/2008
• Est. Priority Date: 06/02/2006
• Status: Abandoned Application

• Current Assignee: Siemens Medical Solutions USA Incorporated (Siemens AG)
• Original Assignee: Siemens Medical Solutions USA Incorporated (Siemens AG)
• Inventors: Owens, Steven F., Datta, Debarshi, Wiessler, Wolfgang
• Application Number:
  US11/756,886
• Publication Number:
  US 20080222121A1
• Time in Patent Office: Days
• US Class Current: 707/4
• CPC Class Codes: G06F 16/258 Data format conversion from or to a database
• CPC Class Codes: G06F 16/8358 Query translation

Abstract

An input processor receives a plurality of different first query messages in a corresponding plurality of different formats. A repository includes stored data elements in a first storage data structure. An intermediary processor automatically: parses the plurality of first query messages to identify requested data elements; maps the identified requested data elements to stored data elements in the first storage data structure of the repository; generates a plurality of second query messages in a format compatible with the repository for acquiring the stored data elements; acquires the stored data elements from the repository using the generated plurality of second query messages; and processes the acquired stored data elements in the plurality of second query messages for output in a format compatible with the corresponding plurality of different formats of the first query messages.

Claims

1. A system for adaptively querying a data storage repository, comprising:

an input processor for receiving a plurality of different first query messages in a corresponding plurality of different formats;

a repository of stored data elements in a first storage data structure; and

an intermediary processor for automatically performing the activities of;

parsing said plurality of first query messages to identify requested data elements,

mapping said identified requested data elements to stored data elements in said first storage data structure of said repository,

generating a plurality of second query messages in a format compatible with said repository for acquiring said stored data elements,

acquiring said stored data elements from said repository using said generated plurality of second query messages, and

processing said stored data elements acquired in response to said plurality of second query messages for output in a format compatible with said corresponding plurality of different formats of said first query messages.

2. A system according to claim 1, wherein said intermediary processor automatically performs said activities by embodying information related to said activities in at least one file comprising data describing details related to performing said activities.

3. A system according to claim 2, wherein said at least one file comprises a core schema file comprising data defining said requested data elements.

4. A system according to claim 3, wherein said core schema file comprises data defining respective names of said requested data elements.

5. A system according to claim 3, wherein said at least one file comprises a extension schema file comprising data defining further requested data elements.

6. A system according to claim 5, wherein said extension schema file comprises data defining respective names of said requested data elements.

7. A system according to claim 2, wherein said at least one file comprises an output schema file comprising data specifying respective relationships among said requested data elements.

8. A system according to claim 2, wherein said output schema file comprises data defining an output hierarchy.

9. A system according to claim 8, wherein said output schema file comprises data defining requested data elements.

10. A system according to claim 9 wherein said output schema file comprises data defining levels, said level defining data comprising data defining requested data elements and data defining requested data defined in other levels.

11. A system according to claim 2, wherein said at least one file comprises a mapping file comprising data specifying the correspondence among requested data elements and data elements in the storage data structure in the repository.

12. A system according to claim 11, wherein said mapping file comprises data relating a requested data element to a table in said storage data structure in said repository, and data relating said requested data element to a field in said table in said storage data structure in said repository.

13. A system according to claim 2, wherein said at least one file comprises a resource file comprising data specifying external data sources in said repository.

14. A system according to claim 13, wherein said resource file comprises data for accessing said external source.

15. A system according to claim 14 wherein said data for accessing said external source is output is a format compatible with said corresponding plurality of different formats of said first query messages.

16. A system according to claim 2, wherein said at least one file comprises a query schema file comprising data defining the respective content and structure of said first query messages.

17. A system according to claim 16, wherein said at least one file comprises a query file comprising data defining said first query messages.

18. A system according to claim 1, wherein said intermediary processor automatically performs said activities without re-compiling executable code used in performing said activities.

19. A system according to claim 1, wherein said intermediary processor automatically performs said activities without re-testing executable code used in performing said activities.

20. A system according to claim 1, wherein:

said first query messages comprise query files conforming to a query schema; and

said second query messages comprise queries executable by said repository.

21. A system according to claim 1, wherein said first query messages are in a format determined by a query schema and comprising at least one of, (a) SQL compatible query format and (b) XQuery compatible query format.

22. A system according to claim 7, wherein said query schema determines at least one of, (a) query search depth of hierarchical data elements in said repository and (b) restrictions on searching said repository.

23. A system according to claim 1, wherein said format compatible with said corresponding plurality of different formats of said first query messages are determined by an output schema.

24. A system according to claim 1, further comprising data determining a core schema indicating data fields accessible in said first storage data structure in said repository of stored data elements.

25. A system according to claim 1, further comprising a mapping schema determining said mapping of said identified requested data elements to said stored data elements in said first storage data structure of said repository.

27. A system according to claim 10, wherein said instruction determining said data format for providing said information comprises a markup language output schema.

28. A system according to claim 10, wherein said markup language output schema is an XML schema.

26. A system for adaptively querying a data storage repository, comprising:

an input processor for receiving at least one first query message comprising a request for information and an instruction determining a data format for providing said information, said instruction being alterable to adaptively change said information and said data format for providing said information;

a repository of stored data elements in a first storage data structure; and

an intermediary processor for automatically performing the activities of;

parsing said at least one first query message to identify requested data elements,

mapping said identified requested data elements to stored data elements in said first storage data structure of said repository,

generating at least one second query message in a format compatible with said repository for acquiring said stored data elements,

acquiring said stored data elements from said repository using said generated at least second query messages, and

processing said stored data elements acquired in response to said at least one second query message for output in a format compatible with said data format determined by said instruction in said at least one first query message.