Release 5 Ballot

This page is part of the FHIR Specification (v5.0.0-ballot: FHIR R5 Ballot Preview). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions

12.8 Pattern ParticipantLiving - Content

FHIR Infrastructure Maturity Level: 1Informative

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

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:

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.

12.8.4 References to this Pattern

12.8.5 Pattern Content

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. ParticipantLiving IParticipantContactableParticipant Pattern

Elements defined in Ancestors: identifier, active, name, telecom, address
... birthDate 0..1dateThe date of birth for the individual
... gender 0..1codemale | female | other | unknown
AdministrativeGender (Required)
... photo 0..*AttachmentImage of the participant


doco Documentation for this format

 

Alternate definitions: Master Definition XML + JSON.

12.8.5.1 Terminology Bindings

PathDefinitionTypeReference
ParticipantLiving.gender

The gender of a person used for administrative purposes.

RequiredAdministrativeGender
ParticipantLiving.communication

This value set includes common codes from BCP-47 (http://tools.ietf.org/html/bcp47)

Preferred, but limited to AllLanguagesCommonLanguages

12.8.5.2 Mappings

birthDate gender photo communication
Patient 1 1 1 1
Practitioner 1 1 1 1
RelatedPerson 1 1 1 1

Each non-grey cell contains a number, the number of elements and extensions (if > 0) mapped in the resource that are mapped to the pattern element in the column. If there are 0 elements and extensions, the number is not shown. In addition, the cell has a color and some character flags.

Colors:

  • Grey: the resource has no element or extension for the pattern element
  • White: the resource has an element that implements the pattern element with the same name
  • Yellow: the resource has a documented extension that implements the pattern element with the same name
  • Blue: the resource has an element that implements the pattern element with a different name
  • Red: the resource has an element that implements that pattern element, but the type or cardinality does not match

Flags:

  • E: pattern element implemented by an extension
  • N: pattern element implemented by an element with a different name
  • T: pattern element implemented by an element with a different type
  • C: pattern element implemented by an element with a different cardinality