 AccessCredential | |
| AlternateDocumentID | The DocumentID serves as an identifier of an entity corresponding to the noun instance (i.e., the entity being managed in an interaction). In many cases, trading partner requirements may make it necessary to associate multiple indentifiers for an entity. Only a single DocumentID is permitted within any noun instance, but multiple AlternateDocumentIDs are permitted. |
| CreditCard | Credit Card account information. |
 DocumentID | |
| DocumentSequence | Intended as an identifier on different instances of a noun in a BOD message instance. It is possible to have a single BOD message instance with both multiple nouns instances and multiple ActionExpressions. In support of this need, every noun is defined with DocumentID and DocumentSequence property elements. The DocumentID serves as an identifier of an entity corresponding to the noun. The DocumentSequence serves as an identifier on the different instances of a noun in a message instance; the sequence numbers are specific to the message instance (i.e. in the case of a message instance with two noun instances, the first noun instance may have a DocumentSequence of "1" and the second noun instance would have a DocumentSequence of "2". |
| FCRAIndicator | Identifies if the requirements must meet the FCRA criteria. |
| ResultDueDateTime |
The date on which the related screening must be completed and returned to the CRA.This is formatted representation of a date, which may be specified as a date, date/time, year, or year/month. |
| ScopeOfWork | |
| ScreeningMessage | Contains a message from either trading partner regarding the order. For example, "Rush Order. Please expedite." |
| ScreeningVendorCourtOrder | |
| ScreeningVendorOrderCode | |
| ScreeningVendorSubject | |
| SearchFee | The pricing agreed upon between the CRA and Provider. The pricing agreed upon between the CRA and Provider. |
| SubmittedDateTime |
The date the related document, report, or related entity was communicated to a receiving or approving entity.This is formatted representation of a date, which may be specified as a date, date/time, year, or year/month. |
| UserArea | Allows the implementer to extend the base HR-XML specification.
This is done by defining the additional information in XML Schema and referencing the new schema in the xml instance document throught the use of namespaces. Once this is done the additional information defined there can be carried in the BOD XML instance document.
Allows the implementer to extend the base HR-XML specification.
This is done by defining the additional information in XML Schema and referencing the new schema in the xml instance document throught the use of namespaces. Once this is done the additional information defined there can be carried in the BOD XML instance document.
|
| UserID | A character string or name distinquishing a user to a system or process. Generally used in context of system login or access. |