1 / 16

UML Modeling and XML Representation of DICOM SR

Exploring the integration of UML modeling with XML to represent DICOM SR information models, discussing processes, XML DTD, SR XML documents, and their validation. Conclusions on the advantages, limitations, and potential solutions.

scotthughes
Download Presentation

UML Modeling and XML Representation of DICOM SR

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. UML Modeling and XML Representation of DICOM SR Jingkun Hu, KP Lee, Doug Sluis, Alfredo Tirado-Ramos June 8, 2001

  2. Outline • Why UML modeling • Modeling processes • Why XML • XML DTD • SR XML documents and their validation • Conclusions

  3. Why UML Modeling • Help to understand DICOM SR information model • Bridge from DICOM to non-DICOM world, e. g., HL7 CDA. • Bridge from entity-relationship (E-R) tables to XML DTDs or schemas

  4. UML Modeling Processes • DICOM IOD is mapped to class • Each IE is mapped to a class • Each Module is mapped to a class • Each Macro is mapped to a class • All attributes, Macros, and sequences under a sequence are mapped to the members of a class.

  5. UML Modeling Processes (Cont) • Naming rules for a class • Capitalize the first letter of a single word • Remove the white space • Naming rules for an attribute • change all the upper case letters to lower case • replace the blank space between two words with an underscore • remove apostrophes and brackets • replace hyphen (-) and slash (/ or \) with an underscore.

  6. UML Modeling Processes (Cont) • Usage • M (mandatory) : required • U (user defined) : optional • Type • Type 1 and type 2 : required • Type 1C, Type 2C, and Type 3: optional

  7. UML Modeling Processes (Cont) • VRs (value representation)

  8. Modeling Results • Comprehensive SR IOD • Patient IE • Study IE • Series IE • Equipment IE • Document IE • Complete Model for Comprehensive SR IOD

  9. Limitations Cannot represent: • Conditions • Tag information: e. g., tag, VR • Rich DICOM VRs: different types of string • The number of items within a sequence

  10. Why XML • Web browser is the most popular viewer • XML is web supported • XML defines a universal exchange format

  11. XML DTD for DICOM SR • Generate automatically with XML toolkit • It is almost unreadable • Generate manually with XML Authority toolkit together with the UML model • Added detailed DICOM tag information, e.g., tag, type, and meaning, as attributes

  12. SR XML DTD • The complete SR XML DTD • A sample SR XML document based on this DTD and content of an SR specification • Document validation

  13. Limitations • Cannot represent attribute information such as tag, usage, value representation • Cannot represent constraints conditions • Demonstration What’s the solution to it? An answer is XML Schema

  14. SR XML Schema • Work in Progress • SR XML schemas • Automatic generation of Schema from Spec.

  15. Conclusions • SR UML class models ease understanding of DICOM SR • SR XML DTDs can represent DICOM SR structure clearly • DTD cannot represent rich DICOM VRs and constraints • Current approach: XML Schemas

  16. Q & A Thankyou!

More Related