A Protocol is described as an entry in the PROTOCOL file and can be viewed as a module of code. Each module of code may optionally contain other modules of code. Other fields in each file entry determine conditions under which the module should be executed, what should be presented to the user, etc. (3RCE)
Protocol usage can be listed under three categories: (3RCF)
- A Protocol is used by the Order Entry / Results Reporting (OE/RR) package to support the ordering of medical tests and other activities. The Kernel includes several protocol-type options for enhanced menu displays within the OE/RR package. The processing of protocols in OE/RR is made possible by the Kernel Unwinder (XQOR*). For more information, please refer to the Kernel Unwinder: documentation at: http://www.va.gov/vdl/Infrastructure.asp?appID=13 (3RCG)
- Protocols of type ‘event driver’ and ‘subscriber’ are used in the HL7 messaging context. Please see the HL7 Data (if available) in the ‘Pharmacy Application Linkages and Encapsulation Research’ document for more details. (3RCH)
- The List Manager provides a generic method of presenting lists of items. ‘Menu’ type protocols are generally used by the List Manager utility. Please see the ‘List Template’ section to get more information on how ‘protocols’ are used in List Templates. OE/RR uses List Manager. (3RCI)