Untitled record

PRIORITY CLAIM

In accordance with 37 C.F.R. 1.76, a claim of priority is included in an Application Data Sheet filed concurrently herewith. Accordingly, the present invention claims priority under 35 U.S.C. §'119(e), 120, 121, and/or 365(c) to U.S. Provisional Patent Application No. 61/619,049, entitled “SOCIAL SECURITY CLAIM AND PROGRESSION MANAGEMENT”, filed on Apr. 2, 2012. The contents of which the above referenced application is incorporated herein by reference in its entirety.

Government agencies have developed rules and regulations for applying for and receiving government benefits. These agencies also have developed rules and procedures for adjudication of disability requests. In particular, the Social Security Administration receives probably the most requests for retirement and disability benefits of all of the government agencies which pay out benefits. Medicare provides health insurance under Title XVIII of the Social Security act. Therefore, the Social Security Administration must process Medicare claims in addition to retirement claims. There is also the Social Security Disability Insurance program which handles disability claims and benefits for those individuals who qualify. Again, there are rules and procedures for the processing of these disability claims. There are businesses, in particular law firms that file for Social Security benefits on behalf of their clients. Currently, this is a very tedious, difficult, and time consuming process. This process becomes even more difficult when the conditions under which the initial benefit claim was made changes. For example, when a claim for a medical benefit has initially been made and there is a change in the medical condition of the claimant, different forms need to be completed and specific procedures need to be followed. Also, if a claim or claims for benefits have been denied, there are specific procedures that need to be followed to properly appeal the denial decision of the Social Security Administration or other government agencies.

Thus, what is needed in the art is a process for filing benefit claims with the Social Security Administration, or other government agencies, which can follow the proper claim procedures to assure the claimant receives the benefits that he/she is entitled to. Also a process that will enable filing of updated and/or changes in status of benefits. Further, a process that will assure a proper and correct filing of an appeal for denial of certain benefits.

FIELD OF THE INVENTION

The present invention relates to a system and method for submitting and processing benefit claims, such as Social Security claims. The present invention permits the user to make the initial application for benefits, respond to denials of benefits, if necessary, and appeal negative decisions.

BACKGROUND OF THE INVENTION

Description of the Prior Art

U.S. Published Patent Application No. 2011/0077981 discloses a method and system for automated processing of medical data for insurance and disability determinations.

U.S. Published Patent Application No. 2003/0158750 discloses a computer implemented process and system for processing compensation requests.

U.S. Published Patent Application No. 2008/0059249 discloses a system and process for storing healthcare information, records, or history of an individual or healthcare provider.

U.S. Published Patent Application No. 2010/0145734 discloses a computer based automated loss verification system for evaluating the validity of claims filed under an insurance policy or debt protection contract.

U.S. Published Patent Application No. 2010/0185466 discloses a method for tracking health related spending for validation of disability benefits claims. The method includes tracking, by the Medicare Secondary Payer statute-compliance company, healthcare related expenditures by the recipient.

U.S. Published Patent Application No. 2003/0167220 discloses a computer aided method of computing coverage benefit costs for a retirement plan having respective accounts for individuals.

U.S. Published Patent Application No. 2002/0035488 discloses a system and method of administering, tracking, and managing claim processing.

U.S. Published Patent Application No. 2009/0222290 discloses a system for automated, predictive modeling of the outcome of benefits claims including a profile generator, an evaluation component, and a case management application.

U.S. Published Patent Application No. 2009/0192827 discloses a rules based system for information relating to health or retirement benefits. The information is stored in the form of statements or clauses relating to financial, medical, or personal characteristics relevant to certain statures or regulations.

U.S. Patent Application No. 2008/0010279 discloses a system and method of educational accountability reporting for Federal, State, and local initiatives such as the Federal No Child Left Behind (NCLB) program. The system also includes a detailed process for handling appeals and reconsiderations of disputed assessments or demographic data being utilized for the calculation of statistics.

U.S. Published Patent Application No. 2010/0318393 discloses a system and method for dispatching a workflow responsive request including a plurality of dispatch rules which may be defined based on a user's input.

U.S. Pat. No. 7,753,263 discloses a method and system for automatic case determination and assignment for a business transaction.

U.S. Published Patent Application No. 2003/0074277 discloses a method for processing an application from a user for a product using a first computer. The information is sent to a second computer for processing. The computers can be a client and a server respectively.

U.S. Pat. No. 7,600,252 discloses a system, method, and computer program for providing communication between different devices having similar or different characteristics and facilitating seamless operability between the devices.

U.S. Pat. No. 7,185,273 discloses a method for the completion of forms including receiving location information, retrieving user information, configuring the user information for merging with the form, and printing a form that contains at least some of the user information.

SUMMARY OF THE INVENTION

The present invention is a computer implemented method and system for gathering information from a user related to, filing for, and obtaining government benefits, such as Social Security benefits. The present invention also enables the user to track the benefit application approval process and reminders when certain data or responses are due. There is a feature which enables the user to modify the data submitted for the benefits when circumstances warrant. The system presents questions in a systematic method to reduce the time it takes to complete an intake. Based on answers provided, the intake wizards guides the user through appropriate questions to ask based on the previous answers provided. for example if the potential client is a veteran the intake will ask service related questions that can be evaluated for an SSA claim and/or VA claim. If an answer disqualifies the claimant from SSDI or SSI for a “technical” reason, the questionnaire is terminated so that the user can move on to the next intake quickly and efficiently. If an answer does not disqualify the claimant from the intake process, the intake moves onto the next sections of the questionnaire. The system assists the user in computing what stage in the process the claimant is currently at. For example, Needs to File an Application, Initial Application, Denied Initial Claim, Reconsideration, Denied Reconsideration, Hearing Filed, Ready to Schedule a Hearing, Hearing Scheduled, Awaiting Decision, Appeals Council, or Federal Claim (many claimants get confused and this is an important part of the application process). Questions are presented related to the claimant's medical history to determine if the user has a valid claim for benefits. The system may in certain instances medically approve the client for representation. When an intake is accepted, the intake wizard assigns the intake to a person responsible for getting the retainer signed, the intake system programmatically fills in SSA forms for the client to sign, emails the forms when appropriate, determines what SSA district office is assigned to the claimant, and then programmatically completes the three SSA Application forms when appropriate. There is also a decision appeal process feature.

Accordingly, it is an objective of the present invention to provide a computer implemented method and system for inputting data into a government benefits system.

It is a further objective of the present invention to provide an intake wizard which permits a user to automatically populate a form by input data related to obtaining government benefits, including medical conditions.

It is yet another objective of the present invention to provide an intake wizard which assists a user in responding to denial of government benefits.

It is a still further objective of the present invention to provide an import wizard which handles incoming mail, outgoing mail, workflow documents, medical records, document attachments, and collections.

It is a still further objective of the present invention to provide an application wizard which enables a user to correction complete an application form for government benefits.

It is a still further objective of the present invention to provide a computer implemented method and system which enables multiple individuals to file on behalf of multiple users for government benefits, maintain the records of these users and respond to different requests and/or information from a government agency regarding the application for the users' benefits requests.

Other objectives and advantages of this invention will become apparent from the following description taken in conjunction with any accompanying drawings wherein are set forth, by way of illustration and example, certain embodiments of this invention. Any drawings contained herein constitute a part of this specification and include exemplary embodiments of the present invention and illustrate various objects and features thereof.

BRIEF DESCRIPTION OF THE FIGURES

<figref idref="DRAWINGS">FIGS. 1A-1F</figref> is a benefit claim progression flow chart;

<figref idref="DRAWINGS">FIG. 2</figref> is a claim progression view;

<figref idref="DRAWINGS">FIG. 3</figref> is a screen shot of a claim progression view;

<figref idref="DRAWINGS">FIG. 4</figref> is a screen shot of a claim progression view;

<figref idref="DRAWINGS">FIG. 5</figref> is workflow view;

<figref idref="DRAWINGS">FIG. 6</figref> is a screen shot of a workflow view;

<figref idref="DRAWINGS">FIG. 7</figref> is a screen shot of a workflow view;

<figref idref="DRAWINGS">FIG. 8</figref> is a screen shot of a workflow view;

<figref idref="DRAWINGS">FIG. 9</figref> is a screen shot of a workflow view;

<figref idref="DRAWINGS">FIG. 10</figref> is a screen shot of a workflow view;

<figref idref="DRAWINGS">FIG. 11</figref> is a screen shot of a workflow view;

<figref idref="DRAWINGS">FIG. 12</figref> is a screen shot of a workflow view;

<figref idref="DRAWINGS">FIG. 13</figref> is a screen shot of a workflow view;

<figref idref="DRAWINGS">FIG. 14</figref> is a screen shot of a workflow view;

<figref idref="DRAWINGS">FIG. 15</figref> is a screen shot of an Intake Wizard;

<figref idref="DRAWINGS">FIG. 16</figref> is a screen shot of an Intake Wizard;

<figref idref="DRAWINGS">FIG. 17</figref> is a screen shot of an Intake Wizard;

<figref idref="DRAWINGS">FIG. 18</figref> is a screen shot of an Intake Wizard;

<figref idref="DRAWINGS">FIG. 19</figref> is a screen shot of an Intake Wizard;

<figref idref="DRAWINGS">FIG. 20</figref> is a screen shot of an Intake Wizard;

<figref idref="DRAWINGS">FIG. 21</figref> is a screen shot of an Intake Wizard;

<figref idref="DRAWINGS">FIG. 22</figref> is a screen shot of an Intake Wizard;

<figref idref="DRAWINGS">FIG. 23</figref> is a screen shot of an Intake Wizard;

<figref idref="DRAWINGS">FIG. 24</figref> is a screen shot of an Intake Wizard;

<figref idref="DRAWINGS">FIG. 25</figref> is a screen shot of an Intake Wizard;

<figref idref="DRAWINGS">FIG. 26</figref> is a screen shot of an Intake Wizard;

<figref idref="DRAWINGS">FIG. 27</figref> is a screen shot of an Intake Wizard;

<figref idref="DRAWINGS">FIG. 28</figref> is a screen shot to an Intake Wizard;

<figref idref="DRAWINGS">FIG. 29</figref> is a screen shot of an Intake Wizard;

<figref idref="DRAWINGS">FIG. 30</figref> is a screen shot of an Intake Wizard;

<figref idref="DRAWINGS">FIG. 31</figref> is a screen shot of an Intake Wizard;

<figref idref="DRAWINGS">FIG. 32</figref> is a screen shot of medical conditions on the Intake Wizard;

<figref idref="DRAWINGS">FIG. 33</figref> is a screen shot of medical conditions on the Intake Wizard;

<figref idref="DRAWINGS">FIGS. 34</figref><i>a</i>-<b>34</b><i>b </i>are charts explaining the termination reasons;

<figref idref="DRAWINGS">FIG. 35</figref> is screen shot of termination reasons;

<figref idref="DRAWINGS">FIG. 36</figref> is screen shot of termination reasons;

<figref idref="DRAWINGS">FIGS. 37</figref><i>a</i>-<b>37</b><i>b </i>are a screen shot of termination reasons;

<figref idref="DRAWINGS">FIGS. 38</figref><i>a</i>-<b>38</b><i>b </i>are a screen shot of termination reasons;

<figref idref="DRAWINGS">FIG. 39</figref> is a screen shot of an Import Wizard;

<figref idref="DRAWINGS">FIG. 40</figref> is a screen shot of an Import Wizard;

<figref idref="DRAWINGS">FIG. 41</figref> is a screen shot of an Import Wizard;

<figref idref="DRAWINGS">FIG. 42</figref> is a screen shot of an Import Wizard;

<figref idref="DRAWINGS">FIG. 43</figref> is a screen shot of an Import Wizard;

<figref idref="DRAWINGS">FIG. 44</figref> is a screen shot of an Import Wizard;

<figref idref="DRAWINGS">FIG. 45</figref> is a screen shot of an Import Wizard;

<figref idref="DRAWINGS">FIG. 46</figref> is a screen shot of an Import Wizard;

<figref idref="DRAWINGS">FIG. 47</figref> is a screen shot of an Import Wizard;

<figref idref="DRAWINGS">FIG. 48</figref> is a screen shot of an Import Wizard;

<figref idref="DRAWINGS">FIG. 49</figref> is a screen shot of an Import Wizard;

<figref idref="DRAWINGS">FIG. 50</figref> is a screen shot of an Import Wizard;

<figref idref="DRAWINGS">FIG. 51</figref> is a screen shot of an Import Wizard;

<figref idref="DRAWINGS">FIG. 52</figref> is a screen shot of an Import Wizard;

<figref idref="DRAWINGS">FIG. 53</figref> is a screen shot of an Import Wizard;

<figref idref="DRAWINGS">FIG. 54</figref> is a screen shot of an Import Wizard;

<figref idref="DRAWINGS">FIGS. 55</figref><i>a</i>-<b>55</b><i>b </i>are a screen shot of an Import Wizard;

<figref idref="DRAWINGS">FIG. 56</figref> is a screen shot of an Import Wizard;

<figref idref="DRAWINGS">FIG. 57</figref> is a screen shot of an Import Wizard;

<figref idref="DRAWINGS">FIG. 58</figref> is a screen shot of an Import Wizard;

<figref idref="DRAWINGS">FIG. 59</figref> is a screen shot of an Import Wizard;

<figref idref="DRAWINGS">FIG. 60</figref> is a screen shot of an Import Wizard;

<figref idref="DRAWINGS">FIG. 61</figref> is a screen shot of an Import Wizard;

<figref idref="DRAWINGS">FIG. 62</figref> is a screen shot of an Import Wizard;

<figref idref="DRAWINGS">FIG. 63</figref> is a screen shot of an Import Wizard;

<figref idref="DRAWINGS">FIG. 64</figref> is a screen shot of an Import Wizard;

<figref idref="DRAWINGS">FIG. 65</figref> is a screen shot of an Import Wizard;

<figref idref="DRAWINGS">FIG. 66</figref> is a screen shot of an Import Wizard;

<figref idref="DRAWINGS">FIGS. 67</figref><i>a</i>-<b>67</b><i>b </i>are a screen shot of an Import Wizard;

<figref idref="DRAWINGS">FIG. 68</figref> is a screen shot of an Import Wizard;

<figref idref="DRAWINGS">FIG. 69</figref> is a screen shot of an Import Wizard;

<figref idref="DRAWINGS">FIGS. 70</figref><i>a</i>-<b>70</b><i>b </i>are a screen shot of an Import Wizard;

<figref idref="DRAWINGS">FIG. 71</figref> is a screen shot of an Import Wizard;

<figref idref="DRAWINGS">FIG. 72</figref> is a screen shot of an Import Wizard;

<figref idref="DRAWINGS">FIG. 73</figref> is a screen shot of an Import Wizard;

<figref idref="DRAWINGS">FIG. 74</figref> is a screen shot of an Import Wizard;

<figref idref="DRAWINGS">FIG. 75</figref> is a screen shot of an Import Wizard;

<figref idref="DRAWINGS">FIGS. 76</figref><i>a</i>-<b>76</b><i>b </i>are a screen shot of an Import Wizard;

<figref idref="DRAWINGS">FIG. 77</figref> is a screen shot of an Import Wizard;

<figref idref="DRAWINGS">FIG. 78</figref> is a screen shot of an Import Wizard;

<figref idref="DRAWINGS">FIG. 79</figref> is a screen shot of an Import Wizard;

<figref idref="DRAWINGS">FIG. 80</figref> is a screen shot of an Import Wizard;

<figref idref="DRAWINGS">FIG. 81</figref> is a screen shot of an Import Wizard;

<figref idref="DRAWINGS">FIG. 82</figref> is a screen shot of an Import Wizard;

<figref idref="DRAWINGS">FIG. 83</figref> is a screen shot of an Import Wizard;

<figref idref="DRAWINGS">FIG. 84</figref> is a screen shot of an Import Wizard;

<figref idref="DRAWINGS">FIG. 85</figref> is a screen shot of an Import Wizard;

<figref idref="DRAWINGS">FIG. 86</figref> is a screen shot of an Import Wizard;

<figref idref="DRAWINGS">FIG. 87</figref> is a screen shot of an Import Wizard;

<figref idref="DRAWINGS">FIG. 88</figref> is a screen shot of an Import Wizard;

<figref idref="DRAWINGS">FIG. 89</figref> is a screen shot of an Import Wizard;

<figref idref="DRAWINGS">FIG. 90</figref> is a screen shot of an Import Wizard;

<figref idref="DRAWINGS">FIG. 91</figref> is a screen shot of an Import Wizard;

<figref idref="DRAWINGS">FIG. 92</figref> is a screen shot of an Import Wizard;

<figref idref="DRAWINGS">FIGS. 93</figref><i>a</i>-<b>93</b><i>b </i>are a screen shot of an Import Wizard;

<figref idref="DRAWINGS">FIG. 94</figref> is a screen shot of an Import Wizard;

<figref idref="DRAWINGS">FIG. 95</figref> is a screen shot of an Import Wizard;

<figref idref="DRAWINGS">FIG. 96</figref> is a screen shot of an Import Wizard;

<figref idref="DRAWINGS">FIG. 97</figref> is a screen shot of an Import Wizard;

<figref idref="DRAWINGS">FIG. 98</figref> is a screen shot of an Import Wizard;

<figref idref="DRAWINGS">FIG. 99</figref> is a screen shot of an Import Wizard;

<figref idref="DRAWINGS">FIG. 100</figref> is a screen shot of an Import Wizard;

<figref idref="DRAWINGS">FIG. 101</figref> is a screen shot of an Import Wizard;

<figref idref="DRAWINGS">FIG. 102</figref> is a screen shot of an Import Wizard;

<figref idref="DRAWINGS">FIG. 103</figref> is a screen shot of an Import Wizard;

<figref idref="DRAWINGS">FIG. 104</figref> is a screen shot of an Import Wizard;

<figref idref="DRAWINGS">FIG. 105</figref> is a screen shot of an Import Wizard;

<figref idref="DRAWINGS">FIG. 106</figref> is a screen shot of an Import Wizard;

<figref idref="DRAWINGS">FIG. 107</figref> is a screen shot of an Import Wizard;

<figref idref="DRAWINGS">FIG. 108</figref> is a screen shot of a locator module;

<figref idref="DRAWINGS">FIG. 109</figref> is a screen shot of a locator module;

<figref idref="DRAWINGS">FIG. 110</figref> is a screen shot of a locator module;

<figref idref="DRAWINGS">FIG. 111</figref> is a screen shot of a locator module;

<figref idref="DRAWINGS">FIG. 112</figref> is a screen shot of a locator module;

<figref idref="DRAWINGS">FIG. 113</figref> is a screen shot of a locator module;

<figref idref="DRAWINGS">FIG. 114</figref> is a screen shot of a locator module;

<figref idref="DRAWINGS">FIG. 115</figref> is a screen shot of a locator module;

<figref idref="DRAWINGS">FIG. 116</figref> is a screen shot of a locator module;

<figref idref="DRAWINGS">FIG. 117</figref> is a screen shot of a locator module;

<figref idref="DRAWINGS">FIG. 118</figref> is a screen shot of a locator module;

<figref idref="DRAWINGS">FIG. 119</figref> is a screen shot of a locator module;

<figref idref="DRAWINGS">FIG. 120</figref> is a screen shot of a locator module;

<figref idref="DRAWINGS">FIG. 121</figref> is a screen shot of a locator module;

<figref idref="DRAWINGS">FIG. 122</figref> is a screen shot of an Application Wizard;

<figref idref="DRAWINGS">FIG. 123</figref> is a screen shot of an Application Wizard;

<figref idref="DRAWINGS">FIG. 124</figref> is a screen shot of an Application Wizard;

<figref idref="DRAWINGS">FIG. 125</figref> is a screen shot of an Application Wizard;

<figref idref="DRAWINGS">FIG. 126</figref> is a screen shot of an Application Wizard;

<figref idref="DRAWINGS">FIG. 127</figref> is a screen shot of an Application Wizard;

<figref idref="DRAWINGS">FIG. 128</figref> is a screen shot of an Application Wizard;

<figref idref="DRAWINGS">FIG. 129</figref> is a screen shot of an Application Wizard;

<figref idref="DRAWINGS">FIG. 130</figref> is a screen shot of an Application Wizard;

<figref idref="DRAWINGS">FIG. 131</figref> is a screen shot of an Application Wizard;

<figref idref="DRAWINGS">FIG. 132</figref> is a screen shot of an Application Wizard;

<figref idref="DRAWINGS">FIG. 133</figref> is a screen shot of an Application Wizard;

<figref idref="DRAWINGS">FIG. 134</figref> is a screen shot of an Application Wizard;

<figref idref="DRAWINGS">FIG. 135</figref> is a screen shot of an Application Wizard;

<figref idref="DRAWINGS">FIG. 136</figref> is a screen shot of an Application Wizard;

<figref idref="DRAWINGS">FIG. 137</figref> is a screen shot of an Application Wizard;

<figref idref="DRAWINGS">FIG. 138</figref> is a screen shot of an Application Wizard;

<figref idref="DRAWINGS">FIG. 139</figref> is a screen shot of a CD Landing Page;

<figref idref="DRAWINGS">FIGS. 140</figref><i>a</i>-<b>140</b><i>c </i>are a screen shot of a CD Landing Page;

<figref idref="DRAWINGS">FIG. 141</figref> is a screen shot of a CD Landing Page;

<figref idref="DRAWINGS">FIG. 142</figref> is a screen shot of a CD Landing Page;

<figref idref="DRAWINGS">FIG. 143</figref> is a screen shot of a CD Landing Page;

<figref idref="DRAWINGS">FIG. 144</figref> is a screen shot of a CD Landing Page;

<figref idref="DRAWINGS">FIG. 145</figref> is a screen shot of a CD Landing Page;

<figref idref="DRAWINGS">FIG. 146</figref> is a screen shot of a CD Landing Page;

<figref idref="DRAWINGS">FIG. 147</figref> is a screen shot of a CD Landing Page;

<figref idref="DRAWINGS">FIG. 148</figref> is a screen shot of a CD Landing Page;

<figref idref="DRAWINGS">FIG. 149</figref> is a screen shot of a CD Landing Page;

<figref idref="DRAWINGS">FIG. 150</figref> is a screen shot of a CD Landing Page;

<figref idref="DRAWINGS">FIG. 151</figref> is a screen shot of a CD Landing Page;

<figref idref="DRAWINGS">FIGS. 152</figref><i>a</i>-<b>152</b><i>b </i>are a screen shot of a CD Landing Page;

<figref idref="DRAWINGS">FIG. 153</figref> is a screen shot of a CD Landing Page;

<figref idref="DRAWINGS">FIG. 154</figref> is a screen shot of a CD Landing Page;

<figref idref="DRAWINGS">FIG. 155</figref> is a screen shot of a CD Landing Page;

<figref idref="DRAWINGS">FIGS. 156</figref><i>a</i>-<b>156</b><i>c </i>are a screen shot of a CD Landing Page;

<figref idref="DRAWINGS">FIGS. 157</figref><i>a</i>-<b>157</b><i>b </i>are a screen shot of a CD Landing Page;

<figref idref="DRAWINGS">FIG. 158</figref> is a screen shot of a CD Landing Page;

<figref idref="DRAWINGS">FIG. 159</figref> is a screen shot of a CD Landing Page;

<figref idref="DRAWINGS">FIG. 160</figref> is a screen shot of a CD Landing Page;

<figref idref="DRAWINGS">FIG. 161</figref> is a screen shot of a CD Landing Page;

<figref idref="DRAWINGS">FIG. 162</figref> is a screen shot of a CD Landing Page;

<figref idref="DRAWINGS">FIG. 163</figref> is a screen shot of a CD Landing Page;

<figref idref="DRAWINGS">FIGS. 164</figref><i>a</i>-<b>164</b><i>b </i>are a screen shot of a CD Landing Page;

<figref idref="DRAWINGS">FIG. 165</figref> is a screen shot of a CD Landing Page;

<figref idref="DRAWINGS">FIGS. 166</figref><i>a</i>-<b>166</b><i>b </i>are a screen shot of a CD Landing Page;

<figref idref="DRAWINGS">FIGS. 167</figref><i>a</i>-<b>167</b><i>b </i>are a screen shot of a CD Landing Page;

<figref idref="DRAWINGS">FIGS. 168</figref><i>a</i>-<b>168</b><i>b </i>are a screen shot of a CD Landing Page;

<figref idref="DRAWINGS">FIG. 169</figref> is a screen shot of a CD Landing Page;

<figref idref="DRAWINGS">FIGS. 170</figref><i>a</i>-<b>170</b><i>c </i>are a screen shot of a CD Landing Page;

<figref idref="DRAWINGS">FIGS. 171</figref><i>a</i>-<b>171</b><i>c </i>are a screen shot of a CD Landing Page;

<figref idref="DRAWINGS">FIGS. 172</figref><i>a</i>-<b>172</b><i>c </i>are a screen shot of a CD Landing Page;

<figref idref="DRAWINGS">FIGS. 173</figref><i>a</i>-<b>173</b><i>b </i>are a screen shot of a CD Landing Page;

<figref idref="DRAWINGS">FIGS. 174</figref><i>a</i>-<b>174</b><i>b </i>are a screen shot of a CD Landing Page;

<figref idref="DRAWINGS">FIG. 175</figref> is a screen shot of a CD Landing Page;

<figref idref="DRAWINGS">FIGS. 176</figref><i>a</i>-<b>176</b><i>b </i>are a screen shot of a CD Landing Page;

<figref idref="DRAWINGS">FIGS. 177</figref><i>a</i>-<b>177</b><i>b </i>are a screen shot of a CD Landing Page;

<figref idref="DRAWINGS">FIG. 178</figref> is a screen shot of a CD Landing Page;

<figref idref="DRAWINGS">FIG. 179</figref> is a screen shot of a CD Landing Page;

<figref idref="DRAWINGS">FIG. 180</figref> is a screen shot of a CD Landing Page;

<figref idref="DRAWINGS">FIG. 181</figref> is a screen shot of a CD Landing Page;

<figref idref="DRAWINGS">FIG. 182</figref> is a screen shot of a CD Landing Page;

<figref idref="DRAWINGS">FIG. 183</figref> is a screen shot of a CD Landing Page;

<figref idref="DRAWINGS">FIG. 184</figref> is a screen shot of a CD Landing Page;

<figref idref="DRAWINGS">FIGS. 185</figref><i>a</i>-<b>185</b><i>b </i>are a screen shot of a CD Landing Page;

<figref idref="DRAWINGS">FIGS. 186</figref><i>a</i>-<b>186</b><i>c </i>are a screen shot of a CD Landing Page;

<figref idref="DRAWINGS">FIG. 187</figref> is a screen shot of a CSR Landing Page;

<figref idref="DRAWINGS">FIGS. 188</figref><i>a</i>-<b>188</b><i>b </i>are a screen shot of a CSR Landing Page;

<figref idref="DRAWINGS">FIGS. 189</figref><i>a</i>-<b>189</b><i>b </i>are a screen shot of a CSR Landing Page;

<figref idref="DRAWINGS">FIG. 190</figref> is a screen shot of a CSR Landing Page;

<figref idref="DRAWINGS">FIGS. 191</figref><i>a</i>-<b>191</b><i>d </i>are a screen shot of a VA Landing Page;

<figref idref="DRAWINGS">FIGS. 192</figref><i>a</i>-<b>192</b><i>b </i>are a screen shot of Calls and Notes Pages;

<figref idref="DRAWINGS">FIGS. 193</figref><i>a</i>-<b>193</b><i>b </i>are a screen shot of Calls and Notes pages;

<figref idref="DRAWINGS">FIGS. 194</figref><i>a</i>-<b>194</b><i>c </i>are a screen shot of Calls and Notes pages;

<figref idref="DRAWINGS">FIGS. 195</figref><i>a</i>-<b>195</b><i>c </i>are a screen shot of Calls and Notes pages;

<figref idref="DRAWINGS">FIG. 196</figref> is a screen shot of Audit History pages;

<figref idref="DRAWINGS">FIGS. 197</figref><i>a</i>-<b>197</b><i>b </i>are a screen shot of Audit History pages;

<figref idref="DRAWINGS">FIG. 198</figref> is a screen shot of Audit History pages;

<figref idref="DRAWINGS">FIGS. 199</figref><i>a</i>-<b>199</b><i>b </i>are a screen shot of a File Directory;

<figref idref="DRAWINGS">FIG. 200</figref> is a screen shot of a File Directory;

<figref idref="DRAWINGS">FIG. 201</figref> is a screen shot of a File Directory;

<figref idref="DRAWINGS">FIGS. 202</figref><i>a</i>-<b>202</b><i>b </i>are a screen shot of the Domino Directory;

<figref idref="DRAWINGS">FIGS. 203</figref><i>a</i>-<b>203</b><i>b </i>are a screen shot of the Bulletin Board IM;

<figref idref="DRAWINGS">FIGS. 204</figref><i>a</i>-<b>204</b><i>b </i>are a screen shot of the Bulletin Board IM;

<figref idref="DRAWINGS">FIGS. 205</figref><i>a</i>-<b>205</b><i>b </i>are a screen shot of the LA Field;

<figref idref="DRAWINGS">FIG. 206</figref> is a screen shot of the LA Field;

<figref idref="DRAWINGS">FIGS. 207</figref><i>a</i>-<b>207</b><i>b </i>are a screen shot of Symphony Templates and Bookmarks;

<figref idref="DRAWINGS">FIGS. 208</figref><i>a</i>-<b>208</b><i>b </i>are a screen shot of Symphony Templates and Bookmarks;

<figref idref="DRAWINGS">FIGS. 209</figref><i>a</i>-<b>209</b><i>b </i>are a screen shot of Symphony Templates and Bookmarks;

<figref idref="DRAWINGS">FIGS. 210</figref><i>a</i>-<b>210</b><i>b </i>are a screen shot of Symphony Templates and Bookmarks;

<figref idref="DRAWINGS">FIGS. 211</figref><i>a</i>-<b>211</b><i>c </i>are a screen shot of Symphony Templates and Bookmarks;

<figref idref="DRAWINGS">FIGS. 212</figref><i>a</i>-<b>212</b><i>b </i>are a screen shot of Symphony Templates and Bookmarks;

<figref idref="DRAWINGS">FIG. 213</figref> is a screen shot of Mail Description pages;

<figref idref="DRAWINGS">FIGS. 214</figref><i>a</i>-<b>214</b><i>b </i>are a screen shot of Mail Descriptions pages;

<figref idref="DRAWINGS">FIGS. 215</figref><i>a</i>-<b>215</b><i>c </i>are a screen shot of Mail Descriptions pages;

<figref idref="DRAWINGS">FIG. 216</figref> is a screen shot of Mail Descriptions pages;

<figref idref="DRAWINGS">FIG. 217</figref> is a screen shot of Reminder pages;

<figref idref="DRAWINGS">FIG. 218</figref> is a screen shot of Reminder pages;

<figref idref="DRAWINGS">FIGS. 219</figref><i>a</i>-<b>219</b><i>d </i>are a screen shot of Reminder pages;

<figref idref="DRAWINGS">FIGS. 220</figref><i>a</i>-<b>220</b><i>b </i>are a screen shot of Reminder pages;

<figref idref="DRAWINGS">FIGS. 221</figref><i>a</i>-<b>221</b><i>b </i>are a screen shot of Reminder pages;

<figref idref="DRAWINGS">FIGS. 222</figref><i>a</i>-<b>222</b><i>b </i>are a screen shot of Reminder pages;

<figref idref="DRAWINGS">FIG. 223</figref> is a screen shot of Initial Call Questionnaire pages;

<figref idref="DRAWINGS">FIGS. 224</figref><i>a</i>-<b>224</b><i>b </i>are a screen shot of Initial Call Questionnaire pages;

<figref idref="DRAWINGS">FIGS. 225</figref><i>a</i>-<b>225</b><i>b </i>are a screen shot of Initial Call Questionnaire pages;

<figref idref="DRAWINGS">FIG. 226</figref> is a screen shot of Initial Call Questionnaire pages;

<figref idref="DRAWINGS">FIGS. 227</figref><i>a</i>-<b>227</b><i>b </i>are a screen shot of Initial Call Questionnaire pages;

<figref idref="DRAWINGS">FIG. 228</figref> is a screen shot of Initial Call Questionnaire pages;

<figref idref="DRAWINGS">FIGS. 229</figref><i>a</i>-<b>229</b><i>b </i>are a screen shot of Initial Call Questionnaire pages;

<figref idref="DRAWINGS">FIGS. 230</figref><i>a</i>-<b>230</b><i>c </i>are a screen shot of Initial Call Questionnaire pages;

<figref idref="DRAWINGS">FIG. 231</figref> is a screen shot of Initial Call Questionnaire pages;

<figref idref="DRAWINGS">FIG. 232</figref> is a screen shot of Initial Call Questionnaire pages;

<figref idref="DRAWINGS">FIGS. 233</figref><i>a</i>-<b>233</b><i>b </i>are a screen shot of Initial Call Questionnaire pages;

<figref idref="DRAWINGS">FIG. 234</figref> is a screen shot of Initial Call Questionnaire pages;

<figref idref="DRAWINGS">FIGS. 235</figref><i>a</i>-<b>235</b><i>b </i>are a screen shot of Initial Call Questionnaire pages;

<figref idref="DRAWINGS">FIG. 236</figref> is a screen shot of Initial Call Questionnaire pages;

<figref idref="DRAWINGS">FIG. 237</figref> is a screen shot of Initial Call Questionnaire pages;

<figref idref="DRAWINGS">FIGS. 238</figref><i>a</i>-<b>238</b><i>b </i>are a screen shot of Initial Call Questionnaire pages;

<figref idref="DRAWINGS">FIG. 239</figref> is a screen shot of Initial Call Questionnaire pages;

<figref idref="DRAWINGS">FIG. 240</figref> is a screen shot of Initial Call Questionnaire pages;

<figref idref="DRAWINGS">FIGS. 241</figref><i>a</i>-<b>241</b><i>b </i>are a screen shot of Initial Call Questionnaire pages;

<figref idref="DRAWINGS">FIGS. 242</figref><i>a</i>-<b>242</b><i>b </i>are a screen shot of Initial Call Questionnaire pages;

<figref idref="DRAWINGS">FIG. 243</figref> is a screen shot of Initial Call Questionnaire pages;

<figref idref="DRAWINGS">FIG. 244</figref> is a screen shot of Initial Call Questionnaire pages;

<figref idref="DRAWINGS">FIG. 245</figref> is a screen shot of Initial Call Questionnaire pages;

<figref idref="DRAWINGS">FIGS. 246</figref><i>a</i>-<b>246</b><i>b </i>are a screen shot of SSA Hearing Views pages;

<figref idref="DRAWINGS">FIG. 247</figref> is a screen shot of SSA Hearing Views pages;

<figref idref="DRAWINGS">FIG. 248</figref> is a screen shot of SSA Hearing Views pages;

<figref idref="DRAWINGS">FIG. 249</figref> is a screen shot of SSA Hearing Views pages;

<figref idref="DRAWINGS">FIG. 250</figref> is a screen shot of SSA Hearing Views pages;

<figref idref="DRAWINGS">FIG. 251</figref> is a screen shot of SSA Hearing Views pages;

<figref idref="DRAWINGS">FIG. 252</figref> is a screen shot of SSA Hearing Views pages;

<figref idref="DRAWINGS">FIG. 253</figref> is a screen shot of SSA Hearing Views pages;

<figref idref="DRAWINGS">FIG. 254</figref> is a screen shot of SSA Hearing Views pages;

<figref idref="DRAWINGS">FIGS. 255</figref><i>a</i>-<b>255</b><i>b </i>are a screen shot of SSA Hearing Views pages;

<figref idref="DRAWINGS">FIG. 256</figref> is a screen shot of SSA Hearing Views pages;

<figref idref="DRAWINGS">FIG. 257</figref> is a screen shot of SSA Hearing Views pages;

<figref idref="DRAWINGS">FIG. 258</figref> is a screen shot of SSA Hearing Views pages;

<figref idref="DRAWINGS">FIGS. 259</figref><i>a</i>-<b>259</b><i>b </i>are a screen shot of SSA Hearing Views pages;

<figref idref="DRAWINGS">FIG. 260</figref> is a screen shot of SSA Hearing Views pages;

<figref idref="DRAWINGS">FIGS. 261</figref><i>a</i>-<b>261</b><i>b </i>are a screen shot of SSA Hearing Views pages;

<figref idref="DRAWINGS">FIGS. 262</figref><i>a</i>-<b>262</b><i>b </i>are a screen shot of SSA Hearing Views pages;

<figref idref="DRAWINGS">FIGS. 263</figref><i>a</i>-<b>263</b><i>b </i>are a screen shot of SSA Hearing Views pages;

<figref idref="DRAWINGS">FIG. 264</figref> is a screen shot of SSA Hearing Views pages;

<figref idref="DRAWINGS">FIG. 265</figref> is a screen shot of SSA Hearing Views pages;

<figref idref="DRAWINGS">FIG. 266</figref> is a screen shot of SSA Hearing Views pages;

<figref idref="DRAWINGS">FIG. 267</figref> is a screen shot of SSA Hearing Views pages;

<figref idref="DRAWINGS">FIG. 268</figref> is a screen shot of SSA Hearing Views pages;

<figref idref="DRAWINGS">FIG. 269</figref> is a screen shot of SSA Hearing Views pages;

<figref idref="DRAWINGS">FIGS. 270</figref><i>a</i>-<b>270</b><i>b </i>are a screen shot of SSA Hearing Views pages;

<figref idref="DRAWINGS">FIGS. 271</figref><i>a</i>-<b>271</b><i>b </i>are a screen shot of SSA Hearing Views pages;

<figref idref="DRAWINGS">FIGS. 272</figref><i>a</i>-<b>272</b><i>c </i>are a screen shot of SSA Hearing Views pages;

<figref idref="DRAWINGS">FIGS. 273</figref><i>a</i>-<b>273</b><i>c </i>are a screen shot of SSA Hearing Views pages;

<figref idref="DRAWINGS">FIG. 274</figref> is a screen shot of SSA Hearing Views pages;

<figref idref="DRAWINGS">FIGS. 275</figref><i>a</i>-<b>275</b><i>b </i>are a screen shot of SSA Hearing Views pages;

<figref idref="DRAWINGS">FIG. 276</figref> is a screen shot of SSA Hearing Views pages;

<figref idref="DRAWINGS">FIG. 277</figref> is a screen shot of SSA Hearing Views pages;

<figref idref="DRAWINGS">FIGS. 278</figref><i>a</i>-<b>278</b><i>b </i>are a screen shot of SSA Hearing Views pages;

<figref idref="DRAWINGS">FIGS. 279</figref><i>a</i>-<b>279</b><i>e </i>are a screen shot of SSA Hearing Views pages;

<figref idref="DRAWINGS">FIGS. 280</figref><i>a</i>-<b>280</b><i>b </i>are a screen shot of SSA Hearing Views pages;

<figref idref="DRAWINGS">FIGS. 281</figref><i>a</i>-<b>281</b><i>b </i>are a screen shot of SSA Hearing Views pages;

<figref idref="DRAWINGS">FIG. 282</figref> is a screen shot of SSA Hearing Views pages;

<figref idref="DRAWINGS">FIGS. 283</figref><i>a</i>-<b>283</b><i>c </i>are a description of auto-fax instructions;

<figref idref="DRAWINGS">FIG. 284</figref> is a description of auto-fax instructions;

<figref idref="DRAWINGS">FIG. 285</figref> is a screen shot of the client portal;

<figref idref="DRAWINGS">FIG. 286</figref> is a screen shot of the client portal;

<figref idref="DRAWINGS">FIG. 287</figref> is a screen shot of the client portal;

<figref idref="DRAWINGS">FIGS. 288</figref><i>a</i>-<b>288</b><i>b </i>are a screen shot of the client portal;

<figref idref="DRAWINGS">FIG. 289</figref> is a screen shot of the client portal;

<figref idref="DRAWINGS">FIG. 290</figref> is a screen shot of the client portal;

<figref idref="DRAWINGS">FIG. 291</figref> is a screen shot of the client portal;

<figref idref="DRAWINGS">FIGS. 292</figref><i>a</i>-<b>292</b><i>b </i>are a screen shot of the client portal;

<figref idref="DRAWINGS">FIG. 293</figref> is a screen shot of the client portal;

<figref idref="DRAWINGS">FIG. 294</figref> is a screen shot of the client portal;

<figref idref="DRAWINGS">FIG. 295</figref> is a screen shot of the client portal;

<figref idref="DRAWINGS">FIG. 296</figref> is a screen shot of the client portal;

<figref idref="DRAWINGS">FIG. 297</figref> is a screen shot of the client portal;

<figref idref="DRAWINGS">FIG. 298</figref> is a screen shot of the client portal;

<figref idref="DRAWINGS">FIG. 299</figref> is a screen shot of the client portal;

<figref idref="DRAWINGS">FIG. 300</figref> is a screen shot of the client portal;

<figref idref="DRAWINGS">FIG. 301</figref> is a screen shot of the client portal.

DETAILED DESCRIPTION OF THE INVENTION

While the present invention is susceptible of embodiment in various forms, there is shown in the drawings and will hereinafter be described a presently preferred, albeit not limiting, embodiment with the understanding that the present disclosure is to be considered an exemplification of the present invention and is not intended to limit the invention to the specific embodiments illustrated.

<figref idref="DRAWINGS">FIGS. 1-282</figref>, which are now referenced, illustrate the present invention and the manner in which it is performed.

Referring to <figref idref="DRAWINGS">FIGS. 1A-1F</figref> is shown a general method of claim progression relating to social security disability. The instant invention is portable across other areas of law and also to other industries. For example, this method of claim progression is useful for insurance benefit claims and other administrative proceedings.

The claim process administration begins at step <b>100</b>, which defines a process by which client leads are generated. The client leads are generated through traditional and modern means including television, internet and social networking advertising and marketing. The client leads are received into a software suite. The flow charts <figref idref="DRAWINGS">FIGS. 1A and 1B</figref> illustrate the path that a claim for a benefit from a government agency will take according to the present invention. In a preferred embodiment a claim for a benefit from the Social Security Administration is described. It should be noted that other claims for other benefits and services from other that the government can also be obtained utilizing the present invention.

A determination is made at step <b>102</b> if an individual needs to file a claim for a benefit. At step <b>104</b> the response triggers a work flow for the initial application for benefits. At step <b>106</b> the initial application work flow is complete and the application is produced and/or the application data is filled in/populated automatically. This procedure depends on the manner in which the system is set up and the specific software that the system is utilizing. The application is then filed with the specific government agency, in the preferred embodiment, the Social Security Administration. At step <b>108</b> a determination is made to accept or reject the benefit claim at the government agency. If the benefit claim is accepted at step <b>110</b> a letter indicating this acceptance is sent to the individual or firm who submitted the benefit claim application. At step <b>112</b> the status that the claim has been approved is indicated.

Should the claim be denied, an AOD appeal is initiated at step <b>118</b>. Additionally, a reconsideration request is initiated at step <b>122</b>. At step <b>126</b> the reconsideration of the claim denial is filed. Next, the process goes to step <b>138</b> where it is joined with another type of claim denial appeal prior to filing for a hearing at step <b>142</b>.

If there is a letter from the government administration, such as the Social Security Administration, denying the benefits from the initial filing of the application for benefits, then a letter is mailed at step <b>114</b>. This letter can trigger specific work flows relating to the denial at step <b>116</b>. Alternatively, there is a procedure relating to the denial that occurs at step <b>120</b>. Subsequent to steps <b>120</b> and <b>116</b> the work flow is complete at step <b>124</b>. If the individual and/or law firm decides to go back to the agency for reconsideration of the agency's denial of benefits, the process then proceeds to step <b>128</b>. Here the reconsideration process and work flow related to the reconsideration process begins.

Next, there will be a letter from the Social Security Administration approving the reconsideration request <b>130</b> or denying the reconsideration request <b>134</b>. When the reconsideration request is approved the process moves to <b>132</b> where the reconsideration takes place. If the reconsideration is denied, an AOD appeal is next at <b>138</b>. The hearing for the AOD appeal takes place at <b>142</b>.

After receiving the reconsideration request denial letter from the Social Security Administration a specific work flow is triggered at <b>136</b> regarding the denial. Alternatively, the denial proceeds to step <b>140</b> then onto step <b>144</b> where the work flow is complete. Also, from <b>136</b> the process proceeds to step <b>144</b>. Next, a hearing is filed at <b>146</b>. There can be three results of the filing. First, the hearing is fully favorable to the individual/law firm and a letter is sent to the individual/law firm from the Social Security Administration (SSA). The process ends with a fully favorable reconsideration of the benefit request at <b>152</b>. Second, a letter is send from the SSA approving an OTR at <b>148</b>. The process ends here with a fully favorable reconsideration of the benefit request at <b>154</b>. Finally, a letter form the SSA is mailed with an RTS notice at <b>158</b>.

The following steps are found in <figref idref="DRAWINGS">FIG. 1B</figref>. Next, a letter from the SSA is mailed regarding the hearing notice at <b>160</b>. From here either there is a scheduled hearing at <b>162</b> or a scheduled hearing at <b>170</b>. From both <b>162</b> and <b>170</b> there is a post hearing at <b>174</b>. The next step is awaiting a decision at <b>176</b>. There can be three results from the decision. First, a letter from the SSA is mailed which is fully favorable at <b>178</b>. Then at step <b>180</b> the fully favorable decision is recorded. Next, at <b>172</b>, there is a letter from the SSA indicating a remand where the A/C overturns the FF. From here there is a fully favorable decision at <b>168</b> and a letter from the SSA is mailed at <b>166</b>. The process then proceeds to <b>164</b> where there is a RTS, the A/C overturns the FF. The process then proceeds back to step <b>160</b>. Second, there is a letter from the SSA indicating a partially favorable decision from the hearing at <b>186</b>. This letter triggers certain work flow at <b>188</b> and then proceeds to <b>196</b> where the work flow regarding a partially favorable decision is complete. From step <b>186</b> there is a partially favorable hearing at <b>192</b>. Then the process proceeds to step <b>196</b>. Finally, there is a letter from the SSA indicating that the decision is unfavorable at <b>184</b>. This letter triggers specific work flow at <b>182</b> and this workflow proceeds to an assessment of the unfavorable decision at <b>194</b>. From <b>184</b> the process can proceed to <b>190</b> where assessment of the unfavorable decision starts.

From step <b>194</b> there can be three results. First, at <b>198</b> a new application is filed. Second, at <b>202</b> a decision is made to not pursue any further action at <b>202</b>. Finally, at <b>200</b> a decision is made to appeal the unfavorable decision. The next step is the appeals council at <b>214</b>. From step <b>196</b> there can be two results. First, there is no appeal of the partially favorable decision at <b>206</b>. Second, a decision is made to appeal the partially favorable decision at <b>204</b>. After the decision at <b>204</b> the process proceeds to the appeal council at <b>214</b>.

From the decision of appeal council the process can proceed in one of 4 different ways. First, at <b>208</b> there is a letter from the SSA that the appeal was successful at <b>208</b> and the process concludes at <b>220</b>. Second, there is a letter from the SSA remanding the appeal at <b>210</b>. The process proceeds to step <b>222</b> and then to step <b>230</b> where a letter from the SSA contains a RTS notice. Next, at step <b>234</b> there is a letter from the SSA containing the hearing notice. Then the hearing is scheduled at <b>236</b> and the process returns to step <b>170</b>. Third, there is a letter from the SSA dismissing the appeal at <b>218</b>. This letter triggers work flow at <b>212</b> which concludes at <b>244</b> where the dismissal can proceed in one of two ways. After step <b>218</b> the process can proceed to step <b>224</b> where the A/C is dismissed. Fourth, there is a letter from the SSA denying the appeal at <b>220</b>. As a result of this letter, the process can proceed to either of steps <b>216</b> or <b>228</b>.

At step <b>216</b> there are triggers for work flow to come to a final decision that there will be no further appeal. At step <b>228</b> there are triggers for work flow to come to a decision that there will be a further appeal. At step <b>246</b> there is assessment to see if the work flow is complete. From step <b>246</b> there can be a denial decision at <b>248</b> at the Federal level. There can also be a denial decision at step <b>250</b>. From step <b>248</b> the process proceeds to step <b>252</b> which is the Federal level. From here there are two outcomes. First, there is a letter from the SSA denying the appeal at step <b>254</b>. Second, there is a letter from the SSA granting the benefit and this decision is published as a final order at <b>256</b>.

There can also be a remand of the decision at the Federal level at step <b>262</b>. From here the process proceeds to step <b>238</b> where a letter from the SSA indicates a RTS notice. Next, there is a RTS (Federal Remand) step <b>240</b>. Then, at step <b>242</b> there is a letter from the SSA containing a notice of the hearing. The hearing is scheduled at step <b>260</b> and the process proceeds back to step <b>170</b>.

Referring to <figref idref="DRAWINGS">FIG. 1C</figref>, a simplified flow chart is provided depicting the computer driven systematic method of populating social security claim forms comprising the steps of: providing a series of on-line contact information questions to a claimant <b>280</b> where the claimant enters contact information. The answers provide by the claimant are compared against a database <b>282</b> to determine a service track for the claimant by determining which government benefit programs the claimant is eligible for. The method determines if the claimant has a valid claim for Social Security Disability Insurance (SSDI) <b>284</b>, Supplemental Security Income (SSI) <b>286</b>, or veterans disability <b>288</b> based upon questions selected from said service track. The claimant is then directed through appropriate through appropriate questions and sequences based on answers and valid claim <b>290</b> and provides the appropriate questions to determine medical qualifies <b>292</b>, financial qualifiers <b>294</b> and claim status qualifiers <b>296</b>. A determination is then made if the claimant can be evaluated for a Disability claim <b>298</b> wherein the claimant is directed to a processing stage <b>300</b> and an inquiry is made to determine if the intake review is complete <b>302</b>. If the intake review is incomplete the intake is denied <b>304</b>, if the intake review is complete the intake is accepted <b>306</b> based on the claimant's medical history and determining that the claimant has a valid claim for benefits. The documents are generated for a mobile representative or mailed upon assigning <b>308</b> a Social Security District Office by zip code. Representation forms are populated for the claimant to sign <b>310</b> and the forms are submitted to the assigned Social Security District Office when appropriate <b>312</b>. If the claim status fails, the claim does not need to be filed. A further review of the intake review is performed and status still indicates fail, the intake is denied. If the further review of the intake review is performed and status indicates accepted <b>306</b>′, the claimant is passed to document preparation <b>308</b>′.

<figref idref="DRAWINGS">FIGS. 2-284</figref> are screen shots of the above noted process. The screen shot indicate different possible selections and decisions at various steps in the above noted process.

The Import Wizard allows users to attach documents directly to client's files. Wizard is a trademark of the applicant. The wizard connects to a network folder called a Source folder where scanned documents are stored in PDF format. The user can see the selected document in a preview window within the Wizard to easily identify the document and the specific client. The user can select from 6 different import options depending on the type of documents they are importing. <ul id="ul0001" list-style="none"><li id="ul0001-0001" num="0000"><ul id="ul0002" list-style="none"><li id="ul0002-0001" num="0346">Incoming Mail</li><li id="ul0002-0002" num="0347">Outgoing Mail</li><li id="ul0002-0003" num="0348">Collections</li><li id="ul0002-0004" num="0349">Medical Records</li><li id="ul0002-0005" num="0350">Pickups</li><li id="ul0002-0006" num="0351">Work-flow Documents</li></ul></li></ul>

When a specific client is searched and found their contact and claim information will appear in right side panel. The user will have the option to import the current document in the preview window, skip the current document in the preview window, or pick from a list of all documents in the network folder.

Once the document is imported it is automatically moved into a Target folder.

Importing Pickups: The Pickups Import Wizard is used to import the initial representation paperwork signed by a client.

The user will click Import to attach the document to the specific clients file.

After clicking Import a dialog will appear showing the three different categories the signed paperwork will go into: Pickup Package, 1696 &amp; FA, and L&amp;N Release.

After one the categories is imported it is indicated on the right panel under “Imported Subjects”. To complete a pickup all three categories need to be imported.

Incoming Mail: This section of the import wizard is used to import incoming mail documents relating to the clients claim. The user will select from a list of pre-determined letter titles depending on what they are importing. The user can assign each imported document to another user if needed.

The user will click Import to attach the document to the specific clients file.

After clicking import an Import Window dialog will appear. The user will be able to update multiple data fields relating to the document they are importing. The data fields that are updated in the import window will be updated on the clients claim page.

Outgoing Mail: This section of the import wizard is used to upload outgoing mail documents.

The user will click Import to attach the document to the specific clients file.

The user will select from a list of pre-determined letter titles depending on what they are importing.

Workflow documents: Several workflows have been created to require a document to be attached to EZ claim as part of the workflow.

The user will click Import to attach the document to the specific clients file.

Claims have multiple workflows pending at any given time so a dialog will appear to ensure the user is importing the document to complete the correct one.

The workflow must be on the “Import” step (most workflows have multiple steps, Import being the last).

The workflow will appear in yellow in the right side panel which indicates it is on the Import step (it will be white if it's on any other step of the workflow).

Medical Records: This section of the Import Wizard is used to import Medical Records relating to the clients claim.

In addition to the clients contact and claim information, their treating sources will also appear in the right panel.

An “Add doctor/facility” button will also appear on the right panel which will allow the user to add a new doctor or facility if needed.

The user will click Import to attach the document to the specific clients file.

A dialog will appear giving the options Client, Facility, or ODAR. The user will select one of these options depending on where the record was received from.

If the user selects the Client option they must then determine whether the document they are importing is a “Medical Record” from a Doctor/Facility or if it would be categorized as “Other” which is anything that does not fall into the Medical Record category.

If the user selects Medical Record they will then need to select whether the Record was “Requested” or “Unrequested”.

The “Requested” option means our office has already requested the records being imported and allows the user to match the received records to the records requested.

The “Unrequested” option means our office has not requested the records and the user must assign such records to a Doctor/Facility.

If the Unrequested option is selected the user will select the doctor or facility of the medical records received by the client.

Once the doctor/facility is selected the doctor/facility contact information appears in the Import window.

The user must then select from a pre-determined list the type of record that has been received.

The user must also select from a pre-determined list the way the records were received into the office.

There is a Comments box available for the user to write additional notes to describe the record that was received.

The user can assign the additional notes to another user with the record attached in PDF format.

The user can select “Reminders” within the import window. By selecting the Reminders tab a view will appear with pending Reminders found within the clients claim. The user can place a check mark on existing Reminders to remove them.

The user can add new Reminders by clicking Add. This will bring up a dialog box that will allow the user to add a new Reminder.

If the user selects the option “Other” they will need to determine whether or not the record was Requested or Unrequested.

If the user selects Unrequested they will choose the type of record from a pre-determined list.

If the user selects “Facility” as the source where the Medical Record was received from they will then select “Medical Record” or “Invoice” as the type of record to attach.

If the user selects “Medical Record”, the user will select whether the record was Requested or Unrequested.

If the user selects requested, the will also need to select the Facility from which the records were received. Once the facility is selected it will show the date range of the requested records.

The user will have the option to select Close in order to document when records are not received or when the request needs to be consolidated.

The user will select the option which best describes the reason no records were received: Need to Request, Not seen since, Not relevant. If needed the user can write in the comments area any further details regarding the reason for closing the request.

When the user clicks Save with one of the options described it will close the request.

To Consolidate a record the user must select which record needs to be consolidated.

The user must then select the Consolidate option and a Resulting Record box will appear.

The Resulting record box shows a list of open requests for facilities which the selected request can be consolidated into.

Once the user has selected which facility the records need to be consolidated and imported under, a Receive Information box appears for the user to select then to enter the record information to be imported.

If the user selects “Invoice” they will choose the Doctor/Facility from which the Invoice was received.

An Invoice can only be imported if there is an open or satisfied request in the system. Otherwise there will be no Doctors/Facilities to choose from and the system will not allow anything to be imported.

The user must select to either import as an invoice or pre-bill. Once it is imported the bill goes onto the SSA Hearing-Medical Record-Invoices-To Pay list. If the pre-bill option is selected the bill goes to the top of the “To Pay” list to be paid first regardless if other invoices were received before it.

The user must select whether the bill can be paid by check, online, or by phone. Depending upon the option selected is where the bill will appear on the “To Pay” list. If online or phone is selected the Check Name and Check Address will appear.

If an Invoice/Pre-Bill was not invoiced correctly the user can select to Dispute it. Once Dispute is selected a new dialog box will appear to place the amount we are being incorrectly charged.

The user must select the action needed on the Invoice/Pre-Bill. Based upon the option selected the bill will go to the appropriate section on the “To Pay” list. If CD approval is selected a new dialog box will appear “Assigned” to assign the bill to a person to determine whether it will be paid or cancelled.

If the user selects “ODAR” as the source where the record was received from they will then need to select “Requested” or “Unrequested”.

If the user selects Unrequested they will choose the type of record from a pre-determined list.

Importing Collections: This section of the Import Wizard is used to import any payment mail relating to a clients claim.

The user will click Import to attach the document to the specific clients file.

A dialog will appear giving the options New Fee Request, New Fee Mail, Existing Fee Request, and Existing Fee Mail. The user will select one of these options depending on what they are importing.

If the user selects “New Fee Request” they will select Received or Requested. If the user selects Received the date will automatically populate in the Check Received field.

The user will also select the Type to categorize the type of payment received, and Issued By to specify who issued the payment.

The user will then select the Fee Type from a pre-determined list.

The user will select the Attorney's name that appears on the check from a pre-determined list, the amount received, and a note if needed.

The user will select the AR Status from a pre-determined list and enter the date. This information will be reflected on the clients claim for tracking purposes.

The user will also have the option to update the clients claim status if necessary.

As described in #58, if the user selects New Fee Mail they will select the Subject and Fee Type from pre-determined lists.

The user will enter the Fee Amounts into each field accordingly and can add notes if needed.

If the user selects Existing Fee Request they will choose from a list of all Fee Requests imported under “New Fee Request” in order to edit the information.

If the user selects Existing Fee Mail they will choose from a list of all Fee Mail imported under “New Fee Mail” in order to edit the information.

The Application Wizard is an extension of the Intake Wizard. Once the Intake Wizard is completed the user is redirected to the Application Wizard for completion.

The user will be automatically redirected based on the clients claim status. The Intake Wizard predicts whether or not an Application needs to be completed based on a series of questions that are asked.

If the Intake Wizard predicts the client needs to file an application the user will redirected to the Application Wizard to begin.

All of the information gathered on the Intake Wizard is automatically populated into the Application Wizard to avoid retrieving duplicate information.

As each question is answered it allows more questions to appear. If a question does not apply due to previous answers the question will stay hidden.

If the user clicks Add Spouse a dialog will open and they will enter the all of the appropriate information which, upon saving, will populate in a summary box.

By clicking on any of the buttons on the Application Wizard a dialog will appear so that the user can enter the corresponding information. The information is then displayed in a summary box.

Once the Application Wizard is completed the client will appear on the Application Wizard View. On this view each application is categorized by the status of the Application Wizard and then sub-categorized by the user assigned to the application.

By double clicking on the client from the Application Wizard view that specific clients completed Application Wizard will open to be reviewed.

The Reviewer can add any revisions for the user to make once the Application Wizard is returned to them.

After reviewing the Application Wizard the user will click Return to Submitter and then from a dialog box they will select Revise and Return, Revise and OK to Submit, or OK to Submit.

Once the Application Wizard is under the category OK to Submit the user will click the Submit to SSA button.

The Social Security Application for Disability Benefits is a series of three (3) extensive forms. The Application Wizard has grouped the questions from these forms together to drastically shorten the completion time and to avoid gathering duplicate information.

Once all of the information is gathered using the Application Wizard the user can generate all three (3) Social Security forms by clicking the Submit to SSA button. Each application will open one at a time and the information gathered on the Application Wizard is populated into the corresponding fields on the SSA Application forms.

Now referring to <figref idref="DRAWINGS">FIGS. 285-301</figref>, disclosed is MyClaimGo, a client portal, the client will go to www.myclaim.com. They can also access the portal from our website, www.disabilitylawclaims.com by clicking on the MyClaim link. MyClaim and MyClaimGo are trademarks of the Applicant. To Register the client will click on Register to use the site.

The client will enter their personal information and create a username and password.

Once the client registers, their information will be linked directly to their claim in Lotus using their Last Name, Date of Birth, and the Last four digits of their Social Security Number.

Once the client registers and logs in they will have access to their claim status information, contact information, emergency contact information, medical treatment information, prescription information, medical conditions, and work history.

If the client clicks on Emergency Contacts they will be able to view, Edit, or Remove all existing contacts. They will also have the ability to add New contacts.

If the client requests to add, edit, or remove a contact the request will appear in their Pending Requests window.

All client requests to add, edit, or remove information is sent our Admin Console which a user is checking daily.

If the client clicks on Medical Treatment they will be able to view, Edit, or Remove all existing Medical Treating sources. They will also have the ability to add new Treating Sources.

If the client requests to add, edit, or remove a medical treating source the request will appear in their Pending Requests window.

If the client clicks on Prescriptions they will be able to view, Edit, or Remove all existing Prescriptions. They will also have the ability to add new Prescriptions.

If the client requests to add, edit, or remove a prescription the request will appear in their Pending Requests window.

As described in #5←this doesn't make sense here because my numbers are not included, if the client clicks on Medical Conditions they will be able to view, Edit, or Remove all existing Medical Conditions. They will also have the ability to add new Conditions.

If the client requests to add, edit, or remove a medical condition the request will appear in their Pending Requests window.

If the client clicks on Work History they will be able to view, Edit, or Remove all existing Work History. They will also have the ability to add new Work History.

If the client requests to add, edit, or remove a Work History the request will appear in their Pending Requests window.

The client can also click on Additional Comments to enter any information or request they'd like to be reviewed by the firm.

All client requests submitted to the Admin Console are reviewed daily and will be updated in the clients claim that will reflect on MyClaimGo.com in real time.

All patents and publications mentioned in this specification are indicative of the levels of those skilled in the art to which the invention pertains. All patents and publications are herein incorporated by reference to the same extent as if each individual publication was specifically and individually indicated to be incorporated by reference.

It is to be understood that while a certain form of the invention is illustrated, it is not to be limited to the specific form or arrangement herein described and shown. It will be apparent to those skilled in the art that various changes may be made without departing from the scope of the invention and the invention is not to be considered limited to what is shown and described in the specification and any drawings/figures included herein.

One skilled in the art will readily appreciate that the present invention is well adapted to carry out the objectives and obtain the ends and advantages mentioned, as well as those inherent therein. The embodiments, methods, procedures and techniques described herein are presently representative of the preferred embodiments, are intended to be exemplary and are not intended as limitations on the scope. Changes therein and other uses will occur to those skilled in the art which are encompassed within the spirit of the invention and are defined by the scope of the appended claims. Although the invention has been described in connection with specific preferred embodiments, it should be understood that the invention as claimed should not be unduly limited to such specific embodiments. Indeed, various modifications of the described modes for carrying out the invention which are obvious to those skilled in the art are intended to be within the scope of the following claims.