Table 25.2 indicates the protocols defined to date.
Field | Length | Description | Format | Mandatory? | Notes | |||
---|---|---|---|---|---|---|---|---|
Header line |
||||||||
1 |
5 |
Line number |
NNNNN |
Y |
Always 00001 for header |
|||
2 |
10 |
Fixed text |
‘UKBTSSTART’ |
Y |
|
|||
3 |
8 |
Date |
YYYYMMDD |
Y |
|
|||
4 |
4 |
Time |
HHMM |
Y |
|
|||
5 |
6 |
Protocol number |
NNNNNN |
Y |
Allocated by UK SACIT |
|||
6 |
6 |
Source ID |
XXXXXX |
Y |
|
|||
7 |
6 |
Destination ID |
XXXXXX |
Y |
|
|||
8 |
2 |
Checksum |
NN |
Y |
|
|||
9 |
1 |
Terminator |
Carriage return |
Y |
|
|||
Footer line |
||||||||
1 |
5 |
Line number |
NNNNN |
Y |
|
|||
2 |
9 |
Fixed text |
‘UKBTSSTOP’ |
Y |
|
|||
3 |
5 |
No. of records |
NNNNN |
Y |
|
|||
4 |
2 |
Checksum |
NN |
Y |
|
|||
5 |
1 |
Terminator |
Carriage return |
Y |
|
Protocol number | Title | Description |
---|---|---|
000001 |
Blood component dispatch information |
Defines the message used to transfer information on blood component issues |
000002 |
Blood derivative dispatch information |
Defines the message used to transfer information on blood derivative issues |
000003 |
Reagent dispatch information |
Defines the message used to transfer information on reagent issues |
000004 |
Blood component dispatch acknowledgement |
Defines the message used to transfer information on blood components received |
000005 |
Blood component fate information |
Defines the message used to transfer information on the fate of blood components received |
The message protocols contain a range of data defined as either mandatory or optional. The mandatory fields give essential information and must contain valid data. The optional fields give the flexibility to build in a wide range of additional information, but if not required are left as blank (space character) fields.