transparency_in_network

One billing code entry from a transparency file. A file may list the same billing code in several entries with differing descriptions or bundles, so each entry is kept separately rather than merged.

Primary Key:

• transparency_file_id
• in_network_id

Foreign Keys:

• transparency_file_id => transparency_file.transparency_file_id

Indexes:

• transparency_in_network_billing_code_idx - billing_code, billing_code_type, transparency_file_id

Column	Data Type	Nullable	Indexed	Description
transparency_file_id	bigint	No	Yes	Link to the file this entry came from. Entry IDs are only unique within a file.
in_network_id	integer	No	Yes	Position of this entry in the file's in_network list. Assigned by the loader because the payer gives entries no ID, and positional so repeated billing codes stay distinct.
billing_code	text	No	Yes	The code itself, for example 99213
billing_code_type	text	No	Yes	Code system, for example CPT, HCPCS, or MS-DRG
billing_code_type_version	text	No	No	Version of the code system, for example 2026
negotiation_arrangement	transparency_negotiation_arrangement_type	No	No	How the rate is arranged
severity_of_illness	text	Yes	No	APR-DRG severity level, which is part of what identifies the entry, since a payer lists one billing code several times with identical descriptions and only this differing.
name	text	No	No	Payer's short name for the code
description	text	No	No	Payer's description of the code
bundled_codes	jsonb	Yes	No	Codes bundled with this one, kept as JSON because it is rare and its shape varies
covered_services	jsonb	Yes	No	Services covered by a capitation arrangement, kept as JSON because it is rare and its shape varies