TIBCO Foresight® Transaction Insight® · In the absence of the Foresight Translator Claims Attachment Adapter, users must create their own 275/277 generation solution. Foresight

TIBCO Foresight® Transaction Insight®

275 and 277 Transactions

Software Release 5.2

September 2017

Two-second advantage®

Important Information

SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH EMBEDDED OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (OR PROVIDE LIMITED ADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THE EMBEDDED OR BUNDLED SOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANY OTHER TIBCO SOFTWARE OR FOR ANY OTHER PURPOSE.

USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS AND CONDITIONS OF A LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED SOFTWARE LICENSE AGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THE CLICKWRAP END USER LICENSE AGREEMENT WHICH IS DISPLAYED DURING DOWNLOAD OR INSTALLATION OF THE SOFTWARE (AND WHICH IS DUPLICATED IN THE LICENSE FILE) OR IF THERE IS NO SUCH SOFTWARE LICENSE AGREEMENT OR CLICKWRAP END USER LICENSE AGREEMENT, THE LICENSE(S) LOCATED IN THE “LICENSE” FILE(S) OF THE SOFTWARE. USE OF THIS DOCUMENT IS SUBJECT TO THOSE TERMS AND CONDITIONS, AND YOUR USE HEREOF SHALL CONSTITUTE ACCEPTANCE OF AND AN AGREEMENT TO BE BOUND BY THE SAME.

This document contains confidential information that is subject to U.S. and international copyright laws and treaties. No part of this document may be reproduced in any form without the written authorization of TIBCO Software Inc.

TIBCO, Two-Second Advantage, TIBCO ActiveMatrix BusinessWorks, TIBCO BusinessConnect, TIBCO Foresight EDISIM, TIBCO Foresight HIPAA Validator Desktop, TIBCO Foresight Instream, TIBCO Foresight Transaction Insight, and TIBCO Foresight Translator Claims Attachment Adapter are either registered trademarks or trademarks of TIBCO Software Inc. in the United States and/or other countries.

Enterprise Java Beans (EJB), Java Platform Enterprise Edition (Java EE), Java 2 Platform Enterprise Edition (J2EE), and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle Corporation in the U.S. and other countries.

The United States Postal Service holds the copyright in the USPS City State Zip Codes. (c) United States Postal Service 2017.

All other product and company names and marks mentioned in this document are the property of their respective owners and are mentioned for identification purposes only.

THIS SOFTWARE MAY BE AVAILABLE ON MULTIPLE OPERATING SYSTEMS. HOWEVER, NOT ALL OPERATING SYSTEM PLATFORMS FOR A SPECIFIC SOFTWARE VERSION ARE RELEASED AT THE SAME TIME. SEE THE README FILE FOR THE AVAILABILITY OF THIS SOFTWARE VERSION ON A SPECIFIC OPERATING SYSTEM PLATFORM. THIS DOCUMENT IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT.

THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS. CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESE CHANGES WILL BE INCORPORATED IN NEW EDITIONS OF THIS DOCUMENT. TIBCO SOFTWARE INC. MAY MAKE IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S) AND/OR THE PROGRAM(S) DESCRIBED IN THIS DOCUMENT AT ANY TIME.

THE CONTENTS OF THIS DOCUMENT MAY BE MODIFIED AND/OR QUALIFIED, DIRECTLY OR INDIRECTLY, BY OTHER DOCUMENTATION WHICH ACCOMPANIES THIS SOFTWARE, INCLUDING BUT NOT LIMITED TO ANY RELEASE NOTES AND "READ ME" FILES.

Copyright © 2010-2017 TIBCO Software Inc. ALL RIGHTS RESERVED.

TIBCO Software Inc. Confidential Information

General Contact Information

TIBCO Software Inc.

3303 Hillview Avenue

Palo Alto, CA 94304 USA

Tel: +1 650 846 1000

Fax: +1 650 846 1005

Technical Support

E-mail: [email protected]

Web: https://support.tibco.com

(Note: Entry to this site requires a username and password. If you do not have one, you can request one. You must have a valid

maintenance or support contract to use this site.)

mailto:[email protected]

https://support.tibco.com/

275 and 277 Transactions 1

Contents

Introduction 1

Overview 1

Typical Scenario .................................................................................................... 1

TIBCO Foresight Tools 2

Transaction Insight Role ........................................................................................ 2 Foresight Translator Claims Attachment Adapter Role ......................................... 2

275 Attachments Page 3

Configuration .......................................................................................................... 3 Configuring Transaction Insight ............................................................................. 3 Customizing the 275 Settings File (Optional) ........................................................ 5 Granting User Permissions .................................................................................... 7 Using the 275 Attachments Page .......................................................................... 8

277 Attachment Requests 11

Configuration ........................................................................................................ 11 Configuring Transaction Insight ........................................................................... 11 Customizing the 277 Settings File (Optional) ...................................................... 12 Granting User Permissions .................................................................................. 13 Using the 277 Attachment Request Page............................................................ 15

Integration with the Foresight Translator Claims Attachment Adapter 17

Creating a 275 with Embedded Attachment ........................................................ 17 Extracting an Embedded Attachment from a 275 ................................................ 17 Creating a 277 ...................................................................................................... 17 Transmitting a 275 or 277 .................................................................................... 18

Appendix A: Attachment Files 19

Appendix B: DDE File Details 21

Appendix C: 275 Attachments Page Data Map 22

Appendix D: 277 Settings File Customization Details 24

Defining ControlValues ........................................................................................ 26

Appendix E: How TIBCO Foresight Programs work with 275s 27



Introduction

This document contains administration, configuration, and general usage information

about theTIBCO Foresight® Transaction Insight® Healthcare Edition 275 Attachment

and 277 Attachment Request capabilities and how those capabilities work with the

TIBCO Foresight® Translator Claims Attachment Adapter to provide a solution for

generation and delivery of 275 (with embedded attachments) and 277 transactions.

Note: Foresight® Translator Claims Attachment Adapter is sold separately; contact

your TIBCO Foresight representative for more information.

Overview

275 Health Care Services Review and 277 Health Care Claim Request transactions

are used by Payers and Providers as a method of requesting and supplying

information for healthcare claims processing.

Transaction Insight® provides users working with health care claims the ability to

create the data files needed to generate 275 (with embedded attachments) and 277

transactions.

Foresight Translator Claims Attachment Adapter can then be used to

generate and transmit the 275 and/or 277 transactions and to extract the

embedded attachment from a 275.

Note: In the absence of the Foresight Translator Claims Attachment Adapter,

Payers and Providers must create their own 275/277 generation, delivery, and

extraction solutions.

Typical Scenario

This scenario illustrates the use of 275s and 277s:

1. The Payer receives an 837 Healthcare Claim from a Provider pertaining to services

rendered.

2. The Payer decides that supporting information (e.g., an x-ray) is needed from the

Provider before the claim can be processed.

3. The Payer uses Transaction Insight to generate data files for use in the creation of a

277 request for additional information.

4. The Payer passes the data files to the Foresight Translator Claims Attachment

Adapter, which generates a 277 transaction and delivers it to the Provider.

5. The Provider receives the 277 request and uses Transaction Insight to generate data

files for use in the creation of a 275 with the requested attachment embedded in the

275s BDS03 segment.

6. The Provider passes the data files to the Foresight Translator Claims Attachment

Adapter, which generates a 275 with an embedded attachment and delivers it to the

Payer.

7. The Payer uses the Foresight Translator Claims Attachment Adapter to extract the

embedded attachment from the 275s BDS03 segment.


TIBCO Foresight Tools

This section details the roles that Transaction Insight and Foresight Translator

Claims Attachment Adapter play in creating 275 and 277 transactions. When

working with these products you may find it useful to refer to the following

documents:

TIBCO Foresight Transaction Insight Common Administration

TIBCO Foresight Transaction Insight User’s Guide

TIBCO Foresight Translator Claims Attachment Adapter User’s Guide

For a description of how other TIBCO Foresight products, such as TIBCO Foresight®

EDISIM® and TIBCO Foresight® Instream®, work with 275/277 transactions, see

Appendix E: How TIBCO Foresight Programs work with 275s on page 27.

Transaction Insight Role

Transaction Insight is used to create the data files necessary for generation of a 275

transaction with an embedded attachment and/or a 277 transaction.

This is achieved by using the following pages within Transaction Insight:

275 Attachments Page – creates two data files: an attachment file and a DDE

file.

277 Attachment Request Page – creates an attachment request data DDE

file.

These file are then passed to the Foresight Translator Claims Attachment Adapter

for generation of the 275 or 277 transaction.

In the absence of the Foresight Translator Claims Attachment Adapter, users

must create their own 275/277 generation solution.

Foresight Translator Claims Attachment Adapter Role

The Foresight Translator Claims Attachment Adapter is a customizable set of tools

that gives users the ability to take the files generated by Transaction Insight and

perform the following tasks:

Create a 6020 275X316 Health Care Services Review transaction containing

an attachment (with a CDA header and wrapped in MIME) stored in the

BDS03 segment

Create 277 Health Care Claim Request for Additional Information transaction

Communicate with a Secure Exchange Solutions (SES) Direct server in order

to send and receive messages containing SES XML and attachments

Extract health care claim attachments from 6020 275X316 transactions.

In the absence of the Foresight Translator Claims Attachment Adapter, users must

create their own 275/277 generation, delivery, and extraction solutions.

Note: The Foresight Translator Claims Attachment Adapter is compatible with 5010

versions of 275s and 277s however Transaction Insight only supports the 6020

versions.


275 Attachments Page

Configuration

Before users can access the 275 Attachments page, configuration by the Transaction

Insight administrator is required.

Configuring Transaction Insight

1. Access the Transaction Insight Common Administration Admin | Settings page.

2. Click the General Settings tab.

3. Edit the following settings:

275AttachmentFileMaximumSize Enter the Maximum Size limit for the 275

attachment file in megabytes. Default is 64MB, the

X12N limit per BDS segment. Recommendation:

do not exceed this limit.

275AttachmentFilesDirectory This is a directory where Transaction Insight will

store:

The attachment – uploaded when a user

clicks Upload Attachment from the 275

Attachments page.

The corresponding DDE file – created

when a user clicks Save Attachment from

the 275 Attachments page.

Do not use quotation marks in the path.

Be sure the path ends with a slash or back slash (/

or \).


Example:

C:/Foresight/TransactionInsight/

275AttachData/

Note: Set this to a directory that has ASP.NET

read/write permission (see Step 5).

4. Create or verify the directory for the 275 DDE file and attachments:

5. Check the directory’s ASP.NET permission:

a. Right-click on the directory and choose Properties > Security (or equivalent

on your system):

b. Under Security, look for ASP.NET and be sure that it has read/write/execute

permissions.


c. If ASP.NET is not in the list of names, add it. Type servername \ASPNET and click

Check Names. If it becomes underlined, it is correct and you can add it and then

select the necessary permissions:

Customizing the 275 Settings File (Optional)

The information on the 275 Attachments page and the settings in the 275settings.xml

file are used to create a DDE file, which supplies the values for the elements in the

275 that is created by the Foresight Claims Attachment Adapter.

In the TIPortal > TIWeb directory, there are three 275Settings files.

275Settings.xml – the settings file always used by Transaction Insight during

data creation. By default this file contains the same content as

275Settings_6020_BW.xml.

275Settings_6020_BC.xml – a file with settings suitable for use with TIBCO

BusinessConnect™.

275Settings_6020_BW.xml – a file with settings suitable for use with TIBCO

ActiveMatrix BusinessWorks™.

Comments and default values within 275Settings.xml can be customized but note

that doing so has no impact on the appearance of the 275 Attachments page.

Recommendation: If customizations are made, make a backup copy of your

modified 275Settings.xml file and store it in a safe directory. As new versions of

Transaction Insight are installed, the 275settings.xml file located in TIPortal > TIWeb

may be overwritten with a new default file.


Use the following steps to customize 275settings.xml.

1. Open 275settings.xml with an XML tool or a text editor.

2. If you are not using the Foresight Translator Claims Attachment Adapter, continue

with Step 3.

If you are using the Foresight Translator Claims Attachment Adapter:

- TIBCO ActiveMatrix BusinessWorks™ customers - continue with Step 3.

- TIBCO BusinessConnect™ customers - copy the content of

275Settings_6020_BC.xml file and paste it into 275settings.xml, replacing all

text. Save and continue with Step 3.

3. To add comments, select the Comment field:

Edit as desired:

4. To change default values, select the Value field.

Change values to the ones you want to use in the 275s you will be creating.

Notes:

Do not include trailing spaces. Values will automatically be padded to meet

minimum lengths.

Only change tags that already have values. For example, the FileName

tag is empty, so leave it empty. It will be filled automatically by

Transaction Insight.

Keep proper XML structure with starting and ending tags, etc.

5. Save.


Granting User Permissions

1. Log on to the Transaction Insight Portal as an administrator.

2. Under Roles, edit the Administrators role.

3. Verify that 275 Attachments is selected.

4. If non-administrators will be creating 275s, either add that permission to their

existing roles or create a new role especially for those who create 275s.

5. Under the Roles | Users tab, assign that role to users who will create 275s.

Here are permissions that affect the ability to upload and view 275s in

Transaction Insight:

Permission Access Granted Additional Abilities

Admin All pages under the Admin label on

the left menu

Control ability to

restrict/permit 275 upload

page access

Statistics User can view all pages under the

Statistics label on the main menu

Users having access to All

Partners can view 275

summary data

Files 275 Upload Page – Upload

attachment file and save attachment

details to create 275 documents

Upload 275 documents

Search The Documents page under the

Search label on the main menu

Search for 275 documents

Example 1 – Users who only upload 275s

Permissions Upload 275 Attachments

Partner Group None

User gets this menu

When users click 275 Attachments, they are taken to the screen described on page 8.


Example 2 – General purpose user with 275 upload

Permissions Statistics Read

Tasks Read

Files Upload

View

275 Attachment

Partner Group Hillsdale

User gets this

menu

(can see only

data for Hillsdale

partner)

Using the 275 Attachments Page

1. Log in to the portal with a username that has 275 permission (see Granting User

Permissions on page 7).

2. Choose 275 Attachments on the Files menu.

3. The 275 Claim Attachments Page appears.


When you access the 275 Claim Attachments Page for the first time, all fields are

blank. After you’ve submitted a 275 Claim Attachments Page once, the form will be

pre-populated with the values you used previously.

Before uploading an attachment you must populate (at a minimum) all required field

on the form. Required fields are marked with a blue asterisk.

4. At the top, click Choose File and choose the attachment file.

5. Click Upload Attachment.

Look for the “Successfully uploaded file” message.

(A Remove This File link appears in case you upload the wrong file.)


Results

For each upload, two files are saved to the directory specified in Settings > General

Settings > 275AttachmentFilesDirectory

the attachment

the corresponding DDE file

Each file is named using an automatically generated GUID.

See Appendix A: Attachment Files on page 19.

See Appendix B: DDE File Details on page 21.


277 Attachment Requests

Configuration

Before users can access the 277 Attachment Request page, configuration by the

Transaction Insight administrator is required.

Configuring Transaction Insight

1. Access the Transaction Insight Common Administration Admin > Settings page.

2. Click the General Settings tab.

3. Edit the following settings:

277AttachmentRequestFiles

Directory

This is a directory where Transaction Insight will

store 277 Attachment Requests.

Do not use quotation marks in the path.

Be sure the path ends with a slash or back slash

(/ or \).

Example:

C:/Foresight/TransactionInsight/

277AttachmentRequest/

277AttachmentRequestTemplate

File

Enter the path and filename of the 277 Attachment

Requests template file. See Customizing the 277

Settings File (Optional) on page 12.

By default, this is set to ~/277Settings.xml


4. Verify/create the directory for the 277 Attachment Requests:

Customizing the 277 Settings File (Optional)

277Settings.xml is a template file in the Transaction Insight environment’s TIWeb

directory that contains settings used to define the structure of the 277 Attachment

Request page.

In the TIPortal > TIWeb directory, there are three 277Settings files.

277Settings.xml – the default settings file used by Transaction Insight during

data creation. By default this file contains the same content as

277Settings_6020_BW.xml.

277Settings_6020_BC.xml – a file with settings suitable for use with TIBCO

BusinessConnect™.

277Settings_6020_BW.xml – a file with settings suitable for use with TIBCO

ActiveMatrix BusinessWorks™.

The default 277Settings.xml file produces a basic 277 Attachment Request page with

a workable structure, containing values that represent the most common usage for

the fields.

The file is customizable and you may opt to create your own template or multiple

templates, depending on your needs.

Recommendation: If customizations are made, make a backup copy of your

modified 277Settings.xml file and store it in a safe directory. As new versions of

Transaction Insight are installed, the 277settings.xml file located in TIPortal > TIWeb

may be overwritten with a new default file.


To customize:

1. Edit 277Settings.xml with an XML tool or a text editor.

2. Change the settings as needed to produce your desired 277 Attachment Request

page.

Example:

There are numerous fields that can be customized. For details, see Appendix D: 277

Settings File Customization Details on page 24.

Notes:

Do not include trailing spaces. Values will automatically be padded to meet

minimum lengths.

Keep proper XML structure with starting and ending tags, etc.

3. Save the file, renaming if desired.

4. To use a renamed file, specify the correct template name in Settings | General

Settings | 277AttachmentRequestTemplateFile (see Configuring on page 11).

Granting User Permissions

1. Log on to the Transaction Insight Portal as an administrator.

2. Under Roles, edit the Administrators role.

3. Verify that 277 Attachment Requests is selected.

4. If non-administrators will be creating 277 Attachment Requests, either add that

permission to their existing roles or create a new role especially for those who

will be doing so.


5. Under the Roles | Users tab, assign that role to users who will create 277

Attachment Requests.

Here are permissions that affect the ability to upload and view 277 Attachment

Requests in Transaction Insight:

Permission Access Granted Additional Abilities

Admin All pages under the Admin label on

the left menu

Control ability to

restrict/permit 277 page

access

Statistics User can view all pages under the

Statistics label on the main menu

Users having access to All

Partners can view 277

summary data

Files 277 Attachment Requests Page –

Create 277 Attachment Requests

Create 277 documents

Search The Documents page under the

Search label on the main menu

Search for 277 documents

Example 1 – Users who Create 277 Attachment Requests

Permissions Generate 277 Attachment requests

Partner Group None

User gets these

options From the Files menu

From an 837 view

When users click 277 Attachment Request, they are taken to the screen described

in Using the 277 Attachment Request Page on page 15.


Example 2 – General purpose user with 277 Attachment Requests

Permissions Statistics Read

Tasks Read

Files Upload

View

275 Attachment

277 Attachment Requests

Partner Group Hillsdale

User gets this

menu

(can see only

data for Hillsdale

partner)

Using the 277 Attachment Request Page

For complete details about the 277 Attachment Request Page, refer to the TIBCO

Foresight Transaction Insight User’s Guide.

1. Log in to the portal with a username that has 277 permissions (see Granting User

Permissions on page 13).

2. Use one of two ways to access the 277 Attachments Request Page.

a. Select Files | 277 Attachment Request.

Accessing the form in this way results in a blank 277 document.

b. Click Generate Attachment Request at the bottom of an 837 document

view page.

Accessing the form in this way causes the 277 Attachment Request to be pre-

populated with information.


3. If needed, populate the form. Required fields are marked with a blue asterisk.

Note that the content of the page is configured by the Transaction Insight

administrator, who may opt to pre-populate certain fields.

4. Click Submit Request or Cancel to exit.

Results

For each submission, a file containing the attachment request is saved to the

directory specified in Settings | General Settings |

277AttachmentRequestFilesDirectory


Integration with the Foresight Translator Claims Attachment

Adapter

Note: Refer to the TIBCO Foresight Translator Claims Attachment Adapter User’s

Guide for complete information about the Claims Attachment Adapter.

After creation of the appropriate files by Transaction Insight, the Foresight Claims

Attachment Adapter can be used to generate and transmit the 275 (with embedded

attachment) and/or 277 transactions and to extract the embedded attachment from a

275.

The Foresight Claims Attachment Adapter can be used for both unsolicited and

solicited 275s.

An unsolicited 275 is one which a Provider creates and submits to a Payer

without having been asked to do so.

A solicited 275 is one which a Payer has requested from a Provider, typically

using a 277 Health Care Claim transaction.

Creating a 275 with Embedded Attachment

Input the Transaction Insight-generated 275 attachment and DDE files along with a

CDA file into the Foresight Claims Attachment Adapter.

Refer to CDA File in the TIBCO Foresight Translator Claims Attachment Adapter

User’s Guide.

The Foresight Claims Attachment Adapter creates a 6020 275X316 Health Care

Services Review transaction with the requested attachment contained in the BDS03

segment.

Refer to Completed 6020 275X316 Details in the TIBCO Foresight Translator Claims

Attachment Adapter User’s Guide.

Extracting an Embedded Attachment from a 275

Input the 275 (with embedded attachment) into the Foresight Claims Attachment

Adapter.

The Foresight Claims Attachment Adapter is used to extract the attachment from the

6020 275X316 BDS03 segment and saves the information into two EDI files: CDA

header and attachment.

Refer to Extracting the 275 in the TIBCO Foresight Translator Claims Attachment

Adapter User’s Guide.

Creating a 277

Input the Transaction Insight-generated 277 DDE file into the Foresight Claims

Attachment Adapter.

The Foresight Claims Attachment Adapter creates a compliant 277 Health Care

Claim Request.


Transmitting a 275 or 277

The Foresight Claims Attachment Adapter can be used to communicate with a

Secure Exchange Solutions (SES) Direct server in order to send and receive

messages containing SES XML and attachments.

Refer to SES Direct Communication in the TIBCO Foresight Translator Claims

Attachment Adapter User’s Guide.


Appendix A: Attachment Files

The attachment file contains binary information that goes into the 275s BDS03

element.

In general, an attachment can be of any file type. Some examples are:

an x-ray in .jpg format

clinical notes in .pdf format

an MRI in .gif format

bloodwork results in .doc format.

When following the X12N limit per BDS segment, the attachment size has a limit of

64 MB. Otherwise the attachment size is unlimited.

Example

The file xray.jpg contains the x-ray.

Viewed as a graphic, it looks like this:

It is actually binary information...


...and will appear in the BDS03 element as such:

------=_Part_0_1795616519.1427119732914

Content-Type: application/octet-stream; name=xray.jpg

Content-Transfer-Encoding: base64

Content-Disposition: attachment; filename=xray.jpg

Content-ID: xray.jpg

/9j/4AAQSkZJRgABAQAAAQABAAD/2wCEAAkGBxMTEhUUExQVFhQUGBcaGBcXFxcdHBUcFRcYF

xcY

HBgYHCggGBo

lHBgUITEhJSkrLi4uGB8zODMsNygtLisBCgoKDg0OGxAQGywkICQsLCwsLCwsLCws

LCwsLCwsLCwsLCwsLCwsLCwsL

CwsLCwsLCwsLCwsLCwsLCwsLCwsLP/AABEIAMIBAwMBEQACEQED EQH/

xAAbAAABBQEBAAAAAAAAAAAAAAACAAEDBAUGB

//EAEIQAAEDAgMECAUBBQcDBQAAAAEAAhED

IQQSMQVBUWEGE3GBkaGx8CIyQsHRUhQjM2LhB3KSorLS8UOCwhVTc4Pi

/8QAGgEAAwEBAQEAAAAA AAAAAAAAAQIDAAQFBv/

EADURAAICAQIDBQgCAgIDAQEAAAABAhEDITEEEkEiUWFx8AUTMoGRobHR

.

.

.

------=_Part_0_1795616519.1427119732914


Appendix B: DDE File Details

These files supply the values for the elements in the 275 that is created by the

Foresight Claims Attachment Adapter:

A user-created DDE file (created with Transaction Insight’s 275 Attachments

page)

The DDE file is an XML representation of your data. It must contain X12-required

segments such as TRN, NM1, and BDS. The file is used to populate the created 275

transaction.

275Settings.xml, in the environment’s TIWeb directory.

Refer to Customizing the 275 Settings File (Optional) on page 5.

Note the comments that show which element will get the value:

<E-I07_ISA_08 Comment="ISA08 - Receiver ID">KAVER866004791</ E-I07_ISA_08>

The following non-EDI value is included in the BDS element:

Element Contents Example

FileName Name of the attachment file

(after uploading if using

Transaction Insight to create

the DDE file)

46c174d1-8e7f-49fc-b294-

faf9c3a1f858. Attach


Appendix C: 275 Attachments Page Data Map

Field on 275 attachments page 275 EDI file

Attachment Type Code 2100A CAT02

Transaction Set Purpose Code BGN01

Claim Status Category Code 2000A STC01.01

Additional Information Request Code 2000A STC01.02

Sender ID ISA06

Receiver ID ISA08

Source Last or Organization Name 1000A NM103

Source First Name 1000A NM104

Source ID Code Qualifier 1000A NM108

Source ID Code 1000A NM109

Source Entity Identifier 1000A NM111

Source Contact Name 1000A PER02

Source Contact Type 1000A PER03

Source Contact Value 1000A PER04

Source License Type 1000A REF01

Source License Number 1000A REF02

Receiver Last or Organization Name 1000B NM103

Receiver First Name 1000B NM104

Receiver ID Code Qualifier 1000B NM108

Receiver ID Code 1000B NM109

Receiver Entity Identifier 1000B NM111

Receiver Contact Name 1000B PER02

Receiver License Type 1000B REF01

Receiver License Number 1000B REF02

Patient Entity Identifier 1000C NM101

Patient Last Name 1000C NM103

Patient First Name 1000C NM104

Patient ID Code Qualifier 1000C NM108

Patient ID Code 1000C NM109

Patient Account Number 1000C REF02 (REF01=EJ)


Field on 275 attachments page 275 EDI file

Patient Tracking Number 1000C REF02 (REF01=2I)

Filter ID Code BDS01

Payer Claim Control Number or Provider

Attachment Control Number TRN02


Appendix D: 277 Settings File Customization Details

The default 277Settings.xml file produces a basic 277 Attachment Request page with

a workable structure, containing values that represent the most common usage for

the fields.

Some fields in this file can be customized and you may opt to create your own

template or multiple templates, depending on your needs.

Customization is an advanced activity requiring knowledge of:

XML structure and elements.

Xpath expressions.

Note: Non-mandatory lines may be removed during customization. Removing a

mandatory line will result in an error from the Foresight Claims Attachment Adapter.

Element Description Options Example Notes

OutputComments Determines

whether the

Comment attributes

are included in the

output DDE file.

True

False

OutputComments=”False”

Comment Allows you to put in

text with no effect

on processing.

There is No length

limit on this

element.

Comment="Source = GS03 /

Target = GS02"

This can be used

as notes to

yourself about the

field. Comments

will be displayed

as tooltips on the

277 page.

EmptyField Specifies what

should be done if

the field is empty.

DoNotShowOrOutput

DoNotOutput

DoNotShow

ShowAndOutput

EmptyField="DoNotOutput"

Repeat An Xpath

expression which

indicates which

loops can be

repeating.

Repeat=".//_2000A/_2000B/

_2300/_2400 |

.//_2000A/_2000B/_2000C/_

2300/_2400"

Usage The utilization of

the element. Will be

passed down the

structure hierarchy

to the child nodes

of each parent.

Mandatory – a

required field

Usage="Mandatory" Appears on page.

Optional Usage="Optional" Appears on page.

Blanks are ok

Excluded - Excluded

from a mandatory or

optional segment.

Usage="Excluded" Does not appear

on page.

Not Specified Determined by the

parent tag’s

Usage value


Element Description Options Example Notes

Label Text for label on left

of screen

Label837D,

Label837I, and

Label837P can be

used to supply

different labels for

each of those

transaction sets.

Label="Claim Status

Category Code 3"

Default Used to

prepopulate a

particular field with

a specified value or

an Xpath statement

showing where on

the 837 the value

comes from

(2000A/2110, etc.).

There are also

several unique

defaults that get

calculated

Default837D,

Default837I, and

Defaults837P can be

used to supply

different defaults for

each of those

transaction sets.

Unique defaults

options are shown to

the right.

Default="0"

Default="__currenttime__"

Default=”__currentdate__”

Default=”__icnnumber__”

ControlType Control type for the

field. Can only be

used with leaf

nodes (at the

bottom of the XML

chain).

TextBox

(Default)

ControlType="TextBox"

DropDownList ControlType="DropDownList

"

RadioButtonList ControlType="RadioButtonL

ist"

Calendar

CalendarShort

CalendarRange

ControlType="Calendar"

CheckBox ControlType="CheckBox"

ControlValues Values available for

the ControlType.

DropDownList See Defining ControlValues on

page 26.

RadioButtonList See Defining ControlValues on

page 26.

CheckBox See Defining ControlValues on

page 26.

Panel Creates a

collapsible panel

for grouping

controls on the

page.

Panel="Patient

Information"

Only for Parent

Nodes.


Defining ControlValues

Element Format Example

DropDownList Values for list using

_ _ (double underscore) as

primary delimiter separating

values

Double pipe separates the

code that is in the EDI file

ControlValues="ED||EDI Access Number

(ED)__EM||Electronic Mail (EM)__FX||Facsimile

(FX)__TE||Telephone (TE)"

For example

EDI Access Number (ED) > if chosen, ED is placed in the output DDE file.

Electronic Mail (EM) > if chosen, EM is placed in the output DDE file.

Values can also be

populated using a query

statement.

ControlValues="QUERY::GetCodeTableDescriptions"

RadioButtonList Values for list using



values.

ControlValues="1||Person (1)__2||Non-Person Entity (2)"

For example:

Person (1) > if chosen, 1 is placed in the output DDE file.

Non-Person Entity (2) > if chosen, 2 is placed in the output DDE file.

CheckBox Values for Unchecked/False

and Checked/True using



values.

ControlValues="0__1"

0 = unchecked/false

1= checked/true


Appendix E: How TIBCO Foresight Programs work with 275s

Program Capabilities

EDISIM® Analyzer Skips BDS03 when validating

Comparator

Document Builder

Standards Editor

Test Data Generator

Validator Skips BDS03 when validating

HIPAA Validator®

Desktop

Validate Skips BDS03 when validating

Library

Instream® Validate Skips BDS03 when validating

Response Generator Responses to 275 include 997, 999, 824 (no 277

or custom reports)

Docsplitter Any kind of splitting (at ST or 2000A)

Dataswapper Any swapping that does not include the BDS03

Transaction

Insight

Import 275 statistics (not the EDI or attachments)

See statistics for 275 in portal; No 275 form, raw EDI view, extended fields, or

tasks