This page is part of the FHIR Specification v6.0.0-ballot3: Release 6 Ballot (3rd Draft) (see Ballot Notes ). The current version is 5.0.0 . For a full list Continuous Integration Build of available versions, see FHIR (will be incorrect/inconsistent at times).
See the Directory of published versions

• Content
• Detailed Descriptions
• Mappings
• Implementations
• Detailed Analysis

12.6.2 12.5.2 Pattern participant - Analysis

Responsible Owner: FHIR Infrastructure

Maturity Level : 1 Informative

Detailed Cross Analysis for the participant.

12.6.2.1 12.5.2.1 Mappings

Participant.identifier
Participant.identifier : Identifier [0..*]
Resource	Matches	Issues	Tasks	Status	Notes
CareTeam	CareTeam.identifier : Identifier [0..*] identifier does not contain the recommended logical text for short (Pattern: Business Identifier for care team; ; Resource: External Ids for this team) - no reason provided identifier does not contain the recommended logical text for definition (Pattern: Business identifiers assigned to this care team by one of the applications involved. These identifiers remain constant as the resource is updated and propagates from server to server.; ; Resource: Business identifiers assigned to this care team by the performer or other systems which remain constant as the resource is updated and propagates from server to server.) - no reason provided identifier does not contain the recommended logical text for comments (Pattern: Note: This is a business identifier, not a resource identifier (see [discussion](resource.html#identifiers)). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number.; ; Resource: This is a business identifier, not a resource identifier (see [discussion](resource.html#identifiers)). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number.) - no reason provided
Device	Device.identifier : Identifier [0..*] IsSummary differs (Pattern: true; ; Resource: false) - no reason provided identifier does not contain the recommended logical text for short (Pattern: Business Identifier for device; ; Resource: Instance identifier) - no reason provided identifier does not contain the recommended logical text for definition (Pattern: Business identifiers assigned to this device by one of the applications involved. These identifiers remain constant as the resource is updated and propagates from server to server.; ; Resource: Unique instance identifiers assigned to a device by manufacturers other organizations or owners.) - no reason provided identifier does not contain the recommended logical text for comments (Pattern: Note: This is a business identifier, not a resource identifier (see [discussion](resource.html#identifiers)). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number.; ; Resource: Certain attributes, like serial number and UDI Carrier (the HRF or AIDC barcode string) are not device instance identifiers as they are not consistently able to uniquely identify the instance of a device, thus are not appropriate to be used to value Device.identifier. The barcode string from a barcode present on a device label or package may identify the instance, include names given to the device in local usage, or may identify the type of device. If the identifier identifies the type of device, Device.type element should be used. The identifier is typically valued if the serialNumber or lotNumber is not valued and represents a different type of identifier. However, it is permissible to still include those identifiers in DeviceDefinition.identifier with the appropriate identifier.type.) - no reason provided identifier does not contain the recommended logical text for requirements (Pattern: Allows identification of the device as it is known by various participating systems and in a way that remains consistent across servers.; ; Resource: ) - no reason provided
Group	Group.identifier : Identifier [0..*] identifier does not contain the recommended logical text for short (Pattern: Business Identifier for group; ; Resource: Business Identifier for this Group) - no reason provided identifier does not contain the recommended logical text for definition (Pattern: Business identifiers assigned to this group by one of the applications involved. These identifiers remain constant as the resource is updated and propagates from server to server.; ; Resource: Business identifiers assigned to this participant by one of the applications involved. These identifiers remain constant as the resource is updated and propagates from server to server.) - no reason provided identifier does not contain the recommended logical text for comments (Pattern: Note: This is a business identifier, not a resource identifier (see [discussion](resource.html#identifiers)). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number.; ; Resource: Note: This is a business identifier, not a resource identifier (see [discussion](resource.html#identifiers)). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types.) - no reason provided
HealthcareService	HealthcareService.identifier : Identifier [0..*] identifier does not contain the recommended logical text for short (Pattern: Business Identifier for healthcare service; ; Resource: External identifiers for this item) - no reason provided identifier does not contain the recommended logical text for definition (Pattern: Business identifiers assigned to this healthcare service by one of the applications involved. These identifiers remain constant as the resource is updated and propagates from server to server.; ; Resource: External identifiers for this item.) - no reason provided identifier does not contain the recommended logical text for comments (Pattern: Note: This is a business identifier, not a resource identifier (see [discussion](resource.html#identifiers)). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number.; ; Resource: ) - no reason provided identifier does not contain the recommended logical text for requirements (Pattern: Allows identification of the healthcare service as it is known by various participating systems and in a way that remains consistent across servers.; ; Resource: ) - no reason provided
Location	Location.identifier : Identifier [0..*] identifier does not contain the recommended logical text for short (Pattern: Business Identifier for location; ; Resource: Unique code or number identifying the location to its users) - no reason provided identifier does not contain the recommended logical text for definition (Pattern: Business identifiers assigned to this location by one of the applications involved. These identifiers remain constant as the resource is updated and propagates from server to server.; ; Resource: Unique code or number identifying the location to its users.) - no reason provided identifier does not contain the recommended logical text for comments (Pattern: Note: This is a business identifier, not a resource identifier (see [discussion](resource.html#identifiers)). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number.; ; Resource: ) - no reason provided identifier does not contain the recommended logical text for requirements (Pattern: Allows identification of the location as it is known by various participating systems and in a way that remains consistent across servers.; ; Resource: Organization label locations in registries, need to keep track of those.) - no reason provided
Organization	Organization.identifier : Identifier [0..*] identifier does not contain the recommended logical text for short (Pattern: Business Identifier for organization; ; Resource: Identifies this organization across multiple systems) - no reason provided identifier does not contain the recommended logical text for definition (Pattern: Business identifiers assigned to this organization by one of the applications involved. These identifiers remain constant as the resource is updated and propagates from server to server.; ; Resource: Identifier for the organization that is used to identify the organization across multiple disparate systems.) - no reason provided identifier does not contain the recommended logical text for comments (Pattern: Note: This is a business identifier, not a resource identifier (see [discussion](resource.html#identifiers)). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number.; ; Resource: ) - no reason provided identifier does not contain the recommended logical text for requirements (Pattern: Allows identification of the organization as it is known by various participating systems and in a way that remains consistent across servers.; ; Resource: Organizations are known by a variety of ids. Some institutions maintain several, and most collect identifiers for exchange with other organizations concerning the organization.) - no reason provided
Patient	Patient.identifier : Identifier [0..*] identifier does not contain the recommended logical text for short (Pattern: Business Identifier for patient; ; Resource: An identifier for this patient) - no reason provided identifier does not contain the recommended logical text for definition (Pattern: Business identifiers assigned to this patient by one of the applications involved. These identifiers remain constant as the resource is updated and propagates from server to server.; ; Resource: An identifier for this patient.) - no reason provided identifier does not contain the recommended logical text for comments (Pattern: Note: This is a business identifier, not a resource identifier (see [discussion](resource.html#identifiers)). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number.; ; Resource: Systems MAY use identifier for user identities (using the type='USER'). Refer to the [Security and Privacy](administration-module.html#secpriv) section for additional guidance on representing user identities.) - no reason provided identifier does not contain the recommended logical text for requirements (Pattern: Allows identification of the patient as it is known by various participating systems and in a way that remains consistent across servers.; ; Resource: Patients are almost always assigned specific numerical identifiers.) - no reason provided
Practitioner	Practitioner.identifier : Identifier [0..*] identifier does not contain the recommended logical text for short (Pattern: Business Identifier for practitioner; ; Resource: An identifier for the person as this agent) - no reason provided identifier does not contain the recommended logical text for definition (Pattern: Business identifiers assigned to this practitioner by one of the applications involved. These identifiers remain constant as the resource is updated and propagates from server to server.; ; Resource: An identifier that applies to this person in this role.) - no reason provided identifier does not contain the recommended logical text for comments (Pattern: Note: This is a business identifier, not a resource identifier (see [discussion](resource.html#identifiers)). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number.; ; Resource: ) - no reason provided identifier does not contain the recommended logical text for requirements (Pattern: Allows identification of the practitioner as it is known by various participating systems and in a way that remains consistent across servers.; ; Resource: Often, specific identities are assigned for the agent.) - no reason provided
PractitionerRole	PractitionerRole.identifier : Identifier [0..*] identifier does not contain the recommended logical text for short (Pattern: Business Identifier for practitioner role; ; Resource: Identifiers for a role/location) - no reason provided identifier does not contain the recommended logical text for definition (Pattern: Business identifiers assigned to this practitioner role by one of the applications involved. These identifiers remain constant as the resource is updated and propagates from server to server.; ; Resource: Business Identifiers that are specific to a role/location.) - no reason provided identifier does not contain the recommended logical text for comments (Pattern: Note: This is a business identifier, not a resource identifier (see [discussion](resource.html#identifiers)). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number.; ; Resource: A specific identifier value (e.g. Minnesota Registration ID) may appear on multiple PractitionerRole instances which could be for different periods, or different Roles (or other reasons). A specific identifier may be included multiple times in the same PractitionerRole instance with different identifier validity periods.) - no reason provided identifier does not contain the recommended logical text for requirements (Pattern: Allows identification of the practitioner role as it is known by various participating systems and in a way that remains consistent across servers.; ; Resource: Often, specific identities are assigned for the agent.) - no reason provided
RelatedPerson	RelatedPerson.identifier : Identifier [0..*] identifier does not contain the recommended logical text for short (Pattern: Business Identifier for related person; ; Resource: A human identifier for this person) - no reason provided identifier does not contain the recommended logical text for definition (Pattern: Business identifiers assigned to this related person by one of the applications involved. These identifiers remain constant as the resource is updated and propagates from server to server.; ; Resource: Identifier for a person within a particular scope.) - no reason provided identifier does not contain the recommended logical text for comments (Pattern: Note: This is a business identifier, not a resource identifier (see [discussion](resource.html#identifiers)). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number.; ; Resource: RelatedPerson identifiers might not be unique across instances within a system, as a single human individual may be represented as many different RelatedPerson resources with different roles, periods, or relationships. Systems MAY use identifier for user identities (using the type='USER'). Refer to the [Security and Privacy](administration-module.html#secpriv) section for additional guidance on representing user identities.) - no reason provided identifier does not contain the recommended logical text for requirements (Pattern: Allows identification of the related person as it is known by various participating systems and in a way that remains consistent across servers.; ; Resource: People are known by a variety of ids. Some institutions maintain several, and most collect identifiers for exchange with other organizations concerning the patient. Examples are national person identifier and local identifier.) - no reason provided
Participant.active
Participant.active : boolean [0..1]
Resource	Matches	Issues	Tasks	Status	Notes
CareTeam	CareTeam.status : code [0..1] Resource does not support types that are part of the pattern (Pattern: boolean) - no reason provided Resource supports types that are not part of the pattern (; Resource: code) - no reason provided IsModifier differs (Pattern: false; ; Resource: true) - no reason provided Only one element has bindings (Pattern: false; ; Resource: true) - no reason provided active does not contain the recommended logical text for short (Pattern: Whether the care team is currently active; ; Resource: proposed | active | suspended | inactive | entered-in-error) - no reason provided active does not contain the recommended logical text for definition (Pattern: Whether this care team record is in active use.; ; Resource: Indicates the current state of the care team.) - no reason provided	Names are different. Type Mismatch.
Device	Device.status : code [0..1] Resource does not support types that are part of the pattern (Pattern: boolean) - no reason provided Resource supports types that are not part of the pattern (; Resource: code) - no reason provided IsModifier differs (Pattern: false; ; Resource: true) - no reason provided Only one element has bindings (Pattern: false; ; Resource: true) - no reason provided active does not contain the recommended logical text for short (Pattern: Whether the device is currently active; ; Resource: active | inactive | entered-in-error) entered-in-error | unknown) - no reason provided active does not contain the recommended logical text for definition (Pattern: Whether this device record is in active use.; ; Resource: The Device record status. This is not the status of the device like availability.) - no reason provided	Names are different. Type Mismatch.
HealthcareService	HealthcareService.active : boolean [0..1] IsModifier differs (Pattern: false; ; Resource: true) - no reason provided active does not contain the recommended logical text for short (Pattern: Whether the healthcare service is currently active; ; Resource: Whether this HealthcareService record is in active use) - no reason provided active does not contain the recommended logical text for definition (Pattern: Whether this healthcare service record is in active use.; ; Resource: This flag is used to mark the record to not be used. This is not used when a center is closed for maintenance, or for holidays, the notAvailable period is to be used for this.) - no reason provided
Location	Location.status : code [0..1] Resource does not support types that are part of the pattern (Pattern: boolean) - no reason provided Resource supports types that are not part of the pattern (; Resource: code) - no reason provided IsModifier differs (Pattern: false; ; Resource: true) - no reason provided Only one element has bindings (Pattern: false; ; Resource: true) - no reason provided active does not contain the recommended logical text for short (Pattern: Whether the location is currently active; ; Resource: active | suspended | inactive) - no reason provided active does not contain the recommended logical text for definition (Pattern: Whether this location record is in active use.; ; Resource: The status property covers the general availability of the resource, not the current value which may be covered by the operationalStatus, or by a schedule/slots if they are configured for the location.) - no reason provided	Names are different. Type Mismatch.
Organization	Organization.active : boolean [0..1] IsModifier differs (Pattern: false; ; Resource: true) - no reason provided active does not contain the recommended logical text for short (Pattern: Whether the organization is currently active; ; Resource: Whether the organization's record is still in active use) - no reason provided active does not contain the recommended logical text for definition (Pattern: Whether this organization record is in active use.; ; Resource: Whether the organization's record is still in active use.) - no reason provided
Patient	Patient.active : boolean [0..1] IsModifier differs (Pattern: false; ; Resource: true) - no reason provided active does not contain the recommended logical text for short (Pattern: Whether the patient is currently active; ; Resource: Whether this patient's record is in active use) - no reason provided
Practitioner	Practitioner.active : boolean [0..1] IsModifier differs (Pattern: false; ; Resource: true) - no reason provided active does not contain the recommended logical text for short (Pattern: Whether the practitioner is currently active; ; Resource: Whether this practitioner's record is in active use) - no reason provided active does not contain the recommended logical text for definition (Pattern: Whether this practitioner record is in active use.; ; Resource: Whether this practitioner's record is in active use.) - no reason provided
PractitionerRole	PractitionerRole.active : boolean [0..1] active does not contain the recommended logical text for short (Pattern: Whether the practitioner role is currently active; ; Resource: Whether this practitioner role record is in active use) - no reason provided
RelatedPerson	RelatedPerson.active : boolean [0..1] IsModifier differs (Pattern: false; ; Resource: true) - no reason provided active does not contain the recommended logical text for short (Pattern: Whether the related person is currently active; ; Resource: Whether this related person's record is in active use) - no reason provided
Participant.name
Participant.name : string [0..1]
Resource	Matches	Issues	Tasks	Status	Notes
CareTeam	CareTeam.name : string [0..1] name does not contain the recommended logical text for short (Pattern: A name for the care team; ; Resource: Name of the team, such as crisis assessment team) - no reason provided name does not contain the recommended logical text for definition (Pattern: Description of the care team as presented to a consumer while searching.; ; Resource: A label for human use intended to distinguish like teams. E.g. the "red" vs. "green" trauma teams.) - no reason provided
Device	Device.name : BackboneElement [0..*] Maximum Cardinality differs (Pattern: 1; ; Resource: *) - no reason provided Resource does not support types that are part of the pattern (Pattern: string) - no reason provided Resource supports types that are not part of the pattern (; Resource: BackboneElement) - no reason provided IsSummary differs (Pattern: true; ; Resource: false) - no reason provided name does not contain the recommended logical text for short (Pattern: A name for the device; ; Resource: The name or names of the device as known to the manufacturer and/or patient) - no reason provided name does not contain the recommended logical text for definition (Pattern: Description of the device as presented to a consumer while searching.; ; Resource: This represents the manufacturer's name of the device as provided by the device, from a UDI label, or by a person describing the Device. This typically would be used when a person provides the name(s) or when the device represents one of the names available from DeviceDefinition.) - no reason provided	Type Mismatch. Cardinality Problem.
Group	Group.name : string [0..1] name does not contain the recommended logical text for short (Pattern: A name for the group; ; Resource: Label for Group) - no reason provided name does not contain the recommended logical text for definition (Pattern: Description of the group as presented to a consumer while searching.; ; Resource: A label assigned to the group for human identification and communication.) - no reason provided
HealthcareService	HealthcareService.name : string [0..1] name does not contain the recommended logical text for short (Pattern: A name for the healthcare service; ; Resource: Description of service as presented to a consumer while searching) - no reason provided name does not contain the recommended logical text for definition (Pattern: Description of the healthcare service as presented to a consumer while searching.; ; Resource: Further description of the service as it would be presented to a consumer while searching.) - no reason provided
Location	Location.name : string [0..1] name does not contain the recommended logical text for short (Pattern: A name for the location; ; Resource: Name of the location as used by humans) - no reason provided name does not contain the recommended logical text for definition (Pattern: Description of the location as presented to a consumer while searching.; ; Resource: Name of the location as used by humans. Does not need to be unique.) - no reason provided
Organization	Organization.name : string [0..1] name does not contain the recommended logical text for short (Pattern: A name for the organization; ; Resource: Name used for the organization) - no reason provided name does not contain the recommended logical text for definition (Pattern: Description of the organization as presented to a consumer while searching.; ; Resource: A name associated with the organization.) - no reason provided
Patient	Patient.name : HumanName [0..*] Maximum Cardinality differs (Pattern: 1; ; Resource: *) - no reason provided Resource does not support types that are part of the pattern (Pattern: string) - no reason provided Resource supports types that are not part of the pattern (; Resource: HumanName) - no reason provided name does not contain the recommended logical text for short (Pattern: A name for the patient; ; Resource: A name associated with the patient) - no reason provided name does not contain the recommended logical text for definition (Pattern: Description of the patient as presented to a consumer while searching.; ; Resource: A name associated with the individual.) - no reason provided	Type Mismatch. Cardinality Problem.
Practitioner	Practitioner.name : HumanName [0..*] Maximum Cardinality differs (Pattern: 1; ; Resource: *) - no reason provided Resource does not support types that are part of the pattern (Pattern: string) - no reason provided Resource supports types that are not part of the pattern (; Resource: HumanName) - no reason provided name does not contain the recommended logical text for short (Pattern: A name for the practitioner; ; Resource: The name(s) associated with the practitioner) - no reason provided name does not contain the recommended logical text for definition (Pattern: Description of the practitioner as presented to a consumer while searching.; ; Resource: The name(s) associated with the practitioner.) - no reason provided	Type Mismatch. Cardinality Problem.
PractitionerRole	PractitionerRole.code : CodeableConcept [0..*] Maximum Cardinality differs (Pattern: 1; ; Resource: *) - no reason provided Resource does not support types that are part of the pattern (Pattern: string) - no reason provided Resource supports types that are not part of the pattern (; Resource: CodeableConcept) - no reason provided Only one element has bindings (Pattern: false; ; Resource: true) - no reason provided name does not contain the recommended logical text for short (Pattern: A name for the practitioner role; ; Resource: Roles which this practitioner may perform) - no reason provided name does not contain the recommended logical text for definition (Pattern: Description of the practitioner role as presented to a consumer while searching.; ; Resource: Roles which this practitioner is authorized to perform for the organization.) - no reason provided	Names are different. Type Mismatch. Cardinality Problem.
RelatedPerson	RelatedPerson.name : HumanName [0..*] Maximum Cardinality differs (Pattern: 1; ; Resource: *) - no reason provided Resource does not support types that are part of the pattern (Pattern: string) - no reason provided Resource supports types that are not part of the pattern (; Resource: HumanName) - no reason provided name does not contain the recommended logical text for short (Pattern: A name for the related person; ; Resource: A name associated with the person) - no reason provided name does not contain the recommended logical text for definition (Pattern: Description of the related person as presented to a consumer while searching.; ; Resource: A name associated with the person.) - no reason provided	Type Mismatch. Cardinality Problem.