Oracle Multimedia DICOM provides a relational interface, which is defined in the ORD_DICOM PL/SQL package. This package provides the same features as those provided by the ORDDicom object interface, in the relational environment. The DICOM relational interface adds Oracle Multimedia support to medical image data stored in BLOBs and BFILEs, rather than in the ORDDicom object type.
Application developers who create medical imaging applications without using the Oracle Multimedia ORDDicom object type to store and manage medical image data in relational tables can use the Oracle Multimedia DICOM relational interface to manage their medical image data. In addition, application developers who do not want to migrate their existing medical image applications to use Oracle Multimedia ORDDicom objects can use this relational interface to manage their medical image data.
The ORD_DICOM package is defined in the ordcpksp.sql file. After installation, this file is available in the Oracle home directory at:
<ORACLE_HOME>/ord/im/admin (on Linux and UNIX)
<ORACLE_HOME>\ord\im\admin (on Windows)
This chapter describes the functions and procedures in the DICOM relational interface. See Table 3-1 for information about other DICOM application programming interfaces (APIs).
This chapter contains these sections:
The functions and procedures for the DICOM relational 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. See Section 9.1.2 when reading through these examples.
Before using DICOM relational interface functions and procedures, you must load some data into the table. For example, you can use SQL*Loader or the importFrom( ) procedure. Substitute your DICOM files for those in the examples.
See Also:
Oracle Database Sample Schemas for information about the PM and other sample schemas
Issue the following statements before executing the examples, where c:\mydir\work is the directory where the user pm can find the DICOM files:
CREATE OR REPLACE DIRECTORY DICOMDIR as 'c:\mydir\work'; GRANT READ, WRITE ON DIRECTORY DICOMDIR TO pm;
Note:
At the beginning of each database session, call the setDataModel( ) procedure.See the setDataModel( ) Procedure for more information.
Before loading data into the table, you must create the table and columns where the data is to be stored. The following PL/SQL code segment creates the
MEDICAL_IMAGE_REL table with five columns.
CONNECT pm
Enter password: password
CREATE TABLE MEDICAL_IMAGE_REL
(
id integer primary key,
blob_src blob,
bfile_src bfile,
image_src ordsys.ordimage,
blob_dest blob
);
where:
blob_src: the source DICOM content in the BLOB.
bfile_src: the source DICOM content in the BFILE.
image_src: the source DICOM content in the ORDImage object.
blob_dest: the destination DICOM content in the BLOB.
The ORD_DICOM package defines these DICOM relational functions:
extractMetadata(
data IN BFILE,
extractOption IN VARCHAR2 DEFAULT 'ALL',
docName IN VARCHAR2 DEFAULT 'ordcmmp.xml')
RETURN SYS.XMLTYPE
Returns the DICOM metadata as an XML document for a specified mapping document. The default mapping document refers to the default metadata namespace http://xmlns.oracle.com/ord/dicom/metadata_1_0.
The input DICOM content stored in a BFILE.
A string that specifies the types of metadata to extract from the DICOM content. Valid values are: ALL, MAPPED, and STANDARD. The default is ALL.
When the value of the extractOption parameter is ALL, all attributes in the DICOM content are extracted. When the value is set to MAPPED, only mapped attributes are extracted. And, when the value is set to STANDARD, only attributes that conform to the DICOM standard and mapped attributes are extracted.
The name of the mapping document. The default mapping document ordcmmp.xml is loaded during installation.
Use the preference parameter XML_SKIP_ATTR to specify size limits for DICOM attributes to be omitted when encoding into XML. See Section 11.2.5.10 for more information about this preference parameter.
Use the preference parameter VALIDATE_METADATA to specify whether the XML documents are validated against a specific XML schema that is registered with Oracle XML DB, either as a global or local XML schema. See Section 11.2.5.9 for more information about this preference parameter.
Calling this function when the value of the preference parameter VALIDATE_METADATA is set to true raises an error if the metadata namespace in the mapping document is not available to the current user.
extractMetadata(
data IN BLOB,
extractOption IN VARCHAR2 DEFAULT 'ALL',
docName IN VARCHAR2 DEFAULT 'ordcmmp.xml')
RETURN SYS.XMLTYPE
Returns the DICOM metadata as an XML document for a specified mapping document. The default mapping document refers to the default metadata namespace http://xmlns.oracle.com/ord/dicom/metadata_1_0.
The input DICOM content stored in a BLOB.
A string that specifies the types of metadata to extract from the DICOM content. Valid values are: ALL, MAPPED, and STANDARD. The default is ALL.
When the value of the extractOption parameter is ALL, all attributes in the DICOM content are extracted. When the value is set to MAPPED, only mapped attributes are extracted. And, when the value is set to STANDARD, only attributes that conform to the DICOM standard and mapped attributes are extracted.
The name of the mapping document. The default mapping document ordcmmp.xml is loaded during installation.
Use the preference parameter XML_SKIP_ATTR to specify size limits for DICOM attributes to be omitted when encoding into XML. See Section 11.2.5.10 for more information about this preference parameter.
Use the preference parameter VALIDATE_METADATA to specify whether the XML documents are validated against a specific XML schema that is registered with Oracle XML DB, either as a global or local XML schema. See Section 11.2.5.9 for more information about this preference parameter.
Calling this function when the value of the preference parameter VALIDATE_METADATA is set to true raises an error if the metadata namespace in the mapping document is not available to the current user.
extractMetadata(
data IN ORDSYS.ORDImage,
extractOption IN VARCHAR2 DEFAULT 'ALL',
docName IN VARCHAR2 DEFAULT 'ordcmmp.xml')
RETURN SYS.XMLTYPE
Returns the DICOM metadata as an XML document for a specified mapping document. The default mapping document refers to the default metadata namespace http://xmlns.oracle.com/ord/dicom/metadata_1_0.
The input DICOM content stored in an ORDImage object.
A string that specifies the types of metadata to extract from the DICOM content. Valid values are: ALL, MAPPED, and STANDARD. The default is ALL.
When the value of the extractOption parameter is ALL, all attributes in the DICOM content are extracted. When the value is set to MAPPED, only mapped attributes are extracted. And, when the value is set to STANDARD, only attributes that conform to the DICOM standard and mapped attributes are extracted.
The name of the mapping document. The default mapping document ordcmmp.xml is loaded during installation.
Use the preference parameter XML_SKIP_ATTR to specify size limits for DICOM attributes to be omitted when encoding into XML. See Section 11.2.5.10 for more information about this preference parameter.
Use the preference parameter VALIDATE_METADATA to specify whether the XML documents are validated against a specific XML schema that is registered with Oracle XML DB, either as a global or local XML schema. See Section 11.2.5.9 for more information about this preference parameter.
Calling this function when the value of the preference parameter VALIDATE_METADATA is set to true raises an error if the metadata namespace in the mapping document is not available to the current user.
isAnonymous(
src IN BFILE,
anonymityDocName IN VARCHAR2 DEFAULT 'ordcman.xml')
RETURN INTEGER
Determines whether the input DICOM content is anonymous, using a specified anonymity document. This function returns a value of 1 if the data is anonymous; otherwise it returns a value of 0.
The input DICOM content stored in a BFILE.
The name of the anonymity document. The default name is ordcman.xml.
Determines whether the input DICOM content is anonymous, using a specified anonymity document. This function returns a value of 1 if the data is anonymous; otherwise it returns a value of 0.
The input DICOM content stored in a BLOB.
The name of the anonymity document. The default name is ordcman.xml.
isAnonymous(
src IN ORDSYS.ORDImage,
anonymityDocName IN VARCHAR2 DEFAULT 'ordcman.xml')
RETURN INTEGER
Determines whether the input DICOM content is anonymous, using a specified anonymity document. This function returns a value of 1 if the data is anonymous; otherwise it returns a value of 0.
The input DICOM content stored in an ORDImage object.
The name of the anonymity document. The default name is ordcman.xml.
Performs a conformance validation check to determine whether the input DICOM content conforms to a specified set of constraints identified by the constraintName parameter. This function returns a value of 1 if conformance is valid; otherwise it returns a value of 0.
This function also logs error messages from the constraint documents, which can be viewed by querying the public view orddcm_conformance_vld_msgs. The public view orddcm_constraint_names contains the list of constraint names.
The input DICOM content stored in a BFILE.
The name of the constraint to be used for conformance validation checking.
If this function is called from a SQL query, ensure that the constraint rule definition does not contain any <ACTION> elements.
Use the preference parameter EXP_IF_NULL_ATTR_IN_CONSTRAINT to indicate whether to throw exceptions when encountering missing attributes or null attribute values during conformance validation. See Section 11.2.5.3 for more information about this preference parameter.
Delete any existing conformance validation messages. Check if the DICOM content stored in a BFILE is conformance valid. Then, show any new conformance validation messages that are generated.
-- clear the previous conformance validation messages
delete from orddcm_conformance_vld_msgs;
-- conformance validate the DICOM content
declare
src bfile;
begin
select bfile_src into src from medical_image_rel where id = 1;
dbms_output.put_line('isConformanceValid(PatientModule) ' ||
ord_dicom.isConformanceValid(src, 'PatientModule'));
end;
/
-- get the logged conformance validation messages
select message, msg_time time from orddcm_conformance_vld_msgs
where rule_name='PatientModule';
Performs a conformance validation check to determine whether the input DICOM content conforms to a specified set of constraints identified by the constraintName parameter. This function returns a value of 1 if conformance is valid; otherwise it returns a value of 0.
This function also logs error messages from the constraint documents, which can be viewed by querying the public view orddcm_conformance_vld_msgs. The public view orddcm_constraint_names contains the list of constraint names.
The input DICOM content stored in a BLOB.
The name of the constraint to be used for conformance validation checking.
If this function is called from a SQL query, ensure that the constraint rule definition does not contain any <ACTION> elements.
Use the preference parameter EXP_IF_NULL_ATTR_IN_CONSTRAINT to indicate whether to throw exceptions when encountering missing attributes or null attribute values during conformance validation. See Section 11.2.5.3 for more information about this preference parameter.
Delete any existing conformance validation messages. Check if the DICOM content stored in a BLOB is conformance valid. Then, show any new conformance validation messages that are generated.
-- clear the previous conformance validation messages
delete from orddcm_conformance_vld_msgs;
-- conformance validate the DICOM content
declare
src blob;
begin
select blob_src into src from medical_image_rel where id = 1;
dbms_output.put_line('isConformanceValid(PatientModule) ' ||
ord_dicom.isConformanceValid(src, 'PatientModule'));
end;
/
-- get the logged conformance validation messages
select message, msg_time time from orddcm_conformance_vld_msgs
where rule_name='PatientModule';
Performs a conformance validation check to determine whether the input DICOM content conforms to a specified set of constraints identified by the constraintName parameter. This function returns a value of 1 if conformance is valid; otherwise it returns a value of 0.
This function also logs error messages from the constraint documents, which can be viewed by querying the public view orddcm_conformance_vld_msgs. The public view orddcm_constraint_names contains the list of constraint names.
The input DICOM content stored in an ORDImage object.
The name of the constraint to be used for conformance validation checking.
If this function is called from a SQL query, ensure that the constraint rule definition does not contain any <ACTION> elements.
Use the preference parameter EXP_IF_NULL_ATTR_IN_CONSTRAINT to indicate whether to throw exceptions when encountering missing attributes or null attribute values during conformance validation. See Section 11.2.5.3 for more information about this preference parameter.
Delete any existing conformance validation messages. Check if the DICOM content stored in an ORDImage object is conformance valid. Then, show any new conformance validation messages that are generated.
-- clear the previous conformance validation messages
delete from orddcm_conformance_vld_msgs;
-- conformance validate the DICOM content
declare
src ordimage;
begin
select image_src into src from medical_image_rel where id = 1;
dbms_output.put_line('isConformanceValid(PatientModule) ' ||
ord_dicom.isConformanceValid(src, 'PatientModule'));
end;
/
-- get the logged conformance validation messages
select message, msg_time time from orddcm_conformance_vld_msgs
where rule_name='PatientModule';
The ORD_DICOM package defines these DICOM relational procedures:
Note:
In this section, <unique-UID> represents a 64-byte, dot-concatenated, numeric string that represents a globally unique identifier for DICOM content worldwide. 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 within that organization. For some examples in this section, you must replace <unique-UID> with the appropriate UID.Creates a DICOM image from a source image and DICOM metadata. If the source content that is input to this procedure is DICOM content, the resulting destination DICOM content contains only the metadata that was input to this procedure in the metadata parameter. Thus, in the destination DICOM content, the metadata in the source DICOM content is removed and replaced by the metadata that was input.
The source raster image stored in a BFILE.
DICOM metadata stored in data type XMLType. The metadata must include all standard and private attributes. It must include a new SOP instance UID for the destination DICOM image, ensuring that the destination DICOM content is globally unique.
An empty BLOB in which to store the DICOM image created from the source image and metadata.
See Appendix C for information about the encoding rules that support image content processing.
Use the preference parameter VALIDATE_METADATA to specify whether the XML documents are validated against the Oracle default DICOM metadata schema. See Section 11.2.5.9 for more information about this preference parameter.
Create a DICOM image from a source BFILE and DICOM metadata:
declare
src bfile;
dest blob;
metadata xmltype;
begin
metadata := xmltype(bfilename('DICOMDIR', 'wm_meta.xml'),
nls_charset_id('AL32UTF8'),
'http://xmlns.oracle.com/ord/dicom/metadata_1_0');
select bfile_src, blob_dest into src, dest from medical_image_rel
where id = 1 for update;
ord_dicom.createDicomImage(src, metadata, dest);
end;
/
Creates a DICOM image from a source image and DICOM metadata. If the source content that is input to this procedure is DICOM content, the resulting destination DICOM content contains only the metadata that was input to this procedure in the metadata parameter. Thus, in the destination DICOM content, the metadata in the source DICOM content is removed and replaced by the metadata that was input.
The source raster image stored in a BLOB.
DICOM metadata stored in data type XMLType. The metadata must include all standard and private attributes. It must include a new SOP instance UID for the destination DICOM image, ensuring that the destination DICOM content is globally unique.
An empty BLOB in which to store the DICOM image created from the source image and metadata.
See Appendix C for information about the encoding rules that support image content processing.
Use the preference parameter VALIDATE_METADATA to specify whether the XML documents are validated against the Oracle default DICOM metadata schema. See Section 11.2.5.9 for more information about this preference parameter.
Create a DICOM image from a source BLOB and DICOM metadata:
declare
src blob;
dest blob;
metadata xmltype;
begin
metadata := xmltype(bfilename('DICOMDIR', 'wm_meta.xml'),
nls_charset_id('AL32UTF8'),
'http://xmlns.oracle.com/ord/dicom/metadata_1_0');
select blob_src, blob_dest into src, dest from medical_image_rel
where id = 1 for update;
ord_dicom.createDicomImage(src, metadata, dest);
end;
/
Creates a DICOM image from a source image and DICOM metadata. If the source content that is input to this procedure is DICOM content, the resulting destination DICOM content contains only the metadata that was input to this procedure in the metadata parameter. Thus, in the destination DICOM content, the metadata in the source DICOM content is removed and replaced by the metadata that was input.
The source raster image stored in an ORDImage object.
DICOM metadata stored in data type XMLType. The metadata must include all standard and private attributes. It must include a new SOP instance UID for the destination DICOM image, ensuring that the destination DICOM content is globally unique.
An empty BLOB in which to store the DICOM image created from the source image and metadata.
See Appendix C for information about the encoding rules that support image content processing.
Use the preference parameter VALIDATE_METADATA to specify whether the XML documents are validated against the Oracle default DICOM metadata schema. See Section 11.2.5.9 for more information about this preference parameter.
Create a DICOM image from a source ORDImage object and DICOM metadata:
declare
src ordimage;
dest blob;
metadata xmltype;
begin
metadata := xmltype(bfilename('DICOMDIR', 'wm_meta.xml'),
nls_charset_id('AL32UTF8'),
'http://xmlns.oracle.com/ord/dicom/metadata_1_0');
select image_src, blob_dest into src, dest from medical_image_rel
where id = 1 for update;
ord_dicom.createDicomImage(src, metadata, dest);
end;
/
export(
src IN BLOB,
dest_type IN VARCHAR2,
dest_location IN VARCHAR2,
dest_name IN VARCHAR2)
Exports DICOM content in a BLOB to a specified destination. The data remains in the source BLOB when it is copied to the destination.
The source location of the DICOM content.
The type of the destination (only FILE is supported).
The location of the destination (must be a valid Oracle directory object).
The name of the destination file.
The export( ) procedure writes only to a database directory object that the user has privilege to access. That is, you can access a directory object that you have created using the SQL statement CREATE DIRECTORY, or one to which you have been granted READ and WRITE access.
For example, the following SQL*Plus commands create a directory object and grant the user pm permission to read and write to any file within the directory c:\mydir\work:
CONNECT sys as sysdba
Enter password: password
CREATE OR REPLACE DIRECTORY DICOMDIR AS 'c:\mydir\work';
GRANT READ,WRITE ON DIRECTORY DICOMDIR TO pm;
See Section 9.1 for more information about these directory and table definitions.
importFrom(
dest IN OUT NOCOPY BLOB,
source_type IN VARCHAR2,
source_location IN VARCHAR2,
source_name IN VARCHAR2)
The storage destination of the imported DICOM file.
The type of the source (only FILE is supported).
The location of the source (must be a valid Oracle directory object).
The name of the source file.
The importFrom( ) procedure reads only from a database directory object that the user has privilege to access. That is, you can access a directory object that you have created using the SQL statement CREATE DIRECTORY, or one to which you have been granted READ access.
For example, the following SQL*Plus commands create a directory object and grant the user pm permission to read any file within the directory c:\mydir\work:
CONNECT sys as sysdba
Enter password: password
CREATE OR REPLACE DIRECTORY DICOMDIR AS 'c:\mydir\work';
GRANT READ ON DIRECTORY DICOMDIR TO pm;
See Section 9.1 for more information about these directory and table definitions.
makeAnonymous(
src IN BFILE,
dest_sop_instance_uid IN VARCHAR2,
dest IN OUT NOCOPY BLOB,
anonymityDocName IN VARCHAR2 DEFAULT 'ordcman.xml')
Removes patient identifying information from the source DICOM content after copying it into another DICOM content BLOB, based on a specified anonymity document.
The input DICOM content stored in a BFILE.
The SOP instance UID of the destination DICOM content. It must ensure that the destination DICOM content is globally unique.
An empty BLOB in which to store the anonymous DICOM content.
The name of the anonymity document. The default name is ordcman.xml.
Remove patient identifying information from the embedded DICOM content stored in a BFILE:
Note:
Replace <unique-UID> with the UID that identifies the organization producing the DICOM content and the DICOM content within that organization.
declare
src bfile;
dest blob;
dest_sop_instance_uid varchar2(128) := '<unique-UID>';
begin
select bfile_src, blob_dest into src, dest from medical_image_rel
where id = 1 for update;
ord_dicom.makeAnonymous(src, dest_sop_instance_uid, dest, 'ordcman.xml');
end;
/
makeAnonymous(
src IN BLOB,
dest_sop_instance_uid IN VARCHAR2,
dest IN OUT NOCOPY BLOB,
anonymityDocName IN VARCHAR2 DEFAULT 'ordcman.xml')
Removes patient identifying information from the source DICOM content after copying it into another DICOM content BLOB, based on a specified anonymity document.
The input DICOM content stored in a BLOB.
The SOP instance UID of the destination DICOM content. It must ensure that the destination DICOM content is globally unique.
An empty BLOB in which to store the anonymous DICOM content.
The name of the anonymity document. The default name is ordcman.xml.
Remove patient identifying information from the embedded DICOM content stored in a BLOB:
Note:
Replace <unique-UID> with the UID that identifies the organization producing the DICOM content and the DICOM content within that organization.
declare
src blob;
dest blob;
dest_sop_instance_uid varchar2(128) := '<unique-UID>';
begin
select blob_src, blob_dest into src, dest from medical_image_rel
where id = 1 for update;
ord_dicom.makeAnonymous(src, dest_sop_instance_uid, dest, 'ordcman.xml');
end;
/
makeAnonymous(
src IN ORDSYS.ORDImage,
dest_sop_instance_uid IN VARCHAR2,
dest IN OUT NOCOPY BLOB,
anonymityDocName IN VARCHAR2 DEFAULT 'ordcman.xml')
Removes patient identifying information from the source DICOM content after copying it into another DICOM content BLOB, based on a specified anonymity document.
The input DICOM content stored in an ORDImage object.
The SOP instance UID of the destination DICOM content. It must ensure that the destination DICOM content is globally unique.
An empty BLOB in which to store the anonymous DICOM content.
The name of the anonymity document. The default name is ordcman.xml.
Remove patient identifying information from the embedded DICOM content stored in an ORDImage object:
Note:
Replace <unique-UID> with the UID that identifies the organization producing the DICOM content and the DICOM content within that organization.
declare
src ordimage;
dest blob;
dest_sop_instance_uid varchar2(128) := '<unique-UID>';
begin
select image_src, blob_dest into src, dest from medical_image_rel
where id = 1 for update;
ord_dicom.makeAnonymous(src, dest_sop_instance_uid, dest, 'ordcman.xml');
end;
/
Reads the DICOM content that is input from the source BFILE, performs the specified processing operations on the image, and then stores the resulting image in the destination BLOB. The original DICOM content in the source BFILE remains unchanged.
The input DICOM content stored in the source BFILE.
A command string that accepts a processing operator as input. Valid values include: fileFormat, frame, contentFormat, compressionFormat, cut, scale, and rotate. See Appendix D for information about processing operators.
An empty BLOB in which to store the destination content.
See Appendix C for information about the encoding rules that support DICOM content processing. See Appendix D for more information about DICOM processing.
Use the preference parameter VALIDATE_METADATA to specify whether the XML documents are validated against the Oracle default DICOM metadata schema. See Section 11.2.5.9 for more information about this preference parameter.
processCopy(src IN BFILE,
command IN VARCHAR2,
dest_sop_instance_uid IN VARCHAR2,
dest IN OUT NOCOPY BLOB,
metadata IN SYS.XMLTYPE DEFAULT NULL)
Reads the DICOM content that is input from the source BFILE, performs the specified processing operations on the image, updates it with the new metadata, and then stores the resulting image in the destination BLOB. The original DICOM content in the source BFILE remains unchanged.
The input DICOM content stored in the source BFILE.
A command string that accepts a processing operator as input. Valid values include: frame, contentFormat, compressionFormat, cut, scale, and rotate. See Appendix D for information about processing operators.
The SOP instance UID of the destination DICOM content. It must ensure that the destination DICOM content is globally unique.
An empty BLOB in which to store the destination content.
The new metadata to be written into the new DICOM content.
See Appendix C for information about the encoding rules that support DICOM content processing. See Appendix D for more information about DICOM processing.
Use the preference parameter VALIDATE_METADATA to specify whether the XML documents are validated against the Oracle default DICOM metadata schema. See Section 11.2.5.9 for more information about this preference parameter.
Generate a new compressed DICOM image:
Note:
Replace <unique-UID> with the UID that identifies the organization producing the DICOM content and the DICOM content within that organization.
src bfile;
dest blob;
dest_sop_instance_uid varchar2(128) := '<unique-UID>';
begin
select bfile_src, blob_dest into src, dest from medical_image_rel
where id = 1 for update;
ord_dicom.processCopy(
src, 'CompressionFormat=jpeg', dest_sop_instance_uid, dest);
end;
/
Reads the DICOM content that is input from the source BLOB, performs the specified processing operations on the image, and then stores the resulting image in the destination BLOB. The original DICOM content in the source BLOB remains unchanged.
The input DICOM content stored in the source BLOB.
A command string that accepts a processing operator as input. Valid values include: fileFormat, frame, contentFormat, compressionFormat, cut, scale, and rotate. See Appendix D for information about processing operators.
An empty BLOB in which to store the destination content.
See Appendix C for information about the encoding rules that support DICOM content processing. See Appendix D for more information about DICOM processing.
Use the preference parameter VALIDATE_METADATA to specify whether the XML documents are validated against the Oracle default DICOM metadata schema. See Section 11.2.5.9 for more information about this preference parameter.
processCopy(src IN BLOB,
command IN VARCHAR2,
dest_sop_instance_uid IN VARCHAR2,
dest IN OUT NOCOPY BLOB,
metadata IN SYS.XMLTYPE DEFAULT NULL)
Reads the DICOM content that is input from the source BLOB, performs the specified processing operations on the image, updates it with the new metadata, and then stores the resulting image in the destination BLOB. The original DICOM content in the source BLOB remains unchanged.
The input DICOM content stored in the source BLOB.
A command string that accepts a processing operator as input. Valid values include: frame, contentFormat, compressionFormat, cut, scale, and rotate. See Appendix D for information about processing operators.
The SOP instance UID of the destination DICOM content. It must ensure that the destination DICOM content is globally unique.
An empty BLOB in which to store the destination content.
The new metadata to be written into the new DICOM content.
See Appendix C for information about the encoding rules that support DICOM content processing. See Appendix D for more information about DICOM processing.
Use the preference parameter VALIDATE_METADATA to specify whether the XML documents are validated against the Oracle default DICOM metadata schema. See Section 11.2.5.9 for more information about this preference parameter.
Create a new compressed DICOM image:
Note:
Replace <unique-UID> with the UID that identifies the organization producing the DICOM content and the DICOM content within that organization.
declare
src blob;
dest blob;
dest_sop_instance_uid varchar2(128) := '<unique-UID>';
begin
select blob_src, blob_dest into src, dest from medical_image_rel
where id = 1 for update;
ord_dicom.processCopy(
src, 'CompressionFormat=jpeg', dest_sop_instance_uid, dest);
end;
/
Reads the DICOM content that is input from the source ORDImage object, performs the specified processing operations on the image, and then stores the resulting image in the destination BLOB. The original DICOM content in the source ORDImage object remains unchanged.
The input DICOM content stored in the source ORDImage object.
A command string that accepts an image processing operator as input. Valid values include: fileFormat, frame, contentFormat, compressionFormat, cut, scale, and rotate. See Appendix D for information about image processing operators.
An empty BLOB in which to store the destination content.
Use this procedure to get a non-DICOM image that is suitable for presentation on the Web from the embedded DICOM content.
See Appendix C for information about the encoding rules that support image content processing. See Appendix D for more information about DICOM processing.
Use the preference parameter VALIDATE_METADATA to specify whether the XML documents are validated against the Oracle default DICOM metadata schema. See Section 11.2.5.9 for more information about this preference parameter.
processCopy(src IN ORDSYS.ORDImage,
command IN VARCHAR2,
dest_sop_instance_uid IN VARCHAR2,
dest IN OUT NOCOPY BLOB,
metadata IN SYS.XMLTYPE DEFAULT NULL)
Reads the DICOM content that is input from the source ORDImage object, performs the specified processing operations on the image, updates it with the new metadata, and then stores the resulting image in the destination BLOB. The original DICOM content in the source ORDImage object remains unchanged.
The input DICOM content stored in the source ORDImage object.
A command string that accepts an image processing operator as input. Valid values include: frame, contentFormat, compressionFormat, cut, scale, and rotate. See Appendix D for information about image processing operators.
The SOP instance UID of the destination DICOM image. It must ensure that the destination DICOM content is globally unique.
An empty BLOB in which to store the destination content.
The new metadata to be written into the new DICOM content.
Use this procedure to get a non-DICOM image that is suitable for presentation on the Web from the embedded DICOM content.
See Appendix C for information about the encoding rules that support image content processing. See Appendix D for more information about DICOM processing.
Use the preference parameter VALIDATE_METADATA to specify whether the XML documents are validated against the Oracle default DICOM metadata schema. See Section 11.2.5.9 for more information about this preference parameter.
Create a new compressed DICOM image:
Note:
Replace <unique-UID> with the UID that identifies the organization producing the DICOM content and the DICOM content within that organization.
declare
src ordimage;
dest blob;
dest_sop_instance_uid varchar2(128) := '<unique-UID>';
begin
select image_src, blob_dest into src, dest from medical_image_rel
where id = 1 for update;
ord_dicom.processCopy(
src, 'CompressionFormat=jpeg', dest_sop_instance_uid, dest);
end;
/
Writes or modifies the current DICOM content with the metadata provided by making a copy of the existing DICOM content in the destination BLOB, and then modifying the metadata. The original DICOM content remains unchanged. The attributes in the destination DICOM content are copied from the metadata that was input.
The input DICOM content stored in a BFILE.
The input metadata stored in data type XMLType. In the destination DICOM content, the input metadata is used to update the values for attributes that are identical to attributes in the source DICOM content, or to add any new attributes. The metadata must conform to the default metadata schema with the namespace http://xmlns.oracle.com/ord/dicom/metadata_1_0. The SOP instance UID in the metadata must ensure that the destination DICOM content is globally unique.
An empty BLOB in which to store the new DICOM content with the new metadata.
See Appendix C for information about the encoding rules that support metadata extraction.
Use the preference parameter VALIDATE_METADATA to specify whether the XML documents are validated against the Oracle default DICOM metadata schema. See Section 11.2.5.9 for more information about this preference parameter.
Use the preference parameter SQ_WRITE_LEN to specify how the DICOM sequence (SQ) types are encoded. See Section 11.2.5.8 for more information about this preference parameter.
Write the new metadata to the copy of the DICOM content in the destination BLOB:
declare
src bfile;
dest blob;
metadata xmltype;
begin
metadata := xmltype(bfilename('DICOMDIR', 'wm_meta.xml'),
nls_charset_id('AL32UTF8'),
'http://xmlns.oracle.com/ord/dicom/metadata_1_0');
select bfile_src, blob_dest into src, dest from medical_image_rel
where id = 1 for update;
ord_dicom.writeMetadata(src, metadata, dest);
end;
/
Writes or modifies the current DICOM content with the metadata provided by making a copy of the existing DICOM content in the destination BLOB, and then modifying the metadata. The original DICOM content remains unchanged. The attributes in the destination DICOM content are copied from the metadata that was input.
The input DICOM content stored in a BLOB.
The input metadata stored in data type XMLType. In the destination DICOM content, the input metadata is used to update the values for attributes that are identical to attributes in the source DICOM content, or to add any new attributes. The metadata must conform to the default metadata schema with the namespace http://xmlns.oracle.com/ord/dicom/metadata_1_0. The SOP instance UID in the metadata must ensure that the destination DICOM content is globally unique.
An empty BLOB in which to store the new DICOM content with the new metadata.
See Appendix C for information about the encoding rules that support metadata extraction.
Use the preference parameter VALIDATE_METADATA to specify whether the XML documents are validated against the Oracle default DICOM metadata schema. See Section 11.2.5.9 for more information about this preference parameter.
Use the preference parameter SQ_WRITE_LEN to specify how the DICOM sequence (SQ) types are encoded. See Section 11.2.5.8 for more information about this preference parameter.
Write the new metadata to the copy of the DICOM content in the destination BLOB:
declare
src blob;
dest blob;
metadata xmltype;
begin
metadata := xmltype(bfilename('DICOMDIR', 'wm_meta.xml'),
nls_charset_id('AL32UTF8'),
'http://xmlns.oracle.com/ord/dicom/metadata_1_0');
select blob_src, blob_dest into src, dest from medical_image_rel
where id = 1 for update;
ord_dicom.writeMetadata(src, metadata, dest);
end;
/
Writes or modifies the current DICOM content with the metadata provided by making a copy of the existing DICOM content in the destination BLOB, and then modifying the metadata. The original DICOM content remains unchanged. The attributes in the destination DICOM content are copied from the metadata that was input.
The input DICOM content stored in an ORDImage object.
The input metadata stored in data type XMLType. In the destination DICOM content, the input metadata is used to update the values for attributes that are identical to attributes in the source DICOM content, or to add any new attributes. The metadata must conform to the default metadata schema with the namespace http://xmlns.oracle.com/ord/dicom/metadata_1_0. The SOP instance UID in the metadata must ensure that the destination DICOM content is globally unique.
An empty BLOB in which to store the new DICOM content with the new metadata.
See Appendix C for information about the encoding rules that support metadata extraction.
Use the preference parameter VALIDATE_METADATA to specify whether the XML documents are validated against the Oracle default DICOM metadata schema. See Section 11.2.5.9 for more information about this preference parameter.
Use the preference parameter SQ_WRITE_LEN to specify how the DICOM sequence (SQ) types are encoded. See Section 11.2.5.8 for more information about this preference parameter.
Write the new metadata to the copy of the DICOM content in the destination BLOB:
declare
src ordimage;
dest blob;
metadata xmltype;
begin
metadata := xmltype(bfilename('DICOMDIR', 'wm_meta.xml'),
nls_charset_id('AL32UTF8'),
'http://xmlns.oracle.com/ord/dicom/metadata_1_0');
select image_src, blob_dest into src, dest from medical_image_rel
where id = 1 for update;
ord_dicom.writeMetadata(src, metadata, dest);
end;
/