The successful development of our prototype will demonstrate that it
is possible to develop software in which events tied to data entry in a
seperate application can be defined and detected independently of the other
application. We will then be ready to continue with full development of
the application, concentrating on the steps listed below.
Generalize what we had done so that it would work with all types of
protocols. Complete the development of the engine.
Deal with network problems which will be encountered when Engine is
run independently of, but concurrently with principal data entry package.
When the engine sees that in scanning data sees that a Protocol Triggering
Event has occurred, it will need to be able to determine which work station
was the source of that data in case it needs to take any actions that require
user notification.
Begin adding features to the Rules Enforcer so that it would have more
functionality, printing forms, sending letters, etc.. when used in a situation
where it accesses third party data, but not in a situation where the program
calls it.
Convert our own package ck_medical to work with protocol engine.
Contact vendors of general medical billing, and patient record applications.
Show them how the engine works, see if they would be interested in using
it as a dynamic link library, and work closely with them, in setting up
the data definitions, and in making the calls between packages. If they
are not interested in this approach, ask if they would provide us with
detailed data definitions, so that we could set up the engine to work on
its own as an add on to their package.
Give talks at conferences interested in protocol development, about
what we have found out in developing the engine, the obstacles we have
had to overcome, and what we have come up with.
Begin marketing efforts, and try to locate additional funding sources
to augment Phase II development funds.