This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "Bolus"

From HL7Wiki
Jump to navigation Jump to search
Line 1: Line 1:
 
{{INM Workitem}}
 
{{INM Workitem}}
"Bolus" is one of the current v2/v3 methods of responding to a query.  
+
!3 Summary
 +
The "BOLUS" query response mode refers to a query in which a
 +
the response to a query is sent back to the client as a completely
 +
normal set of apparently unsolicited HL7 messages, instead of as
 +
segments within special query/response messages.  The BOLUS response
 +
mode is useful if the query mechanism is being grafted into an
 +
infastructure that already supports unsolicted transactions, and the
 +
decision is made not to engineer the query/response/continuation
 +
protocol into the existing HL7 flows, but rather to use existing
 +
unsolicted messages.
 +
!3 Introduction
 +
Normally, when a client makes an HL7 query, it interacts with
 +
the HL7 query server by exchanging query and reseponse messages.  The
 +
query may contain a QBP and an RCP segment, and the data comes back in messages
 +
containing QAK and RCP segments, as well as the "data" being asked for.
  
*T: "a series of responses sent at the same time without use of batch formatting" (to quote the definition from HL7 versions 2.4 and 2.5, in both Appendix A and chapter 5. It is defined identically in chapter 5 of version 2.6. The term bolus does not appear in versions 2.2, 2.3, or 2.3.1.)
+
For example, the client asks for the visit note
Suggestion was made by Mark Tucker (a former InM co-chair) that responses would be sent as if they were ''unsollicited'' messages, which is radically different (from a dynamic model aspect) than ''a series of responses''.
 
  
The other options are:
+
MSH|...|DQBP^ZRG1|MSG922<br>
*R: a response using a [[Message Based Interaction]]
+
QPD|ZQ1^Query For Report^RG|Q003|VN-232-131321|<br>
*B: an immediate response using a [[Batch Based Interaction]]
+
RCP|I|R<br>
  
The problem is that one interaction results in multiple response interactions. This is not valid under the current [[Dynamic Model]], it could be supported using the proposed [[CPM]].  
+
....
  
Question: are there use-cases for this? If not, we should probably drop this option.
+
and gets back an answer
*Mark: query to main repository, asking for snapshot of certain data. Triggers unsollicited messages to be sent. Responses are not part of the query/response protocol. Has "Event Replay" aspects, but is not the same use-case.
 
  
Question: is there documentation anywhere that supports the definition Mark put forward about responses being sent as if they were unsolicited messages?
+
MSH|...|RSP^ZRG1|<br>
 +
MSA|MSG922<br>
 +
QAK|Q003|OK|ZQ1^Query forReport^RG|1|<br>
 +
QPD|ZQ1^Query For Report^RG|Q003|VN-232-131321|<br>
 +
PID|...<br>
 +
OBR|...<br>
 +
OBX|....<br>

Revision as of 13:31, 5 December 2006

!3 Summary The "BOLUS" query response mode refers to a query in which a the response to a query is sent back to the client as a completely normal set of apparently unsolicited HL7 messages, instead of as segments within special query/response messages. The BOLUS response mode is useful if the query mechanism is being grafted into an infastructure that already supports unsolicted transactions, and the decision is made not to engineer the query/response/continuation protocol into the existing HL7 flows, but rather to use existing unsolicted messages. !3 Introduction Normally, when a client makes an HL7 query, it interacts with the HL7 query server by exchanging query and reseponse messages. The query may contain a QBP and an RCP segment, and the data comes back in messages containing QAK and RCP segments, as well as the "data" being asked for.

For example, the client asks for the visit note

MSH|...|DQBP^ZRG1|MSG922
QPD|ZQ1^Query For Report^RG|Q003|VN-232-131321|
RCP|I|R

....

and gets back an answer

MSH|...|RSP^ZRG1|
MSA|MSG922
QAK|Q003|OK|ZQ1^Query forReport^RG|1|
QPD|ZQ1^Query For Report^RG|Q003|VN-232-131321|
PID|...
OBR|...
OBX|....