Transaction Viewer

The Detail View WebAcc~MemGetDetailCol# can display one or more segments as a Transaction Viewer segment.

When configured, the Detail View page displays a label and an icon for the segment. When a user clicks the icon, a pop-up window opens and shows the data that is configured for Transaction Viewer. Transaction Viewer supports implementation-defined segments, but does not support any custom formatting options used by the predefined segments.

Transaction Viewer is segment-based rather than attribute-based. Therefore, if you define multiple attributes for a segment and then set up that segment in Transaction Viewer, all the attributes show up in Transaction Viewer. For example, if you are using the segment MemAddr, you typically have a HOMEADDR and WORKADDR attributes for the MemAddr segment. If you define a Transaction Viewer window for MemAddr, you cannot limit it by a specific attribute so both HOMEADDR and WORKADDR rows display in the viewer.

To configure the Transaction Viewer, you must add the following entry to mpi_appprop:

For Person member type:

INSERT INTO mpi_appprop VALUES 
(101,101,"'A'",01,00,01,"'WebAcc~MemGetDetailCol1~PopUp'",
"'MemExtc,Event Summary,event.gif'");

For Provider member type:

INSERT INTO mpi_appprop VALUES 
(101,101,"'A'",01,00,02,"'WebAcc~MemGetDetailCol1~PopUp'",
"'MemCont,Contracts,contract.gif'");

For Guest member type:

INSERT INTO mpi_appprop VALUES 
(101,101,"'A'",01,00,03,"'WebAcc~MemGetDetailCol1~PopUp'",
"'MemExtc,Event Summary,stay.gif'");

Column #1 to Column #5 have the same definition as described in other topics.

Column #6 represents the ordering of the icons.

Column #7 - WebAcc~MemGetDetailCol#~PopUp is the key value that is used to indicate to InfoSphere® MDM Enterprise Viewer that you want to configure a Transaction Viewer segment. The # must be replaced with the member type.

Column #8 contains three tilde (~) delimited configuration parameters:

  1. Lists the segment class name to display. This is the not case-sensitive segcode name that is defined in mpi_seghead.segcode, for example: MemExta, MemExtb, MemExtc, MemExtd, MemCont. Reference the Java™ API documentation for more information. The mpi_seghead table can be used to determine both implementation-defined segment names and predefined segment names.
  2. The label to display on the page that describes the icon.
  3. The icon graphic name. The icon.gif file must be in the viewer.war file in the \images directory. Default icons that exist are event.gif (Person member type), contract.gif (Provider member type), and stay.gif (Guest member type).

After the Column #7 key is defined, the Column #8 key signals Enterprise Viewer to look for more configuration information with the key of WebAcc~MemExtc1.

INSERT INTO mpi_AppProp VALUES 
(101,101,"'A'",01,00,01,"'WebAcc~MemExtc1'","'AcctNumber~String~Acct Num'");
INSERT INTO mpi_AppProp VALUES 
(101,101,"'A'",01,00,02,"'WebAcc~MemExtc1'","'EncDate~Date~Encounter Date~-'");
INSERT INTO mpi_AppProp VALUES 
(101,101,"'A'",01,00,03,"'WebAcc~MemExtc1'","'DisDate~Date~Discharge Date'");
INSERT INTO mpi_AppProp VALUES 
(101,101,"'A'",01,00,04,"'WebAcc~MemExtc1'","'PatType~String~Patient Type'");
INSERT INTO mpi_AppProp VALUES 
(101,101,"'A'",01,00,05,"'WebAcc~MemExtc1'","'SvcType~String~Service Type'");
INSERT INTO mpi_AppProp VALUES 
(101,101,"'A'",01,00,06,"'WebAcc~MemExtc1'","'SvcLoc~String~Service Location'");
INSERT INTO mpi_AppProp VALUES 
(101,101,"'A'",01,00,07,"'WebAcc~MemExtc1'","'Phys1~String~Physician 1'");
INSERT INTO mpi_AppProp VALUES 
(101,101,"'A'",01,00,08,"'WebAcc~MemExtc1'","'Phys2~String~Physician 2'");
INSERT INTO mpi_AppProp VALUES 
(101,101,"'A'",01,00,09,"'WebAcc~MemExtc1'","'Plan1~String~Plan 1'");
INSERT INTO mpi_AppProp VALUES 
(101,101,"'A'",01,00,10,"'WebAcc~MemExtc1'","'Plan2~String~Plan 2'");
INSERT INTO mpi_AppProp VALUES 
(101,101,"'A'",01,00,11,"'WebAcc~MemExtc1'","'User1~String~User 1'");
INSERT INTO mpi_AppProp VALUES 
(101,101,"'A'",01,00,12,"'WebAcc~MemExtc1'","'User2~String~User 2'");

Column #6 represents the ordering of the fields on the window from left to right.

Column #7 is the key that consists of the application code "'WebAcc'" and the segment key, as previously defined, MemExtc with the memtypeno of 1appended to it. The full value of this key is "'WebAcc~MemExtc1'".

Column #8 contains four ~ delimited parameters that relate to the display of segment data.

  1. The first parameter is the Java method name that is used to retrieve the data from the segment. Typically this is the database column name.
  2. The data type of the field name. String, Date, Time, and DateTime are the supported data types. Other numeric data types should be configured as a String.
  3. The label to display on the table header for the data.
  4. The sorting option. The dash - means descending and plus sign + means ascending, while no value means that this field name is not used in sorting. You can define more than one column in the sort. The order is determined by the printing order: the first - or + found based on the Column 6 order is the major sort, and the next one found would be the minor sort, and so on.
Attention: You must remove the "‘get'" keyword before the field name because it causes an error when those columns are sorted. This parameter is not case-sensitive. The Java SDK documentation can be helpful in determining the correct field names for non-implementation-defined segments. The table mpi_segxfld can be used to look up field names for both implementation-defined and non-implementation-defined segments.


Last updated: 13 Dec 2016