HL7 Terminology (THO)
2.1.34 - Continuous Process Integration (ci build) [UP-218]

HL7 Terminology (THO), published by HL7 International - Vocabulary Work Group. This is not an authorized publication; it is the continuous build for version 2.1.34). This version is based on the current content of https://github.com/HL7/UTG/ and changes regularly. See the Directory of published versions

ValueSet: ParticipationInformationRecipient

Summary

Defining URL:http://terminology.hl7.org/ValueSet/v3-ParticipationInformationRecipient
Version:2.0.0
Name:ParticipationInformationRecipient
Status:Active as of 2014-03-26
Definition:

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.

OID:2.16.840.1.113883.1.11.10263 (for OID based terminology systems)
Source Resource:XML / JSON / Turtle

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 v3.0.0 (CodeSystem)

All codes in this table are from the system http://terminology.hl7.org/CodeSystem/v3-ParticipationType

LvlCodeDisplayDefinition
0IRCPinformation recipientA 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.
1  NOTugent notification contactAn 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).
1  PRCPprimary information recipientInformation 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.
1  REFBReferred ByA 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).
1  REFTReferred toThe person who receives the patient
1  TRCtrackerA 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
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

DateActionCustodianAuthorComment
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