9 Overview of DICOM Administration

9.1 Assigning Administrator Roles and Privileges

After installing Oracle Multimedia DICOM, the ORDADMIN role is created, with the database system privileges required for administration of the DICOM data model repository.

The ORDADMIN role must be assigned to the administrator of the DICOM data model repository. The following code segment shows a sample GRANT statement for the administrator dcmadmin:

GRANT ORDADMIN to dcmadmin;

Because of the way database roles behave, tasks for which the administrator must write PL/SQL named procedures require explicit privileges. The following code segment shows a sample of a GRANT statement for an administrator named dcmadmin:

GRANT EXECUTE on ORD_DICOM_ADMIN to dcmadmin;
GRANT SELECT on orddcm_document_refs to dcmadmin;

Administrators must also be granted the write privilege for specified directories. For example, during operations where configuration documents are exported, administrators must have write access to the directory where those documents are to be stored.

All users can load the data model repository into memory structures and view several public information views. Only administrators can export, insert, or delete configuration documents from the data model repository. And, only administrators can query administrator-only information views.

9.2 Managing XML Schemas

The DICOM XML schemas in Oracle Multimedia DICOM are registered as global XML schemas in Oracle Database with Oracle XML DB. (See Appendix B for listings of the installed DICOM XML schemas.)

If you define custom XML schemas, you must register them as global schemas with Oracle XML DB. See Oracle XML DB Developer's Guide for more information about registering XML schemas.

Querying the dictionary view ALL_XML_SCHEMAS enables you to find and examine the registered XML schemas. See Oracle Database Reference for more information about this dictionary view.

exec ord_dicom.setdatamodel;
 
select t.doc_name, xmlcast(xmlquery(
       'declare default element namespace
       "http://xmlns.oracle.com/ord/dicom/mapping_1_0"; $x//NAMESPACE'
      passing ord_dicom_admin.getdocumentcontent(t.doc_name) as "x" 
      returning content) as varchar2(4000) ) as schema_url
  from orddcm_documents  t
  where t.installed_by_oracle=0 and t.doc_type= 'MAPPING'
  order by t.doc_id asc;
 
DOC_NAME             SCHEMA_URL
-------------------- -------------------------------------
sample_map_10.xml     http://www.mycompany.com/metatest10
sample_map_11.xml     http://www.mycompany.com/metatest11

9.3 Loading the Data Model Repository

At the start of every database session, administrators and users must load the data model repository from the database into memory structures. Users load the data model by calling the setDataModel( ) procedure. Administrators load the data model by calling either the setDataModel( ) procedure or the editDataModel( ) procedure.

After loading the repository into memory, administrators and users can call the setDataModel( ) procedure whenever the application requires the new data model changes.

Using the DICOM data model utility in the ORD_DICOM package, administrators and users call the setDataModel( ) procedure as follows:

exec ord_dicom.setdatamodel;

See the setDataModel( ) Procedure for reference information.

Using the ORD_DICOM_ADMIN package, administrators call the editDataModel( ) procedure as follows:

exec ord_dicom_admin.editDataModel();

See the editDataModel( ) Procedure for reference information.

9.4 Browsing the Repository with Information Views

Several public information views are available for browsing the DICOM repository. An administrator-only information view is also available to assist with DICOM repository administration. Information views provide details about documents in the repository, including names of documents, types of documents, references to other documents, names of constraints, and constraint validation messages.

Table 9-2 lists the information views and indicates which views are available to all users (public) or only to administrators.

Administrators can use the orddcm_document_refs information view to see the list of documents that are referenced by other documents in the repository. This read-only information view is available to administrators only. (See orddcm_document_refs.)

In addition, administrators (and other users) can use the orddcm_documents view to see the list of details about the documents stored in the repository. They can also use the orddcm_document_types view, which identifies the supported Oracle Multimedia DICOM document types by providing the list of codes for the document types. These public information views are read-only. (See orddcm_documents and orddcm_document_types.)

Two other public information views are available. The orddcm_constraint_names view lists the names of the constraints installed in the repository. In addition, the orddcm_conformance_vld_msgs view lists the constraint messages generated during constraint validation only for the schema that belongs to the user. (See orddcm_constraint_names and orddcm_conformance_vld_msgs.)

Administrators commonly use the orddcm_documents, orddcm_document_types, and orddcm_document_refs views when inserting, updating, and deleting documents from the repository.

9.5 Exporting Documents from the Repository

Before exporting documents from the repository (and possibly before making any changes to the configuration documents), administrators should perform the following tasks:

1. Call the setDataModel( ) procedure at the beginning of each database session to load the repository from the database into memory structures. Locking the repository at this point is not required.

   Administrators (and other users) can also call this procedure whenever the application requires the new data model changes.

   See Chapter 4 for reference information about the setDataModel( ) procedure.

2. Obtain copies of the existing documents in the repository, using either the getDocumentContent( ) function or the exportDocument( ) procedure.

   The getDocumentContent( ) function returns the specified document as data type XMLType.

   The exportDocument( ) procedure writes the contents of the specified document to a specified file in a directory for which the administrator has been granted the write privilege.

   See Chapter 10 for reference information about the getDocumentContent( ) function and the exportDocument( ) procedure.

9.6 Inserting Documents into the Repository

The process of inserting documents into the repository can involve the use of these procedures:

• editDataModel( )

• insertDocument( )

• publishDataModel( )

• rollbackDataModel( )

See Chapter 10 for reference information about these procedures. See Chapter 11 for an example of the insertion process.

The following subsections briefly describe the insertion process for different types of documents.

9.7 Updating Documents in the Repository

The process of updating documents in the repository can involve the use of these procedures:

• editDataModel( )

• exportDocument( )

• deleteDocument( )

• insertDocument( )

• publishDataModel( )

• rollbackDataModel( )

See Chapter 10 for reference information about these procedures. See Chapter 11 for an example of the update process.

The following subsections briefly describe the update process for different types of documents.

9.8 Deleting Documents from the Repository

The process of deleting documents from the repository can involve the use of these procedures:

• editDataModel( )

• exportDocument( )

• deleteDocument( )

• publishDataModel( )

• rollbackDataModel( )

Use the exportDocument( ) procedure to save a copy of an original document before deleting it from the repository.

Only user-defined documents can be deleted. Documents installed by Oracle are default documents that cannot be removed. Additionally, to ensure conformance with referenced constraints, remove documents in the reverse order from the order in which they were loaded.

See Chapter 10 for reference information about these procedures. See Chapter 11 for an example of the deletion process.

The following subsections briefly describe the deletion process for different types of documents.

9.9 Oracle Data Pump Utilities Support for the Data Model Repository

Export and import using Oracle Data Pump is described in Oracle Database Utilities. This section provides guidelines and examples for using the Oracle Data Pump commands expdp and impdp to perform export and import operations on the DICOM data model repository, which is stored in the ORDDATA schema. Do so only if you have made changes to your data model repository.

See Oracle Database Utilities for more information about Oracle Data Pump and its command-line clients, expdp and impdp.

These examples use the commands expdp and impdp. After you enter the command with your user name and the appropriate parameters, you are prompted for a password. The examples in this section do not show these prompts.

expdp SCHEMAS=ORDDATA CONTENT=ALL DIRECTORY=DUMP_DIR 
  DUMPFILE=exp_orddata.dmp LOGFILE=exp_orddata.log

impdp SCHEMAS=ORDDATA CONTENT=ALL TABLE_EXISTS_ACTION=REPLACE 
  DIRECTORY=DUMP_DIR DUMPFILE=exp_orddata.dmp LOGFILE=imp_orddata.log