CDA Examples
1.0.0 - active United States of America flag

CDA Examples, published by Health Level Seven. This guide is not an authorized publication; it is the continuous build for version 1.0.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/CDA-Examples/ and changes regularly. See the Directory of published versions

Performers, Authors, Informants, and Participants

Participation in Clinical Document Architecture (CDA) documents can be complex since multiple roles can be played by the same person. In such cases, the person should be identified for each appropriate participation. Within CDA documents there are four participant types common to any clinical section or entry (i.e. act types of <act>, <encounter>, <observation>, <procedure>, and <substanceAdministration>). The following four participant types are shown with a definition from CDA R2.0 standard:

  • <author> Represents the humans and/or machines that authored the [document/section/entry/act].
  • <performer> A person who actually and principally carries out an action.
  • <informant> An informant (or source of information) is a person that provides relevant information, such as the parent of a comatose patient who describes the patient’s behavior prior to the onset of coma.
  • <participant> Used to represent other participants not explicitly mentioned by other classes, that were somehow involved in the documented activities

The usage of <author> is often required within clinical documents to meet data provenance requirements for certified health information technology. The specific <templateId root=“2.16.840.1.113883.10.20.22.5.6” /> may be used when an author is conformant to the Author Provenance template. For more information on data provenance, see USCDI requirements.

The following tables provide informative guidance for what different participants may mean within different sections of a C-CDA document. This was created as part of a C-CDA 2020 Implement-a-thon and reviewed by the CDA Examples Task Force operating under the guidance of the HL7 Structured Documents Working Group in 2021.

Entries in Each Clinical Domain Performer Author Informant Participant
Allergies Who diagnosed Who composed the record Other information source (e.g. patient or guardian) The allergen
Encounters Who performs Who composed the record Other information source (e.g. patient or guardian) Where performed
Immunizations & Medications See details on next table
Payers Payer, or Guarantor Who composed the record Other information source (e.g. patient or guardian) Member, patient or subscriber
Planned Activity or Observation Who plans to perform Who composed the record Other information source (e.g. patient or guardian)
Problems Who diagnosed Who composed the record Other information source (e.g. patient or guardian)
Procedures Who performs (e.g. surgeon) Who composed the record Other information source (e.g. patient or guardian) Device & where performed
Results Who performs (e.g. lab or imaging center) Who composed the record or who provides interpretation/reading Other information source (e.g. patient or guardian)
Vital Signs Who performs Who composed the record Other information source (e.g. patient or guardian)

Additional Detail on Medication (or Immunization) Scenarios

Entries in Each Clinical Domain Performer* Author Informant Participant
New Medication (or existing)
Medications, Planned
moodCode="INT"
Who will administer a medication (often omitted) The prescriber(s). May also be who composed the record with use of functionCode. Other information source (e.g. patient or guardian) A vehicle for drug administration (e.g. Normal Saline)
Ongoing Medication
moodCode="INT"
Who has and/or will administer a medication (often omitted) The prescriber(s). May also be who composed the record with use of functionCode. Other information source (e.g. patient or guardian) A vehicle for drug administration (e.g. Normal Saline)
Past Medication
(may be one-time, discontinued or patient reported)
moodCode="EVN"
Who has administered The past prescriber(s). May also be who composed the record with use of functionCode. Other information source (e.g. patient or guardian) A vehicle for drug administration (e.g. Normal Saline)

* To document pharmacy information within a medication activity, use a performer within the following sub-templates:

  • IF NEW OR ONGOING MEDICATION (moodCode=”INT”): The ttp://hl7.org/cda/us/ccda/StructureDefinition/MedicationSupplyOrder template, where a prescription was sent h
  • IF ONGOING OR PAST MEDICATION (moodCode=”EVN”): The Medication Dispense template, where the prescription was dispensed