We would like to design and develop a prototype protocol engine, as a model for how software protocols should be designed, set up and implemented. In our model a protocol engine would be made up of four seperate components: a protocol definer, an event monitor, a message handler, and a rule enforcer. We would like to prototype this application in Windows with the ultimate goal of developing it as a Dynamic Link Library, so that any of its modules could be accessed by any other Windows application. Our intention is to use a format independent interface to access data, so that so that the library could work with data from other packages.

The objectives of the first phase of the project are as follows:

1. Complete a thorough compilation of trends and plans in Protocol Management, and Medical Data Standardization.
2. Prioritize and define protocol types which it will be most necessary to implement in a managed care environment.
3. Detailed design of Protocol Engine specifications, including operating requirements, data definitions, and trackable event descriptions.
4. Development of a Windows prototype which will work either as an independent or as an add on product, and will demonstrate definition of the highest priority protocol types.
5. Develop specifications for access by an external software package, and a demonstration of how the process works.
6. Establish feasability of Phase II Work to develop a fully functional Windows DLL to handle protocol management and setup