HL7 Terminology (THO)
5.1.0 - Publication International flag

This page is part of the HL7 Terminology (v5.1.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

ValueSet: ParticipationInformationRecipient

Official URL: http://terminology.hl7.org/ValueSet/v3-ParticipationInformationRecipient Version: 2.0.0
Active as of 2014-03-26 Computable Name: ParticipationInformationRecipient
Other Identifiers: id: urn:oid:2.16.840.1.113883.1.11.10263

A party, who may or should receive or who has recieved the Act or subsequent or derivative information of that Act. Information recipient is inert, i.e., independent of mood.” Rationale: this is a generalization of a too diverse family that the definition can’t be any more specific, and the concept is abstract so one of the specializations should be used.

References

This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)

Logical Definition (CLD)

 

Expansion

This value set contains 6 concepts

Expansion based on ParticipationType v4.0.0 (CodeSystem)

LevelCodeSystemDisplayDefinition
1  IRCPhttp://terminology.hl7.org/CodeSystem/v3-ParticipationTypeinformation recipient

A party, who may or should receive or who has recieved the Act or subsequent or derivative information of that Act. Information recipient is inert, i.e., independent of mood." Rationale: this is a generalization of a too diverse family that the definition can't be any more specific, and the concept is abstract so one of the specializations should be used.

2    NOThttp://terminology.hl7.org/CodeSystem/v3-ParticipationTypeugent notification contact

An information recipient to notify for urgent matters about this Act. (e.g., in a laboratory order, critical results are being called by phone right away, this is the contact to call; or for an inpatient encounter, a next of kin to notify when the patient becomes critically ill).

2    PRCPhttp://terminology.hl7.org/CodeSystem/v3-ParticipationTypeprimary information recipient

Information recipient to whom an act statement is primarily directed. E.g., a primary care provider receiving a discharge letter from a hospitalist, a health department receiving information on a suspected case of infectious disease. Multiple of these participations may exist on the same act without requiring that recipients be ranked as primary vs. secondary.

2    REFBhttp://terminology.hl7.org/CodeSystem/v3-ParticipationTypeReferred By

A participant (e.g. provider) who has referred the subject of an act (e.g. patient).

Typically, a referred by participant will provide a report (e.g. referral).

2    REFThttp://terminology.hl7.org/CodeSystem/v3-ParticipationTypeReferred to

The person who receives the patient

2    TRChttp://terminology.hl7.org/CodeSystem/v3-ParticipationTypetracker

A secondary information recipient, who receives copies (e.g., a primary care provider receiving copies of results as ordered by specialist).


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
System 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

DateActionCustodianAuthorComment
2022-10-18reviseTSMGMarc DuteauFixing missing metadata; up-349
2020-05-06reviseVocabulary WGTed KleinMigrated to the UTG maintenance environment and publishing tooling.
2014-03-26revise2014T1_2014-03-26_001283 (RIM release ID)Vocabulary (Woody Beeler) (no record of original request)Lock all vaue sets untouched since 2014-03-26 to trackingId 2014T1_2014_03_26