The Master Data Model for Veteran Care

Developer Documentation » VDM » Usr_Action-8930_8

Usr Action (8930.8)

This file encodes actions which occur in connection with clinical narrative documents. These actions are referenced by entries in the User Authorization/Subscription file to associate users with actions. This file contains 2 kinds of actions: those a user is authorized to perform on a document, and those a user subscribes to for a document. For example, a user is authorized to perform the Signature action, but a user subscribes to (“signs up to receive”) a Notification action.

Global: ^USR(8930.8,

Domain: Non-Clinical

Properties

Label/Field Name Field # Description Datatype Attributes Range
Name
  name
.01 These are names of events which occur in connection with clinical
narrative documents. These are referenced by the User
Authorization/Subscription file to associate users with events.
STRING INDEXED
REQUIRED
 
Event Type
  event_type
.02 This file contains two types of events: those a user is AUTHORIZED to
perform and those a user SUBSCRIBES to. For example, a user is authorized
to perform the Signature event, but a user subscribes to (“signs up to
receive”) a Notification event.
This field helps to define the meaning of an event and its relationship to
a user.
ENUMERATION   authorization: A
subscription: S
Applies To
  applies_to
.03   ENUMERATION   definition: DEF
document: DOC
Associated Protocol
  associated_protocol
.04   POINTER   Protocol-101
User Verb
  user_verb
.05 This word or phrase is displayed in explanatory messages when the user is
denied authority to perform the given action. Such a message might read,
“You cannot SIGN this unsigned progress note”, where the USER VERB is
“SIGN”.

The USER VERB must make grammatical sense inserted in a sentence of the
form: “You cannot [ ] this unsigned progress note.”

Please use uppercase, 3-50 characters.
STRING    
Document Verb
  document_verb
.06 This word or phrase is used in business rule options when displaying
an authorization in sentence form.

A business rule might read: “An unsigned Progress Note can BE SIGNED by
an author/dictator.” The DOCUMENT VERB in this rule is “BE SIGNED”.

The DOCUMENT VERB must make grammatical sense inserted in a sentence of
the form: “An unsigned progress note can [ ] by an author/dictator.”

Please use uppercase, 3-40 characters.
STRING    
User Verb Modifier
  user_verb_modifier
.07 Sometimes, in writing messages to the user denying a permission, the
action must be split into two parts. In such cases, the USER VERB
MODIFIER is the second part.

Example: In “You cannot LINK this UNSIGNED PROGRESS NOTE with a request”,
the USER VERB is “LINK”, and the USER VERB MODIFIER is “with a request”.

The USER VERB MODIFIER must make grammatical sense when inserted in:
“You cannot LINK this UNSIGNED PROGRESS NOTE [ ].”

Please use lowercase, 3-30 characters.

If an action has an IDENTIFYING PHRASE or a USER VERB MODIFIER, the
business rule ADD or EDIT action presents the user with a clarifying note
about the rule they are creating immediately after the user enters an
action.
STRING    
Identifying Phrase
  identifying_phrase
.08 This field is NOT required. It is available for use in helping users
identify the correct action when writing business rules. It appears
when selecting actions from a list.

For examples, see actions ATTACH TO ID NOTE, and ATTACH ID ENTRY.

If an action has an IDENTIFYING PHRASE or a USER VERB MODIFIER, the
business rule ADD or EDIT action presents the user with a clarifying note
about the rule they are creating immediately after the user enters an
action.
STRING    
Implied Event
  implied_event
1 Some events imply other events. For example, the ability to Sign a
document implies the ability to View the document. Thus, View is an
implied event for the Signature event.

Authorization/Subscription file, the user will be shown implied events for
the given event and asked if they wish to include implied events for the
current entry. If so, a copy of the current entry will be created for each
implied event.
POINTER   Usr_Action-8930_8
Description
  description
2
The event description will be used in conjunction with the
Authorization/Subscription field to define what it means to associate
users with the event.
In most cases, this event description will suffice to determine the
meaning of User Authorization/Subscription file entries.

In rare cases, further description of what an event means when associated
with users, document type and document status will be made in the
description field of the User Authorization/Subscription file. For
example, a signature event associated with documents of status
completed means a walkup signature.

This information will be used by persons creating entries in the User
Authorization/Subscription file and by persons assigning users to user
classes, when checking what events those user classes are associated with.
STRING    

↑ Return to top


Document generated on August 31st 2017, 2:55:41 pm