This page is part of the FHIR Clinical Documents (v1.0.0-ballot: STU1 Ballot 1) based on FHIR (HL7® FHIR® Standard) R4. . For a full list of available versions, see the Directory of published versions
Official URL: http://hl7.org/fhir/uv/fhir-clinical-document/ValueSet/clinical-doc-participant-types-vs | Version: 1.0.0-ballot | |||
Standards status: Informative | Computable Name: ClinicalDocParticipantTypesVs | |||
Copyright/Legal: Used by permission of HL7 International, all rights reserved Creative Commons License |
Subset of codes from v3-ParticipationType for use as Clinical Document Participant Type codes
References
Generated Narrative: ValueSet clinical-doc-participant-types-vs
http://terminology.hl7.org/CodeSystem/v3-ParticipationType
Code | Display | Definition |
ENT | data entry person | A person entering the data into the originating system. The data entry person is collected optionally for internal quality control purposes. This includes the transcriptionist for dictated text. |
INF | informant | A source of reported information (e.g., a next of kin who answers questions about the patient's history). For history questions, the patient is logically an informant, yet the informant of history questions is implicitly the subject. |
IRCP | 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. |
PRCP | 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. |
TRC | tracker | A secondary information recipient, who receives copies (e.g., a primary care provider receiving copies of results as ordered by specialist). |
Generated Narrative: ValueSet
Expansion based on codesystem ParticipationType v5.0.0 (CodeSystem)
This value set contains 5 concepts
Code | System | Display | Definition |
ENT | http://terminology.hl7.org/CodeSystem/v3-ParticipationType | data entry person | A person entering the data into the originating system. The data entry person is collected optionally for internal quality control purposes. This includes the transcriptionist for dictated text. |
INF | http://terminology.hl7.org/CodeSystem/v3-ParticipationType | informant | A source of reported information (e.g., a next of kin who answers questions about the patient's history). For history questions, the patient is logically an informant, yet the informant of history questions is implicitly the subject. |
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. |
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. |
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 |