Blood code

BLC carries blood product identification and quantity data within transfusion and blood-bank messages. It links a coded blood product (such as packed red cells or platelets) with the amount ordered or dispensed.

The blood_product_code field uses CWE with HL7 table 0426:

from zato.hl7v2.v2_9 import BLC, CWE

blc = BLC()
blc.blood_product_code = CWE(
    identifier='PRBC',
    text=
        'Packed Red Blood Cells',
    name_of_coding_system=
        'HL70426'
)

The blood_amount field uses the CQ (composite quantity) datatype:

from zato.hl7v2.v2_9 import BLC, CQ

blc = BLC()
blc.blood_amount = CQ(
    quantity='2',
    units='U'
)

Yes, set the units component to the appropriate volume measure:

from zato.hl7v2.v2_9 import BLC, CQ

blc = BLC()
blc.blood_amount = CQ(
    quantity='250',
    units='mL'
)

Access the fields directly after creating the segment:

from zato.hl7v2.v2_9 import BLC

blc = BLC()
blc.blood_product_code = 'PRBC'
blc.blood_amount = '2'

product = blc.blood_product_code
amount = blc.blood_amount

Zato connects to any system that speaks HL7v2 over MLLP or FHIR over REST. This includes Epic, Cerner, Meditech, Allscripts, and other EHR platforms.

Yes, Zato has built-in MLLP support for sending and receiving HL7v2 messages. MLLP channels handle the framing protocol automatically.

Zato supports HL7 v2.9, which is backward compatible with earlier versions including v2.3, v2.5, and v2.7. Standard segments and datatypes are available as typed Python classes.

Yes. Zato handles both HL7v2 and FHIR natively, so you can parse v2 messages and build FHIR resources with IG-specific extensions in the same service. Typed Python classes are available for both protocols, including extensions from US Core, UK Core, Da Vinci, and other Implementation Guides.