Precise UML modeling framework of the DICOM information model

• US 7,373,596 B2
• Filed: 08/01/2002
• Issued: 05/13/2008
• Est. Priority Date: 08/01/2002
• Status: Expired due to Fees

• Current Assignee: Koninklijke Philips Electronics N.V. (Koninklijke Philips N.V.)
• Original Assignee: Koninklijke Philips Electronics N.V. (Koninklijke Philips N.V.)
• Inventors: Tirado-Ramos, Alfredo, Lee, Kwok Pun, Hu, Jingkun
• Primary Examiner(s): DESAI, RACHNA SINGH
• Application Number:
  US10/210,520
• Publication Number:
  US 20040025110A1
• Time in Patent Office: 2,112 Days
• Field of Search: 715/513, 715/523
• US Class Current: 715/239
• CPC Class Codes: G16H 30/20 for handling medical images, e.g. DICOM, HL7 or PACS
• CPC Class Codes: G16H 50/50 for simulation or modelling of medical disorders

Abstract

A method for mapping a DICOM document into a UML document is disclosed and claimed by this invention. The method includes mapping each DICOM Information Entity in the DICOM document into a corresponding UML class in the UML document, mapping each DICOM IOD Module in the DICOM document into a corresponding UML class in the UML document, mapping each DICOM Macro in the DICOM document into a corresponding UML class in the UML document, and mapping each DICOM Attribute in the DICOM document into a corresponding UML attribute in the UML document. It also includes a UML profile for DICOM information model which guides the UML modeling for all the DICOM IODs. It can also guide the genertion of XML schemas and DTDs from UML models based on this profile.

Claims

1. A method for converting an electronic DICOM document into an electronic UML document utilizing a constrained UML profile, the method comprising the acts of:

converting each DICOM Information Entity in the DICOM document into a corresponding UML class in the UML document utilizing a naming convention based on a name of each DICOM Information Entity converted,

converting each DICOM IOD Module in the DICOM document into a corresponding UML class in the UML document utilizing a naming convention based on a name of each DICOM IOD Module converted,

converting each DICOM Macro in the DICOM document into a corresponding UML class in the UML document utilizing a naming convention based on a name of each DICOM Macro converted,

converting each DICOM Attribute in the DICOM document into a corresponding UML attribute in the UML document utilizing a naming convention based on a name of each DICOM Attribute converted, each act of converting based on the constrained UML profile, and

providing the electronic UML document, based on results from the converting acts, to at least one of a user, a storage device, and a UML processing system for processing.

2. The method as claimed in claim 1, wherein converting each DICOM Information Entity comprises the act of converting

each DICOM Information Entity into the corresponding UML class with a class name that corresponds to the Information Entity name.

3. The method as claimed in claim 1, wherein converting each DICOM IOD Module comprises the act of converting

each DICOM IOD Module into the corresponding UML class with a class name that corresponds to the module name modified to remove space characters if present in the module name.

4. The method as claimed in claim 1, wherein converting each DICOM IOD Module comprises the act of converting

each DICOM Macro name having a “

Macro”

postfix into the corresponding UML class with a class name that corresponds to the macro name modified to remove the “

Macro”

postfix.

5. The method as claimed in claim 1, where in

each DICOM Sequence has a name, the method comprising the act of converting each DICOM Sequence into a corresponding UML class with a UML class name that corresponds to a Sequence name, wherein the UML class has two UML attributes in XSDattribute stereotype representing a DICOM tag and a DICOM name of each DICOM Sequence based on the constrained UML profile.

6. The method as claimed in claim 1, wherein converting each DICOM Attribute comprises the act of converting

each DICOM Attribute into the corresponding UML attribute with a UML attribute name that corresponds to the DICOM Attribute name,

modified to replace each upper case letter in the DICOM Attribute name with a corresponding lower case letter,

modified to replace each blank space in the DICOM Attribute name with an underscore character,

modified to replace each hyphen character in the DICOM Attribute name with an underscore character,

modified to remove each apostrophe character from the DICOM Attribute name,

modified to remove each bracket character from the DICOM Attribute name, and,

each UML attribute has its associated types capturing its DICOM type, DICOM tag, and DICOM Name.

7. A computer program, stored on a computer readable medium, the computer program configured to be executed on a computer system and is configured to receive a DICOM document and produce a UML document by the method of claim 1.

8. A method for electronically converting a DICOM atomic attribute into a UML class attribute utilizing a constrained UML profile, the method comprising the acts of:

copying each lower case letter from the atomic attribute to the class attribute,

converting each upper case letter from the atomic attribute to a corresponding lower case letter of the class attribute,

converting each blank space from the atomic attribute to an underscore character of the class attribute,

converting each hyphen character from the atomic attribute to an underscore character of the class attribute, and

providing the UML class attribute, based on results from the converting acts, to at least one of a user, a storage device, and a UML processing system for processing.

9. A DICOM to Object-Oriented-representation converter stored in a memory, comprising:

an DICOM document to UML document converter that is configured convert an electronic DICOM document into an electronic UML document utilizing a constrained UML package, the converter further configured to;

convert each DICOM Information Entity in the DICOM document into a corresponding UML class in the UML document utilizing a naming convention based on a name of each DICOM Information Entity converted,

convert each DICOM IOD Module in the DICOM document into a corresponding UML class in the UML document utilizing a naming convention based on a name of each DICOM IOD Module converted,

convert each DICOM Macro in the DICOM document into a corresponding UML class in the UML document utilizing a naming convention based on a name of each DICOM Macro converted,

convert each DICOM Attribute in the DICOM document into a corresponding UML attribute in the UML document utilizing a naming convention based on a name of each DICOM Attribute converted, wherein the converting is based on the constrained UML package, and

provide the electronic UML document, based on results of the converting, to at least one of a user, a storage device, and a UML processing system for processing.

10. The converter of claim 9, wherein each UML atomic attribute is converted from a corresponding DICOM Element with four attributes:

coding_scheme, code_id, type, and value.

11. The converter of claim 9, further comprising:

a UML document to DICOM document converter that is configured to;

map each UML class in the UML document into a corresponding DICOM DTD element.

map each UML class attribute in the UML document into a corresponding DICOM DTD element,

map each UML association and uses relationship in the UML document into a corresponding DICOM DTD element, and

map each UML atomic attribute class in the UML document into a corresponding DICOM element.

12. The converter of claim 11, wherein the DICOM document to UML document converter is further configured to:

convert each DICOM recursive element into a corresponding pair of UML elements that reference each other.