Method and system to provide online application forms

• US 20070250783A1
• Filed: 04/24/2006
• Published: 10/25/2007
• Est. Priority Date: 04/24/2006
• Status: Abandoned Application

• Current Assignee: eHealthInsurance Services, Inc. (eHealth, Inc.)
• Original Assignee: eHealthInsurance Services, Inc. (eHealth, Inc.)
• Inventors: Wu, Jiang, Bass, Michael, Reicheneder, Stefan, Wang, Sheldon, Ku, George
• Application Number:
  US11/410,421
• Publication Number:
  US 20070250783A1
• Time in Patent Office: Days
• US Class Current: 715/762
• CPC Class Codes: G06F 40/174 Form filling; Merging

Abstract

A system and method are provided to build an application form (e.g., an online application form). The method may comprise providing a graphical user interface (GUI) to a user, the GUI including page layout zone and page and a page type zone include a plurality of reference page types. User placement of selected reference page types in the layout zone is monitored and the selected reference page types are automatically interconnecting based on their relative placement in the layout zone. Interconnection data may define a sequence in which the selected pages are to be presented in the application form. Page data may be created by various wizards or by a page editor. Rules that are associated with each page may be defined by a rules editor.

Claims

1. A method of building an application form, the method comprising:

providing a graphical user interface (GUI) to a user, the GUI including page layout zone and a page type zone including a plurality of reference page types;

monitoring user placement of selected reference page types in the layout zone, each reference page including page data;

automatically interconnecting the selected reference page types based on their relative placement in the layout zone;

generating page flow data in response to the automatically interconnecting the selected reference page types;

identifying rules data associated with each selected reference page type, wherein the rules data that defines required data to be captured at runtime for the selected reference page; and

storing the page flow data, the page data and the rules data in a storage media for subsequent conversion to web-based markup language at runtime.

2. The method of claim 1, wherein the page flow data, the page data and the rules data is Extensible Markup Language (XML) data which is for subsequent conversion to Hyper Text Transfer Protocol Language (HTML) at runtime.

3. The method of claim 1, wherein the storing the page flow data, rules data and the page data in the storage media provides an abstraction layer between the application form and an HTML page generated at runtime.

4. The method of claim 1, which monitors dragging and dropping a selected reference page into the layout zone by the user.

5. The method of claim 1, which comprises associating the page flow data, the page data and the rule data with a data model comprising core-data and other-data, the core-data identifying data that is common to a plurality of application forms and the other-data being specific to an associated application form.

6. The method of claim 1, in which the page flow data defines one or more follow-up reference pages which are specific to an application data requested on an associated page.

7. The method of claim 6, wherein the rules data is retrieved from a rules library which includes sets of rules each associated with a selected reference page.

8. The method of claim 1, in which the rules data includes page rules to validate data captured from an applicant at runtime.

9. The method of claim 1, in which the rules data includes business rules associated with the health insurance industry.

10. The method of claim 1, wherein the reference page types are selected from the group including a page to obtain applicant information, a page to obtain health coverage information, a page to obtain health history information, and health insurance rider information.

11. The method of claim 1, wherein the reference page type is a page to obtain applicant information, the applicant information selected from the group including name, birth date, age, height, weight, gender, marital status, relation, college-student, tobacco use, and occupation.

12. The method of claim 1, wherein the reference page type is a page to obtain address information, contact telephone number, and financial instrument details.

13. The method of claim 1, wherein the reference page type is a page to obtain health history information, the health history information relating previous health history of members of a health insurance plan.

14. The method of claim 1, which comprises invoking a wizard to create prequalification pages before building application pages of the application form.

15. The method of claim 1, which comprises invoking a wizard to create an electronic signature page after building application pages of the application form.

16. The method of claim 1, which comprises:

monitoring user selection of a page editor and, upon selection thereof, providing editing functionality to allow a user to define properties of the selected page;

monitoring user selection of a rules editor and, upon selection thereof, providing editing functionality to allow a user to define rules associated with the selected page; and

monitoring user selection of a page flow editor and, upon selection thereof, providing editing functionality to allow a user to alter a relative position of the selected page in the page flow in the page layout zone.

17. The method of claim 1, wherein the application form is a health insurance plan application form selected from the group consisting of an Individual and Family insurance plan, a short-term insurance plan, a student health insurance plan, a health care savings plan, and a small business group plan.

18. A machine-readable medium embodying instructions which, when executed by a machine, cause the machine to:

provide a graphical user interface (GUI) to a user, the GUI including page layout zone and a page type zone including a plurality of reference page types;

monitor user placement of selected reference page types in the layout zone, each reference page including page data;

automatically interconnect the selected reference page types based on their relative placement in the layout zone;

generate page flow data in response to the automatically interconnecting the selected reference page types;

identify rules data associated with each selected reference page type, wherein the rule data that defines required data to be captured at runtime for the selected reference page;

using page building wizards or a page editor to create page data; and

store the page data, the page data and the rule data in a storage media for subsequent conversion to web-based markup language at runtime.

19. A system to build an application form, the system comprising:

a graphical interface module (GUI) that generates a graphical user interface (GUI) for a user, the GUI including page layout zone and page type zone include a plurality of reference page types;

a monitoring module to monitor user placement of selected reference page types in the layout zone, each reference page including page data;

an interconnection module to automatically interconnect the selected reference page types based on their relative placement in the layout zone;

a rules module identify rules data associated with each selected reference page type, wherein the rules data that defines required data to be captured at runtime for the selected reference page; and

a storage medium to store the page data, page flow data and the rules data for subsequent conversion to web-based markup language at runtime.

20. The system of claim 19, wherein the page flow data, the page data and the rules data is Extensible Markup Language (XML) which is for subsequent conversion to Hyper Text Transfer Protocol Language (HTML) at runtime.

21. The system of claim 19, wherein the storing the page flow data, and the page data and the rules data in the database provides an abstraction layer between the online application form and an HTML page generated from the page flow data and the page data at runtime.

22. The system of claim 19, in which the monitoring module monitors dragging and dropping a selected reference page into the layout zone by the user.

23. The system of claim 19, wherein the page data, the page data and the rule data in a data model is associated with core-data and other-data, the core-data identifying data that is common to a plurality of application forms and the other-data being specific to an associated application form.

24. A system to build an application form, the system including:

means for providing a graphical user interface (GUI) to a user, the GUI including page layout zone and a page type zone including a plurality of reference page types;

means for monitoring user placement of selected reference page types in the layout zone, each reference page including page data;

means for automatically interconnecting the selected reference page types based on their relative placement in the layout zone;

means for generating page flow data in response to the automatically interconnecting the selected reference page types;

means for identifying rules data associated with each selected reference page type, wherein the rule data that defines required data to be captured at runtime for the selected reference page; and

means for storing the page data, the page data and the rule data in a storage media for subsequent conversion to web-based markup language at runtime.