This transaction set communicates underwriting requirements and supporting documentation between insurance carriers and underwriting service providers or between underwriting systems. Typically sent by underwriting departments, third-party administrators, or medical review organizations in response to application submissions or during active case review, the 186 organizes complex underwriting data hierarchically. Key structural segments include the BGN (Beginning Segment) to establish the reporting context, ACT (Account Identification) to identify specific insurance cases or applicants, and BOR (Beginning of Report) to demarcate distinct underwriting requirement sections, with each section potentially containing laboratory results (via LTR), demographic details, specimen information, and detailed underwriting criteria.

Consider a scenario where HealthGuard Insurance receives a new term life application from applicant Sarah Chen. HealthGuard’s underwriting department uses the 186 to report its requirements to MediReview Services, a preferred medical review vendor. The 186 transaction identifies the applicant through NM1 segments, specifies required laboratory tests and their results via LTR segments, includes underwriting questions and responses through the hierarchical HL structure, and documents underwriting status through UD segments. MediReview receives the complete requirement package—including necessary medical history, financial information, and risk factors—enabling them to generate the focused medical evaluation HealthGuard needs to make an underwriting decision within service-level agreements.