Clinical Document Architecture
2.0.0-sd - release

This page is part of the CDA: Clinical Document Architecture (v2.0.0-sd: CDA2 - Informative) generated with FHIR (HL7® FHIR® Standard) v5.0.0. This is the current published version. For a full list of available versions, see the Directory of published versions

ValueSet: CDAParticipationType

Official URL: http://hl7.org/cda/stds/core/ValueSet/CDAParticipationType Version: 2.0.0-sd
Draft as of 2024-05-17 Computable Name: CDAParticipationType

A code specifying the meaning and purpose of every Participation instance. Each of its values implies specific constraints on the Roles undertaking the participation. Limited to values allowed in original CDA definition

References

Logical Definition (CLD)

  • Include these codes as defined in http://terminology.hl7.org/CodeSystem/v3-ParticipationType
    CodeDisplayDefinition
    ADMadmitterThe practitioner who is responsible for admitting a patient to a patient encounter.
    ATNDattenderThe practitioner that has responsibility for overseeing a patient's care during a patient encounter.
    CALLBCKcallback contactA person or organization who should be contacted for follow-up questions about the act in place of the author.
    CONconsultantAn advisor participating in the service by performing evaluations and making recommendations.
    DISdischargerThe practitioner who is responsible for the discharge of a patient from a patient encounter.
    ESCescortOnly with Transportation services. A person who escorts the patient.
    REFreferrerA person having referred the subject of the service to the performer (referring physician). Typically, a referring physician will receive a report.
    INDindirect targetTarget 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.
    BENbeneficiaryTarget 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.
    COVcoverage targetThe 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.
    HLDholderParticipant who posses an instrument such as a financial contract (insurance policy) usually based on some agreement with the author.
    RCTrecord targetThe 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.
    RCVreceiverThe person (or organization) who receives the product of an Act.
    AUTauthor (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.
    ENTdata entry personA 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.
    INFinformantA 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.
    WITwitnessOnly 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.
    IRCPinformation 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.
    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).
    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.
    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).
    REFTReferred toThe person who receives the patient
    TRCtrackerA secondary information recipient, who receives copies (e.g., a primary care provider receiving copies of results as ordered by specialist).
    PRFperformer**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.
    DISTdistributorDistributes material used in or generated during the act.
    PPRFprimary performerThe principal or primary performer of the act.
    SPRFsecondary performerA person assisting in an act through his substantial presence and involvement This includes: assistants, technicians, associates, or whatever the job titles may be.
    DEVdeviceParticipant 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.
    NRDnon-reuseable deviceA 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.
    RDVreusable deviceA 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.
    SBJsubjectThe 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.
    SPCspecimenThe subject of non-clinical (e.g. laboratory) observation services is a specimen.
    DIRdirect targetTarget participant that is substantially present in the act and which is directly involved in the action (includes consumed material, devices, etc.).
    BBYbabyIn an obstetric service, the baby.
    CSMconsumableParticipant material that is taken up, diminished, altered, or disappears in the act.
    DONdonorIn 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.
    PRDproductParticipant 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).
    LOClocationThe 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.)
    DSTdestinationThe destination for services. May be a static building (or room therein) or a movable facility (e.g., ship).
    ELOCentry locationA location where data about an Act was entered.
    ORGoriginThe location of origin for services. May be a static building (or room therein) or a movable facility (e.g., ship).
    RMLremoteSome 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."
    VIAviaFor services, an intermediate location that specifies a path between origin an destination.
    VRFverifierA person who verifies the correctness and appropriateness of the service (plan, order, event, etc.) and hence takes on accountability.
    AUTHENauthenticatorA 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.
    LAlegal authenticatorA 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.
    RESPresponsible partyThe 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.
    CSTcustodianAn 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.).

 

Expansion

Expansion based on codesystem ParticipationType v4.0.0 (CodeSystem)

This value set contains 48 concepts.

CodeSystemDisplayDefinition
  ADMhttp://terminology.hl7.org/CodeSystem/v3-ParticipationTypeadmitter

The practitioner who is responsible for admitting a patient to a patient encounter.

  ATNDhttp://terminology.hl7.org/CodeSystem/v3-ParticipationTypeattender

The practitioner that has responsibility for overseeing a patient's care during a patient encounter.

  CALLBCKhttp://terminology.hl7.org/CodeSystem/v3-ParticipationTypecallback contact

A person or organization who should be contacted for follow-up questions about the act in place of the author.

  CONhttp://terminology.hl7.org/CodeSystem/v3-ParticipationTypeconsultant

An advisor participating in the service by performing evaluations and making recommendations.

  DIShttp://terminology.hl7.org/CodeSystem/v3-ParticipationTypedischarger

The practitioner who is responsible for the discharge of a patient from a patient encounter.

  ESChttp://terminology.hl7.org/CodeSystem/v3-ParticipationTypeescort

Only with Transportation services. A person who escorts the patient.

  REFhttp://terminology.hl7.org/CodeSystem/v3-ParticipationTypereferrer

A person having referred the subject of the service to the performer (referring physician). Typically, a referring physician will receive a report.

  INDhttp://terminology.hl7.org/CodeSystem/v3-ParticipationTypeindirect 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.

  BENhttp://terminology.hl7.org/CodeSystem/v3-ParticipationTypebeneficiary

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.

  COVhttp://terminology.hl7.org/CodeSystem/v3-ParticipationTypecoverage 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.

  HLDhttp://terminology.hl7.org/CodeSystem/v3-ParticipationTypeholder

Participant who posses an instrument such as a financial contract (insurance policy) usually based on some agreement with the author.

  RCThttp://terminology.hl7.org/CodeSystem/v3-ParticipationTyperecord 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.

  RCVhttp://terminology.hl7.org/CodeSystem/v3-ParticipationTypereceiver

The person (or organization) who receives the product of an Act.

  AUThttp://terminology.hl7.org/CodeSystem/v3-ParticipationTypeauthor (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.

  ENThttp://terminology.hl7.org/CodeSystem/v3-ParticipationTypedata 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.

  INFhttp://terminology.hl7.org/CodeSystem/v3-ParticipationTypeinformant

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.

  WIThttp://terminology.hl7.org/CodeSystem/v3-ParticipationTypewitness

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.

  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.

  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).

  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.

  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).

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

The person who receives the patient

  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).

  PRFhttp://terminology.hl7.org/CodeSystem/v3-ParticipationTypeperformer

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.

  DISThttp://terminology.hl7.org/CodeSystem/v3-ParticipationTypedistributor

Distributes material used in or generated during the act.

  PPRFhttp://terminology.hl7.org/CodeSystem/v3-ParticipationTypeprimary performer

The principal or primary performer of the act.

  SPRFhttp://terminology.hl7.org/CodeSystem/v3-ParticipationTypesecondary 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.

  DEVhttp://terminology.hl7.org/CodeSystem/v3-ParticipationTypedevice

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.

  NRDhttp://terminology.hl7.org/CodeSystem/v3-ParticipationTypenon-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.

  RDVhttp://terminology.hl7.org/CodeSystem/v3-ParticipationTypereusable 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.

  SBJhttp://terminology.hl7.org/CodeSystem/v3-ParticipationTypesubject

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.

  SPChttp://terminology.hl7.org/CodeSystem/v3-ParticipationTypespecimen

The subject of non-clinical (e.g. laboratory) observation services is a specimen.

  DIRhttp://terminology.hl7.org/CodeSystem/v3-ParticipationTypedirect target

Target participant that is substantially present in the act and which is directly involved in the action (includes consumed material, devices, etc.).

  BBYhttp://terminology.hl7.org/CodeSystem/v3-ParticipationTypebaby

In an obstetric service, the baby.

  CSMhttp://terminology.hl7.org/CodeSystem/v3-ParticipationTypeconsumable

Participant material that is taken up, diminished, altered, or disappears in the act.

  DONhttp://terminology.hl7.org/CodeSystem/v3-ParticipationTypedonor

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.

  PRDhttp://terminology.hl7.org/CodeSystem/v3-ParticipationTypeproduct

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).

  LOChttp://terminology.hl7.org/CodeSystem/v3-ParticipationTypelocation

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.)

  DSThttp://terminology.hl7.org/CodeSystem/v3-ParticipationTypedestination

The destination for services. May be a static building (or room therein) or a movable facility (e.g., ship).

  ELOChttp://terminology.hl7.org/CodeSystem/v3-ParticipationTypeentry location

A location where data about an Act was entered.

  ORGhttp://terminology.hl7.org/CodeSystem/v3-ParticipationTypeorigin

The location of origin for services. May be a static building (or room therein) or a movable facility (e.g., ship).

  RMLhttp://terminology.hl7.org/CodeSystem/v3-ParticipationTyperemote

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."

  VIAhttp://terminology.hl7.org/CodeSystem/v3-ParticipationTypevia

For services, an intermediate location that specifies a path between origin an destination.

  VRFhttp://terminology.hl7.org/CodeSystem/v3-ParticipationTypeverifier

A person who verifies the correctness and appropriateness of the service (plan, order, event, etc.) and hence takes on accountability.

  AUTHENhttp://terminology.hl7.org/CodeSystem/v3-ParticipationTypeauthenticator

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.

  LAhttp://terminology.hl7.org/CodeSystem/v3-ParticipationTypelegal 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.

  RESPhttp://terminology.hl7.org/CodeSystem/v3-ParticipationTyperesponsible 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.

  CSThttp://terminology.hl7.org/CodeSystem/v3-ParticipationTypecustodian

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.).


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