Oracle Corporation and its affiliates disclaim any responsibility for any harm caused by the use of this software in dangerous applications. This software and documentation may provide access to or information on content, products and services from third parties.
List of Examples
List of Tables
Preface
Audience
Documentation Accessibility
Related Documents
For more information about medical imaging standards, see the documentation provided by the National Electrical Manufacturers Association (NEMA). For more information about Java, including information about Java Advanced Imaging (JAI), see the API documentation provided by Sun Microsystems.
Conventions
Many of the examples in this manual are based on the database user PM and the tables MEDICAL_IMAGE_OBJ and MEDICAL_IMAGE_REL, which are created in the Product Media (PM) example schema. See Oracle Database Sample Schemas for information about how these schemas are installed and how you can use them.
Syntax Descriptions
What’s New in Oracle Multimedia DICOM
New Features for Release 11.2
Medical Imaging and Communication
Since then, the DICOM standard has become the dominant standard for radiological imaging and communication. The DICOM standard has two main areas of focus: the data model (or file format) and the communication protocol.
Oracle Multimedia and DICOM
- Oracle Multimedia DICOM Format Support
- ORDDicom Object Type
- DICOM Metadata Extraction
- DICOM Conformance Validation
- DICOM Image Processing
- Making Private DICOM Content Anonymous
- Creating ORDDicom Objects from Images or Video and Metadata
- Run-Time, Updatable DICOM Data Model
With Oracle Database 11g Release 1 (11.1), support for conformance checking is provided, allowing customers to verify that DICOM content adheres to a set of user-defined restriction rules. For example, clinicians require full access to DICOM content and metadata for every patient they treat.
Oracle Multimedia DICOM Architecture
At the client level, the ability to access ORDDicom objects in the database is supported through the Oracle Multimedia DICOM Java API. See the Oracle Multimedia DICOM Java API Reference for information on using Oracle Multimedia DICOM with Java.
Oracle Multimedia DICOM Storage
DICOM content (element 3), which is the original DICOM content in unmodified form, stored in the database, under transaction control as a BLOB. recommended) or stored in an operating system-specific file on the local file system with pointers stored in the database. Figure 2-3 shows the structure of a simple table in a medical database containing an ORDDicom object.
Model-Driven Design
The points above the dashed line show the parts of the data model that are related to the metadata extraction function. The points below the dashed line show the software runtime components of the extract metadata function accessing the data model.
DICOM Data Model Repository
- Configuration Documents in the Repository
- Administrator and User Sessions in the Repository
The data model is at State 1, reflecting the published changes from edit session XG1. The data model is now at State 1, reflecting the published changes from edit session XG1.
Extraction of Metadata from DICOM Content
If the extract option is associated (item 4), only associated attributes are included in the XML metadata document. If the extract option is all (item 6), then all attributes included in the DICOM content are extracted and encoded into the XML metadata document.
Validation of DICOM Content
After a constraint document is inserted into the repository, users can validate DICOM content against the general constraint rules defined in the constraint document. For example, users can verify that the DICOM content conforms to the installed global constraint rule named OracleOrdDicomImage.
Image Conversion and Creation of New DICOM Content
Using an image, such as an ORDImage object, that stores a JPEG file, TIFF file, or other supported image file (item 4) and a DICOM metadata document (item 5), the image converter can merge the two elements and produce DICOM -content that can be used to create a new ORDDicom object (item 1). Similarly, the image converter (element 2) can copy and convert the DICOM content (element 4) and an XML metadata document (element 5) into a new ORDDicom object (element 1).
Making DICOM Content Anonymous
The delete action is the default action that deletes an attribute or sets it to zero length in the DICOM content and in the ORDDicom object attributes. The replace action replaces an attribute with a string, which can either be empty or contain a user-defined string in the DICOM content and in the ORDDicom object attributes.
Extraction of DICOM Metadata for Partitioning
Standard Dictionary Documents - XML documents that can be used to represent updates to the DICOM standard. UID definition documents - XML documents that contain the unique identifiers (UIDs) defined by the DICOM standard.
Loading the Repository
Preference documents - XML documents that define runtime parameters, such as enabling or disabling the logging of warning messages or specifying error message categories. Private dictionary documents - XML documents that can be used to extend standard dictionary document definitions.
Accessing Information About Documents in the Repository
Users (and administrators) typically use orddcm_documents and. orddcm_document_types views to view the details of the documents in the repository. The orddcm_constraint_names view lists the names of the constraints installed in the repository.
Loading DICOM Content
The orddcm_conformance_vld_msgs view lists the constraint messages that are generated for a constraint set during a validation operation. This view lists documents in the repository that are referenced by other documents in the repository.
Extracting DICOM Metadata
- Extracting Metadata - Administrator Tasks
- Extracting Metadata - Developer Tasks
The default XML metadata schema defines a complete and generalized data model for storing DICOM attributes. Store the returned XML metadata document in a column in the database associated with the application-specific XML schema for later retrieval.
Searching and Retrieving DICOM Attributes
Writing and Editing DICOM Metadata
Call the writeMetadata() method to write a modified copy of the metadata and DICOM content XML document from the original ORDDicom object to the newly created ORDDicom object. The metadata XML document is used to overwrite the metadata in the DICOM content and object attributes of the new ORDDicom object.
Processing, Converting, and Compressing DICOM Image Data
Creating DICOM Content from Secondary Capture Images and Video
Validating Conformance with DICOM Constraints
- Validating Conformance - Administrator Tasks
- Validating Conformance - Developer Tasks
Example 3–1 shows the constraint rule for the patient module of the DICOM standard, which is defined in the ordcmcmd.xml constraint document installed by Oracle. If your DICOM content does not meet the throttling rules defined for your organization, you have the option of writing another ORDDicom object with corrected DICOM metadata.
Protecting Private Patient Data
- Protecting Privacy - Administrator Tasks
- Protecting Privacy - Developer Tasks
Create an empty ORDDicom object using the empty ORDDicom constructor if you plan to call the makeAnonymous( ) method. Call the makeAnonymous( ) method to copy and make the original ORDDicom object anonymous, and then write the new DICOM content to the empty ORDDicom object.
Improving Storage and Performance When Extracting DICOM Attributes
This chapter describes the functions, procedures, and views of information in the DICOM Data Model Auxiliary Interface that operates in the DICOM Data Model Repository.
DICOM Data Model Utility Functions and Procedures
Description
Parameters
Pragmas
Exceptions
Usage Notes
DICOM Repository Public Information Views
ORDDicom Object Examples
- Directory Definition and Setup
- MEDICAL_IMAGE_OBJ Table Definition
The examples in this chapter use the MEDICAL_IMAGE_OBJ table, which these examples create in the sample product media (PM) schema. For example, you can use the SQL*Loader utility, a Java client, or the import( ) method. Before loading data into the table, you must create the table and the columns where the data will be stored.
Note: If you are manipulating the DICOM content itself (either by directly modifying the BLOB or modifying an external source), call the setProperties() method to ensure that the object's attributes remain in sync.
ORDDicom Object Type
ORDDicom Constructors
ORDDicom( ) for BLOBs
ORDDicom( ) for ORDImage
ORDDicom( ) for Other Sources
ORDDicom Methods
The UID is commonly constructed with a root that uniquely identifies the organization producing the DICOM content and a suffix that uniquely identifies the DICOM content of that organization.
Examples for DICOM Relational Functions and Procedures
- Directory Definition and Setup
- MEDICAL_IMAGE_REL Table Definition
The functions and procedures for the relational DICOM interface described in this chapter show examples based on the MEDICAL_IMAGE_REL table, which these examples create in the Product Media (PM) sample schema. Before you can use the DICOM relational interface functions and procedures, you must load some data into the table.
DICOM Relational Functions
DICOM Relational Procedures
Setting Up Your Environment
Creating a Table with an ORDDicom Column
Loading DICOM Content Using the SQL*Loader Utility
The LocalData LOB will hold the content for the DICOM data to be anonymized. Before calling the SQL*Loader program, you can temporarily disable logging for LOB data to be loaded into the dicom column. Disabling logging can reduce the amount of time it takes to load DICOM data by halving the amount of I/O that will be performed.
After the DICOM data is loaded into the table from the external files, another program is required to complete the dicom column initialization and generate the data to populate the imageThumb and anonDicom columns. And, the anonDicom column object is created using the makeAnonymous( ) method, which requires a unique identifier for one of its input arguments. Example 7–3 defines a genUID( ) function to generate a unique identifier (UID) by concatenating the id column value with a root DICOM UID value that you must define.
Call the ORDDicom method processCopy() to create a JPEG thumbnail image -- which is stored in the imageThumb column. And the third pass creates an anonymous DICOM image to store in the anonDicom column. Because of these repeated read operations, you may want to change the LOB storage property of the dicom column to enable caching of the DICOM content.
Developing DICOM Applications Using the PL/SQL API
- Selecting DICOM Attributes
See Oracle Database Utilities for more information about using the SQL*Loader tool to load objects and LOBs into Oracle Database.
- Creating Thumbnail Images and Changing Image Formats
- Making Anonymous Copies of ORDDicom Objects
- Checking the Conformance of ORDDicom Objects
- Handling Oracle Multimedia DICOM Exceptions in PL/SQL
- Developing DICOM Applications Using the DICOM Java API
- Setting Up Your Environment Variables
- Importing Oracle Java Classes into Your Application
- Handling Oracle Multimedia DICOM Exceptions in Java
- Overview of the DICOM Sample Application
- Description of the DICOM Sample Application
- Logging In to the DICOM Image Archive Interface
- Searching for Specific DICOM Images
- Importing DICOM Images as a Clinician
- Processing DICOM Images as a Researcher
- Logging In to the DICOM Image Archive Administration Interface
- Inserting Configuration Documents
- Assigning Administrator Roles and Privileges
- Managing XML Schemas
- Registering XML Schemas
- Finding User-Defined XML Schemas
- Loading the Data Model Repository
- Browsing the Repository with Information Views
- Exporting Documents from the Repository
- Inserting Documents into the Repository
- Inserting Anonymity, Mapping, and Constraint Documents
- Inserting Dictionary Documents
- Inserting Preference and UID Definition Documents
Administrators are automatically logged in when accessing the DICOM Image Archive Administration interface. Table 8–2 lists all the administrator tasks that are demonstrated in the DICOM Image Archive Administration interface of the DICOM sample application. Exporting documents from the DICOM repository (Download) Inserting documents into the DICOM repository (Add) Deleting documents from the DICOM repository (Delete).
Using the example of the keyword search for dental images, enter the term jaw in the Semantic field on the DICOM Image Archive Home Page. On the DICOM Image Archive home page, select Add DICOM Image to Archive from the task list. On the DICOM Image Archive Home Page, select the thumbnail image of the lungs, which has been anonymized.
The list of configuration documents included in the Oracle Multimedia DICOM Image Archive demo is shown in the table on the DICOM Image Archive Administration home page. Or, start the process from Step 1 on the main page of the DICOM Image Archive Administration Administrator (See Figure 8–16). This section contains user and reference information for administrators of DICOM data model repositories.