Difference between revisions of "Query Transmission Pattern"
Rene spronk (talk | contribs) |
Rene spronk (talk | contribs) |
||
| Line 12: | Line 12: | ||
query continuation/abort [[Query Continuation/Abort Interaction]] | query continuation/abort [[Query Continuation/Abort Interaction]] | ||
| + | |||
| + | There is also a publish/subscribe, which is an extensions of the generic query mechanism, but which has yet to be documented in v3 because nobody has come forward with a use-case yet. | ||
| + | |||
| + | A Responses to a query IS NEVER (i.e. can never be) a notification. It is always a query response, with a queryAck class. The same is true for messages sent as a response to a subscription query. The dynamic model doesn't allow sending query responses as "notifications". (Note that the dynamic model doesn't really cover subscriptions or Bolus-type queries at the moment) | ||
| + | |||
| + | == Notes == | ||
| + | #The only way to send a response to a different system than the querying system is the use of the respondTo class in the transmission wrapper. There is no other mechanism. In such circumstances a copy of the queryParameters in the response is probably useful. | ||
| + | #Querying should not be confused with Polling. These are at two entirely different conceptual levels. | ||
Revision as of 18:19, 10 February 2006
The Transmission Sender (an HL7 Application) sends the initial Query Transmission, including all applicable query parameter values. The Transmission Receiver (another HL7 Application) performs an accept-level validation, and sends an accept-level acknowledgement transmission if the Sender had requested such an acknowledgement.
The timing and delivery method of the Response Transmission (a.k.a. Query Response depends on settings as provided by the Sender with the initial Transmission.
response contains number of responses in total
query continuation/abort Query Continuation/Abort Interaction
There is also a publish/subscribe, which is an extensions of the generic query mechanism, but which has yet to be documented in v3 because nobody has come forward with a use-case yet.
A Responses to a query IS NEVER (i.e. can never be) a notification. It is always a query response, with a queryAck class. The same is true for messages sent as a response to a subscription query. The dynamic model doesn't allow sending query responses as "notifications". (Note that the dynamic model doesn't really cover subscriptions or Bolus-type queries at the moment)
Notes
- The only way to send a response to a different system than the querying system is the use of the respondTo class in the transmission wrapper. There is no other mechanism. In such circumstances a copy of the queryParameters in the response is probably useful.
- Querying should not be confused with Polling. These are at two entirely different conceptual levels.
