Difference between revisions of "Bolus"
Rene spronk (talk | contribs) |
|||
Line 1: | Line 1: | ||
{{INM Workitem}} | {{INM Workitem}} | ||
− | " | + | !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<br> | |
− | + | QPD|ZQ1^Query For Report^RG|Q003|VN-232-131321|<br> | |
− | + | RCP|I|R<br> | |
− | + | .... | |
− | + | and gets back an answer | |
− | |||
− | + | 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|....