TBD | Appendix F Florida Courts Technology Standards
Home About Contact |
Appendix F Florida Courts Technology Standards
AdobeLogo Download

APPENDIX F | DATA EXCHANGE CAPABILITY MODEL

This data exchange standard advances a common set of exchange capabilities that should be built upon to define a specific data exchange. The below general methods describe a minimal set of capabilities that each exchange must implement. However, implementation details are left to the individual exchange which need not define methods with these specific names. Refer to Figure 8. for a representative diagram.

Figure 8. Data Exchange MDE Reference

img-flowchart InitiateExchange

The Data Exchange MDE must allow for an external data source to initiate data exchange at any time. The initiation action for this method includes the direct transfer of data from the external data source to the Data Exchange MDE as part of the Initiate Exchange message. The Data Exchange MDE must respond synchronously with a message denoting receipt of the data or failure of the transfer. Failure messages must include a reason for failure if such a reason is identifiable by the Data Exchange MDE.

RequestExchange

The Data Exchange MDE may request an exchange of data from another Data Exchange MDE. The receiving MDE must respond synchronously with the data requested, an error message, or by invoking the ScheduleExchangeRequest operation on the consuming Data Exchange MDE to schedule a date/time when the request will be filled. The RequestExchange message must include a unique identifier for the request that must be used through subsequent operations.





ScheduleExchangeRequest

The Data Exchange MDE may satisfy a RequestExchange action by scheduling a date and time when the requested data will be provided. Messages must use the unique identifier established during the original RequestExchange operation.

FillExchangeRequest

The Data Exchange MDE must resolve a ScheduleExchangeRequest operation by providing the data originally requested by invoking the FillExhangeRequest operation on the requesting Data Exchange MDE. The FillExchangeRequest must use the unique identifier associated with the original RequestExchange operation. The message must contain the data requested. The Data Exchange MDE must respond synchronously with a message denoting receipt of data or failure of the transfer. Failure messages must include a reason for failure if such a reason is identifiable by the Data Exchange MDE.

OtherExchangeNotification

The Data Exchange MDE must define a capability to establish arbitrary data exchanges. The complexity of court data exchange will necessitate specialized exchanges between local data providers. The OtherExchangeNotification operation should provide a mechanism for meeting this local exchange need through the appropriate message namespaces while remaining compliant with this specification.

QueryExchangeCriteria

A Local Data Exchange MDE may obtain the necessary exchange criteria parameters from a Data Exchange MDE by invoking the QueryExchangeCriteria operation. The invocation of the QueryExchangeCriteria must include a specific exchange UUID for which to receive criteria as the exchange of different data products may impose different limitations. The Data Exchange MDE returns a machine-readable WSDL describing specific limitations associated.

The following methods should not be exposed for general consumption. They are intended to provide management capabilities to local and/or internal data management systems authorized to interact with a specific instance of a Data Exchange MDE. In particular, the implementation details of the Local Data Management MDE is left to the specific jurisdiction. While it is expected that the accepted method of interaction with the Data Exchange MDE is via a web services protocol, the interaction between the Local Data Management MDE need not be constructed as a web service. This element of the diagram intends to illustrate the functionality that the Data Exchange MDE needs to define. For example, the Data Exchange MDE must have the functionality to enable a local, authorized data management system to initiate a request for data via the Data Exchange MDE. However, while the request for data may be accomplished via web services, the initiation could be accomplished by different means such as another web service, a locally defined message queue, or even a simple set of scheduled jobs.

InitiateRequest

The Local Data Management MDE may invoke this operation on the Data Exchange MDE to retrieve data from an external data provider. The Data Exchange MDE must respond synchronously reporting the date/time that the data was requested (via the RequestExchange operation) and the unique identifier for the request. The Data Exchange MDE must respond asynchronously with the requested data, the date/time the data is scheduled to be provided, or an error message indicating failure of the data transfer.

GetExchangeAction

The Data Exchange MDE may invoke the GetExchangeAction on the local data management MDE if that system provides for it. The Local Data Management MDE must respond synchronously with a method, location, or mechanism to store or process the data received from the Data Exchange MDE.

ExchangeStatusNotification

The Data Exchange MDE must define a capability to exchange status and other relevant information with the Local Data Management MDE through appropriate messages and namespaces.

Florida Courts Technology Commission (11/20)

Congratulations! You're now booked up on Appendix F from the Florida Courts Technology Standards!

Please use it to get the justice you deserve.

Sincerely,



www.TextBookDiscrimination.com
Icon-Email-WBIcon-Email-WG Icon-Youtube-WBIcon-Youtube-WG Icon-Share-WBIcon-Share-WG
Pages You Might Also Like