Skip Navigation Links | |
Exit Print View | |
Understanding Oracle Java CAPS Master Index Configuration Options (Repository) Java CAPS Documentation |
Understanding Oracle Java CAPS Master Index Configuration Options (Repository)
About Oracle Java CAPS Master Index (Repository)
Oracle Java CAPS Master Index Configuration
Features of Oracle Java CAPS Master Index
Configuration Overview for Oracle Java CAPS Master Index (Repository)
About the Configuration Files for Oracle Java CAPS Master Index (Repository)
Master Index Object Definition File
Master Index Candidate Select File
Master Index Field Validation File
Master Index Enterprise Data Manager File
Match and Standardization Engine Configuration Files
Using the Editors for Oracle Java CAPS Master Index (Repository)
Configuration Editor - Repository
Master Index Object Definition Configuration (Repository)
Master Index Object Definition Components (Repository)
Master Index Object Definition Objects
Master Index Object Definition Fields
Master Index Object Definition Relationships
The Master Index Object Definition File (Repository)
Modifying the Master Index Object Definition
Object Definition File Description
Object Definition File Example
Candidate Select Configuration (Repository)
Query Builder Components (Repository)
Basic Queries in a Master Index (Repository)
Blocking Queries in a Master Index (Repository)
Phonetic Queries in a Master Index (Repository)
The Candidate Select File (Repository)
Modifying the Candidate Select File
Candidate Select File Description
Range Search Processing (Repository)
Blocking Query Range Searching
Blocking Query Offset and Constant Combinations
Threshold Configuration (Repository)
Manager Service Components (Repository)
The Threshold File (Repository)
Match Field Configuration (Repository)
Matching Service Components (Repository)
Match and Standardization Engines
Block Picker and Pass Controller
Sample Standardization and Matching Sequence (Repository)
The Match Field File (Repository)
Modifying the Match Field File
Best Record Configuration (Repository)
The Survivor Calculator and the SBR (Repository)
Update Manager Components (Repository)
Survivor Helper Default Strategy
Survivor Helper Weighted Strategy
Survivor Helper Union Strategy
Weighted Calculator SourceSystem Strategy
Weighted Calculator SystemAgreement Strategy
Weighted Calculator MostRecentModified Strategy
Update Manager Update Policies
Update Manager Update Policy Flag
The Best Record File (Repository)
Modifying the Best Record File
Field Validation Configuration (Repository)
The Field Validation File (Repository)
Modifying the Field Validation File
The Enterprise Data Manager (EDM) is the web-based user interface for the master index application that allows you to monitor and modify data in the index. This interface is highly configurable, and can be customized by modifying the Enterprise Data Manager file in the maser index project.
The following topics describe the EDM, the Enterprise Data Manager file structure, and how the EDM can be configured:
The EDM is a web-based interface that allows you to manage and monitor the data in your master index database. Using the EDM, you can search for records; add, update, deactivate, and reactivate records; review and resolve potentially duplicate records; compare records; and merge and unmerge records. You can also view a transaction history for each record and an audit log of access to the database. This interface is highly configurable, allowing you to customize certain processing properties as well as the appearance of certain windows.
The EDM facilitates the use of screen readers and other assistive technology by providing information through HTML tags. It also provides tooltips when the cursor is placed over links and images on the EDM pages.
You can configure several properties of the EDM to display the information you want in the way you want, to define the way searches can be processed, and to define the criteria that can be used for each search. Certain implementation options are also configured in the Enterprise Data Manager file, such as application server information, debug options, and security information.
The configurable properties of the user interface fall into these five categories:
In the Enterprise Data Manager file, you can specify which objects appear on the EDM windows and the order in which they appear. You can also specify the fields displayed in each object and configure properties for each field. You can specify a field’s name, length, order of appearance on the EDM, required data type, whether text can be entered into a field or if it must be selected from a predefined value, whether a field or combination of fields must be unique to the parent object, and whether the value of the field is hidden under certain circumstances. You can also specify whether the format of a field is dependent on the value of a related field (for example, the format of a credit card number field could be dependent on the type of credit card specified).
In the Enterprise Data Manager file, relationships define the hierarchy of the object types listed for the EDM. By specifying relationships, you define parent and child nodes. The parent and child nodes you specify in the relationships element must also be defined in the node elements of the file. You can specify one parent object; the remaining objects must be child objects to the parent you define. This section is dependent on the relationships section in the Object Definition file, and should only be changed if corresponding changes are made to the Object Definition file.
You can configure several display properties for the pages that appear on the EDM. For most configurable pages, you can specify the number of fields on each row, and for all search pages you can specify the number of results to display on each page. You can also specify the type of object to display on a page and the name of the tabbed heading.
Certain properties of the following pages can be configured:
In the display configuration, you can specify whether an audit log is maintained of all instances in which object information was accessed from the EDM. If the log is maintained, then information about each instance of access can be viewed on the EDM. This is especially useful in healthcare implementations, where privacy of information is mandated.
A local ID is a unique identification code assigned to a record by the system in which the record originated. By default, this code is named “Local ID” on the EDM pages. This name can be modified to a name more recognizable by EDM users.
Of the configurable pages, the page that requires the most configuration is the Search page. In addition to defining the number of fields per row and the number of records to display in the search results list, you can also specify the search criteria that appear and the types of searches allowed from the EDM.
You can define and name several search pages, each with their own configuration. For each page, you specify groups of fields that are displayed in boxed areas. Each boxed area can represent a different type of search, such as a demographic search, address search, EUID search, and so on.
For each search page you define, you must also specify the search types available, such as alphanumeric or phonetic. You can configure searches by specifying a name for the search, the maximum number of records to return, whether the results are weighted, and whether wildcard characters can be used. When you define the search types for the EDM, you must specify a query for each type you define. The queries you specify must already be defined in the Candidate Select file.
The Enterprise Data Manager file defines certain information about the application server for the master index implementation, such as the names of certain validation and management components, debug parameters, and security information. The security for the master index application is based in the application server.
EDM properties are defined in the Enterprise Data Manager file in XML format. Some of the information entered into the default configuration file is based on the fields you defined in the wizard, and some is standard across all implementations. For most implementations, this file will require customization.
The following topics provide information about working with the Enterprise Data Manager file:
You can modify the Enterprise Data Manager file at any time, but you must regenerate the application and redeploy the project after making any changes to the file. Changes made to this file do not affect match processing; it only affects the EDM. Most components of this file cannot be modified using the Configuration Editor; you need to modify the file directly. The possible modifications to this file are restricted by the schema definition, so be sure to validate the file after making any changes.
Table 14 lists each element in the Enterprise Data Manager file and provides a description of each element along with any requirements or constraints for each element.
Table 14 Enterprise Data Manager File Structure
|
Below is a short sample of the Enterprise Data Manager file based on a master index application processing person information.
<node-Person> <field-LastName> <display-name>Last Name</display-name> <display-order>1</display-order> <max-length>40</max-length> <gui-type>TextBox</gui-type> <value-type>string</value-type> <key-type>true</key-type> </field-LastName> <field-FirstName> <display-name>First Name</display-name> <display-order>2</display-order> <max-length>40</max-length> <gui-type>TextBox</gui-type> <value-type>string</value-type> <key-type>true</key-type> </field-FirstName> <field-DOB> <display-name>DOB</display-name> <display-order>3</display-order> <max-length>32</max-length> <gui-type>TextBox</gui-type> <value-type>date</value-type> <key-type>true</key-type> </field-DOB> <field-Gender> <display-name>Gender</display-name> <display-order>4</display-order> <max-length>8</max-length> <gui-type>MenuList</gui-type> <value-list>GENDER</value-list> <value-type>string</value-type> <key-type>true</key-type> </field-Gender> <field-SSN> <display-name>SSN</display-name> <display-order>5</display-order> <max-length>16</max-length> <gui-type>TextBox</gui-type> <value-type>string</value-type> <input-mask>DDD-DD-DDDD</input-mask> <value-mask>DDDxDDxDDDD</value-mask> <is-sensitive>true</is-sensitive> </field-SSN> </node-Person> <node-Alias display-order="1"> <field-LastName> <display-name>LastName</display-name> <display-order>1</display-order> <max-length>40</max-length> <gui-type>TextBox</gui-type> <value-type>string</value-type> <key-type>true</key-type> </field-LastName> <field-FirstName> <display-name>FirstName</display-name> <display-order>2</display-order> <max-length>40</max-length> <gui-type>TextBox</gui-type> <value-type>string</value-type> <key-type>true</key-type> </field-FirstName> </node-Alias> <relationships> <name>Person</name> <children>Alias</children> </relationships> <impl-details> <master-controller-jndi-name>ejb/PersonMasterController </master-controller-jndi-name> <validation-service-jndi-name>ejb/PersonCodeLookup </validation-service-jndi-name> <usercode-jndi-name>ejb/PersonUserCodeLookup</usercode-jndi-name> <reportgenerator-jndi-name>ejb/PersonReportGenerator </reportgenerator-jndi-name> <debug-flag>true</debug-flag> <debug-dest>console</debug-dest> <enable-security>true</enable-security> <object-sensitive-plug-in-class> com.stc.eindex.security.VIPObjectSensitivePlugIn </object-sensitive-plug-in-class> </impl-details> <gui-definition> <system-display-name-overrides> <local-id-header>System Identifier</local-id-header> <local-id>System ID</local-id> </system-display-name-overrides> <page-definition> <eo-search> <root-object>Person</root-object> <tab-name>Person Search</tab-name> <tab-entrance>/EnterEOSearchSimpleAction.do</tab-entrance> <simple-search-page> <screen-title>Advanced Lookup (Phonetic)</screen-title> <field-per-row>2</field-per-row> <show-euid>false</show-euid> <show-lid>false</show-lid> <instruction/> <field-group> <description>Demographics</description> <field-ref>Person.LastName</field-ref> <field-ref>Person.FirstName</field-ref> <field-ref choice="range">Person.DOB</field-ref> <field-ref>Person.Gender</field-ref> <field-ref>Person.SSN</field-ref> </field-group> <search-option> <display-name>Phonetic Search</display-name> <query-builder>BLOCKER-SEARCH2</query-builder> <weighted>true</weighted> <parameter> <name>UseWildcard</name> <value>false</value> </parameter> </search-option> </simple-search-page> <simple-search-page> <screen-title>Advanced Lookup (Alpha)</screen-title> <field-per-row>2</field-per-row> <show-euid>false</show-euid> <show-lid>false</show-lid> <instruction>Enter as much information as possible to narrow the search</instruction> <field-group> <description>Demographics</description> <field-ref>Person.LastName</field-ref> <field-ref>Person.FirstName</field-ref> <field-ref>Person.Gender</field-ref> <field-ref choice="range">Person.DOB</field-ref> <field-ref>Person.SSN</field-ref> </field-group> <search-option> <display-name>Alpha Search</display-name> <query-builder>ALPHA-SEARCH</query-builder> <weighted>false</weighted> <parameter> <name>UseWildcard</name> <value>true</value> </parameter> </search-option> </simple-search-page> <simple-search-page> <screen-title>Simple Person Lookup</screen-title> <field-per-row>2</field-per-row> <show-euid>true</show-euid> <show-lid>true</show-lid> <instruction/> <field-group> <description>SSN</description> <field-ref>Person.SSN</field-ref> </field-group> <search-option> <display-name>Alpha Search</display-name> <query-builder>ALPHA-SEARCH</query-builder> <weighted>false</weighted> <parameter> <name>UseWildcard</name> <value>true</value> </parameter> </search-option> </simple-search-page> <search-result-list-page> <item-per-page>10</item-per-page> <max-result-size>100</max-result-size> <field-ref>Person.LastName</field-ref> <field-ref>Person.FirstName</field-ref> <field-ref>Person.DOB</field-ref> </search-result-list-page> <eo-view-page> <field-per-row>1</field-per-row> </eo-view-page> </eo-search> <create-eo> <root-object>Person</root-object> <tab-name>Create System Record</tab-name> <tab-entrance>/EnterEOCreateAction.do</tab-entrance> </create-eo> <history> <root-object>Person</root-object> <tab-name>History</tab-name> <tab-entrance>/EnterXASearchAction.do</tab-entrance> <xa-search-page> <field-per-row>2</field-per-row> </xa-search-page> <search-result-list-page> <item-per-page>10</item-per-page> <max-result-size>100</max-result-size> <field-ref>Person.FirstName</field-ref> <field-ref>Person.LastName</field-ref> </search-result-list-page> <merge-history-key-field> <field-ref>Person.FirstName</field-ref> <field-ref>Person.LastName</field-ref> </merge-history-key-field> </history> <matching-review> <root-object>Person</root-object> <tab-name>Matching Review</tab-name> <tab-entrance>/EnterPDSearchAction.do</tab-entrance> <pd-search-page> <field-per-row>2</field-per-row> </pd-search-page> <search-result-list-page> <item-per-page>10</item-per-page> <max-result-size>100</max-result-size> </search-result-list-page> </matching-review> <reports> <root-object>Person</root-object> <tab-name>Reports</tab-name> <tab-entrance>/EnterReportSearchAction.do</tab-entrance> <search-page-field-per-row>2</search-page-field-per-row> <report name="Potential Duplicate" title="Potential Duplicate Report"> <enable>true</enable> <max-result-size>2000</max-result-size> <fields> <field-ref>Person.FirstName</field-ref> <field-ref>Person.LastName</field-ref> <field-ref>Person.SSN</field-ref> <field-ref>Person.DOB</field-ref> </fields> </report> </reports> <audit-log> <allow-insert>false</allow-insert> </audit-log> </page-definition> </gui-definition>