HL7 AFF (Professional Affiliation) | Integration Soup HL7 Reference Guide

HL7 AFF Professional Affiliation

Practical notes on AFF fields from experience.

HL7 field reference AFF fields from HL7 v2.5.1 Show fields

These are the generated fields for the version selected at the top of the page. The document stays the same, but the reference panel follows that version.

Fields

Field	Name	Required	Repeatable	Type
AFF.1	Set ID - AFF	Yes	No	SI
AFF.2	Professional Organization	Yes	No	XON
AFF.3	Professional Organization Address	No	No	XAD
AFF.4	Professional Organization Affiliation Date Range	No	Yes	DR
AFF.5	Professional Affiliation Additional Information	No	No	ST

AFF is the HL7 Professional Affiliation segment. The AFF segment adds detailed information regarding professional affiliations with which the staff member identified by the STF segment is/was associated.

Provider and staff segments are identity segments in disguise. Names help humans, but identifiers and assigning authorities help systems avoid mixing up people.

The v2.5.1 structures show AFF in MFN_M02 (Master file - staff practitioner), PMU_B01 (Add personnel record), RSP_K25 (RSP - Personnel Information by Segment Response). That tells you where it can appear, but the local implementation guide still decides which optional fields are meaningful.

Provider feeds are much easier to debug when names, identifiers, and assigning authorities are visible. HL7 Soup Web helps inspect the field shape, and Integration Soup can keep the mapping between local provider codes and receiving-system codes clear.

So this page stays intentionally practical: what each field is for, what shape the generated v2.5.1 data gives it, and where I would be careful before mapping it.

AFF-1 Set ID - AFF RequiredR SingleS TypeSI

AFF-1 is the sequence number for this affiliation entry under the staff member. If one practitioner has several professional memberships or historical affiliations, number the AFF segments predictably. Do not use this as the organization identifier.

AFF-2 Professional Organization RequiredR SingleS TypeXON

AFF-2 is the professional organization the staff member is or was affiliated with. The XON datatype can carry organization name and identifiers, so keep those structured when the source has them. "College of Something" as text is useful; the organization identifier is what lets a receiver match it reliably.

AFF-3 Professional Organization Address OptionalO SingleS TypeXAD

AFF-3 is the organization's postal address, not the practitioner's home or practice address unless that is genuinely the organization's address. Use it when the receiving staff-master workflow needs a contact or jurisdictional address for the affiliation.

AFF-4 Professional Organization Affiliation Date Range OptionalO RepeatableR TypeDR

AFF-4 gives the start and end of the staff member's membership or affiliation. That makes it suitable for historical staff-master feeds where old affiliations should be retained but not treated as current.

If only the year or month is known, do not manufacture a full timestamp. For current affiliations, agree whether the end date is empty, a special high date, or omitted entirely.

AFF-5 Professional Affiliation Additional Information OptionalO SingleS TypeST

AFF-5 is for additional membership context: status notes, role text, chapter information, or other affiliation detail that does not have a structured field in AFF. Do not put licence numbers or certificate details here if CER, PRA, or another credential segment is the agreed home for them.

HL7^® Reference Guide