| # | Name | Location | Type | Details | Index | Description |
|---|---|---|---|---|---|---|
| .01 | name(+) | 0;1 | FREE TEXT | B | 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. | |
| .02 | event type | 0;2 | SET OF CODES | A:authorization S:subscription | 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. | |
| .03 | applies to | 0;3 | SET OF CODES | DOC:document DEF:definition | ||
| .04 | associated protocol | 0;4 | POINTER | 101 | ||
| .05 | user verb | 0;5 | FREE TEXT | 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. | ||
| .06 | document verb | 0;6 | FREE TEXT | 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. | ||
| .07 | user verb modifier | 0;7 | FREE TEXT | 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. | ||
| .08 | identifying phrase | 3;1 | FREE TEXT | 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. | ||
| 1 | implied event | 1;0 | MULTIPLE | 8930.81 | 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. | |
| 2 | description | 2;0 | WORD-PROCESSING | 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. |