Patient is produced for all three FHIR outputs, but the source data available differs. The Patient Everything and Patient Summary bundles populate the resource identically to one another; Bulk Medication History carries less demographic detail. The Fields table below covers both, with a column per output.

Stable ID

The id is derived from the provider’s patient identifier system and value (the same identifier used in the identifier field below). The same patient resolves to the same Patient resource across every output and every request.

Because clinical content plays no part in the Patient id, it is the one resource whose identity does not change when the underlying data changes.

Fields

Field	Patient Everything / Summary	Bulk Med History	Notes
`meta.profile`	1..1	1..1	Always set to the US Core Patient profile URL.
`active`	1..1	1..1	Always `true`.
`identifier`	0..1	1..1	The provider’s patient identifier. `use` is `official`, `system` is `urn:oid:{providerPatientIdentifierSystem}`, and `type` is coded as `MR` using the HL7 v2-0203 identifier type system. The bundles publish only the first identifier, even when the source carries several; Bulk Med History always carries exactly one.
`name`	1..1	1..1	`use` is `official`, with `family` and every non-blank `given` name from the source. Prefix and suffix are present in the source but are not currently mapped in either output.
`gender`	1..1	1..1	Mapped to `male`, `female`, `other`, or `unknown`. The bundles map any unrecognized value to `unknown`; Bulk Med History only recognizes `male`/`m` and `female`/`f`, and defaults everything else (including `other`) to `unknown`.
`birthDate`	0..1	1..1	The patient’s date of birth. Always present in Bulk Med History; may be unknown in the bundles.
`deceased[x]`	1..1	0..0	Bundles only: `deceasedDateTime` when a date of death is known, otherwise `deceasedBoolean` (defaults to `false`). Not populated in Bulk Med History — that source data does not carry deceased status.
Extension: US Core Birth Sex	1..1	1..1	Mapped from the source gender using the same rules in both outputs (`male`/`m` → SNOMED `248153007`, `female`/`f` → SNOMED `248152002`); anything else defaults to the SNOMED “unknown” code `184115007`.
Extension: US Core Race	1..1	0..0	Bundles only. Carries the source race code (normally CDCREC) as `ombCategory` plus a matching `text`; the HL7 null-flavor code `UNK` is published when race is unknown. Not populated in Bulk Med History — that source data does not carry race.
Extension: US Core Ethnicity	1..1	0..0	Bundles only, with the same `UNK` fallback as race. Not populated in Bulk Med History — that source data does not carry ethnicity.
`communication.language`	1..1	1..1	Always fixed to English (United States) (`en-US`), marked `preferred`. This is a fixed value, not an assertion about the patient’s actual language preference.
`address`	0..*	0..*	One entry per distinct address, with street lines, city, state, and postal code. `country` is always set to `US`. In the bundles, addresses are drawn from both the provider-supplied and clinical-record sources and deduplicated case-insensitively; Bulk Med History has a single source address.
`telecom`	0..*	0..0	Bundles only: home, work, and mobile phone numbers, then email addresses, drawn from both the provider-supplied and clinical-record contact details and deduplicated by value. Emails are always published with `use` of `home`. Not populated in Bulk Med History — no phone/email source data is available in that context.

A UNK race or ethnicity means the information was not available — it is not a value reported by the patient. Similarly, gender: unknown and deceasedBoolean: false are defaults applied when the source is silent. deceased[x], US Core Race, and US Core Ethnicity are not populated at all in Bulk Medication History — that source data does not carry deceased status, race, or ethnicity.

Welcome

Product

FHIR

Implementation

APIs

Patient

Stable ID

Fields

​Stable ID

​Fields

Stable ID

Fields