Design Comments: This is used to indicate the party responsible for authorizing an override.

Design Comments: transformation Used when the target Act is a transformation of the source Act. (For instance, used to show that a CDA document is a transformation of a DICOM SR document).

Design Comments: Used when one or more text CD is electronically captured in coded form where the content of the predecessor(s) is being succeeded by the coded CD but may not be an exact replica

Design Comments: This code is used to specify the exact function an actor is authorized to have in authoring a consent override. Could be a staff person authorized by the responsible overriding authority. A provider may exercise perogative and prevent a subject of care from accessing health information in order to protect the patient or others; or to ensure that a provider is able to inform the subject of care directly. This might also be used to indicate that a clerical staff is authorized to enter hard copy prior consent directive into a structured consent based on document’s attestation of the subject.

Design Comments: Used to specify the exact function an actor is authorized to have in authoring a consent directive. This would not be use for the default roles, e.g., where the consent is authored by the subject of consent or for the R_ResponsibleParty acting as a substitute decision maker on behalf of the subject whose manner of participation does not need further specification. However, where the way in which a designated substitute decision maker participates requires more detail, the ConsenterParticipationFunction can be used to indicate that the role is participating as a legal guardian of the subject of consent, a personal representative of the subject of consent, or a a person with healthcare power of attorney for the subject of consent.

Design Comments: One or more consent directives may be predecessors of the focal consent directive. These may be unstructured text. If the hard-copy consent directive is used as evidence of the consenter's attestation to the focal ConsentDirective, e.g., in situations where legally, a signature is required but digital signatures is not technically supported or not legally binding, then attaching a scanned consent directive with a wet signature may satisfy the business requirement.

Design Comments: The text form of the PriorConsentDirective may be scanned and attached.

Design Comments: This code is used to specify the exact function an actor is authorized to have as a receiver of information that is the subject of a consent directive or consent override. This is used to indicate that the recipient is an authorized intermediary of the information, e.g., a Health Bank or PHRS, or a recipient system’s security service management service that will enforce the consent directive rules within the receiving organization.

Design Comments: May be used to specify types of health information rather than an instance

Design Comments: Purpose for a permitted operation on an information artifact, e.g., permission to access may be for the purposes of treatment, payment, operations, or research

Design Comments: Attribute description: A code specifying how branches in an action plan are selected among other branches. Discussion: This attribute is part of the workflow control suite of attributes. An action plan is a composite Act with component Acts. In a sequential plan, each component has a sequenceNumber that specifies the ordering of the plan steps. Branches exist when multiple components have the same sequenceNumber. The splitCode specifies whether a branch is executed exclusively (case-switch) or inclusively, i.e., in parallel with other branches. In addition to exclusive and inclusive split the splitCode specifies how the pre-condition (also known as "guard conditions" on the branch) are evaluated. A guard condition may be evaluated once when the branching step is entered and if the conditions do not hold at that time, the branch is abandoned. Conversely execution of a branch may wait until the guard condition turns true. In exclusive wait branches, the first branch whose guard conditions turn true will be executed and all other branches abandoned. In inclusive wait branches some branches may already be executed while other branches still wait for their guard conditions to turn true.

Design Comments: Obligations, that is, actions to be performed after an action has been executed on data objects, are necessary for some cases. For example, the OECD Accountability Principle states that “A data controller should be accountable for complying with measures which give effect to the principles stated above”. A common approach to implement this principle in operating systems or DBMS is to log each data access as an event. Executing logging actions could be an obligation for the majority of privacy policies.

Design Comments: A code further specifying an obligation that a that results from a permitted act or operation on an information artifact, e.g., the obligation to log and audit.

Design Comments: Attribute description: A code specifying when in the course of an Act a precondition for the Act is evaluated (e.g., before the Act starts for the first time, before every repetition, after each repetition but not before the first, or throughout the entire time of the Act). Discussion: This attribute is part of the workflow control suite of attributes. An action plan is a composite Act with component Acts. In a sequential plan, each component has a sequenceNumber that specifies the ordering of the plan steps. Before each step is executed, those with preconditions have their conditions tested; where the test is positive, the Act has clearance for execution. The repeatNumber may indicate that an Act may be repeatedly executed. The checkpointCode is specifies when the precondition is checked and is analogous to the various conditional statements and loop constructs in programming languages "while-do" vs. "do-while" or "repeat-until" vs. "loop-exit". For all checkpointCodes, except "end", preconditions are being checked at the time when the preceding step of the plan has terminated and this step would be next in the sequence established by the sequenceNumber attribute. When the checkpointCode for a criterion of a repeatable Act is "end", the criterion is tested only at the When the checkpointCode is "entry" the criterion is checked at the beginning of each repetition (if any) whereas "beginning" means the criterion is checked only once before the repetition "loop" starts. The checkpointCode "through" is special in that it requires the condition to hold throughout the execution of the Act, even throughout a single execution. As soon as the condition turns false, the Act should receive an interrupt event (see Act.interruptibleInd) and will eventually terminate. The checkpointCode "exit" is only used on a special plan step that represents a loop exit step. This allows an action plan to exit due to a condition tested inside the execution of this plan. Such exit criteria are sequenced with the other plan components using the ActRelationship.sequenceNumber

Design Comments: Vocabulary domain: RelationshipConjunction (CNE) Attribute description: A code specifying the logical conjunction of the criteria among all the condition-links of Acts (e.g., and, or, exclusive-or). Constraints: All AND criteria must be true. If OR and AND criteria occur together, one criterion out of the OR-group must be true and all AND criteria must be true also. If XOR criteria occur together with OR and AND criteria, exactly one of the XOR criteria must be true, and at least one of the OR criteria and all AND criteria must be true. In other words, the sets of AND, OR, and XOR criteria are in turn combined by a logical AND operator (all AND criteria and at least one OR criterion and exactly one XOR criterion). To overcome this ordering, Act criteria can be nested in any way necessary.

Design Comments: A ConsentPermissionCondition is a prerequisite to be met before any permitted action can be executed

Design Comments: This domain includes observations used to characterize a privilege such as the conditions that must obtain for the privilege to be exercised or the permitted action to be executed.

Design Comments: Attribute description: A time expression specifying the focal or operative time of the Act, the primary time for which the Act holds, the time of interest from the perspective of the Act's intention.