Current Build

4.4.2.90 HL7 v3 Code System ParticipationType

Vocabulary Work Group Maturity Level: N/AExternal Use Context: Any

This code system (http://terminology.hl7.org/CodeSystem/v3-ParticipationType) is defined as part of HL7 v3.

Summary

Defining URL:http://terminology.hl7.org/CodeSystem/v3-ParticipationType
Version:2018-08-12
Name:v3.ParticipationType
Title:v3 Code System ParticipationType
Definition:

**** MISSING DEFINITIONS ****

OID:2.16.840.1.113883.5.90 (for OID based terminology systems)
Source ResourceXML / JSON

This Code system is used in the following value sets:

  • ValueSet: AdverseEvent Participant Function (This value set includes codes that describe the type of involvement of the actor in the adverse event.)
  • ValueSet: SecurityRoleType (This example FHIR value set is comprised of example Actor Type codes, which can be used to value FHIR agents, actors, and other role elements such as those specified in financial transactions. The FHIR Actor value set is based on DICOM Audit Message, C402; ASTM Standard, E1762-95 [2013]; selected codes and derived actor roles from HL7 RoleClass OID 2.16.840.1.113883.5.110; HL7 Role Code 2.16.840.1.113883.5.111, including AgentRoleType; HL7 ParticipationType OID: 2.16.840.1.113883.5.90; and HL7 ParticipationFunction codes OID: 2.16.840.1.113883.5.88. This value set includes, by reference, role codes from external code systems: NUCC Health Care Provider Taxonomy OID: 2.16.840.1.113883.6.101; North American Industry Classification System [NAICS]OID: 2.16.840.1.113883.6.85; IndustryClassificationSystem 2.16.840.1.113883.1.11.16039; and US Census Occupation Code OID: 2.16.840.1.113883.6.243 for relevant recipient or custodian codes not included in this value set. If no source is indicated in the definition comments, then these are example FHIR codes. It can be extended with appropriate roles described by SNOMED as well as those described in the HL7 Role Based Access Control Catalog and the HL7 Healthcare (Security and Privacy) Access Control Catalog. In Role-Based Access Control (RBAC), permissions are operations on an object that a user wishes to access. Permissions are grouped into roles. A role characterizes the functions a user is allowed to perform. Roles are assigned to users. If the user's role has the appropriate permissions to access an object, then that user is granted access to the object. FHIR readily enables RBAC, as FHIR Resources are object types and the CRUDE events (the FHIR equivalent to permissions in the RBAC scheme) are operations on those objects. In Attribute-Based Access Control (ABAC), a user requests to perform operations on objects. That user's access request is granted or denied based on a set of access control policies that are specified in terms of attributes and conditions. FHIR readily enables ABAC, as instances of a Resource in FHIR (again, Resources are object types) can have attributes associated with them. These attributes include security tags, environment conditions, and a host of user and object characteristics, which are the same attributes as those used in ABAC. Attributes help define the access control policies that determine the operations a user may perform on a Resource (in FHIR) or object (in ABAC). For example, a tag (or attribute) may specify that the identified Resource (object) is not to be further disclosed without explicit consent from the patient.)
  • ValueSet: v3 Code System ParticipationType (**** MISSING DEFINITIONS ****)
  • ValueSet: V3 Value SetParticipationVerifier ( A person who verifies the correctness and appropriateness of the service (plan, order, event, etc.) and hence takes on accountability.)
  • ValueSet: Provenance Event History Agent Role Codes (Types of roles indicating how a particular agent was involved with the creation or modification of a resource for use when exposing event history)
  • ValueSet: V3 Value SetParticipationTargetSubject ( The principle target that the service acts on. E.g. the patient in physical examination, a specimen in a lab observation. May also be a patient's family member (teaching) or a device or room (cleaning, disinfecting, housekeeping). Note: not all direct targets are subjects, consumables, and devices used as tools for a service are not subjects. However, a device may be a subject of a maintenance service.)
  • ValueSet: Focal Subject Codes (Example value set composed from SNOMED CT and HL7 V3 codes for observation targets such as donor, fetus or spouse. As use cases are discovered, more values may be added.)
  • ValueSet: ParticipationRoleType (This FHIR value set is comprised of Actor participation Type codes, which can be used to value FHIR agents, actors, and other role elements. The FHIR Actor participation type value set is based on DICOM Audit Message, C402; ASTM Standard, E1762-95 [2013]; selected codes and derived actor roles from HL7 RoleClass OID 2.16.840.1.113883.5.110; HL7 Role Code 2.16.840.1.113883.5.111, including AgentRoleType; HL7 ParticipationType OID: 2.16.840.1.113883.5.90; and HL7 ParticipationFunction codes OID: 2.16.840.1.113883.5.88. This value set includes, by reference, role codes from external code systems: NUCC Health Care Provider Taxonomy OID: 2.16.840.1.113883.6.101; North American Industry Classification System [NAICS]OID: 2.16.840.1.113883.6.85; IndustryClassificationSystem 2.16.840.1.113883.1.11.16039; and US Census Occupation Code OID: 2.16.840.1.113883.6.243 for relevant recipient or custodian codes not included in this value set. If no source is indicated in the definition comments, then these are example FHIR codes.)
  • ValueSet: V3 Value SetParticipationTargetLocation ( The facility where the service is done. May be a static building (or room therein) or a moving location (e.g., ambulance, helicopter, aircraft, train, truck, ship, etc.))
  • ValueSet: ImagingStudy series performer function (Performer function of an agent in an imaging study series)
  • ValueSet: Participant type (This value set defines a set of codes that can be used to indicate how an individual participates in an encounter.)
  • ValueSet: V3 Value SetParticipationPhysicalPerformer ( A person who actually and principally carries out the action. Need not be the principal responsible actor, e.g. a surgery resident operating under supervision of attending surgeon, and may be the patient in self-care, e.g. fingerstick blood sugar. The traditional order filler is a performer. This information should accompany every service event.)
  • ValueSet: V3 Value SetParticipationInformationGenerator ( Parties that may or should contribute or have contributed information to the Act. Such information includes information leading to the decision to perform the Act and how to perform the Act (e.g., consultant), information that the Act itself seeks to reveal (e.g., informant of clinical history), or information about what Act was performed (e.g., informant witness).)
  • ValueSet: Participant type (This value set defines a set of codes that can be used to indicate how an individual participates in an encounter.)
  • ValueSet: V3 Value SetParticipationIndirectTarget ( Target that is not substantially present in the act and which is not directly affected by the act, but which will be a focus of the record or documentation of the act.)
  • ValueSet: SecurityRoleType (This example FHIR value set is comprised of example Actor Type codes, which can be used to value FHIR agents, actors, and other role elements such as those specified in financial transactions. The FHIR Actor value set is based on DICOM Audit Message, C402; ASTM Standard, E1762-95 [2013]; selected codes and derived actor roles from HL7 RoleClass OID 2.16.840.1.113883.5.110; HL7 Role Code 2.16.840.1.113883.5.111, including AgentRoleType; HL7 ParticipationType OID: 2.16.840.1.113883.5.90; and HL7 ParticipationFunction codes OID: 2.16.840.1.113883.5.88. This value set includes, by reference, role codes from external code systems: NUCC Health Care Provider Taxonomy OID: 2.16.840.1.113883.6.101; North American Industry Classification System [NAICS]OID: 2.16.840.1.113883.6.85; IndustryClassificationSystem 2.16.840.1.113883.1.11.16039; and US Census Occupation Code OID: 2.16.840.1.113883.6.243 for relevant recipient or custodian codes not included in this value set. If no source is indicated in the definition comments, then these are example FHIR codes. It can be extended with appropriate roles described by SNOMED as well as those described in the HL7 Role Based Access Control Catalog and the HL7 Healthcare (Security and Privacy) Access Control Catalog. In Role-Based Access Control (RBAC), permissions are operations on an object that a user wishes to access. Permissions are grouped into roles. A role characterizes the functions a user is allowed to perform. Roles are assigned to users. If the user's role has the appropriate permissions to access an object, then that user is granted access to the object. FHIR readily enables RBAC, as FHIR Resources are object types and the CRUDE events (the FHIR equivalent to permissions in the RBAC scheme) are operations on those objects. In Attribute-Based Access Control (ABAC), a user requests to perform operations on objects. That user's access request is granted or denied based on a set of access control policies that are specified in terms of attributes and conditions. FHIR readily enables ABAC, as instances of a Resource in FHIR (again, Resources are object types) can have attributes associated with them. These attributes include security tags, environment conditions, and a host of user and object characteristics, which are the same attributes as those used in ABAC. Attributes help define the access control policies that determine the operations a user may perform on a Resource (in FHIR) or object (in ABAC). For example, a tag (or attribute) may specify that the identified Resource (object) is not to be further disclosed without explicit consent from the patient.)
  • ValueSet: ParticipationRoleType (This FHIR value set is comprised of Actor participation Type codes, which can be used to value FHIR agents, actors, and other role elements. The FHIR Actor participation type value set is based on DICOM Audit Message, C402; ASTM Standard, E1762-95 [2013]; selected codes and derived actor roles from HL7 RoleClass OID 2.16.840.1.113883.5.110; HL7 Role Code 2.16.840.1.113883.5.111, including AgentRoleType; HL7 ParticipationType OID: 2.16.840.1.113883.5.90; and HL7 ParticipationFunction codes OID: 2.16.840.1.113883.5.88. This value set includes, by reference, role codes from external code systems: NUCC Health Care Provider Taxonomy OID: 2.16.840.1.113883.6.101; North American Industry Classification System [NAICS]OID: 2.16.840.1.113883.6.85; IndustryClassificationSystem 2.16.840.1.113883.1.11.16039; and US Census Occupation Code OID: 2.16.840.1.113883.6.243 for relevant recipient or custodian codes not included in this value set. If no source is indicated in the definition comments, then these are example FHIR codes.)
  • ValueSet: AdverseEvent Participant Function (This value set includes codes that describe the type of involvement of the actor in the adverse event.)
  • ValueSet: V3 Value SetParticipationInformationTranscriber ( An entity entering the data into the originating system. The data entry entity is collected optionally for internal quality control purposes. This includes the transcriptionist for dictated text transcribed into electronic form.)
  • ValueSet: Focal Subject Codes (Example value set composed from SNOMED CT and HL7 V3 codes for observation targets such as donor, fetus or spouse. As use cases are discovered, more values may be added.)
  • ValueSet: ImagingStudy series performer function (Performer function of an agent in an imaging study series)
  • ValueSet: Provenance Event History Agent Role Codes (Types of roles indicating how a particular agent was involved with the creation or modification of a resource for use when exposing event history)
  • ValueSet: V3 Value SetParticipationTargetDirect ( Target that is substantially present in the service and which is directly affected by the service action (includes consumed material, devices, etc.).)

Release Date: 2018-08-12

LevelCodeDisplayDefinition
1PART Participation Indicates that the target of the participation is involved in some manner in the act, but does not qualify how.
2  (_ParticipationAncillary) Abstract  Participations related, but not primary to an act. The Referring, Admitting, and Discharging practitioners must be the same person as those authoring the ControlAct event for their respective trigger events.
3    ADM admitter The practitioner who is responsible for admitting a patient to a patient encounter.
3    ATND attender The practitioner that has responsibility for overseeing a patient's care during a patient encounter.
3    CALLBCK callback contact A person or organization who should be contacted for follow-up questions about the act in place of the author.
3    CON consultant An advisor participating in the service by performing evaluations and making recommendations.
3    DIS discharger The practitioner who is responsible for the discharge of a patient from a patient encounter.
3    ESC escort Only with Transportation services. A person who escorts the patient.
3    REF referrer A person having referred the subject of the service to the performer (referring physician). Typically, a referring physician will receive a report.
2  (_ParticipationInformationGenerator) Abstract  Parties that may or should contribute or have contributed information to the Act. Such information includes information leading to the decision to perform the Act and how to perform the Act (e.g., consultant), information that the Act itself seeks to reveal (e.g., informant of clinical history), or information about what Act was performed (e.g., informant witness).
3    AUT author (originator) Definition: A party that originates the Act and therefore has responsibility for the information given in the Act and ownership of this Act.
Example: the report writer, the person writing the act definition, the guideline author, the placer of an order, the EKG cart (device) creating a report etc. Every Act should have an author. Authorship is regardless of mood always actual authorship.
Examples of such policies might include:
The author and anyone they explicitly delegate may update the report;
All administrators within the same clinic may cancel and reschedule appointments created by other administrators within that clinic;
A party that is neither an author nor a party who is extended authorship maintenance rights by policy, may only amend, reverse, override, replace, or follow up in other ways on this Act, whereby the Act remains intact and is linked to another Act authored by that other party.
3    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.
3    TRANS Transcriber An entity entering the data into the originating system. The data entry entity is collected optionally for internal quality control purposes. This includes the transcriptionist for dictated text transcribed into electronic form.
4      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.
3    WIT witness Only with service events. A person witnessing the action happening without doing anything. A witness is not necessarily aware, much less approves of anything stated in the service event. Example for a witness is students watching an operation or an advanced directive witness.
2  CST custodian An entity (person, organization or device) that is in charge of maintaining the information of this act (e.g., who maintains the report or the master service catalog item, etc.).
2  DIR direct target Target participant that is substantially present in the act and which is directly involved in the action (includes consumed material, devices, etc.).
3    ALY analyte The target of an Observation action. Links an observation to a Role whose player is the substance or most specific component entity (material, micro-organism, etc.) being measured within the subject.
Examples: A "plasma porcelain substance concentration" has analyte a Role with player substance Entity "porcelain".
UsageNotes: The Role that this participation connects to may be any Role whose player is that substance measured. Very often, the scoper may indicate the system in which the component is being measured. E.g., for "plasma porcelain" the scoper could be "Plasma".
3    BBY baby In an obstetric service, the baby.
3    CAT catalyst The catalyst of a chemical reaction, such as an enzyme or a platinum surface. In biochemical reactions, connects the enzyme with the molecular interaction
3    CSM consumable Participant material that is taken up, diminished, altered, or disappears in the act.
4      TPA therapeutic agent Something incorporated in the subject of a therapy service to achieve a physiologic effect (e.g., heal, relieve, provoke a condition, etc.) on the subject. In an administration service the therapeutic agent is a consumable, in a preparation or dispense service, it is a product. Thus, consumable or product must be specified in accordance with the kind of service.
3    DEV device Participant used in performing the act without being substantially affected by the act (i.e. durable or inert with respect to that particular service).
Examples: monitoring equipment, tools, but also access/drainage lines, prostheses, pace maker, etc.
4      NRD non-reuseable device A device that changes ownership due to the service, e.g., a pacemaker, a prosthesis, an insulin injection equipment (pen), etc. Such material may need to be restocked after he service.
4      RDV reusable device A device that does not change ownership due to the service, i.e., a surgical instrument or tool or an endoscope. The distinction between reuseable and non-reuseable must be made in order to know whether material must be re-stocked.
3    DON donor In some organ transplantation services and rarely in transfusion services a donor will be a target participant in the service. However, in most cases transplantation is decomposed in three services: explantation, transport, and implantation. The identity of the donor (recipient) is often irrelevant for the explantation (implantation) service.
3    EXPAGNT ExposureAgent Description: The entity playing the associated role is the physical (including energy), chemical or biological substance that is participating in the exposure. For example in communicable diseases, the associated playing entity is the disease causing pathogen.
3    EXPART ExposureParticipation Description:Direct participation in an exposure act where it is unknown that the participant is the source or subject of the exposure. If the participant is known to be the contact of an exposure then the SBJ participation type should be used. If the participant is known to be the source then the EXSRC participation type should be used.
4      EXPTRGT ExposureTarget Description: The entity playing the associated role is the target (contact) of exposure.
4      EXSRC ExposureSource Description:The entity playing the associated role is the source of exposure.
3    PRD product Participant material that is brought forth (produced) in the act (e.g., specimen in a specimen collection, access or drainage in a placement service, medication package in a dispense service). It does not matter whether the material produced had existence prior to the service, or whether it is created in the service (e.g., in supply services the product is taken from a stock).
3    SBJ subject The principle target on which the action happens.
Examples: The patient in physical examination, a specimen in a lab observation. May also be a patient's family member (teaching) or a device or room (cleaning, disinfecting, housekeeping).
UsageNotes: Not all direct targets are subjects. Consumables and devices used as tools for an act are not subjects. However, a device may be a subject of a maintenance action.
4      SPC specimen The subject of non-clinical (e.g. laboratory) observation services is a specimen.
2  IND indirect target Target that is not substantially present in the act and which is not directly affected by the act, but which will be a focus of the record or documentation of the act.
3    BEN beneficiary Target on behalf of whom the service happens, but that is not necessarily present in the service. Can occur together with direct target to indicate that a target is both, as in the case where the patient is the indirect beneficiary of a service rendered to a family member, e.g. counseling or given home care instructions. This concept includes a participant, such as a covered party, who derives benefits from a service act covered by a coverage act.
Note that the semantic role of the intended recipient who benefits from the happening denoted by the verb in the clause. Thus, a patient who has no coverage under a policy or program may be a beneficiary of a health service while not being the beneficiary of coverage for that service.
3    CAGNT causative agent Definition: A factor, such as a microorganism, chemical substance, or form of radiation, whose presence, excessive presence, or (in deficiency diseases) relative absence is essential, in whole or in part, for the occurrence of a condition.
Constraint: The use of this participation is limited to observations.
3    COV coverage target The target participation for an individual in a health care coverage act in which the target role is either the policy holder of the coverage, or a covered party under the coverage.
3    GUAR guarantor party The target person or organization contractually recognized by the issuer as a participant who has assumed fiscal responsibility for another personaTMs financial obligations by guaranteeing to pay for amounts owed to a particular account
Example:The subscriber of the patientaTMs health insurance policy signs a contract with the provider to be fiscally responsible for the patient billing account balance amount owed.
3    HLD holder Participant who posses an instrument such as a financial contract (insurance policy) usually based on some agreement with the author.
3    RCT record target The record target indicates whose medical record holds the documentation of this act. This is especially important when the subject of a service is not the patient himself.
3    RCV receiver The person (or organization) who receives the product of an Act.
2  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.
3    NOT 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).
3    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.
3    REFB 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).
3    REFT Referred to The person who receives the patient
3    TRC tracker A secondary information recipient, who receives copies (e.g., a primary care provider receiving copies of results as ordered by specialist).
2  LOC location The facility where the service is done. May be a static building (or room therein) or a moving location (e.g., ambulance, helicopter, aircraft, train, truck, ship, etc.)
3    DST destination The destination for services. May be a static building (or room therein) or a movable facility (e.g., ship).
3    ELOC entry location A location where data about an Act was entered.
3    ORG origin The location of origin for services. May be a static building (or room therein) or a movable facility (e.g., ship).
3    RML remote Some services take place at multiple concurrent locations (e.g., telemedicine, telephone consultation). The location where the principal performing actor is located is taken as the primary location (LOC) while the other location(s) are considered "remote."
3    VIA via For services, an intermediate location that specifies a path between origin an destination.
2  PRF performer Definition: A person, non-person living subject, organization or device that who actually and principally carries out the action. Device should only be assigned as a performer in circumstances where the device is performing independent of human intervention. Need not be the principal responsible actor.
Exampe: A surgery resident operating under supervision of attending surgeon, a search and rescue dog locating survivors, an electronic laboratory analyzer or the laboratory discipline requested to perform a laboratory test. The performer may also be the patient in self-care, e.g. fingerstick blood sugar. The traditional order filler is a performer. This information should accompany every service event.
Note: that existing HL7 designs assign an organization as the playing entity of the Role that is the performer. These designs should be revised in subsequent releases to make this the scooping entity for the role involved.
3    DIST distributor Distributes material used in or generated during the act.
3    PPRF primary performer The principal or primary performer of the act.
3    SPRF secondary performer A person assisting in an act through his substantial presence and involvement This includes: assistants, technicians, associates, or whatever the job titles may be.
2  RESP responsible party The person or organization that has primary responsibility for the act. The responsible party is not necessarily present in an action, but is accountable for the action through the power to delegate, and the duty to review actions with the performing actor after the fact. This responsibility may be ethical, legal, contractual, fiscal, or fiduciary in nature.
Example: A person who is the head of a biochemical laboratory; a sponsor for a policy or government program.
2  VRF verifier A person who verifies the correctness and appropriateness of the service (plan, order, event, etc.) and hence takes on accountability.
3    AUTHEN authenticator A verifier who attests to the accuracy of an act, but who does not have privileges to legally authenticate the act. An example would be a resident physician who sees a patient and dictates a note, then later signs it. Their signature constitutes an authentication.
3    LA legal authenticator A verifier who legally authenticates the accuracy of an act. An example would be a staff physician who sees a patient and dictates a note, then later signs it. Their signature constitutes a legal authentication.