Schedule a demo
Segment

Unsolicited selection

Carried selection criteria for unsolicited update messages in HL7 v2's original-mode framework, allowing the subscribing system to filter which results or updates it wanted to receive. It appeared alongside URD in UDM messages. Withdrawn from the current standard, it is retained as an empty stub for backward compatibility with legacy interfaces.

0fields
0required
v2.9HL7 version
urs.py
from zato.hl7v2.v2_9 import URS

# Withdrawn segment, retained for legacy parsing
urs = URS()
print(urs.to_er7())

Build URS segments in Python

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

1

Legacy selection stub

Empty withdrawn segment retained for backward-compatible parsing

from zato.hl7v2.v2_9 import URS

# Legacy unsolicited selection stub
urs = URS()
2

Compatibility placeholder

Minimal wire form when a partner still emits the segment id only

from zato.hl7v2.v2_9 import URS

# No fields on modern builds; keep for parsers
urs = URS()
3

Interface migration note

Comment-only usage documents intent without populating fields

from zato.hl7v2.v2_9 import URS

# Retained for legacy unsolicited filter flows
urs = URS()

Learn by building

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

Frequently asked questions

HL7 withdrew the original URS definition from current guides. The class remains so legacy messages parse, but there are no modern fields to populate.

No. Prefer current subscription and notification patterns your integration guide specifies. Emit URS only when a downstream system still requires the segment for compatibility.

Map the business need to supported segments and message types in your profile, then retire URS once partners confirm they no longer expect the stub row.

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.

URS field reference

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

#Python nameDatatypeUsageRepeatableTable

Ready to build integrations?

Get started with Zato and connect your systems in minutes.

Open source In Python