Page tree
Skip to end of metadata
Go to start of metadata


Owning committee name

Will be one of Public Health & Emergency Response or Patient Administration Working Group but up to the completion of the first ballot it is temporarily owned by FHIR Core Team

Contributing or Reviewing Work Groups

All work groups may have cause to use this resource at some time, but no one group has a special requirement.

FHIR Resource Development Project Insight ID


Scope of coverage

A group represents a defined collection of entities that may be discussed or acted upon collectively but which are not expected to act collectively and are not formally or legally recognized as such. Members of such a group will be identifiable "things" of some form, for example Patients, Practitioners, Devices, Medicines.

Groups may have a business identifier and as such constitute an entity in their own right outside FHIR (unlike lists which may be of a specific type, but are not identifiable as list instances other than by means of their FHIR URL).

Groups may be defined by criteria for inclusion or by enumeration (unlike lists which can only be enumerated). As well, the specific members of the Group may not be known - or even relevant, while with List, they must always be known.

RIM scope


classCode may be used to further specify the type of resource that the group refers to. Specific members are instances used to define the "kind"

Resource appropriateness

Dealing with collections of objects is a universal concept both in healthcare and in information modelling. Most commonly used in public health, clinical trials, research, etc.

Expected implementations

Most real world implementations will have to use this concept at some point. In part created to ensure that existing structures aren't misused

Content sources

  • RCRIM DMIM (eligibility criteria)

Example Scenarios

  1. Defining a set of patients participating in a group therapy
  2. Defining 3 different treatment groups
  3. Listing available devices for use

Resource Relationships

Hugh Glover 10:10, 18 June 2013 (UTC): This is a very generic - any offers for some additional specific uses ...

  1. Any resource that has a subject may have reason to refer to a group rather than an individual - Document and DeviceObservation do this as can MedicationPrescription.
  2. Group links to the resource instances that are members of the group


Ready for ballot in September 2013

gForge Users



Hugh Glover 10:10, 18 June 2013 (UTC) Not sure about scope, definition implies member of group could be any resource, but the group resource definition only explicitly mentions Patient, Practitioner, Device and Medication.

Hugh Glover 10:10, 18 June 2013 (UTC): Any offers for a more specific implementation?