Abstract: Interactive methods and systems for directing, integrating, documenting, and tracking steps taken by medical providers during the process of care for a patient's given condition. Doctors' actions are directed by a prescriptive protocol—a checklist of discrete steps designed for efficient or optimal care of an individual patient's specific condition. The step-by-step checklist is abstracted from decision tree guidelines for the optimal work up and treatment for the condition using probability-based methodology. The care protocols can be derived from widely available and non-proprietary guidelines and decision trees based on public medical research literature. In one embodiment, the invention can be employed by a primary care clinician at the point of referral into the specialist sector, and at the specialist level when proposing a risky or expensive or otherwise problematic medical or surgical diagnostic or treatment intervention.

Abstract: A user-driven, service-oriented application model, in which conformant applications implement and process instances of two program object types. Components in conformant applications consist of objects having built-in behaviors that are common across different applications. Each application object is either an instance of a predefined active object type, or an instance of a predefined reactive object type. Active objects are associated with individual users of their application, are allowed to activate services, and encapsulate all their inputs and outputs within a bounded space. Reactive objects are instantiated or processed by services, and, in one embodiment, each one is owned by an individual active object at any given point in time. During operation of the disclosed system, services activated by active objects route reactive objects to active objects. An active object assumes ownership of a received reactive object upon receipt.

Abstract: A system and method for providing composite applications for software-based systems that uses a built-in application model having at least one general purpose object type, and providing dynamic late-binding of object implementations through an object typing system decoupled from pre-run time program code, using persistently stored objects. The application model may require that program objects in a conformant application be instances of a predefined active object type, or optionally instances of a predefined reactive object type. The application model enables integration of applications into composite applications, and further integration of composite applications into subsequently defined systems. The run-time object typing system for persistently stored objects is independent of the class typing system that is defined at compile-time or link-time, and enables convenient and practical modifications during development, deployment and maintenance of composite applications.

Abstract: A system and method for binding software objects to the program code that implements them in accordance with run-time object typing that is independent of the program code typing system. Persistently-stored, run-time object instances (“persistent objects”) are maintained by a software-based system across transactions, user sessions, and application executions, and are identified by unique, typed names. Dynamic binding is provided through software constructs that are associated with corresponding persistent objects, and referred to as “Associators”. Associators provide links between object types and the program code that implements them.