EP1350185A2 - Modele uml et representations xml d'images et de communications numeriques dans des rapports medicaux structures (dicom sr) - Google Patents

Modele uml et representations xml d'images et de communications numeriques dans des rapports medicaux structures (dicom sr)

Info

Publication number
EP1350185A2
EP1350185A2 EP01978388A EP01978388A EP1350185A2 EP 1350185 A2 EP1350185 A2 EP 1350185A2 EP 01978388 A EP01978388 A EP 01978388A EP 01978388 A EP01978388 A EP 01978388A EP 1350185 A2 EP1350185 A2 EP 1350185A2
Authority
EP
European Patent Office
Prior art keywords
uml
dicom
document
attribute
class
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Withdrawn
Application number
EP01978388A
Other languages
German (de)
English (en)
Inventor
Alfredo Tirado-Ramos
Jingkun Hu
Yasser Alsafadi
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Koninklijke Philips NV
Original Assignee
Koninklijke Philips Electronics NV
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Koninklijke Philips Electronics NV filed Critical Koninklijke Philips Electronics NV
Publication of EP1350185A2 publication Critical patent/EP1350185A2/fr
Withdrawn legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/25—Integrating or interfacing systems involving database management systems
    • G06F16/258—Data format conversion from or to a database
    • G—PHYSICS
    • G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
    • G16H30/00—ICT specially adapted for the handling or processing of medical images
    • G16H30/20—ICT specially adapted for the handling or processing of medical images for handling medical images, e.g. DICOM, HL7 or PACS
    • G—PHYSICS
    • G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
    • G16H30/00—ICT specially adapted for the handling or processing of medical images
    • G16H30/40—ICT specially adapted for the handling or processing of medical images for processing medical images, e.g. editing

Definitions

  • This invention relates to the field of modeling and data representation, and in particular to the modeling and representation of medical reports, via the use of DICOM SR relational data.
  • DICOM SR Digital Imaging and Communications in Medicine
  • SR Documentation Model upon which it is based, improves the expressiveness, precision, and comparability of documentation of diagnostic images and waveforms.
  • DICOM SR supports the interchange of expressive compound reports in which the critical features shown by images and waveforms can be denoted unambiguously by the observer, indexed, and retrieved selectively by subsequent reviewers. Findings may be expressed by the observer as text, codes, and numeric measurements, or via location coordinates of specific regions of interest within images or waveforms, or references to comparison images, sound, waveforms, curves, and previous report information.
  • the observational and historical findings recorded by the observer may include any evidence referenced as part of an interpretation procedure.
  • DICOM SR supports not only the reporting of diagnostic observations, but the capability to document fully the evidence that evoked the observations. This capability provides significant new opportunities for large- scale collection of structured data for clinical research, training, and outcomes assessment as a routine by-product of diagnostic image and waveform interpretation, and facilitates the pooling of structured data for multi-center clinical trials and evaluations.
  • the DICOM SR is based on a relational data technology, and has been standardized by the National Electrical Manufacturers Association (NEMA). Supplement 23: Structured Reporting Storage SOP Classes to the DICOM Standard, published by the DICOM Standards Committee, 1300 N. 17 th Street, Rosslyn, VA 22209 USA, introduces the SR Service-Object Pair (SOP) Classes for transmission and storage of documents that describe or refer to any number of images or waveforms or to the specific features that they contain, and is incorporated by reference herein. This standard is expected to be adopted by the medical equipment manufacturers and providers at large, to provide text, image, and waveform content in a structured reporting format.
  • NEMA National Electrical Manufacturers Association
  • DICOM SR standard provides for a consistent reporting and recording scheme
  • the use of the information contained in a DICOM SR is limited to DICOM compliant applications that can process this information using the DICOM specific format.
  • Application developers must be DICOM literate, and a methodology for deploying applications that interoperate with other applications outside the DICOM domain has not yet been developed.
  • the Object-Oriented processing paradigm is particularly well suited for facilitating the sharing of information, as well as the sharing of processes that use the information, among heterogeneous systems.
  • the Object Management Group (OMG) has formulated the Unified Modeling Language (UML) for exchanging information that is particularly well suited for Object-Oriented processing.
  • UML is a language for specifying, constructing, visualizing, and documenting objects produced within software- intensive systems, as well as for business modeling and other non-software systems.
  • the UML is independent of any particular programming language, but provides a formal and consistent basis for expressing, exchanging, and processing information within the context of the specified object-oriented model.
  • XML World Wide Web Consortium Extensible Markup Language
  • SGML Standard Generalized Markup Language
  • XML is used to describe information as well as structure, it is particularly well suited as a data description language.
  • the XML is a metalanguage that allows one to describe other languages, wherein the other languages include the definitions of how information in a document will appear in an application that displays it, and other details.
  • DTDs Document Type Definitions
  • UML and XML are relatively new and specialized languages, it can be expected that more programmers and other computer professionals will be familiar with UML and XML than those who are familiar with DICOM. Additionally, it can be expected that more general-purpose utilities and applications will be available for use on UML and XML encoded information than will be available for use on DICOM SR encoded information.
  • an object of this invention to provide a method and system that facilitates the creation of UML representations of DICOM SR representations and associated information. It is a further object of this invention to provide a method and system that facilitates the creation of XML representations of DICOM SR representations and associated information.
  • DICOM SR information from the DICOM relational model into an Object-Oriented representation.
  • a methodology is presented for converting the DICOM SR specification into a UML-based Object-Oriented representation of the specification, and for converting DICOM SR reports into UML-compatible representations.
  • open exchangeable representations using the World Wide Web Consortium XML DTD and Schema specifications are also provided.
  • This methodology for representing the DICOM SR specification provides a clear and comprehensive view of DICOM's semantically rich framework, its structures, and constructs.
  • FIG. 1 illustrates an example flow diagram for converting the DICOM SR specification into UML and XML representations that facilitate program development in accordance with this invention.
  • FIG. 2 illustrates an example flow diagram for converting the DICOM SR reports into UML and XML representations for processing by UML and XML enabled applications in accordance with this invention.
  • FIG. 3 illustrates an example DICOM SR to UML converter in accordance with this invention.
  • FIG. 4 illustrates an example flow diagram for converting a DICOM SR attribute to a UML attribute in accordance with this invention.
  • FIG. 5 illustrates an example flow diagram for converting a DICOM SR recursive data element to a set of UML elements in accordance with this invention.
  • FIG. 6 illustrates an example UML representation of a DICOM SR Information Object Definition (IOD) Module in accordance with this invention.
  • IOD Information Object Definition
  • FIG. 7A illustrates an example XML Document Type Definition (DTD) representation of a UML representation of a DICOM SR Information Object Definition (IOD) Module in accordance with this invention.
  • DTD Document Type Definition
  • IOD Information Object Definition
  • FIG. 7B illustrates an example XML Schema representation of a UML representation of a DICOM SR Information Object Definition (IOD) Module in accordance with this invention.
  • IOD Information Object Definition
  • FIG. 1 illustrates an example flow diagram for converting the DICOM SR specification 110 into UML 130 and XML 170 representations that facilitate program development in accordance with this invention.
  • applications can be developed that utilize DICOM's relational structured reporting scheme directly, it can be expected that the number of programmers and other computer professions who are familiar with UML and XML and object-oriented technologies and techniques will be substantially greater than those who are familiar with DICOM and relational technologies and techniques.
  • This invention is based on the premise that DICOM-related application programs can be more efficiently developed as UML and XML enabled applications.
  • This UML structure 130 can be used to facilitate the development 140 of an application program 150 that uses the UML structure 130, or it can be further converted, via converter 160, into elements of an.XML Document Type Definition (DTD) and/or an XML Schema, collectively illustrated at 170.
  • DTD Document Type Definition
  • XML Schema XML Schema
  • UML application program development 140 and the XML application program development 180 can be expected to require fewer resources than an application program development that uses the DICOM SR specification directly.
  • a number of UML and XML utility routines can be expected to be available for use in this development, based on the increasing use of UML and XML in the computer industry.
  • both UML and XML are object-oriented languages, and an objective of the object-oriented paradigm is to facilitate the transport and re-use of object-oriented software.
  • FIG. 2 illustrates an example flow diagram for converting the DICOM SR reports 210 into UML 230 and XML 270 documents for processing by the aforementioned UML 150 and XML 190 enabled applications, in accordance with this invention. That is, the programs 150, 190 whose development was facilitated by the DICOM converters 120, 160 of this invention, or other UML and XML programs, can be used to process individual DICOM SR reports 210, merely by converting the reports 210 into corresponding UML 230 and XML 270 documents.
  • the UML 150 or XML 190 applications may include, for example, applications that render 280 the content of the individual SR report 210 for viewing by a diagnostician, applications that transfer the content of the individual SR report 210 to processing facilities that do not have DICOM SR enabled applications, applications that collect the information from individual SR reports 210 and perform analyses for clinical studies, and so on.
  • FIG. 3 illustrates an example DICOM SR to UML converter 300.
  • Example DICOM entities 311- 317 are illustrated on the left of the converter 300, and corresponding UML entities 321-327 are illustrated on the right of the converter 300.
  • particular rules are associated with the various DICOM SR entity types to effect the conversion.
  • the DICOM SR includes five "Information Entities (IE)" 311: Patient, Study, Series, Equipment, and Document.
  • the rule for creating corresponding UML entities is to create a UML "Class” 321 corresponding each IE 311 , wherein the class assumes the same name as the corresponding IE, except that the UML class corresponding to the Patient IE is named "Patients", because, as discussed below, another DICOM entity also has the name "Patient”, whereas UML requires a unique naming of each class.
  • Alternative techniques for generating unique names, such as appending an incrementing numeral to a name, are common in the art.
  • the DICOM SR includes nine "Information Object Definition (IOD)
  • UML Modules Patient, Specimen Identification, General Study, SR Document Series, General Equipment, SR Document General, SR Document Content, and SOP Common.
  • the rule for creating corresponding UML entities is to create a UML "Class" 322 corresponding each IOD Module 312, wherein the class assumes the same name as the corresponding IOD module 312, except that blank spaces, if any are removed from the corresponding UML class name, because UML requires a single contiguous name for each class. Alternatively, a substitute character can be used to replace blank characters.
  • the DICOM SR includes "Macros" 313.
  • the rule for creating corresponding UML entities is to create a UML "Class” 323 corresponding each Macro 313, wherein the class assumes the same name as the corresponding Macro 313, except that blank spaces, if any, are removed from the corresponding UML class name, as well as the postfix "Macro", as illustrated in FIG. 3, wherein the DICOM SR "SOP Instance Macro" 313' is converted to a UML Class named "SOPInstance" 323'. Alternatively, a substitute character can be used to replace blank characters, and/or the Macro postfix can be retained.
  • the DICOM SR includes "Attributes” 314.
  • the rule for creating corresponding UML entities is to create a UML "Class Attribute” 324 corresponding each Attribute 314, respectively.
  • FIG. 4 illustrates an example flow diagram for converting DICOM SR Attribute names to UML Class Attribute names.
  • the DICOM SR attribute name is initially copied to form the UML attribute name, at 410, and converted to lower case, at 420.
  • each blank and hyphen character is identified, at 440, and replaced with an underscore character, at 450, and each apostrophe or bracket character is identified, at 460, and deleted from the UML attribute name, at 470.
  • the resultant UML attribute name is stored, at 490.
  • each DICOM SR sequence attribute 314' is mapped to a corresponding UML class attribute 324', using the rules illustrated in FIG. 4.
  • the sub- attributes 315 under a specific sequence 315' are mapped into class attributes 325 in a class 325' with the same name as the sequence, except that the postfix "Sequence” is removed.
  • the DICOM SR "Verifying Observer Sequence" 315' includes sub-attributes
  • DICOM defines a value representation (VR) for each attribute that offers a DICOM-internal primitive data type.
  • the DICOM value representations include: Application Entity (AE), Age String (AS), Attribute Tag (AT), Code String (CS), Date (DA), Decimal String (DS), Date Time (DT), Floating Point Single (FL) and Double (FD), and Integer String (IS).
  • AE Application Entity
  • AS Age String
  • AT Attribute Tag
  • CS Code String
  • DA Date
  • DS Date Time
  • DT Floating Point Single
  • FD Floating Point Single
  • FD Floating Point Single
  • IS Integer String
  • the DICOM SR includes a variety of "Constraints” 317, including mandatory, conditional, and other varieties.
  • the rule for creating corresponding UML entities is to map mandatory and conditional DICOM SR constraints to the UML stereotypes of "required” and “conditional”, respectively, and to map all other DICOM SR constraints into the UML stereotype of "optional”.
  • these DICOM SR constraints may be mapped to the UML via representations that are provided the Object Constraint Language (OCL) and others.
  • OCL Object Constraint Language
  • FIG. 5 A illustrates this recursion in the SR Document Content module 500, via the Document Relationship Macro 520.
  • the Document Relationship Macro 520 may include a Content module 530, and this Content module 530 may contain a document relationship 532 that includes another Content module 540, and so on.
  • the SR Document Content UML representation 560 includes elements DocumentRelationship 570 and DocumentContent 590, and the Document Relationship representation 570 and the Content representation 580 each reference each other, thereby effecting a recursive relationship.
  • DICOM SR specification documents and DICOM SR content documents are converted into a modeling language that is more often used by computer professionals, thereby providing the opportunity to ease the task and cost of producing application programs that can be used for processing DICOM related material.
  • FIG. 6 illustrates an example UML representation of portions of DICOM SR "SR Document General” Information Object Definition (IOD) Module, using the above described rules for converting DICOM SR elements into UML representations. Note that the representation of FIG. 6 is not an exhaustive representation of the DICOM SR "SR Document General" Information Object Definition (IOD) Module, using the above described rules for converting DICOM SR elements into UML representations. Note that the representation of FIG. 6 is not an exhaustive representation of the DICOM SR "SR
  • the upper-level block 610 illustrates the basic definition of the DICOM SR "SR Document General".
  • the UML "SRDocumentGeneral" class contains a number of sequences that are subsequently referenced as other UML classes 620, 630, and 640 that are related to the upper-level class 610 via the UML "uses" operator.
  • the classes may be nested, as illustrated by the class "ReferencedSeries” 650 which is used by the "SOPInstanceReference" 630.
  • a class 660, 670 may be used by a plurality of classes (620, 650) and (620, 640) respectively.
  • the UML representation that is provided by the converter 300 in accordance with this invention is further converted into an XML DTD and Schema representation, as shown in FIGs. 1 and 2, and further detailed below with regard to FIGs. 7A and 7B.
  • FIG. 7 A illustrates an example XML Document Type Definition (DTD) 701
  • FIG. 7B illustrates an example XML Schema 702, each corresponding to the example UML "SRDocumentGeneral" class 610 in FIG. 6.
  • the XML representation corresponding to a DICOM SR document is converted into an XML DTD 701 and XML Schema 702 via the following rules:

Landscapes

  • Engineering & Computer Science (AREA)
  • Health & Medical Sciences (AREA)
  • Databases & Information Systems (AREA)
  • Medical Informatics (AREA)
  • Primary Health Care (AREA)
  • Public Health (AREA)
  • Theoretical Computer Science (AREA)
  • General Health & Medical Sciences (AREA)
  • Nuclear Medicine, Radiotherapy & Molecular Imaging (AREA)
  • Radiology & Medical Imaging (AREA)
  • Epidemiology (AREA)
  • Physics & Mathematics (AREA)
  • Data Mining & Analysis (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Document Processing Apparatus (AREA)

Abstract

La présente invention concerne une technique de modélisation servant à convertir la spécification DICOM SR en une représentation de la spécification, orientée objet et à base UML, et à convertir des rapports DICOM SR en représentations UML-compatibles. Cette invention concerne également des représentations ouvertes à l'échange par l'intermédiaire du World Wide Web Consortium XML DTD, et des spécifications Schema, faisant intervenir l'utilisation de cette méthode. Cette méthode de représentation de spécification DICOM SR permet une visualisation claire et détaillée d'une syntaxe riche en DICOM d'un point de vue sémantique, de ses structures et de ses constructions. La mise en correspondance de DICOM SR et UML, XML DTD et Schema, permet aux concepteurs, analystes, et concepteurs d'architecture système de mieux comprendre la spécification DICOM SR et de mieux définir et concevoir des applications DICOM SR-compatibles.
EP01978388A 2000-10-10 2001-09-26 Modele uml et representations xml d'images et de communications numeriques dans des rapports medicaux structures (dicom sr) Withdrawn EP1350185A2 (fr)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US68640100A 2000-10-10 2000-10-10
US686401 2000-10-10
PCT/EP2001/011152 WO2002031688A2 (fr) 2000-10-10 2001-09-26 Modele uml et representations xml d'images et de communications numeriques dans des rapports medicaux structures (dicom sr)

Publications (1)

Publication Number Publication Date
EP1350185A2 true EP1350185A2 (fr) 2003-10-08

Family

ID=24756147

Family Applications (1)

Application Number Title Priority Date Filing Date
EP01978388A Withdrawn EP1350185A2 (fr) 2000-10-10 2001-09-26 Modele uml et representations xml d'images et de communications numeriques dans des rapports medicaux structures (dicom sr)

Country Status (4)

Country Link
EP (1) EP1350185A2 (fr)
JP (1) JP2004511853A (fr)
KR (1) KR20020056958A (fr)
WO (1) WO2002031688A2 (fr)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9535912B2 (en) * 2006-09-15 2017-01-03 Oracle International Corporation Techniques for checking whether a complex digital object conforms to a standard
CN103092594B (zh) * 2011-11-07 2016-01-20 金蝶软件（中国）有限公司 模型转换方法及装置
JP6151018B2 (ja) * 2012-12-25 2017-06-21 東芝メディカルシステムズ株式会社 医用情報管理装置

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5708828A (en) * 1995-05-25 1998-01-13 Reliant Data Systems System for converting data from input data environment using first format to output data environment using second format by executing the associations between their fields
US6260021B1 (en) * 1998-06-12 2001-07-10 Philips Electronics North America Corporation Computer-based medical image distribution system and method

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See references of WO0231688A2 *

Also Published As

Publication number Publication date
JP2004511853A (ja) 2004-04-15
WO2002031688A2 (fr) 2002-04-18
KR20020056958A (ko) 2002-07-10
WO2002031688A3 (fr) 2003-07-24

Similar Documents

Publication Publication Date Title
US7373596B2 (en) Precise UML modeling framework of the DICOM information model
US7373600B2 (en) DICOM to XML generator
US6725231B2 (en) DICOM XML DTD/schema generator
US7500185B2 (en) Framework of validating DICOM structured reporting documents using XSLT technology
Golbeck et al. The national cancer institute’s thesaurus and ontology
US6950985B2 (en) Specifying DICOM semantic constraints in XML
US7703007B2 (en) Importing and exporting markup language data in a spreadsheet application document
US20110023022A1 (en) Method for application authoring employing an application template stored in a database
US20060048107A1 (en) Enhanced compiled representation of transformation formats
CN101944162A (zh) 一种基于xml文档的电子病历模板系统及电子病历模板制作方法
Grundy et al. Domain-specific visual languages for specifying and generating data mapping systems
EP1350185A2 (fr) Modele uml et representations xml d'images et de communications numeriques dans des rapports medicaux structures (dicom sr)
O’Connor et al. Unleashing the value of Common Data Elements through the CEDAR Workbench
Gessner et al. Automated Transformation of CDISC ODM to OpenClinica.
Wielinga et al. Methods for porting resources to the semantic web
Narayanan et al. Specifications for mapping UML models to XML schemas
Riesmeier et al. A unified approach for the adequate visualization of structured medical reports
Clark et al. A structured interface to the object-oriented genomics unified schema for XML-formatted data
Zou Techniques and methodologies for the migration of legacy systems to object oriented platforms
CN116466931A (zh) 一种对象模型文件编辑方法、系统、设备和存储介质
Nedevschi et al. DICOM compliant environment for structured reporting in echocardiography
Ni Enumeration and traceability tools for UNIX™ and WINDOWS™ environments
Kuikka et al. A correspondence between UML diagrams and SGML/XML DTDs
Rumiński et al. Integrated, radiological database structure
Bosak et al. Universal Business Language (UBL) Naming and Design Rules 2.0

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

AK Designated contracting states

Kind code of ref document: A2

Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LI LU MC NL PT SE TR

17P Request for examination filed

Effective date: 20040126

17Q First examination report despatched

Effective date: 20050228

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN

18D Application deemed to be withdrawn

Effective date: 20080401