HL7 Terminology
1.0.0 - Publication

This page is part of the HL7 Terminology (v1.0.0: Release) based on FHIR R4. This is the current published version. For a full list of available versions, see the Directory of published versions

ParticipationTypeCDASectionOverride

Summary

Defining URL:http://terminology.hl7.org/ValueSet/v3-ParticipationTypeCDASectionOverride
Version:2.0.0
Name:ParticipationTypeCDASectionOverride
Status:Active
Title:ParticipationTypeCDASectionOverride
Definition:

Identifies the set of participation types context that can be blocked (overridden) at the CDA section or sub-section level of a document.

OID:2.16.840.1.113883.1.11.20472 (for OID based terminology systems)
Source Resource:XML / JSON / Turtle

References

This value set is not used

Content Logical Definition

Logical Definition (CLD)

  • Include these codes as defined in http://terminology.hl7.org/CodeSystem/v3-ParticipationType
    CodeDisplay
    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.
    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.
    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

This value set contains 4 concepts

Expansion based on ParticipationType v2.0.0 (CodeSystem)

All codes from system http://terminology.hl7.org/CodeSystem/v3-ParticipationType

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

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
Source 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

DateActionCustodianAuthorComment
2020-05-06reviseVocabulary WGTed KleinMigrated to the UTG maintenance environment and publishing tooling.
2014-03-26revise2014T1_2014-03-26_001283 (RIM release ID)Vocabulary (Woody Beeler) (no record of original request)Lock all vaue sets untouched since 2014-03-26 to trackingId 2014T1_2014_03_26