HL7.TERMINOLOGY\ParticipationSubset

HL7 Terminology
1.0.0 - Publication

This page is part of the HL7 Terminology (v1.0.0: Release) based on FHIR R4. The current version which supercedes this version is 5.2.0. For a full list of available versions, see the Directory of published versions

ParticipationSubset

Summary

Defining URL:

http://terminology.hl7.org/ValueSet/v3-ParticipationSubset

Version:

2.0.0

Name:

ParticipationSubset

Status:

Active

Title:

ParticipationSubset

Definition:

Used to indicate that the participation is a filtered subset of the total participations of the same type owned by the Act.

Used when there is a need to limit the participations to the first, the last, the next or some other filtered subset.

OID:

2.16.840.1.113883.1.11.19736 (for OID based terminology systems)

Source Resource:

XML / JSON / Turtle

References

This value set is not used

Content Logical Definition

Logical Definition (CLD)

Include codes from http://terminology.hl7.org/CodeSystem/v3-ActRelationshipSubset where concept is-a _ParticipationSubset

Expansion

This value set contains 9 concepts

Expansion based on ActRelationshipSubset v2.0.0 (CodeSystem)

All codes from system http://terminology.hl7.org/CodeSystem/v3-ActRelationshipSubset

Lvl	Code	Display	Definition
0	_ParticipationSubset	ParticipationSubset	Used to indicate that the participation is a filtered subset of the total participations of the same type owned by the Act. Used when there is a need to limit the participations to the first, the last, the next or some other filtered subset.
1	FUTURE	expected future	An occurrence that is scheduled to occur in the future. An Act whose effective time is greater than 'now', where 'now' is the time the instance is authored.
2	FUTSUM	future summary	Represents a 'summary' of all acts that are scheduled to occur in the future (whose effective time is greater than 'now' where is the time the instance is authored.). The effectiveTime represents the outer boundary of all occurrences, repeatNumber represents the total number of repetitions, etc.
2	LAST	expected last	Restricted to the latest known occurrence that is scheduled to occur. The Act with the highest known effective time.
2	NEXT	expected next	Restricted to the nearest recent known occurrence scheduled to occur in the future. The Act with the lowest effective time, still greater than 'now'. ('now' is the time the instance is authored.)
1	PAST	previous	An occurrence that occurred or was scheduled to occur in the past. An Act whose effective time is less than 'now'. ('now' is the time the instance is authored.)
2	FIRST	first known	Restricted to the earliest known occurrence that occurred or was scheduled to occur in the past. The Act with the lowest effective time. ('now' is the time the instance is authored.)
2	PREVSUM	previous summary	Represents a 'summary' of all acts that previously occurred or were scheduled to occur. The effectiveTime represents the outer boundary of all occurrences, repeatNumber represents the total number of repetitions, etc. ('now' is the time the instance is authored.)
2	RECENT	most recent	Restricted to the most recent known occurrence that occurred or was scheduled to occur in the past. The Act with the most recent effective time, still less than 'now'. ('now' is the time the instance is authored.)
1	SUM	summary	Represents a 'summary' of all acts that have occurred or were scheduled to occur and which are scheduled to occur in the future. The effectiveTime represents the outer boundary of all occurrences, repeatNumber represents the total number of repetitions, etc.

Explanation of the columns that may appear on this page:

Level

A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies

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)

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

History

Date

Action

Author

Custodian

Comment

2020-05-06

revise