| # | Name | Location | Type | Details | Index | Description |
|---|---|---|---|---|---|---|
| .01 | name(+) | 0;1 | FREE TEXT | B | This field holds the free-text name of the monitor. | |
| 2 | status | 0;2 | SET OF CODES | A:ACTIVE I:INACTIVE | The values for this set of code field are ACTIVE and INACTIVE. If set to ACTIVE the master job will queue background monitor jobs for the monitor. If set to INACTIVE the master job will ignore the entry. | |
| 3 | short description | 0;3 | FREE TEXT | This field holds a short description of the monitor. | ||
| 4 | requeue min-monitor | 0;4 | NUMERIC | Whenever the master job runs it checks every entry in this HL7 Monitor file (#776.1). If an entry is active, a secondary check is made whether "it is time" to start a background job for the monitor. If the active monitor has never been run, a background job is started. If the monitor has been run, then the next "time to run" is calculated by adding the number of minutes specified in this field to the time the monitor was last run. If the next "time to run" is now (or earlier), a background job for the monitor is started. | ||
| 5 | remote requestable | 0;5 | BOOLEAN | 0:NO 1:YES | This field is not currently in use. | |
| 6 | m startup | 0;6 | FREE TEXT | Background tasks, started by the master job, are queued to the API specified in this field. (The value of this field must be in the format of TAG~ROUTINE, which is converted to TAG^ROUTINE at run time.) | ||
| 7 | m start check | 0;7 | FREE TEXT | Normally, the only test made by the master job to determine whether a monitor job should be started is STATUS (it must be ACTIVE) and the requeue minutes. However, if this field is filled in with an extrinsic function that returns a positive or null value, it can be used as an additional test. Let's say that the extrinsic fuction $$RUNOW^ROUTINE returns a 1 if a background job should be started, or null if not. In this case, "$$RUNOW^ROUTINE" should be entered in this field. | ||
| 41 | technical description | 41;0 | WORD-PROCESSING | This field holds any additional technical notes deemed necessary by the monitor creator. | ||
| 50 | event description | 50;0 | WORD-PROCESSING | This field should be used by the application developer to describe the monitor, and how it is used. (If desired, the application developer may add additional, more technical notes in the TECHNICAL DESCRIPTION word processing field.) | ||
| 51 | mail groups | 60;0 | MULTIPLE | 776.106 | When a monitor runs, the M code can conditionally send a mail message to recipients. This field, and other fields, are used to determine the recipients. In addition, recipients can be added by M code immediately before the sending of the message. The fields used to determine mail message recipients are: * MAIL GROUPS (#60) - pointer to the Mail Group file (#3.8.) * RECIPIENTS (#61) - pointer to the New Person file (#200.) * REMOTES (#62) - free-text remote recipient addresses. And, remember that additional recipients can be added (by populating the XMY array) on-the-fly at the time the message is sent. Please refer to the documentation included with patch HL*1.6*106 for additional explanation. | |
| 52 | recipients | 61;0 | MULTIPLE | 776.1061 | See documentation for the MAIL GROUPS field. | |
| 53 | remotes | 62;0 | MULTIPLE | 776.1062 | See documentation for the MAIL GROUPS field. |