HL7 Terminology (THO)
7.0.0 - publication International flag

This page is part of the HL7 Terminology (v7.0.0: Release) based on 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: FHIR Clinical Document Participant Types Value set

Official URL: http://terminology.hl7.org/ValueSet/fhir-clinical-doc-participant Version: 1.0.0
Active as of 2025-04-04 Responsible: HL7 International Computable Name: FHIRClinicalDocParticipantVs

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

FHIR Clinical Document Participant Types. Author, Authenticator, Custodian, Legal Authenticator, Record Target and Subject are found in distinct, named fields in FHIR. Thus, these types are excluded.

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)

This value set includes codes based on the following rules:

This value set excludes codes based on the following rules:

  • Exclude these codes as defined in http://terminology.hl7.org/CodeSystem/v3-ParticipationType version 📦5.0.0
    CodeDisplayDefinition
    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.
    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.
    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.).
    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.
    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.
    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.

 

Expansion

Expansion performed internally based on codesystem ParticipationType v5.0.0 (CodeSystem)

This value set contains 56 concepts

SystemCodeDisplay (en)InactiveJSONXML
http://terminology.hl7.org/CodeSystem/v3-ParticipationType  PARTParticipation
http://terminology.hl7.org/CodeSystem/v3-ParticipationType  _ParticipationAncillaryParticipationAncillary
http://terminology.hl7.org/CodeSystem/v3-ParticipationType  ADMadmitter
http://terminology.hl7.org/CodeSystem/v3-ParticipationType  ATNDattender
http://terminology.hl7.org/CodeSystem/v3-ParticipationType  CALLBCKcallback contact
http://terminology.hl7.org/CodeSystem/v3-ParticipationType  CONconsultant
http://terminology.hl7.org/CodeSystem/v3-ParticipationType  DISdischarger
http://terminology.hl7.org/CodeSystem/v3-ParticipationType  ESCescort
http://terminology.hl7.org/CodeSystem/v3-ParticipationType  REFreferrer
http://terminology.hl7.org/CodeSystem/v3-ParticipationType  _ParticipationInformationGeneratorParticipationInformationGenerator
http://terminology.hl7.org/CodeSystem/v3-ParticipationType  INFinformant
http://terminology.hl7.org/CodeSystem/v3-ParticipationType  TRANSTranscriber
http://terminology.hl7.org/CodeSystem/v3-ParticipationType  ENTdata entry person
http://terminology.hl7.org/CodeSystem/v3-ParticipationType  WITwitness
http://terminology.hl7.org/CodeSystem/v3-ParticipationType  NOTARYnotary
http://terminology.hl7.org/CodeSystem/v3-ParticipationType  DIRdirect target
http://terminology.hl7.org/CodeSystem/v3-ParticipationType  ALYanalyte
http://terminology.hl7.org/CodeSystem/v3-ParticipationType  BBYbaby
http://terminology.hl7.org/CodeSystem/v3-ParticipationType  CATcatalyst
http://terminology.hl7.org/CodeSystem/v3-ParticipationType  CSMconsumable
http://terminology.hl7.org/CodeSystem/v3-ParticipationType  TPAtherapeutic agentinactive
http://terminology.hl7.org/CodeSystem/v3-ParticipationType  DEVdevice
http://terminology.hl7.org/CodeSystem/v3-ParticipationType  NRDnon-reuseable device
http://terminology.hl7.org/CodeSystem/v3-ParticipationType  RDVreusable device
http://terminology.hl7.org/CodeSystem/v3-ParticipationType  DONdonor
http://terminology.hl7.org/CodeSystem/v3-ParticipationType  EXPAGNTExposureAgent
http://terminology.hl7.org/CodeSystem/v3-ParticipationType  EXPARTExposureParticipation
http://terminology.hl7.org/CodeSystem/v3-ParticipationType  EXPTRGTExposureTarget
http://terminology.hl7.org/CodeSystem/v3-ParticipationType  EXSRCExposureSource
http://terminology.hl7.org/CodeSystem/v3-ParticipationType  PRDproduct
http://terminology.hl7.org/CodeSystem/v3-ParticipationType  SPCspecimen
http://terminology.hl7.org/CodeSystem/v3-ParticipationType  INDindirect target
http://terminology.hl7.org/CodeSystem/v3-ParticipationType  BENbeneficiary
http://terminology.hl7.org/CodeSystem/v3-ParticipationType  CAGNTcausative agent
http://terminology.hl7.org/CodeSystem/v3-ParticipationType  COVcoverage target
http://terminology.hl7.org/CodeSystem/v3-ParticipationType  GUARguarantor party
http://terminology.hl7.org/CodeSystem/v3-ParticipationType  HLDholder
http://terminology.hl7.org/CodeSystem/v3-ParticipationType  RCVreceiver
http://terminology.hl7.org/CodeSystem/v3-ParticipationType  IRCPinformation recipient
http://terminology.hl7.org/CodeSystem/v3-ParticipationType  NOTugent notification contact
http://terminology.hl7.org/CodeSystem/v3-ParticipationType  PRCPprimary information recipient
http://terminology.hl7.org/CodeSystem/v3-ParticipationType  REFBReferred By
http://terminology.hl7.org/CodeSystem/v3-ParticipationType  REFTReferred to
http://terminology.hl7.org/CodeSystem/v3-ParticipationType  TRCtracker
http://terminology.hl7.org/CodeSystem/v3-ParticipationType  LOClocation
http://terminology.hl7.org/CodeSystem/v3-ParticipationType  DSTdestination
http://terminology.hl7.org/CodeSystem/v3-ParticipationType  ELOCentry location
http://terminology.hl7.org/CodeSystem/v3-ParticipationType  ORGorigin
http://terminology.hl7.org/CodeSystem/v3-ParticipationType  RMLremote
http://terminology.hl7.org/CodeSystem/v3-ParticipationType  VIAvia
http://terminology.hl7.org/CodeSystem/v3-ParticipationType  PRFperformer
http://terminology.hl7.org/CodeSystem/v3-ParticipationType  DISTdistributor
http://terminology.hl7.org/CodeSystem/v3-ParticipationType  PPRFprimary performer
http://terminology.hl7.org/CodeSystem/v3-ParticipationType  SPRFsecondary performer
http://terminology.hl7.org/CodeSystem/v3-ParticipationType  RESPresponsible party
http://terminology.hl7.org/CodeSystem/v3-ParticipationType  VRFverifier

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

DateActionAuthorCustodianComment
2025-05-07createBret HealeSDValuesets for FHIR Clinical Documents; up-665