What happens after all transactions are processed?

This section includes three scenarios that describe the behavior of GetTransactions when the InForm Adapter software encounters the last transaction to be processed.

For each scenario, the ResponseODM document has been defined to contain the following:

An ODM element as previously defined.
The status of the last record that was processed: END or OK.
A bookmark.

In addition, transactions A, B, C, and D exist.

Scenario 1
In this scenario, transactions A, B, C, and D contain clinical data. In the first call to GetTransactions, A. B, and C are processed, and C is passed as the bookmark. In the next call, processing begins with D.

Because D contains clinical data:
- The ODM element returns transaction data.
- The Status value is "END."
- The bookmark is D.
Scenario 2
In this scenario, A, B, and C contain clinical data, but D does not contain clinical data. In the first call to GetTransactions, A, B, and C are processed, and C is passed as the bookmark. In the next call, processing begins with D.

Because D does not contain clinical data:
- The ODM element returns an empty ODM document.
- The Status value is "END."
- The bookmark is D.
Scenario 3
In this scenario, A, B, C, and D have been processed by the first call, and D is passed as the bookmark.

Because D is the last transaction:
- An ODM element is not returned.
- The Status value is "END."
- The Bookmark is D. You get back the same bookmark you passed in, because processing reached the last transaction.

After you process any of these scenarios, check to see whether ODM exists, and if it does, process it. If the results of subsequent call is Status = END, the download is complete. If Status is a value other than END, you must make another call using the bookmark.

For more information, see GetTransactions example response.