Segment

Product summary header

Provides header information for a product summary report including the report type, form identifier, report date, interval dates, quantities manufactured, distributed, and in use, along with the number of product experience reports filed by facilities and distributors. It appears in product experience report messages (P07/P08) to frame the statistical context for periodic product surveillance submissions.

14fields

2required

v2.9HL7 version

from zato.hl7v2 import PSH

psh = PSH()
psh.report_type = 'INITIAL'
psh.report_date = '20260601'

Python examples

Build PSH segments in Python

How to construct and work with real-world PSH segments.

Quarterly product summary

Reports a quarterly summary with interval dates, quantity distributed, and filed reports

from zato.hl7v2.v2_9 import PSH

psh = PSH()
psh.report_type = 'QUARTERLY'
psh.report_form_identifier = (
    'FDA-3500A'
)
psh.report_date = '20240401'
psh.report_interval_start_date = (
    '20240101'
)
psh.report_interval_end_date = (
    '20240331'
)
psh.quantity_distributed_method = (
    'A'
)
psh.quantity_distributed_comment = (
    'Eastern region'
)
psh.number_of_product_experience_reports_filed_by_facility = (
    '3'
)
psh.number_of_product_experience_reports_filed_by_distributor = (
    '1'
)

Annual surveillance report

Annual report with quantities in use and distribution method estimation

from zato.hl7v2.v2_9 import PSH

psh = PSH()
psh.report_type = 'ANNUAL'
psh.report_form_identifier = (
    'FDA-3500A'
)
psh.report_date = '20240101'
psh.report_interval_start_date = (
    '20230101'
)
psh.report_interval_end_date = (
    '20231231'
)
psh.quantity_distributed_method = (
    'E'
)
psh.quantity_in_use_method = 'E'
psh.quantity_in_use_comment = (
    'Field estimate'
)
psh.number_of_product_experience_reports_filed_by_facility = (
    '12'
)
psh.number_of_product_experience_reports_filed_by_distributor = (
    '5'
)

Initial product report

Initial report with report date and manufactured quantity only

from zato.hl7v2.v2_9 import PSH

psh = PSH()
psh.report_type = 'INITIAL'
psh.report_date = '20240601'

Tutorials

Learn by building

Step-by-step guides for working with HL7 v2 in Zato.

MLLP

Receive and parse HL7 v2 messages

Set up an MLLP channel, parse incoming messages, and respond with acknowledgments.

Start tutorial Build

Build and send HL7 v2 messages

Construct HL7 v2 messages from scratch using typed segment classes and send them over MLLP.

Start tutorial

FAQ

Frequently asked questions

PSH provides header information for a product summary report, including the report type, form identifier, date, interval dates, manufacturing and distribution quantities, and the number of product experience reports filed. It frames the statistical context for periodic product surveillance submissions.

Use the DTM-typed start and end date fields to define the reporting period:

from zato.hl7v2.v2_9 import PSH

psh = PSH()
psh.report_date = '20240401'
psh.report_interval_start_date = (
    '20240101'
)
psh.report_interval_end_date = (
    '20240331'
)

The quantity_distributed_method and quantity_in_use_method fields use HL7 table 0329:

from zato.hl7v2.v2_9 import PSH

psh = PSH()

# A = Actual count
psh.quantity_distributed_method = 'A'

# E = Estimated
psh.quantity_distributed_method = 'E'

Use the NM-typed count fields to record how many reports were filed:

from zato.hl7v2.v2_9 import PSH

psh = PSH()
psh.number_of_product_experience_reports_filed_by_facility = (
    '3'
)
psh.number_of_product_experience_reports_filed_by_distributor = (
    '1'
)

The report_form_identifier is a free-text ST field for the regulatory form designation:

from zato.hl7v2.v2_9 import PSH

psh = PSH()
psh.report_type = 'QUARTERLY'
psh.report_form_identifier = (
    'FDA-3500A'
)

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.

Reference

PSH field reference

Complete list of fields in the PSH segment, HL7 v2.9.

#	Python name	Datatype	Usage	Repeatable	Table
1	`report_type`	`ST`	Required	No	-
2	`report_form_identifier`	`ST`	Optional	No	-
3	`report_date`	`DTM`	Required	No	-
4	`report_interval_start_date`	`DTM`	Optional	No	-
5	`report_interval_end_date`	`DTM`	Optional	No	-
6	▶`quantity_manufactured`	`CQ`	Optional	No	-
6.1	├`.quantity`	`NM`	Optional	No	-
6.2	└`.units`	`CWE`	Optional	No	-
7	▶`quantity_distributed`	`CQ`	Optional	No	-
7.1	├`.quantity`	`NM`	Optional	No	-
7.2	└`.units`	`CWE`	Optional	No	-
8	`quantity_distributed_method`	`ID`	Optional	No	`HL70329`
9	`quantity_distributed_comment`	`FT`	Optional	No	-
10	▶`quantity_in_use`	`CQ`	Optional	No	-
10.1	├`.quantity`	`NM`	Optional	No	-
10.2	└`.units`	`CWE`	Optional	No	-
11	`quantity_in_use_method`	`ID`	Optional	No	`HL70329`
12	`quantity_in_use_comment`	`FT`	Optional	No	-
13	`number_of_product_experience_reports_filed_by_facility`	`NM`	Optional	No	-
14	`number_of_product_experience_reports_filed_by_distributor`	`NM`	Optional	No	-

Ready to build integrations?

Get started with Zato and connect your systems in minutes.

Get started ▶Read the docs

Open source In Python