Represents a defined collection of entities that may be discussed or acted upon collectively but which are not typically expected to act collectively, and collectively. These collections are also not typically formally or legally recognized; i.e. recognized.

NOTE: Group may be used to define families or households, which in some circumstances may act collectively or have a collection degree of legal or formal recognition. This should be considered an exception. When Group is used for types of entities other than Patient or RelatedPerson, the expectation remains that isn't the Group will not act collectively or have formal recognition - use Organization if these behaviors are needed.

For example, it is possible for a 'family' Group to be a performer of an Organization. Observation or owner of a Task. However, this is not permitted for a Group made up of Practitioners, PractitionerRoles or Organizations. Organization or CareTeam would need to be used instead. A Group of Practitioners could, however, be a subject of an Observation.

If both Group.characteristic and Group.member are present, then the members are the individuals who were found who met the characteristic. It's possible that there might be other candidate members who meet the characteristic and aren't (yet) in the list. All members SHALL have the listed characteristics.

A An absolute URI that is used to identify this Group when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique business and SHOULD be a literal address at which an authoritative instance of this Group is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the Group is stored on different servers.

Allows the Group to be referenced by a single globally unique identifier.

Can be a urn:uuid: or a urn:oid: but real http: addresses are preferred. Multiple instances may share the same URL if they have a distinct version.

The determination of when to create a new version of a resource (same url, new version) vs. defining a new artifact is up to the author. Considerations for making this decision are found in Technical and Business Versions .

In some cases, the resource can no longer be found at the stated url, but the url itself cannot change. Implementations can use the meta.source element to indicate where the current master source of the resource can be found.

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.

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

Note: This is a business identifier, not a resource identifier (see discussion ). It is best practice for the identifier to be 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.

The identifier that is used to identify this version of the Group when it is referenced from external specifications. in a specification, model, design or instance. This is an arbitrary value managed by the Group author and is not expected to be globally unique. For example, it might be a timestamp (e.g. yyyymmdd) if a managed version is not available. There is also no expectation that versions can be placed in a lexicographical sequence without additional knowledge.

There may be different Groups that have the same url but different versions. The version can be appended to the url in a reference to allow a reference to a particular business version of the Group with the format [url]|[version]. The version SHOULD NOT contain a '#' - see Business Version .

Indicates whether the record mechanism used to compare versions to determine which is more current.

If set as a string, this is a FHIRPath expression that has two additional context variables passed in - %version1 and %version2 and will return a negative number if version1 is newer, a positive number if version2 and a 0 if the version ordering can't be successfully be determined.

A label assigned to the group for human identification and communication.

Used to identify the group in human communication.

A short, descriptive, user-friendly title for the Group.

This name does not need to be machine-processing friendly and may contain punctuation, white-space, etc.

The current state of this Group.

Enables tracking the life-cycle of the content and filtering of Groups that are appropriate for use or versus not.

A nominal state-transition diagram can be found in the Definition pattern documentation.

Unknown does not represent 'other' - one of the defined statuses must apply. Unknown is merely being retained used when the authoring system is not sure what the current status is.

See guidance around (not) making local changes to elements here .

A Boolean value to indicate that this Group is authored for historical purposes. testing purposes (or education/evaluation/marketing) and no version of this resource will ever be intended for genuine usage.

Enables experimental content to be active developed following the same lifecycle that would be used for a production-level Group.

Allows filtering of Groups that are appropriate for use versus not. Experimental resources might include example instances in implementation guides, instances created solely for testing purposes, etc. If experimental is 'true' for any version of a resource, it should be true for all versions of the resource. (If experimental changes, then it is being misused or a resource that was never intended for real-world use has unexpectedly changed its purpose.).

Experimental resources are not expected to be stable and may well have breaking changes without a corresponding change to the 'version' element.

The date (and optionally time) when the Group was last significantly changed. The date must change when the business version changes and it must change if no value the status code changes. In addition, it should change when the substantive content of the Group changes.

The date is provided often not tracked until the resource is published, but may be present on draft content. Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the Group. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource.

See guidance around (not) making local changes to elements here .

The name of the organization or individual responsible for the active element release and ongoing maintenance of the Group.

Helps establish the "authority/credibility" of the Group. May also allow for contact.

Need to Usually an organization but may be able an individual. The publisher (or steward) of the Group is the organization or individual primarily responsible for the maintenance and upkeep of the Group. This is not necessarily the same individual or organization that developed and initially authored the content. The publisher is the primary point of contact for questions or issues with the Group. This item SHOULD be populated unless the information is available from context.

Contact details to mark assist a user in finding and communicating with the publisher.

May be a web site, an email address, a telephone number, etc.

See guidance around (not) making local changes to elements here .

Explanation of what the group record as not represents and how it is intended to be used because it used.

The content was created in error developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate Groups.

Assist in searching for appropriate content.

When multiple useContexts are specified, there is otherwise no longer available expectation that all or even any of the contexts apply.

Explanation of why this Group is needed and why it has been designed as it has.

This element does not describe the usage of the Group. Instead, it provides traceability of "why" the resource is either needed or "why" it is defined as it is. This may be used to point to source materials or specifications that drove the structure of this Group.

A copyright statement relating to the Group and/or its contents. Copyright statements are notices of intellectual property ownership and can include restrictions on the use and publishing of the Group.

Consumers must be able to determine any legal restrictions on the use of the Group and/or its content.

The short copyright declaration (e.g. (c) '2015+ xyz organization') should be sent in the copyrightLabel element without the copyright prefix (i.e., do not include '(c)' or the symbol).

A short string (<50 characters), suitable for inclusion in a herd page footer that no longer exists). identifies the copyright holder, effective period, and optionally whether rights are restricted. (e.g. 'All rights reserved', 'Some rights reserved').

Defines the content expected to be rendered in all representations of the artifact.

The copyright symbol and the '(c)' textual representation SHOULD NOT be included in this string. It will be added by software when rendering the notation. Full details about licensing, restrictions, warrantees, etc. goes in the more general 'copyright' element.

Identifies the broad classification of the kind of resources the group includes.

Identifies what type of resources the group is made up of.

Group members SHALL be of the appropriate resource type (Patient for person or animal; or Practitioner, PractitionerRole, Device, Medication CareTeam, HealthcareService, Location, Organization, RelatedPerson, Specimen, Medication, Substance, BiologicallyDerivedProduct, or Substance NutritionProduct for the other types.). types.), or a Group of the resources of the appropriate type.

If true, indicates Basis for membership in the Group:

• 'definitional': The Group.characteristics specified are both necessary and sufficient to determine membership. All entities that meet the resource refers criteria are considered to a specific group be members of real individuals. If false, the group, whether referenced by the group defines or not. If members are present, they are individuals that happen to be known as meeting the Group.characteristics. The list cannot be presumed to be complete.
• 'conceptual': The Group.characteristics specified are both necessary and sufficient to determine membership. The 'conceptual' Group is a set 'definitional' Group in which the Group.type is not bound to FHIR types.
• 'enumerated': The Group.characteristics are necessary but not sufficient to determine membership. Membership is determined by being listed as one of intended individuals. the Group.member.

There are use-cases for groups that define specific collections of individuals, and other groups that define "types" of intended individuals. The requirements for both kinds of groups are similar, so we use a single resource, distinguished by this flag. element.

Provides a specific type A code that describes the use of the group. The use of resource the group includes; e.g. "cow", "syringe", etc. usually dictates what kind of entities can be members of the group.

This would generally The types of entities that can be omitted for Person resources. members needs to align with Group.type

A count of the number of resource instances that are part of the group.

Group size is a common defining characteristic.

Note that the quantity may be less than the number of members if some of the members are not active.

Entity responsible for defining and maintaining Group characteristics and/or registered members.

This does not strictly align with ownership of a herd or flock, but may suffice to represent that relationship in simple cases. More complex cases will require an extension.

Used to specify how two or more characteristics are combined.

Provides the value of "n" when "at-least" or "at-most" codes are used for combinationMethod.

Identifies traits whose presence r absence is shared by members of the group.

Needs to be a generic mechanism for identifying what individuals can be part of a group.

All Some subset (as determined by combinationMethod) of the identified characteristics must be true for an entity to a member of the group.

A code that identifies the kind of trait being asserted.

Need a formal way of identifying the characteristic being described.

The value of the trait that holds (or does not hold - see 'exclude') for members of the group.

The value of the characteristic is what determines group membership.

For Range, it means members of the group have a value that falls somewhere within the specified range.

If true, indicates the characteristic is one that is NOT held by members of the group.

Sometimes group membership is determined by characteristics not possessed.

This is labeled as "Is Modifier" because applications cannot wrongly include excluded members as included or vice versa.

The period over which A short, natural language description of the characteristic is tested; e.g. that could be used to communicate the patient had criteria to an operation during the month of June. end-user.

Need to be able to describe characteristics in natural language so that end users can understand the criteria.

Method for how the characteristic value was determined.

Identifies the resource instances A CQL, FHIRPath, or other expression that are members of is used to generate the group. value for this characteristic.

Often The entity who is expected to evaluate the only thing of interest about a characteristic value for candidate group members.

The expectation is "who's that the determiner is someone who matches the characteristics specified by the referenced entity, not necessarily that the actual reference in it". the instance is to the entity. For example, if specifying a PractitionerRole with just a PractitionerRole.type, it's fine for any PractitionerRole that matches or specializes that type to do the determination.

Defines the reference point for comparison when other than 0.

Number of occurrences meeting the characteristic.

Length of time in which the characteristic is met.

The period over which the characteristic is tested; e.g. the patient had an operation during the month of June.

Timing in which the characteristic is determined.

Identifies the resource instances that are members of the group.

Often the only thing of interest about a group is "who's in it".

A reference to the entity that is a member of the group. Must be consistent with Group.type. If the entity is another group, then the type must be the same.

A code that describes how a user is involved in the group. Some groups (e.g. exposure-group) typically don't have variance between members, or it is not tracked, while for other groups (e.g. family, household) this may be meaningful.

See Relationships inside the group for more detailed family relationships.

The period that the member was in the group, if known.

Need to track who was in a group at a particular time.

A flag to indicate that the member is no longer in the group, but previously may have been a member.

Sometimes you don't know when someone stopped being in a group, but not when.