Abstract: A system maps components of prescribed treatments to multiple appointments of a patient, tracks patient progress through a course of treatment by recording results of treatment in a clinical information system and replaces multiple manual processes to improve concurrent monitoring of a treatment plan versus actual results. A system schedules multiple appointments for a course of patient treatment. The system uses an input processor for receiving data identifying, a treatment type, a frequency of application of the treatment, a start date of the treatment and a number of applications of the treatment. An appointment processor determines validity of the received data and uses the validated received data to generate data representing a schedule of multiple appointments for receiving the treatment. An interface processor provides data representing the schedule of multiple appointments to a destination system.

Abstract: A system maps components of prescribed treatments to multiple appointments of a patient, tracks patient progress through a course of treatment by recording results of treatment in a clinical information system and replaces multiple manual processes to improve concurrent monitoring of a treatment plan versus actual results. A system schedules multiple appointments for a course of patient treatment. The system uses an input processor for receiving data identifying, a treatment type, a frequency of application of the treatment, a start date of the treatment and a number of applications of the treatment. An appointment processor determines validity of the received data and uses the validated received data to generate data representing a schedule of multiple appointments for receiving the treatment. An interface processor provides data representing the schedule of multiple appointments to a destination system.

Abstract: A system employed by at least one web browser compatible executable application for initiating an action by a second executable application, includes the following. A URL processor which generates, in response to a user command, a URL link in a predetermined particular format which includes context information and an action request identifier. The URL link represents an action to be performed by the second executable application. A URL link interpreter, coupled to said URL processor via a first mode of communication, which identifies said particular format URL link, extracts the context information and action request identifier from the particular format URL link, and initiates termination of the first mode of communication. A communication processor, coupled to said URL link interpreter, which initiates communication of said extracted context information and action request identifier to the second executable application by a second mode of communication different from said first mode of communication.