Release 5 R6 Ballot (3rd Draft)

This page is part of the FHIR Specification (v5.0.0: R5 - STU v6.0.0-ballot3: Release 6 Ballot (3rd Draft) (see Ballot Notes ). This is the The current published version in it's permanent home (it will always be available at this URL). is 5.0.0 . For a full list of available versions, see the Directory of published versions

12.8.6 Pattern ParticipantLiving - Detailed Descriptions

FHIR Infrastructure icon Maturity Level : 1 Informative

Detailed Descriptions for the elements in the ParticipantLiving pattern.

ParticipantLiving
Definition

A pattern followed by resources that represent the participant in some activity, process, or responsible for providing information about a resource.

Short Display Participant Pattern
Cardinality 0..*
Type ParticipantContactable
ParticipantLiving.birthDate
Definition

The date when the {{title}} was born.

Short Display The date of birth for the {{title}}
Cardinality 0..1
Type date
Requirements

Used for identity verification and may drive other business processes.

ParticipantLiving.gender
Definition

Administrative Gender - the gender that the {{title}} is considered to have for administration and record keeping purposes.

Short Display male | female | other | unknown
Cardinality 0..1
Terminology Binding AdministrativeGender ( Required )
Type code
Requirements

Needed for identification of the individual, in combination with (at least) name and birth date.

ParticipantLiving.photo
Definition

A facial image of the {{title}}.

Short Display Image of the {{title}
Cardinality 0..*
Type Attachment
Requirements

Many EHR systems have the capability to capture an image of the participant. Fits with newer social media usage too.

ParticipantLiving.communication
Definition

The language which can be used to communicate with the {{title}}.

Short Display Language used by {{title}}
Cardinality 0..*
Terminology Binding All Languages ( Required )
Additional Bindings Purpose
Common Languages Starter Set
Type CodeableConcept
Requirements

Most systems in multilingual countries will want to convey language. Not all systems actually need the regional dialect.

Comments

The ISO-639-1 alpha 2 code in lower case for the language, optionally followed by a hyphen and the ISO-3166-1 alpha 2 code for the region in upper case; e.g. "en" for English, or "en-US" for American English versus "en-AU" for Australian English.