HL7 v2.5.1 Specificationsv2.5.1

to moveEnter to openTry PID-5, ADT, 0004

QSB: Create subscription

This page lists the structures and trigger events QSB defines, taken from the standard. The written commentary that theADT page carries has not been written for QSB.

Recognising QSB messages

QSB announces itself in MSH-9 like this:

MSH-9QSB^Q16^QSB_Q16
  1. MSH-9.1QSBmessage code: what kind of message this is
  2. MSH-9.2Q16trigger event: what happened in the real world: create subscription
  3. MSH-9.3QSB_Q16message structure: which segments to expect, and in what order

How to use these specifications explains MSH-9 in full, with a worked example.

Message structures

QSB takes 1 structure.

QSB_Q16: Create subscription

2 different trigger events send this structure:

The segments below are the same for all 2. HL7 varies the meaning, not the shape: there is no separate QSB_Z83 layout. What changes is MSH-9, which tells the receiver which of the 2 happened and therefore what to do with the message.

You must always send: MSH, QPD, RCP. Everything else is optional, or required only inside a group you chose to send.

SegmentNameOPTCardinality
MSHR1..1
SFTO0..*
QPDR1..1
RCPR1..1
DSCO0..1

Trigger events

The trigger event is the real-world thing that made the message get sent. QSB defines 2.

EventNameStructure
Q16Create subscriptionQSB_Q16
Z83Z83QSB_Q16