12.8 Pattern ParticipantLiving - Content

12.8.1 Scope and Usage

This is NOT a resource. It is not part of the FHIR schema and cannot appear directly in FHIR instances. It is a logical model that defines a pattern adhered to by other resources. This pattern is defined to provide a standard "view" that might be useful for implementers in processing and manipulating all resources that adhere to this pattern. Typically, this appears in object frameworks as an interface that the various resources that adhere to the pattern implement.

A "participant" takes part in a process, and may be the subject of process, or responsible for the event occurring, or may be responsible for recording or reporting information about the event. Examples include patients, practitioners, organizations, groups of patients or practitioners.

A living participant is usually (but not always) a human, and may have information about the participant's bithDate, gender, and language capabilities. In addition, a photo may be provided.

12.8.2 Boundaries and Relationships

This pattern applies to some participants. Other Participant patterns which living participants also follow:

• ParticipantContactable: A participant associated with contact details
• Participant: All participants

12.8.3 Background and Context

Though this pattern is intended instantiated by many resources, as listed below), there is some variation in the value domains of the underlying resources, and any use of the pattern will need to account for this. ConceptMaps describing the relationship in a computable manner are provided as part of the definition.

• Structure
• UML
• Both

Structure

Name	Flags	Card.	Type	Description & Constraints
ParticipantLiving	I		ParticipantContactable	Participant Pattern Elements defined in Ancestors: identifier, active, name, telecom, address
birthDate		0..1	date	The date of birth for the individual
gender		0..1	code	male | female | other | unknown Binding: AdministrativeGender (Required)
photo		0..*	Attachment	Image of the participant
communication		0..*	CodeableConcept	The language which can be used to communicate with the participant Binding: All Languages (Required) Additional Bindings Purpose Common Languages Starter Set
Documentation for this format

Structure

Name	Flags	Card.	Type	Description & Constraints
ParticipantLiving	I		ParticipantContactable	Participant Pattern Elements defined in Ancestors: identifier, active, name, telecom, address
birthDate		0..1	date	The date of birth for the individual
gender		0..1	code	male | female | other | unknown Binding: AdministrativeGender (Required)
photo		0..*	Attachment	Image of the participant
communication		0..*	CodeableConcept	The language which can be used to communicate with the participant Binding: All Languages (Required) Additional Bindings Purpose Common Languages Starter Set
Documentation for this format

UML Diagram (Legend)