Processing insurance related address information

• US 10,417,588 B1
• Filed: 01/29/2014
• Issued: 09/17/2019
• Est. Priority Date: 12/06/2013
• Status: Active Grant

• Current Assignee: Guidewire Software Incorporated
• Original Assignee: Guidewire Software Incorporated
• Inventors: Kreisel, Raymond Timothy, Burn, Mike
• Primary Examiner(s): Stamber, Eric W
• Assistant Examiner(s): Walker, III, George H
• Application Number:
  US14/167,936
• Time in Patent Office: 2,057 Days
• CPC Class Codes: G06Q 10/063 Operations research, analysis or management
• CPC Class Codes: G06Q 40/08 Insurance

Abstract

A technique of processing insurance-related address information includes receiving a starting address specification. It further includes determining a geocode location that is associated with the starting address specification. It further includes providing display information associated with the geocode. It further includes receiving updated address information that is generated within a display of the display information. It further includes determining a reverse geocode associated with the updated address information.

Claims

1. A system, comprising:

a processor configured to;

in response to a user input received via a parent frame directed to a first domain, place a starting address specification in a first hidden field of the parent frame and open an iframe embedded in the parent frame, wherein the embedded iframe is directed to a uniform resource locator (URL) under the first domain, and wherein an initial page at the URL to which the iframe is directed is configured to instruct a proxy to perform a remote proxy call on behalf of the iframe to obtain rendering code hosted on a central host component on a second domain different from the first domain;

obtain, via the proxy, the rendering code hosted on the central host component on the second domain different from the first domain;

execute the rendering code, obtained via the proxy from the central host component on the second domain, in the iframe directed to the first domain that is embedded in the parent frame directed to the first domain, wherein the rendering code executing in the iframe directed to the first domain is configured to;

extract the starting address specification placed, in response to the user input received via the parent frame, in the first hidden field of the parent frame directed to the first domain;

use the starting address specification extracted from the first hidden field of the parent frame to determine a geocode that is associated with the starting address specification; and

render, in the iframe embedded in the parent frame, display information associated with the geocode determined using the starting address specification extracted, by the rendering code executing in the iframe, from the first hidden field of the parent frame;

receive updated address information that is generated within the iframe in which the display information is rendered, wherein the updated address information is associated with an updated geocode different from the determined geocode associated with the starting address specification;

determine a reverse geocode associated with the updated address information;

pass the reverse geocode from the iframe to the parent frame at least in part by placing the reverse geocode in a second hidden field of the parent frame;

extract the reverse geocode from the second hidden field; and

update, using the reverse geocode extracted from the second hidden field, a transactional object used in an insurance-related workflow open in the parent frame; and

a memory coupled to the processor and configured to provide the processor with instructions.

2. The system recited in claim 1, wherein determining a geocode includes determining a set of coordinates corresponding to the starting address specification.

3. The system recited in claim 2, wherein rendering the display information includes rendering, in the iframe embedded in the parent frame, an indication of the geocode on a rendered map.

4. The system recited in claim 3, wherein the rendered indication comprises a marker placed at the geocode on the rendered map.

5. The system recited in claim 1, wherein determining the geocode is performed at least in part by querying a third party engine.

6. The system recited in claim 1, wherein the updated address information is associated with a movement of a marker indicative of a physical location.

7. The system recited in claim 1, wherein the processor is further configured to receive description information associated with the starting address specification.

8. The system recited in claim 1, wherein the starting address specification includes a user-specified starting address.

9. The system recited in claim 1, wherein the starting address specification includes a default starting address.

10. The system recited in claim 1, wherein the updated geocode comprises a set of updated coordinates.

11. The system recited in claim 10, wherein determining a reverse geocode comprises requesting a third party engine to determine a textual representation of an address corresponding to the updated coordinates.

12. The system recited in claim 1, wherein the iframe is rendered inline with a workflow window comprising a browser window.

13. A method, comprising:

in response to a user input received via a parent frame directed to a first domain, placing a starting address specification in a first hidden field of the parent frame and open an iframe embedded in the parent frame, wherein the embedded iframe is directed to a uniform resource locator (URL) under the first domain, and wherein an initial page at the URL to which the iframe is directed is configured to instruct a proxy to perform a remote proxy call on behalf of the iframe to obtain rendering code hosted on a central host component on a second domain different from the first domain;

obtaining, via the proxy, the rendering code hosted on the central host component on the second domain different from the first domain;

executing the rendering code, obtained via the proxy from the central host component on the second domain, in the iframe directed to the first domain that is embedded in the parent frame directed to the first domain, wherein the rendering code executing in the iframe directed to the first domain is configured to;

extract the starting address specification placed, in response to the user input received via the parent frame, in the first hidden field of the parent frame directed to the first domain;

use the starting address specification extracted from the first hidden field of the parent frame to determine a geocode that is associated with the starting address specification; and

render, in the iframe embedded in the parent frame, display information associated with the geocode determined using the starting address specification extracted, by the rendering code executing in the iframe, from the hidden field of the parent frame;

receiving updated address information that is provided within the iframe in which the display information is rendered, wherein the updated address information is associated with an updated geocode different from the determined geocode associated with the starting address specification;

determining a reverse geocode associated with the updated address information;

passing the reverse geocode from the iframe to the parent frame at least in part by placing the reverse geocode in a second hidden field of the parent frame;

extracting the reverse geocode from the second hidden field; and

updating, using the reverse geocode extracted from the second hidden field, a transactional object used in an insurance-related workflow open in the parent frame.

14. A computer program product embodied in a non-transitory computer readable storage medium and comprising computer instructions for:

in response to a user input received via a parent frame directed to a first domain, placing a starting address specification in a first hidden field of the parent frame and open an iframe embedded in the parent frame, wherein the embedded iframe is directed to a uniform resource locator (URL) under the first domain, and wherein an initial page at the URL to which the iframe is directed is configured to instruct a proxy to perform a remote proxy call on behalf of the iframe to obtain rendering code hosted on a central host component on a second domain different from the first domain;

obtaining, via the proxy, the rendering code hosted on the central host component on the second domain different from the first domain;

executing the rendering code, obtained via the proxy from the central host component on the second domain, in the iframe directed to the first domain that is embedded in the parent frame directed to the first domain, wherein the rendering code executing in the iframe directed to the first domain is configured to;

extract the starting address specification placed, in response to the user input received via the parent frame, in the first hidden field of the parent frame directed to the first domain;

use the starting address specification extracted from the first hidden field of the parent frame to determine a geocode location that is associated with the starting address specification; and

render, in the iframe embedded in the parent frame, display information associated with the geocode determined using the starting address specification extracted, by the rendering code executing in the iframe, from the hidden field of the parent frame;

receiving updated address information that is generated within the iframe in which the display information is rendered, wherein the updated address information is associated with an updated geocode different from the determined geocode associated with the starting address specification;

determining a reverse geocode associated with the updated address information;

passing the reverse geocode from the iframe to the parent frame at least in part by placing the reverse geocode in a second hidden field of the parent frame;

extracting the reverse geocode from the second hidden field; and

updating, using the reverse geocode extracted from the second hidden field, a transactional object used in an insurance-related workflow open in the parent frame.