Ndma db schema, dicom to relational schema translation, and xml to sql query transformation

• US 20060282447A1
• Filed: 06/04/2004
• Published: 12/14/2006
• Est. Priority Date: 06/04/2003
• Status: Abandoned Application

• Current Assignee: Trustees Of The University Of Pennsylvania (University of Pennsylvania)
• Original Assignee: Trustees Of The University Of Pennsylvania (University of Pennsylvania)
• Inventors: Hollebeek, Robert J.
• Application Number:
  US10/559,248
• Publication Number:
  US 20060282447A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/86 Mapping to a database
• CPC Class Codes: G16H 10/60 for patient-specific data, e.g. for electronic patient records
• CPC Class Codes: G16H 30/20 for handling medical images, e.g. DICOM, HL7 or PACS
• CPC Class Codes: G16H 30/40 for processing medical images, e.g. editing

Abstract

A translation scheme translates DICOM content into a format compatible for storage in an NDMA relational database. The translation scheme employs a schema for indexing the DICOM content, and employs a mechanism for translating queries embedded in XML into SQL. The translation scheme translates DICOM compatible data into a tab delimited flat representation of the DICOM content. The flat representation is then translated into data compatible with a relational database format, such as SQL, and then into database insert commands. The schema enables capture of the DICOM information into relational tables. Methods are also provided to service XML formatted research and clinical queries, to translate XML queries to optimized SQL and to return query results to XML specified destinations with record de-identification where required. Methods are also provided to interface to NDMA WallPlugs, secured query devices, or GRID devices.

Claims

1. A method for transforming digital imaging and communications in medicine (DICOM) compatible data into national digital mammography archive (NDMA) relational database compatible data, said method comprising the steps of:

transforming said DICOM compatible data into data formatted in accordance with an intermediate format; and

transforming said intermediate formatted data into data compatible with said NDMA compatible relational database.

2. A method in accordance with claim 1, further comprising the steps of:

parsing searchable and indexable elements of a DICOM header of said DICOM compatible data; and

transforming said parsed elements into components of said intermediate format.

3. A method in accordance with claim 2, further comprising the step of:

transforming each of said components of said intermediate format into one of a table indicator, a column indicator and a command compatible with said relational database.

4. A method in accordance with claim 3, further comprising the steps of:

associating each column of said relational database with a database table in accordance with a level of interest of DICOM compatible data in said column.

5. A method in accordance with claim 4, wherein said level of interest includes at least one of:

a first level of interest indicative of DICOM compatible data most likely to be queried;

a second level of interest indicative of DICOM compatible data less likely to be queried than said first level of interest; and

a third level of interest indicative of DICOM compatible data that is not included in said first and second levels of interest.

6. A method in accordance with claim 5, wherein:

DICOM compatible data belonging to said third level is indexable in said database.

7. A method in accordance with claim 1, wherein said DICOM compatible data comprises extensible markup language (XML) formatted text, said method further comprising the step of transforming said XML formatted text into data compatible with said NDMA compatible relational database.

8. A method in accordance with claim 7, wherein said XML text comprises XML requests and said relational database supports structured query language (SQL) queries contained in said XML requests.

9. A method in accordance with claim 1, wherein:

said DICOM compatible data comprises at least one of NDMA protocol wrapped DICOM data, DICOM structured reports, selected DICOM compatible data, and an Open Grid Standard compatible request.

10. A method in accordance with claim 9, wherein:

said Open Grid Standard compatible request comprises at least one of a service request, a storage request, and a retrieval request.

11. A method in accordance with claim 1, wherein said intermediate format comprises a tab delimited flat representation of said DICOM compatible data.

12. A method in accordance with claim 11, further comprising the step of serializing, wherein said intermediate format is serializable.

13. A method in acccordance with claim 11, wherein said intermediate format comprises:

a group and element indicator indicative of a group and element, respectively, to which said DICOM compatible data belongs;

a length indicator indicative of a length of said DICOM compatible data;

a value representation of said DICOM data; and

a description of said DICOM compatible data.

14. A method in accordance with claim 13, wherein said DICOM compatible data comprises at least one group/element pair, said method further comprising for each pair:

translating DICOM items into table column names;

appending an identifier “

H”

to a beginning of each group;

appending an identifier “

H”

to a beginning of each element;

concatenating said appended group and said appended element; and

associating each concatenated group/concatenated element with a column of a relational database.

15. A method in accordance with claim 1, wherein:

only authorized DICOM compatible data is transformed; and

authorized DICOM compatible data is transformed into selected relational database indicators to ensure efficient querying of said relational database.

16. A method in accordance with claim 1, wherein DICOM compatible data is transformed for only authorized enterprises.

17. A method in accordance with claim 1, wherein:

responsive to a clinical query for transformed DICOM compatible data, DICOM compatible data having patient identification information is provided; and

responsive to a research query for transformed DICOM compatible data, de-identified DICOM compatible data is provided.