Person

Examples & Testing

The Person resource stores information about a person outside of a health context; e.g., for administrative purposes.

See the FHIR documentation for more information about Person resources.

Person resources support the following interactions.

When searching for Person resources, the following search parameters are supported.

Name	Type	Prefixes Modifiers	Can be Chained?	Description
_id	Token			Resource id.
address	String	:contains :exact :missing		A server defined search that may match any of the string fields in the Address, including line, city, district, state, country, postalCode, and/or text.
address-city	String	:contains :exact :missing		A city specified in an address.
address-country	String	:contains :exact :missing		A country specified in an address.
address-postalcode	String	:contains :exact :missing		A postal code specified in an address.
address-state	String	:contains :exact :missing		A state specified in an address.
birthdate	Date	ne lt le gt ge sa eb ap :missing		The person's date of birth.
gender	Token	:missing		The gender of the person.
identifier	Token	:missing		A person Identifier.
link	Reference	:missing	yes	Any link has this Patient, Person, RelatedPerson or Practitioner reference.
name	String	:contains :exact :missing		A server defined search that may match any of the string fields in the HumanName, including family, give, prefix, suffix, suffix, and/or text.
relatedpatient	Reference	:missing	yes	See the HL7 FHIR documentation.
telecom	Token	:missing		The value in any kind of contact.

When searching Person resources, it is possible to sort the returned values by the following search parameters.

Only one sort parameter may be specified.

When searching Person resources, it is possible to include the resources referenced by the following field names.