HL7 Terminology (THO)
6.1.0 - Continuous Process Integration (ci build)
HL7 Terminology (THO), published by HL7 International - Vocabulary Work Group. This guide is not an authorized publication; it is the continuous build for version 6.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/UTG/ and changes regularly. See the Directory of published versions
Official URL: http://terminology.hl7.org/ValueSet/v3-ParticipationInformationRecipient | Version: 3.0.0 | |||
Active as of 2014-03-26 | Responsible: Health Level Seven International | Computable Name: ParticipationInformationRecipient | ||
Other Identifiers: OID:2.16.840.1.113883.1.11.10263 | ||||
Copyright/Legal: This material derives from the HL7 Terminology THO. THO is copyright ©1989+ Health Level Seven International and is made available under the CC0 designation. For more licensing information see: https://terminology.hl7.org/license.html |
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)
Generated Narrative: ValueSet v3-ParticipationInformationRecipient
Language: en
http://terminology.hl7.org/CodeSystem/v3-ParticipationType
where concept is-a IRCP
Generated Narrative: ValueSet
Language: en
Expansion based on codesystem ParticipationType v5.0.0 (CodeSystem)
This value set contains 6 concepts
Level | Code | System | Display | Definition |
1 | IRCP | http://terminology.hl7.org/CodeSystem/v3-ParticipationType | information 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 | NOT | http://terminology.hl7.org/CodeSystem/v3-ParticipationType | ugent 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 | PRCP | http://terminology.hl7.org/CodeSystem/v3-ParticipationType | primary 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 | REFB | http://terminology.hl7.org/CodeSystem/v3-ParticipationType | Referred 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 | REFT | http://terminology.hl7.org/CodeSystem/v3-ParticipationType | Referred to | The person who receives the patient |
2 | TRC | http://terminology.hl7.org/CodeSystem/v3-ParticipationType | tracker | 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
Date | Action | Custodian | Author | Comment |
2023-11-14 | revise | TSMG | Marc Duteau | Add standard copyright and contact to internal content; up-476 |
2022-10-18 | revise | TSMG | Marc Duteau | Fixing missing metadata; up-349 |
2020-05-06 | revise | Vocabulary WG | Ted Klein | Migrated to the UTG maintenance environment and publishing tooling. |
2014-03-26 | revise | 2014T1_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 |