This section explains how to configure Functional Group (inner envelope or GS) ePM parameters for HIPAA PM. Figure 6–13 shows an ePM example with these parameters displayed. This section contains the following parameters:
Allows you to set a value to match the Group Name attribute of this business action, set in the B2B Host’s Business Service; required.
For example, a Group Name of “HS” is for a 270 action and “HB” for a 271 action.
None (depends on the current business action)
Allows you to enter a value representing the code identifying the party sending a message transmission. These codes are predefined and agreed upon by the TPs; required
The appropriate valid integer that represents the application sender code.
None
Allows you to enter a value representing the code identifying the party receiving a message transmission. These codes are predefined and agreed upon by the TPs; required.
The appropriate valid integer that represents the application sender code.
None
Allows you to set the date structure for this transaction set, in a format specified under “Required Values;” required.
CCYYMMDD or CCYYYYMMDD; choose from the list to use a four-digit or two-digit year format, for example:
20041201 = December 1, 2004
050112 = January 12, 2004
CCYYMMDD
Allows you to set the time structure for this transaction set, in a format specified under “Required Values;” required.
HHMM, HHMMSS, HHMMSSD, or HHMMSSDD.
Choose from the list to specify seconds and degrees of accuracy, for example:
2359 = 11:59PM
235959 = 11:59:59PM
23595999 = 11:59:59.99PM
The time is expressed in 24-hour (military) clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59); and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99).
HHMM
Allows you to enter the group control number assigned and maintained by the sender.
The appropriate valid integer that represents the group control number.
0
Allows you to enter a value representing the code used in conjunction with data element (DE) 480 used to identify the issuer of the current HIPAA standard; required.
The appropriate correct transaction set code (X is recommended, but you may have to use others, for example, T, as required by the current HIPAA standard being used.
X
Allows you to enter a value representing the code indicating the HIPAA version, release, subrelease, and industry identifier of the EDI standard being used, including the GS and GE segments; required.
If the responsible agency code under the GS07 segment is X (recommended), enter values as follows in the appropriate DE 480 positions:
1 through 3 = the current version number
4 through 6 = the release and subrelease levels of the current version
7 through 12 = the current industry or trade association identifiers (optionally assigned by the user)
If code entered for the GS07 segment is different, for example, T, then other formats are allowed, as required by the current HIPAA standard being used.
00401X091
Allows you to set the group control number that starts calculating the unique identifier for groups. The identifier increments by 1 from this number, for each additional group; required.
The appropriate integer.
0
Allows you to enter the URL for the external third-party validation server.
A valid URL allowing access to the external third-party validation server.
None
Allows you to specify whether to use the functional acknowledgment generated by the external third-party validation server; required.
Select true or false.
false
Allows you to specify whether to save interleaved error reports to text files. If you set this parameter to false, these error reports persist only in Message Tracking; required.
Select true or false.
false
If you do save interleaved error reports to text files (Save Report to Files is set to true), allows you to specify the directory path location where you want these error report files to be saved.
A valid directory path location accessible to eXchange.
None
Allows you to select whether to select third-party message validation is based on algorithms or multiple message responses.
Validation, the default option, assigns unique IDs to incoming transaction sets based on an algorithm embedded in validation routines (externally assigned). Internal assignment supports environments where multiple valid responses to a single unique ID are permissible, and an internally assigned ID is necessary; required.
Select Validation or Internal.
Validation
See Appendix A, Externally Assigned Unique IDs for more information on externally assigned unique IDs.