Install Oracle Database 11g Release 11.1 or later with Oracle Multimedia.

Download and unzip the dicom.zip file into a working directory.

Create the directory object while connected as sysdba. Open a SQL*Plus session, and execute the following commands:

sqlplus sys@<sid> as sysdba
Enter password: <password>

create or replace directory IMAGEDIR as '<file_directory>';

Here, <file_directory> is the location where all the scripts/files you need for this tutorial are located. In this example, we use /home/oracle/wkdir/dicom/files.

Note: if this directory does not exist in the operating system, you need to create it.

Grant read and write access on the directory to the tutorial user. In this tutorial, we use the user PM. If you are using a different user, change the value of PM to your user name.

From your SQL*Plus session, execute the following commands:

grant read, write on directory IMAGEDIR to pm;

From your SQL*Plus session, connect as your tutorial user. In this example, we use the PM user.

Execute the following commands:

connect pm
Enter password: <password>

@create_dicom_table

The create_dicom_table.sql code is as follows:

set echo on

drop table medical_image_table;

create table medical_image_table 
     (id          integer primary key, 
      dicom       ordsys.orddicom,
      imageThumb  ordsys.ordimage, 
      anonDicom   ordsys.orddicom)
      --
      -- metadata extraction expands the ORDDicom object
      pctfree 60
      --
      -- lob storage
      lob(dicom.source.localdata) store as SecureFile
         (nocache filesystem_like_logging),
      lob(imageThumb.source.localdata) store as SecureFile
         (nocache filesystem_like_logging),
      lob(anonDicom.source.localdata) store as SecureFile
         (nocache filesystem_like_logging),
      -- disable in row storage for the extension
      -- so that it does not consume page space
      -- it is usually < 4k in size
      lob(dicom.extension) store as SecureFile
         ( nocache disable storage in row ),
      lob(anonDicom.extension) store as SecureFile
         ( nocache disable storage in row ),
      -- store the metadata as a CLOB,
      -- disable storage in row
      xmltype dicom.metadata store as SecureFile clob
         ( nocache disable storage in row )
      xmltype anonDicom.metadata store as SecureFile clob
         ( nocache disable storage in row )
;

Note: If you use a user with a non-ASSM tablespace, you will see this error on the create table:
>>>> ERROR at line 1:
>>>> ORA-43853: SECUREFILE lobs cannot be used in non-ASSM tablespace "SYSTEM"

From your SQL*Plus session, enter the following commands:

@create_import_procedure

The create_import_procedure.sql code is as follows:

-- Set Data Model Repository
execute ordsys.ord_dicom.setDataModel();


create or replace procedure image_import
  (dest_id number, filename varchar2) 
  is
    dcm ordsys.orddicom;
  begin
    delete from medical_image_table where id = dest_id;
    insert into medical_image_table (id, dicom, imageThumb, anonDicom) 
      values (dest_id, ordsys.orddicom('file', 'IMAGEDIR', filename, 0), 
              ordsys.ordimage.init(), ordsys.orddicom()) 
      returning dicom into dcm;
    dcm.import(1);

    update medical_image_table set dicom=dcm where id=dest_id;  
  
    commit;
end;
/ 
show errors; 

Now you can execute the newly created procedure to import the sample DICOM file. From your SQL*Plus session, enter the following commands:

execute image_import(1,'179.dcm')

This query retrieves the Service-Object Pair Instance UID from the ORDDicom object attribute. This data was extracted from the DICOM content when setProperties was called.  From your SQL*Plus session, execute the following script:

@sop_instance_uid

The sop_instance_uid.sql code is as follows:

select id, 
       t.dicom.getSOPInstanceUID() as SOP_Instance_UID 
from medical_image_table t;        


 

This query retrieves the Service-Object Pair Class UID from the ORDDicom object attribute. This data was extracted from the DICOM content when setProperties was called. From your SQL*Plus session, execute the following script:

@sop_class_uid

The sop_class_uid.sql code is as follows:

select id, 
       t.dicom.getSOPClassUID() as SOP_Class_UID
from medical_image_table t; 

This query retrieves the Study Instance UID from the ORDDicom object attribute.  This data was extracted from the DICOM content when setProperties was called. From your SQL*Plus session, execute the following script:

@study_instance_uid

The study_instance_uid.sql code is as follows:

select id, 
       t.dicom.getStudyInstanceUID() as Study_Instance_UID 
from medical_image_table t; 

This query retrieves the Series Instance UID from the ORDDicom object attribute. This data was extracted from the DICOM content when setProperties was called. From your SQL*Plus session, execute the following script:

@series_instance_uid

The series_instance_uid.sql code is as follows:

select id, 
       t.dicom.getSeriesInstanceUID() as Series_Instance_UID
from medical_image_table t; 

This query retrieves the length of the DICOM content stored in the source attribute. From your SQL*Plus session, execute the following script:

@content_length

The content_length.sql code is as follows:

select id,
       t.dicom.getcontentlength() as content_Length 
from medical_image_table t; 

This query shows how you can extract information from the extracted XML metadata document. From your SQL*Plus session, execute the following script:

@patient_info

The patient_info.sql code is as follows:

column id format 99;
column PATIENT_NAME format A30;
column PATIENT_ID format A10;
column MODALITY format A10;


select m.id, t.PATIENT_NAME, t.PATIENT_ID, t.MODALITY
from medical_image_table m,
  xmltable
    (xmlnamespaces
      (default 'http://xmlns.oracle.com/ord/dicom/metadata_1_0'),
               '/DICOM_OBJECT' 
       passing m.dicom.metadata
       columns
         patient_name varchar2(100) 
           path './*[@name="Patient''''s Name"]/VALUE',
        patient_id varchar2(100) 
           path './*[@name="Patient ID"]',
        modality varchar2(100) 
           path './*[@name="Modality"]'
        ) t ;

To create the generate_thumb procedure, execute the following script from your SQL*Plus session:

@create_thumbnail_procedure

The create_thumbnail_procedure.sql code is as follows:

-- Set Data Model Repository
execute ordsys.ord_dicom.setDataModel();
         
create or replace procedure generate_thumb(source_id number, verb varchar2) 
is
   dcmSrc    ordsys.orddicom;
   imgDst    ordsys.ordimage;
begin
   select dicom, imageThumb 
     into dcmSrc, imgDst 
     from medical_image_table 
     where id = source_id for update;
   dcmSrc.processCopy(verb, imgDst);
         
   update medical_image_table 
   set imageThumb = imgDst 
   where id = source_id;
   commit;
end;
/
show errors;       

From your SQL*Plus session, execute the following script:

@create_thumbnail_image

The create_thumbnail_image.sql code is as follows:

-- Create a JPEG thumbnail image for our test DICOM
execute generate_thumb(1, 'fileformat=jfif fixedscale=75 100');       

Invoke the select_thumbnail.sql script and observe that there is a thumbnail image of size 75 X 100.

From your SQL*Plus session, execute the following script:

@select_thumbnail

The select_thumbnail.sql code is as follows:

column t.imageThumb.getfileformat() format A20;
select id, t.imageThumb.getWidth(), t.imageThumb.getHeight(), 
       t.imageThumb.getFileFormat() 
from medical_image_table t;

To create the generate_anon procedure, execute the following script from your SQL*Plus session:

@create_anonimage_proc

The create_anonimage_proc.sql code is as follows:

-- Set Data Model Repository
execute ordsys.ord_dicom.setDataModel();

create or replace procedure generate_anon(source_id number) is
   dcmSrc    ordsys.orddicom;
   anonDst   ordsys.orddicom;
   dest_sop_inst_uid varchar2(128) := '1.2.3';
         
begin
  select dicom, anonDicom into dcmSrc, anonDst from medical_image_table 
    where id = source_id for update;
  dcmSrc.makeAnonymous(dest_sop_inst_uid, anonDst);
  update medical_image_table set anonDicom = anonDst where id = source_id;
  commit;
end;
/
show errors; 

You should replace the temporary UID for the dest_sop_instance_uid variable in generate_anon with a globally-unique UID. Note, the procedure will run if you don’t do this, but you should then destroy the resulting anonymous DICOM image.

Generate an anonymous copy of your test DICOM. Execute the following command from your SQL*Plus session:

execute generate_anon(1);

You can now review the results. Execute the following script from your SQL*Plus session:

@select_anonimage

To create the check_conform procedure, execute the following script from your SQL*Plus session:

@create_checkconform_proc

The create_checkconform_proc.sql code is as follows:

-- Set Data Model Repository
execute ordsys.ord_dicom.setDataModel();
create or replace procedure check_conform(source_id number) is
    dcmSrc    ordsys.orddicom;
begin
  select dicom into dcmSrc from medical_image_table 
         where id = source_id;
  dbms_output.put_line('isconformanceValid(OracleOrdObject): ' ||
    dcmSrc.isConformanceValid('OracleOrdObject'));
end;
/
show errors;

Check to see if the DICOM image conforms with the constraint rules. Execute the following commands from your SQL*Plus session:

set serverout on
execute check_conform(1); 

If the DICOM image does not conform to the constraint definitions, a message or messages are inserted into a table viewable by querying the ORDDCM_CONFORMANCE_VLD_MSGS view. This view lists the constraint messages generated during constraint validation. Execute the following script from your SQL*Plus session:

@review_conform_msgs

The review_conform_msgs.sql code is as follows:

describe orddcm_conformance_vld_msgs;
select * from orddcm_conformance_vld_msgs;        

Create a procedure that will export the DICOM content to a file in the IMAGEDIR directory. Execute the following script from your SQL*Plus session:

@create_export_proc

The create_export_proc.sql code is as follows:

create or replace procedure dicom_export 
(source_id number, filename varchar2) 
as
  dcmSrc ordsys.orddicom;
begin
   select dicom into dcmSrc from medical_image_table where id = source_id;
   dcmSrc.export('FILE', 'IMAGEDIR', filename);
end;
/
show errors; 

Now you can execute the procedure. Execute the following command from your SQL*Plus session:

execute dicom_export(1, 'dicom_orig.dcm');

To see the file that was created, open another terminal window and execute the following command from the IMAGEDIR directory.

ls -al dicom_orig.dcm

Execute the following script from your SQL*Plus session as the user under which you ran the tutorial:

@cleanup01

The cleanup01.sql code is as follows:

drop procedure image_import;
drop procedure generate_thumb;
drop procedure generate_anon;
drop procedure dicom_export;
drop procedure check_conform;
drop table  medical_image_table;

Log in to SQL*Plus as the SYS user:

sqlplus sys as sysdba

Execute the following script from your SQL*Plus session as the SYS user:

@cleanup02

The cleanup02.sql code is as follows:

drop directory imagedir;

To close your SQL*Plus session, execute the following command:

exit 

In your SQL*Plus session, navigate to your working directory and delete the export file, dicom_orig.dcm, that was created in imagedir.

rm dicom_orig.dcm

If prompted, confirm your deletion.