FHIR CI-Build

This is the Continuous Integration Build of FHIR (will be incorrect/inconsistent at times).
See the Directory of published versions icon

4.4.1.699 ValueSet http://hl7.org/fhir/ValueSet/participant-resource-types

FHIR Infrastructure icon Work Group  Maturity Level: N Normative Use Context: Country: World, Not Intended for Production use
Official URL: http://hl7.org/fhir/ValueSet/participant-resource-types Version: 6.0.0-ballot2
active as of 2025-03-13 Computable Name: ParticipantResourceTypes
Flags: Experimental, Immutable OID: 2.16.840.1.113883.4.642.3.3301

This value set is used in the following places:

All Resource Types that represent participant resources


Generated Narrative: ValueSet participant-resource-types

Last updated: 2025-03-13T06:08:27.015Z

Profile: Shareable ValueSet

  • Include these codes as defined in http://hl7.org/fhir/fhir-types
    CodeDisplayDefinition
    CareTeamCareTeamThe Care Team includes all the people, organizations, and care teams who participate or plan to participate in the coordination and delivery of care.
    DeviceDeviceThis resource describes the properties (regulated, has real time clock, etc.), administrative (manufacturer name, model number, serial number, firmware, etc.), and type (knee replacement, blood pressure cuff, MRI, etc.) of a physical unit (these values do not change much within a given module, for example the serial number, manufacturer name, and model number). An actual unit may consist of several modules in a distinct hierarchy and these are represented by multiple Device resources and bound through the 'parent' element.
    GroupGroupRepresents a defined collection of entities that may be discussed or acted upon collectively but which are not typically expected to act collectively. These collections are also not typically formally or legally recognized. NOTE: Group may be used to define families or households, which in some circumstances may act collectively or have a 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 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 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.
    HealthcareServiceHealthcareServiceThe details of a healthcare service available at a location or in a catalog. In the case where there is a hierarchy of services (for example, Lab -> Pathology -> Wound Cultures), this can be represented using a set of linked HealthcareServices.
    LocationLocationDetails and position information for a place where services are provided and resources and participants may be stored, found, contained, or accommodated.
    OrganizationOrganizationA formally or informally recognized grouping of people or organizations formed for the purpose of achieving some form of collective action.
    PatientPatientDemographics and other administrative information about an individual or animal that is the subject of potential, past, current, or future health-related care, services, or processes.
    PractitionerPractitionerA person who is directly or indirectly involved in the provisioning of healthcare or related services.
    PractitionerRolePractitionerRoleA specific set of Roles/Locations/specialties/services that a practitioner may perform, or has performed at an organization during a period of time.
    RelatedPersonRelatedPersonInformation about a person that is involved in a patient's health or the care for a patient, but who is not the primary target of healthcare.

 

This expansion generated 13 Mar 2025


ValueSet

Expansion performed internally based on codesystem All FHIR Types v6.0.0-ballot2 (CodeSystem)

This value set contains 10 concepts

CodeSystemDisplayDefinition
  CareTeam http://hl7.org/fhir/fhir-types CareTeam

The Care Team includes all the people, organizations, and care teams who participate or plan to participate in the coordination and delivery of care.

  Device http://hl7.org/fhir/fhir-types Device

This resource describes the properties (regulated, has real time clock, etc.), administrative (manufacturer name, model number, serial number, firmware, etc.), and type (knee replacement, blood pressure cuff, MRI, etc.) of a physical unit (these values do not change much within a given module, for example the serial number, manufacturer name, and model number). An actual unit may consist of several modules in a distinct hierarchy and these are represented by multiple Device resources and bound through the 'parent' element.

  Group http://hl7.org/fhir/fhir-types Group

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

NOTE: Group may be used to define families or households, which in some circumstances may act collectively or have a 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 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 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.

  HealthcareService http://hl7.org/fhir/fhir-types HealthcareService

The details of a healthcare service available at a location or in a catalog. In the case where there is a hierarchy of services (for example, Lab -> Pathology -> Wound Cultures), this can be represented using a set of linked HealthcareServices.

  Location http://hl7.org/fhir/fhir-types Location

Details and position information for a place where services are provided and resources and participants may be stored, found, contained, or accommodated.

  Organization http://hl7.org/fhir/fhir-types Organization

A formally or informally recognized grouping of people or organizations formed for the purpose of achieving some form of collective action.

  Patient http://hl7.org/fhir/fhir-types Patient

Demographics and other administrative information about an individual or animal that is the subject of potential, past, current, or future health-related care, services, or processes.

  Practitioner http://hl7.org/fhir/fhir-types Practitioner

A person who is directly or indirectly involved in the provisioning of healthcare or related services.

  PractitionerRole http://hl7.org/fhir/fhir-types PractitionerRole

A specific set of Roles/Locations/specialties/services that a practitioner may perform, or has performed at an organization during a period of time.

  RelatedPerson http://hl7.org/fhir/fhir-types RelatedPerson

Information about a person that is involved in a patient's health or the care for a patient, but who is not the primary target of healthcare.

 

See the full registry of value sets defined as part of FHIR.


Explanation of the columns that may appear on this page:

Lvl A few code lists that FHIR defines are hierarchical - each code is assigned a level. For value sets, levels are mostly used to organize codes for user convenience, but may follow code system hierarchy - see Code System for further information
Source The source of the definition of the code (when the value set draws in codes defined elsewhere)
Code The code (used as the code in the resource instance). If the code is in italics, this indicates that the code is not selectable ('Abstract')
Display The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application
Definition An explanation of the meaning of the concept
Comments Additional notes about how to use the code