Encounter Information

Datasets

US Core 6.1.0 maps each USCDI element to FHIR.

Dataset	US Core 6.1.0 target profile(s)
`encounters`	US Core Encounter
`locations`	US Core Location

encounters

One row per encounter. Several diagnoses or participants stay one row: list the keys ;-separated.

Column	Required	Format / values	Example
`encounter_id`	Yes	stable encounter key; the key other datasets reference	`ENC-9912`
`encounter_id_system`	Yes	URI of the identifier system; a URL you control or an OID	`urn:oid:2.16.840.1.113883.3.99.2`
`patient_identifier`	Yes	patient key	`MRN-4471903`
`status`	Yes	`planned`, `arrived`, `triaged`, `in-progress`, `onleave`, `finished`, `cancelled`, `entered-in-error`, `unknown` encounter-status	`finished`
`class`	Yes	`AMB` ambulatory, `IMP` inpatient, `EMER` emergency, `OBSENC` observation v3-ActEncounterCode	`AMB`
`type_code`	Yes	CPT or SNOMED CT code(s), `;`-separated, with `type_system`; CPT if omitted US Core Encounter Type	`99213`
`period_start`	Recommended	datetime	`2026-04-18T09:00:00-04:00`
`period_end`	Recommended	datetime	`2026-04-18T09:30:00-04:00`
`reason_code`	If available	SNOMED CT or ICD-10-CM code(s), `;`-separated, with `reason_system`; SNOMED CT if omitted encounter-reason	`29857009` chest pain
`location_id`	Recommended	`locations` key	`LOC-221`
`diagnosis_condition_id`	If available	`conditions` key(s), `;`-separated	`CND-4501`
`participant_npi`	If available	10 digits, `;`-separated	`1407006835`
`discharge_disposition_code`	If applicable	NUBC patient discharge status code, as carried in UB-04 field 17, with `discharge_disposition_system` AHA NUBC Patient Discharge Status	`01` discharged to home or self-care
`service_provider_npi`	If available	10 digits	`1234567893`

reason_code is the presenting complaint, not the diagnosis (diagnosis_condition_id). Its binding is preferred, so an ICD-10-CM code off the claim is accepted.
NUBC is a billing code set, not clinical terminology: send the discharge status off the claim. AHA licenses the codes, so the linked page cannot list them.

locations

One row per physical location: a clinic, a hospital ward, a lab draw station.

If you already send the Provider Directory feed, list here only the locations missing from it, such as a facility outside your network where a member was treated.

Column	Required	Format / values	Example
`location_id`	Yes	stable id; the key `encounters` references	`LOC-221`
`location_name`	Yes	text	`Riverdale Family Practice`
`managing_org_npi`	Recommended	10 digits	`1234567893`
`address_line1`	Recommended	text	`88 River Rd`
`city`	Recommended	text	`Yonkers`
`state`	Recommended	2-letter USPS USPS states	`NY`
`zip`	Recommended	5 or 9 digits, as a string	`10701`

location_name is the one mandatory field: a row without it cannot become a Location.
managing_org_npi must match a row in your organizations dataset.

These resources are served by Patient Access, Provider Access, Payer-to-Payer, and Prior Auth.