HL7 PT Processing Type
HL7 datatype components PT components from HL7 v2.5.1 Hide components
These are the generated components for the version selected at the top of the page. The article stays practical, and this panel follows the chosen HL7 version.
Components
PT carries processing type, usually production, training, debugging, or similar processing context. It is familiar from MSH-11 and should match the way the receiver actually treats the message.
In this guide, PT appears in MSH.11. That used-by list is a good reality check: the datatype is only half the story, and the field that uses it tells you the workflow.
The component panel above is expanded by default because most datatype pages are used as quick lookup pages. Start there for the exact HL7 v2.5.1 shape, then use the notes below for the practical gotchas.
PT-1 to PT-2: Component Quick Read
The generated component panel above is the formal quick lookup. The short version is below so you can scan the shape without counting carets by eye.
The table-backed components here are PT-1, PT-2. Keep those values to the table or value set your implementation guide names, especially when the field is crossing organization boundaries.
- PT-1 Processing ID - Processing ID. Type ID. Table 0103.
- PT-2 Processing Mode - Processing Mode. Type ID. Table 0207.
Practical Notes
The safest habit is to populate only the components the receiving profile actually uses, and to keep each meaning in its own component. Empty components are better than a compact display string that a receiver has to reverse-engineer.
In HL7 Soup Web, click a field that uses PT and the interpretation view will show which component you are sitting in and where that value lives in the raw message. That is especially handy with compact datatypes because one missing caret can move every value after it.
Official and Reference Notes
For formal reference, compare the generated HL7 v2.5.1 panel above with the HL7 v2.5.1 datatype list and the HL7 Terminology data type code system. Local implementation guides can narrow allowed values, tables, and component usage.
Related Datatypes
Related quick lookups: ID.