HL7 Table 0202: Telecommunication Equipment Type

HL7 v2 Table 0202 Telecommunication Equipment Type enumerates the device behind a telecommunication address. It is the partner table to HL70201 Telecommunication Use Code — where 0201 says why the contact is reachable (work, home, emergency), 0202 says how the contact is reachable (telephone, fax, beeper, modem, satellite phone). Both codes live inside the XTN composite: 0201 in XTN.2 Telecommunication Use Code and 0202 in XTN.3 Telecommunication Equipment Type.

Purpose

A bare phone number is ambiguous: a fax line, a TDD line, and a cellular number all look identical on the wire, but routing a voice call to a fax modem fails noisily and routing a text to a landline silently drops. Table 0202 lets the sender mark the equipment so the receiver can pick the right channel — fax server, SMS gateway, or voice dialer — without guessing from the digits.

It also disambiguates the historical Internet/X.400 entries: when XTN.4 carries an email address, XTN.3 should carry the value Internet (with XTN.2 set to NET from HL70201) so older parsers that still distinguish email from voice contact land on the right branch.

Where it's used

Table 0202 binds to a single XTN component but appears in every segment that carries a contact:

• XTN.3 Telecommunication Equipment Type — the canonical home for the code.
• PID-13 Phone Number — Home, PID-14 Phone Number — Business.
• NK1-5 Phone Number, NK1-6 Business Phone Number — next of kin.
• STF-10 Phone Number, PRA-8 Office Telephone — staff and provider records.
• ORC-14 Call Back Phone Number, OBR-17 Order Callback Phone Number.
• GT1-7 Guarantor Phone Number — Home, GT1-8 Guarantor Phone Number — Business.
• IN1-7 Insurance Co. Phone Number.

Code list

Code system: http://terminology.hl7.org/CodeSystem/v2-0202 OID: 2.16.840.1.113883.18.110

HL7-defined vs user-defined

Table 0202 is HL7-defined: the values are part of the v2 standard and are not intended to be extended by local profiles. Adding local equipment codes (e.g. WHATSAPP, SIGNAL) is a common temptation but breaks interoperability — receivers built against the published table will reject or coerce unknown values. For new channel types, prefer placing a disambiguator in XTN.6 Area/City Code or XTN.13 Unformatted Telephone Number and keep XTN.3 within the HL7-defined set.

Version differences

• v2.3 — Table introduced with BP, FX, MD, PH, Internet, X.400.
• v2.4 — CP Cellular added; TDD and TTY added to support accessibility-mandated equipment types.
• v2.5 / v2.6 — No code additions; descriptive text refined.
• v2.7 — SAT Satellite Phone added for telemedicine and field-deployment use cases.
• v2.8 / v2.8.1 — Stable. No additions or deprecations vs v2.7.

Common mistakes

• Sending the area code in XTN.3. XTN.3 is the equipment code, not a number fragment. Numeric strings here cause every value-set validator to fail.
• Using PH for cellular numbers. SMS routing downstream depends on CP; mis-tagging a mobile as PH strands SMS notifications.
• Forgetting that Internet requires XTN.2 = NET. The two-table pair (0201 + 0202) is what tells the receiver "this XTN carries an email, not a phone number" — Internet alone in XTN.3 with XTN.2 empty is ambiguous in older parsers.
• Inventing local values like SMS, WHATSAPP, EMAIL. The table is HL7-defined; unknown values do not survive value-set validation in modern integration engines.
• Treating X.400 as a live channel. Receivers should accept it for backward compatibility but should not produce it on outbound — use Internet instead.

Examples

XTN with a work fax (XTN.2 WPN from HL70201, XTN.3 FX from HL70202):

^WPN^FX^^^555^5559999

Cellular mobile contact:

^PRN^CP^^^617^5550101

Email address — both 0201 and 0202 used together:

^NET^Internet^patient@example.org

In context — PID-13 with a home phone and a mobile (field repetition with ~):

PID|1||MRN12345^^^MRN||DOE^JANE^^^^^L||19800101|F|||123 MAIN ST^^BOSTON^MA^02101^USA^M|||^PRN^PH^^^617^5550100~^PRN^CP^^^617^5550101

In context — STF-10 with a TDD line:

STF|1|...|^WPN^TDD^^^617^5559900

Common pitfall — bare phone with no equipment code:

^^^^^617^5550100

This is legal but blind: downstream routing cannot tell if this is voice, fax, or modem.

FHIR mapping

Table 0202 maps to the FHIR ContactPoint.system value set via the v2-to-FHIR IG: ConceptMap table hl70202 to ContactPoint.system.

Pairing matters: FHIR splits HL7's use and system into ContactPoint.use and ContactPoint.system. The 0201/0202 pair must both be read to produce a faithful ContactPoint.

Engine considerations

• Channel routing — outbound notification engines (SMS, fax, email) key off XTN.3 to choose a gateway. A mis-tagged PH on a mobile means a real human gets called for what should be an SMS.
• Value-set strictness — most engines reject unknown 0202 values at the segment parser. Hand-rolled local equipment codes do not round-trip through HAPI, Mirth, or Rhapsody without a custom table override.
• Trim and case — internet (lowercase) and INTERNET are not the same value as Internet. The HL7 table uses mixed case verbatim; engines that uppercase aggressively will lose membership.
• FHIR collapse — five 0202 codes (PH, CP, BP, SAT, and historical PH mobile variants) collapse onto FHIR phone. Round-tripping FHIR → v2 cannot recover the distinction unless the device subtype is preserved in an extension.

How Vorro handles Telecommunication Equipment Type

Vorro treats Table 0202 as the authoritative source for downstream channel routing.

• The XTN parser reads XTN.3 against the published 0202 value set and refuses to silently coerce unknown values; non-conforming codes route to a curation queue with the original value preserved.
• Outbound Internet is always emitted with XTN.2 = NET so legacy receivers can disambiguate email from voice.
• When a profile requires producing a FHIR ContactPoint, Vorro applies the v2-to-FHIR ConceptMap and stores the original 0202 code in a private extension so a later FHIR-to-v2 round-trip restores the equipment subtype.
• Outbound senders never emit X.400; legacy inbound values are accepted and normalized to Internet with a soft warning.

Related pages

• XTN data type — Extended Telecommunication Number
• HL70201 Telecommunication Use Code
• PID segment — Patient Identification

Sources

• HL7 Terminology — CodeSystem v2-0202
• HAPI HL7v2 v2.8.1 javadoc — XTN datatype
• HL7 v2-to-FHIR IG — ConceptMap 0202 to ContactPoint.system
• HL7 v2 product brief