Release 4 Snapshot 3: Connectathon 32 Base

This page is part of the FHIR Specification (v4.0.1: R4 - Mixed Normative and STU (v5.0.0-snapshot3: R5 Snapshot #3, to support Connectathon 32 ) in it's permanent home (it will always be available at this URL). ). The current version which supercedes this version is 5.0.0 . For a full list of available versions, see the Directory of published versions . Page versions: R4B R4 R3

Documentmanifest-fm-attachment

12.6.6 Pattern Participant - Detailed Descriptions

Structured Documents FHIR Infrastructure icon Work Group Maturity Level : N/A 1 Standards Status : Informative Compartments : Device , Encounter , Patient , Practitioner , RelatedPerson

Detailed Descriptions for the elements in the Participant pattern.

Participant
Definition

This is A pattern followed by resources that represent the narrative participant in some activity, process, or responsible for the providing information about a resource. See also the XML , JSON

Short Display Participant Pattern
Cardinality or Turtle 0..*
Type format. This example conforms Logical
Participant.identifier
Definition

Business identifiers assigned to this participant by one of the profile DocumentManifest . A Financial Management Attachment example   applications involved. These identifiers remain constant as the resource is updated and propagates from server to server.

Short Display Business Identifier for participant
Note This is a business identifier, not a resource identifier (see discussion )
Cardinality 0..*
Type Identifier
Requirements

  Allows identification of the participant as it is known by various participating systems and in a way that remains consistent across servers.

Summary true
Comments

Usage note: every effort has been made Note: This is a business identifier, not a resource identifier (see discussion ). It is best practice for the identifier to ensure only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the examples are correct same identifier can exist - possibly even with different resource types. For example, multiple Patient and useful, but they are not a normative part of Person resource instance might share the specification. same social insurance number.

Participant.active
Definition

Whether this participant record is in active use.

Short Display Whether the participant is currently active
Cardinality 0..1
Type boolean
Summary true
Participant.name
Definition

Description of participant as presented to a consumer while searching.

Short Display A name for the participant
Cardinality 0..1
Type string
Summary true