Pointer to the principal object where the Attachment data object <Attachment>can be found.

Must point to the FormInstance object ID.[i]

For e-signed documents, the @PrimaryObjectID will point to the form instance for the document manifest, if one is available.  This will tell the programmer where to begin parsing the documents.  For hybrid documents where there may not be a separate document manifest, the @PrimaryObjectID will point to the first form instance that contains the scanned documents.

@PrimaryObjectID

Y

R[ii]

IDREF

Transaction Reference Guid

Unique Identifier for this message.

Used later in the response (if sent) to link the response with the original request.

GUID in response must match GUID from request.

<TransRefGUID>

Y

R[iii]

GUID

Business Process / Message Type

510 = Forms Instance (Attachment)

<TransType tc=”#”> 510[iv]

Y

R[v]

Type Code

The TransSubType further defines the TransType of 510 into an attachment message.  This element is required if message is sent in accordance with NAVA STP.

NAVA e-docs specifies TransSubType tc="1022500300">Attachment </TransSubType>. 

This is required for 2.20 schema validation.

This field should be optional.  If the Carriers are sending the attachment in accordance with the edoc specific NAVA implementation, then the code above should be sent.  Otherwise, this element may be excluded.[vi]

<TransSubType tc="1022500300">Attachment </TransSubType> -

Y

O

Type Code

For TXLife Request - Date Message was created. 

For TXLife Response – Date Message was responded to

The standard date will be yyyy-mm-dd date.[vii]  Example:  2008-04-24

<TransExeDate>

Y

R[viii]

Date

Time Message was created. Attachments will utilize the GMT offset with the NY time being the base; so, the offset will be either -4 or -5.[ix]  The time format will be 20:49:01-04:00[x] .

<TransExeTime>

Y

R[xi]

Time

Test Indicator

0 = False (Production)

1 = True (Test)

<TestIndicator tc=”#”>

Y

R[xii]

Boolean

Indicator of what the object type is that the PrimaryObjectID is pointing to, so receiving system easily knows what to expect.

Only expected Value:

101- Form Instance[xiii]

<PrimaryObjectType tc=”101”>Object Type

Y

R for TXLife Request[xiv]

Not Used for TXLifeRespons

Type Code

Correlation Identifier– to be used to  relate multiple attachment messages.  This will only be used in Phase II implementation.

<CorrelationGUID/>

O for TXLife Request

Should be passed back on TXLifeResponse if received.

GUID

Specifies the state of the CorrelationGUID. 

1 - Initial

2- Ongoing

3 - Final

<CorrelationGUIDState tc=""/>

C

Req if CorrGuid present[xv]

Type Code

Container object for the business message details

<OLifE>

Y

R for TXLife Request[xvi]

Not used for TXLife Response