Branching script engine

• US 20030198934A1
• Filed: 03/29/2002
• Published: 10/23/2003
• Est. Priority Date: 03/29/2002
• Status: Abandoned Application

• Current Assignee: McKesson Information Solutions LLC (McKesson Corp.)
• Original Assignee: McKesson Information Solutions LLC (McKesson Corp.)
• Inventors: Sendowski, Nachi, Balakrishnan, Roopa, Dorner, Mark, Fernandes, Lovet Xavier
• Application Number:
  US10/112,346
• Publication Number:
  US 20030198934A1
• Time in Patent Office: Days
• US Class Current: 434/350
• CPC Class Codes: G09B 7/02 of the type wherein the student is expected to construct an answer to the question which is presented or wherein the machine gives an answer to the question presented by a student

Abstract

A system and method for providing a question-answer branching session over a stateless network. The invention provides a framework of reusable software objects implementing the creation and execution of any question-answer branching scripts. In the framework, scripts are used for the collection of structured information, surveys, interviews, evaluations, and expert diagnosis from application users. The components are data-driven by script definitions stored in a database. All persisted values, script progress path, and script results are kept in a predefined XML data structure. User interface and reported results are generated from the persisted data and sent to the client software for displaying via extensible style sheet transformation. Script questions are proceeded according to the values collected from previous answers. Script progress can be paused and resumed. Script answers can update token values and contains an additional text field. Script tokens can be used in questions and end of script processing. Questions with multiple answers cause recursive branching or stacking.

Claims

1. A system for providing a question-answer branching session over a stateless network, said system comprising:

a Web server;

a web content medium coupled to said Web server;

a database coupled to said Web content;

a branch script object coupled to said Web content, and a plurality of Web clients;

wherein said Web server and said Web clients communicate over the Internet.

2. The systems of claim 1, wherein said database comprises:

a first table for storing information about how a script path is constructed and what features said script supports;

a second table for storing information about questions;

a third table for storing information about answers;

a fourth table for storing information about sections; and

a fifth table for saving a current script path when said script path is paused or completed.

3. The system of claim 2, wherein said first table comprises:

a first column for an identity of said first table;

a second column for a server timestamp value for concurrency;

a third column for a name of an object that handles special custom treatment for said script;

a fourth column for a name of said script;

a fifth column for a first XSL file that is used to transform the current script path into an HTML page;

a sixth column for a bit value to indicate that said script has sections;

a seventh column for a flag to indicate that said script can be paused;

an eighth column for a flag to indicate that said script displays a progress button;

a ninth column for a page that handles submissions of said script when it is executed;

a tenth column for an image file that is used while said script is being executed; and

an eleventh column for a name of a second XSL file that is used to display the progress.

4. The system of claim 2, wherein said second table comprises:

a first column for an identity of said second table;

a second column for a server timestamp value for concurrency;

a third column for a foreign key to said fourth table that indicates the section to which a question belongs;

a fourth column for a flag that indicates that a question text and a generated text need to be parsed for token names and replaced with token values;

a fifth column for a text that needs to be displayed while said question is being displayed;

a sixth column for a display text that is used when an end result is generated from execution of said script;

a seventh column for an answer type that is expected for said question;

an eighth column for a flag to indicate that said question is a required question;

a ninth column for a text that is used for displaying any help information on said question;

a tenth column for a foreign key to indicate a default question when no answer is given for said question;

an eleventh column for a name of said question used internally within said script; and

a twelfth column for a foreign key to said question to be displayed as a next question at the end of branch.

5. The system of claim 2, wherein said third table comprises:

a first column for an identity of said third table;

a second column for a server timestamp value for concurrency;

a third column for a name of a label which is displayed when said answer is displayed;

a fourth column for a foreign key to a question to which said answer belongs;

a fifth column for a display text that is used when said answer is chosen;

a sixth column for a text that is to be added as a prefix to said display text;

a seventh column for a text that is to be added as a suffix to said display text;

an eighth column for a name of a token that said answer generates;

a ninth column for a foreign key to a next question that is to be displayed when said answer is provided;

a tenth column for a flag to indicate that said answer that is displayed is to be an answer that is entered on an HTML page; and

an eleventh column for a flag to indicate that a text box next to said answer needs to be displayed.

6. The system of claim 2, wherein said fourth table comprises:

a first column for an identity of said fourth table;

a second column for a server timestamp value for concurrency;

a third column for a foreign key of said script to which a section belongs;

a fourth column for a name of said section;

a fifth column for an order of said section; and

a six column for a name of an image file that is to be used when a question to which said section belongs is being displayed.

7. The system of claim 1, wherein said branch script object processes an XML structure, wherein said XML structure comprises a script as a root element, and wherein said root element comprises:

a first attribute that defines a first key in said database for said script;

a second attribute that defines a second key in said database for said script when it is saved;

a third attribute defines a key of a first question that is displayed when said script is executed;

a fourth attribute defines a name of said first question that is displayed when said script is executed;

a fifth attribute that defines a name of an XSL file that is used to display the content of said script;

a sixth attribute that defines a name of a server that deals with any special handling for said script;

a seventh attribute that defines a name of said branch script object;

an eighth attribute that defines the URL of an image that needs to be displayed while said script is being executed;

a ninth attribute that defines the URL to which a form is submitted;

a tenth attribute that defines a flag that indicates that said script can be paused;

an eleventh attribute that defines a flag that indicates that said script is set to show progress button;

a twelfth attribute that defines a flag that indicates that the end of said script is reached;

a thirteenth attribute that defines a flag that indicates that the beginning of said script is reached by moving previous on said script;

a first node that indicates a place holder for section details for different sections in said script;

a second node that indicates a place holder for holding different tokens elements in XML;

a third node that indicates a third holder for each answer that is placed on a stack;

a fourth node that indicates a place holder for each question that has been answered; and

a fifth node that indicates a place holder for a current question that is to be displayed.

8. The system of claim 7, wherein said first node comprises:

a first attribute that defines a key of said section;

a second attribute that defines a name as it exists in said database for said section;

a third attribute that defines an order as it exists in said database for said section; and

a fourth attribute that defines an image value for said section as it exists in said database.

9. The system of claim 7, wherein said second node comprises:

a plurality of child nodes, wherein each said child node indicates a place holder for each token value under said second node.

10. The system of claim 9, wherein said child node comprises:

a first attribute that defines a key of a question that has generated a token;

a second attribute that defines a key of an answer to said question that has generated said token;

a third attribute that defines a name of said token; and

a fourth attribute that defines a value that is entered in an answer field for said question.

11. The system of claim 7, wherein said third node comprises:

a plurality of child nodes, wherein each said child node indicates a place holder for each answer that is placed into said stack.

12. The system of claim 11, wherein said child node comprises:

a first attribute that defines a key of said current question;

a second attribute that defines a key of a next question that is to be displayed for said answer; and

a third attribute that defines a name of said next question that is to be displayed for said answer.

13. The system of claim 7, wherein said fourth node comprises:

a plurality of child notes, wherein each said child node indicates a place holder for each answer that is received from a user for said question;

a first attribute that defines a key of said question that the user has answered;

a second attribute that defines a name of said question as it exists in said database;

a third attribute that defines a text that is to be displayed when said question is being displayed in a progress report;

a fourth attribute that defines a key of a previous question that the user answered before answering said question;

a fifth attribute that defines a flag that indicates that said question was displayed as a result of an answer being popped from said stack; and

a sixth attribute that defines a key of a question that has generated an entry for said question in said stack.

14. The system of claim 13, wherein said child node comprises:

a first attribute that defines a key of a response made by the user; and

a second attribute that defines a value that is to be displayed when the progress for said script is displayed.

15. The system of claim 7, wherein said fifth node comprises:

a plurality of child nodes, wherein each said child node indicates a place holder for each answer that is received from the user for said question;

a first attribute that defines a key of said current question that the user needs to answer;

a second attribute that defines a name of said current question as it exists in said database;

a third attribute that defines a key of a previous question that the user answered prior to answering said current question;

a fourth attribute that defines a key of a section to which said current question belongs;

a fifth attribute that defines a question text that is displayed when the user is prompted with said current question;

a sixth attribute that defines a text that is displayed when the progress is displayed to the user;

a seventh attribute that defines an answer type for said current question;

an eighth attribute that defines a help text for said current question;

a ninth attribute that defines a flag that indicates that said current question is a required question in said database;

a tenth attribute that defines a flag that indicates that said current question was displayed as a result of an answer that is being popped from said stack;

an eleventh attribute that defines a key of a question that has generated an entry for said current question in said stack;

a twelfth attribute that defines a key of a question that is to be a default next question when no answer is provided;

a thirteenth attribute that defines a next root at which the questioning continues once the end of branch is reached; and

a fourteenth attribute for displaying errors.

16. The system of claim 15, wherein said child node comprises:

a first attribute that defines a key of an answer to said current question, wherein said key is stored in said database;

a second attribute that defines a label that is to be displayed for said current answer;

a third attribute that defines a display value for said current answer that is to be displayed;

a fourth attribute that defines a prefix that is to be added to the user response;

a fifth attribute that defines a suffix that is to be appended to the user response;

a sixth attribute that defines a name of a token that is to be generated when the user enters a value as a response;

a seventh attribute that defines a key of a next question that is to be displayed when the user enters a value as a response;

an eighth attribute that defines a flag for displaying said answer as is; and

a ninth attribute that defines a flag for showing a text box for said answer

17. The system of claim 1, wherein said branch script object comprises:

a first property which is used when said branch script object queries said database;

a second property which is a value of said server that is responsible for special handling, if any;

a third property which is an object that is created using said second property;

a fourth property which is a key of said script that is to be executed;

a fifth property which is a document object model that holds said XML;

a sixth property which is a name of a first XSL file that is used to transform XML into HTML;

a seventh property which is a name of a second XSL file that is used to display the progress;

an eighth property which is a name of an image file that is used to display a logo for said script;

a ninth property which is the URL of a page that processes the submission of a script form;

a tenth property which is a key of a question that exists as said fifth node in XML;

an eleventh property which is a key of a previous question that was displayed before said current question;

a twelfth property which returns true if the end of script is reached;

a thirteenth property which returns true if the beginning of script is reached;

a fourteenth property which becomes said fourteenth attribute of said fifth node; and

a fifteenth property which is a login key of the user who attempts to save the progress or resume a paused script.

18. The system of claim 1, wherein said branch script object comprises:

a first method, which is called first for executing said script;

a second method, which is called for setting a stage to display a starting question;

a third method, which is called to rebuild said XML structure using a variable in a form collection of a request object;

a fourth method, which is called to convert said fifth node to an equivalent fourth node using XML;

a fifth method, which is called to take a previous question from said fifth node using XML;

a sixth method, which is called to display said current question;

a seventh method, which is called to display the progress;

an eighth method, which is called when the end of script is reached;

a ninth method, which is called when said script is paused;

a tenth method, which is called when said paused script is to be resumed; and

an eleventh method, which is called for setting a stage to display said paused script from the very point where a session was interrupted.

19. The system of claim 18, wherein, if a script key is passed in, said first method copies said script key into a member variable;

wherein if said script key is not passed in, said method assumes that a value is set using a property procedure; and

wherein said method queries said database for details of said script and creates a base XML structure.

20. The system of claim 18, wherein said second method goes to said database using a starting question key for said script and then creates said fifth node using all values that it retrieved.

21. The system of claim 18, wherein said third method checks if said question is a required question and returns a false if no answer to said required question is provided.

22. The system of claim 18, wherein said fourth method creates a child node under said fourth node using said request object;

wherein before the creation of said child node of said fourth node, said request object checks to make sure that a valid answer exists; and

wherein if no valid answer exists, said object uses a key that is defined by said twelfth attribute of said fifth node to determine a next question.

23. The system of claim 18, wherein if a previous question is not found, said fifth method takes steps of:

getting rid of said fifth node;

setting said thirteenth attribute of said root element; and

returning an indicator; and

wherein if a previous question is found, said fifth method takes steps of;

when said tenth attribute of said fifth node are set,

reinstating said stack for said question using said eleventh attribute of said fifth node;

getting rid of said fifth node;

locating said fourth node;

getting rid of all child nodes under said second node and said third node that were created as a result of said answers to said fourth node;

querying said database using a previous question key;

creating said fifth node; and

copying said previous question key value from said fourth node into said fifth node; and

when said fifth attribute and sixth attribute of said fourth node are set,

copying said fifth attribute and sixth attribute of said fourth node into said fifth node;

getting rid of said fourth node; and

returning said previous question.

24. The system of claim 18, wherein said sixth method, using XML, checks whether said fifth node exists;

wherein if said fifth node exists, said sixth method takes the steps of;

transforming XML using said sixth property;

adding form tags to said transformed XML;

calling a form script;

setting an action to said ninth property value;

hiding said XML in an input item; and

returning HTML.

25. The system of claim 18, wherein said seventh method takes the steps of:

transforming XML using said seventh property;

adding form tags to said transformed XML;

calling a form script;

setting an action to said ninth property value;

hiding said XML in an input item; and

returning HTML.

26. The system of claim 18, wherein said eighth method takes the steps of:

setting said fifteenth property value;

checking if a saved key value exists in said XML;

performing an update using said saved key value if said saved key value is found;

inserting said XML in said fifth table if said saved key value is not found; and

setting a completion.

27. The system of claim 18, wherein said ninth method takes the steps of:

setting said fifteenth property value;

checking if a saved key value exists in said XML;

performing an update using said saved key value if said saved key value is found;

inserting said XML in said fifth table if said saved key value is not found; and

setting a completion.

28. The system of claim 18, wherein said tenth method first authenticates the user and then rebuilds said XML structure by reading said database.

29. The system of claim 18, wherein said eleventh method ensures that said

fifth node exists so that the user can proceed with resuming said paused script.

30. The system of claim 1, wherein said branch script object can be customized by

implementing a method that is called for handling special issues, if any, the first thing when said second method is executed.

31. The system of claim 1, wherein said branch script object can be customized by implementing a method that is called for handling special issues, if any, just before the execution of said second method is completed.

32. The system of claim 1, wherein said branch script object can be customized by implementing a method that is called for handling special issues, if any, the first thing when said fourth method is executed.

33. The system of claim 1, wherein said branch script object can be customized by implementing a method that is called for handling special issues, if any, just before the execution of said fourth method is completed.

34. The system of claim 1, wherein said branch script object can be customized by implementing a method that is called for handling special issues, if any, the first thing when said fifth method is executed.

35. The system of claim 1, wherein said branch script object can be customized by implementing a method that is called for handling special issues, if any, just before the execution of said fifth method is completed.

36. The system of claim 1, wherein said branch script object can be customized by implementing a method that is called for handling special issues, if any, the first thing when said eleventh method is executed.

37. The system of claim 1, wherein said branch script object can be customized by implementing a method that is called for handling special issues, if any, just before the execution of said eleventh method is completed.

38. The system of claim 1, wherein said branch script object can be customized by implementing a method that is called for handling special issues, if any, the first thing when said ninth method is executed.

39. The system of claim 1, wherein said branch script object can be customized by implementing a method that is called for handling special issues, if any, the first thing when said eighth method is executed.

40. The system of claim 1, wherein said branch script object can be customized by implementing a method that is called for handling special issues, if any, the first thing when said sixth method is executed.

41. The system of claim 1, wherein said branch script object can be customized by implementing a method that is called for handling special issues, if any, the first thing when said seventh method is executed.

42. A process for providing a question-answer branching session over a stateless network, said process comprising the steps of:

submitting, by a user, a first answer to a question;

receiving, by a Web server, said first answer;

encoding, by said Web server, a current script path;

calling, by said Web server, said branch script object;

if this is the start of a script path, then

querying, by said branch script object, said database for details of said script;

creating, by said branch object, an XML structure; and

creating, by said branch object, said fifth node using a starting question for said script;

if this is not the start of said script path, then

decoding, by said Web server, said encoded current script path;

rebuilding, by said Web server, said XML structure; and

checking whether an answer is provided;

wherein said answer may be a single answer, a text answer, or a multiple answer.

43. The process of claim 42 and further comprising the steps of:

if said first answer is a text answer, then

adding, by said branch script object, said text answer as a named token to said current script path, wherein said text answer is configured to be a token so that said token can be used in subsequent questions and answers;

if said first answer is a multiple answer, then

finding, by said branch script object, a next question by using said first answer; and

keeping the remaining answers to said stack of said branch script object,

wherein said script path for the remaining answers may be branched when said current script path for a current answer is completed.

44. The process of claim 43 and further comprising the steps of:

adding, by said branch script object, said first answer to the current script path along with said current question; and

querying, by said branch script object, said database for said next question based on said current question and said answer to said current question on said script path;

wherein if there are further questions, said process goes on a first sub-process, and

wherein if there are no further questions, said process goes on a second sub-process.

45. The process of claim 44, wherein said first sub-process comprises the steps of:

adding, by said branch script object, said next question to said current script path, wherein said next question becomes a current question;

formatting, by said branch script object, said question to an HTML page;

sending, by said branch script object, said question to the user'"'"'s browser along with said current script path;

encoding, by said branch script object, said current script path; and

including said current script path into a responding HTML page;

wherein said current script path contains said questions presented to the user including said current question, the user'"'"'s answers to said questions, said remaining answers to be branched, and said tokens that have been collected; and

wherein said responding HTML page contains questions, answers, help text, generated text, and navigational elements.

46. The process of claim 44, wherein said second sub-process comprises the steps of:

saving, by said branch script object, said current script path to said database;

if said current script path has been already saved to said database for a pause request, then

updating said saved current script path;

if said current script path has not been saved yet, then

inserting, by said branch script path, said current script path into said fifth table of said database;

wherein said questions and answers that are contained in said current script path may be retrieved for further processing; and

formatting, by said branch script object, an HTML page that notifies the user the completion of said session.

47. A method for providing a question-answer branching session over a stateless network, said method comprising the steps of:

submitting, by a user, a first answer to a question;

receiving, by a Web server, said first answer;

encoding, by said Web server, a current script path;

calling, by said Web server, said branch script object;

if this is the start of a script path, then

querying, by said branch script object, said database for details of said script;

creating, by said branch object, an XML structure; and

creating, by said branch object, said fifth node using a starting question for said current script;

if this is not the start of said script path, then

decoding, by said Web server, said encoded current script path;

rebuilding, by said Web server, said XML structure; and

checking whether an answer is provided;

wherein said answer may be a single answer, a text answer, or a multiple answer.

48. The method of claim 47 and further comprising the steps of:

if said first answer is a text answer, then

adding, by said branch script object, said text answer as a named token to said current script path, wherein said text answer is configured to be a token so that said token can be used in subsequent questions and answers;

if said first answer is a multiple answer, then

finding, by said branch script object, a next question by using said first answer; and

keeping the remaining answers to said stack of said branch script object,

wherein said script path for the remaining answers may be branched when said current script path for said current answer is completed.

49. The method of claim 48 and further comprising the steps of:

adding, by said branch script object, said first answer to said current script path along with said current question; and

querying, by said branch script object, said database for said next question based on said current question and said answer to said current question on said script path;

wherein if there are further questions, then a step of next question is followed, and

wherein if there are no further questions, then a step of completion is followed.

50. The method of claim 49, wherein said step of next question comprises the sub-steps of:

adding, by said branch script object, said next question to said current script path, wherein said next question becomes a current question;

formatting, by said branch script object, said question to an HTML page;

sending, by said branch script object, said question to the user'"'"'s browser along with said current script path;

encoding, by said branch script object, said current script path; and

including said current script path into a responding HTML page;

wherein said current script path contains said questions presented to the user including said current question, the user'"'"'s answers to said questions, said remaining answers to be branched, and said tokens that have been collected; and

wherein said responding HTML page contains questions, answers, help text, generated text, and navigational elements.

51. The method of claim 50, wherein said step of completion comprises the sub-steps of:

saving, by said branch script object, said current script path to said database;

if said current script path has been already saved to said database for a pause request, then

updating said saved current script path;

if said current script path has not been saved yet, then

inserting, by said branch script path, said current script path into said fifth table of said database;

wherein said questions and answers that are contained in said current script path may be retrieved for further processing; and

formatting, by said branch script object, an HTML page that notifies the user the completion of said session.