HL7 Terminology
2.1.0 - Publication
This page is part of the HL7 Terminology (v2.1.0: Release) based on FHIR R4. The current version which supercedes this version is 5.2.0. For a full list of available versions, see the Directory of published versions
<ValueSet xmlns="http://hl7.org/fhir">
<id value="v3-ParticipationTypeCDASectionOverride"/>
<language value="en"/>
<text>
<status value="extensions"/>
<div xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"><ul><li>Include these codes as defined in <a href="CodeSystem-v3-ParticipationType.html"><code>http://terminology.hl7.org/CodeSystem/v3-ParticipationType</code></a><table class="none"><tr><td style="white-space:nowrap"><b>Code</b></td><td><b>Display</b></td><td><b>Definition</b></td></tr><tr><td><a href="CodeSystem-v3-ParticipationType.html#v3-ParticipationType-AUT">AUT</a></td><td>author (originator)</td><td>**Definition:** A party that originates the Act and therefore has responsibility for the information given in the Act and ownership of this Act.<br/><br/>**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.<br/><br/>Examples of such policies might include:<br/><br/> * The author and anyone they explicitly delegate may update the report;<br/> * All administrators within the same clinic may cancel and reschedule appointments created by other administrators within that clinic;<br/><br/>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.</td></tr><tr><td><a href="CodeSystem-v3-ParticipationType.html#v3-ParticipationType-AUTHEN">AUTHEN</a></td><td>authenticator</td><td>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.</td></tr><tr><td><a href="CodeSystem-v3-ParticipationType.html#v3-ParticipationType-INF">INF</a></td><td>informant</td><td>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.</td></tr><tr><td><a href="CodeSystem-v3-ParticipationType.html#v3-ParticipationType-SBJ">SBJ</a></td><td>subject</td><td>The principle target on which the action happens.<br/><br/>*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).<br/><br/>*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.</td></tr></table></li></ul></div>
</text>
<url
value="http://terminology.hl7.org/ValueSet/v3-ParticipationTypeCDASectionOverride"/>
<identifier>
<system value="urn:ietf:rfc:3986"/>
<value value="urn:oid:2.16.840.1.113883.1.11.20472"/>
</identifier>
<version value="2.0.0"/>
<name value="ParticipationTypeCDASectionOverride"/>
<title value="ParticipationTypeCDASectionOverride"/>
<status value="active"/>
<date value="2014-03-26"/>
<description
value="Identifies the set of participation types context that can be blocked (overridden) at the CDA section or sub-section level of a document."/>
<compose>
<include>
<system value="http://terminology.hl7.org/CodeSystem/v3-ParticipationType"/>
<concept>
<code value="AUT"/>
</concept>
<concept>
<code value="AUTHEN"/>
</concept>
<concept>
<code value="INF"/>
</concept>
<concept>
<code value="SBJ"/>
</concept>
</include>
</compose>
</ValueSet>