Note: Descriptions are shown in the official language in which they were submitted.
CA 02737734 2011-04-19
OVERLAYING IMAGES IN AUTOMATED INSURANCE POLICY
FORM GENERATION
BACKGROUND
Technical Field
This disclosure generally relates to data services, and to automated
form generation and completion.
Description of the Related Art
Insurance agents (e.g., general agents) often compile a repository of
insurance endorsement forms, organize that collection and maintain the format
and version of the forms over time separately for various different insurance
carriers. These processes consume a high number of hours of working time and,
due to the fact that many of the forms have similar appearances and file
names,
such processes can be prone to user error. The insurance carrier delegates
which forms belong on a policy and applies rules for determining when those
forms are mandatory or optional.
Some existing insurance policy issuance utilities require that the
general agent maintain insurance policy document templates (either in
electronic
or paper form) to which the user (e.g., general agent) must attach the proper
policy jackets and include the proper state specific insurance policy stamps.
Typically, a policy is provided in the form of a policy jacket including one
or more
paper documents. The time spent on this insurance policy form maintenance and
generation in the process of issuing insurance policies can add up to hundreds
of
hours wasted each year, reducing the number of policies an individual
insurance
agent can process.
BRIEF SUMMARY
A computer-implemented method may be summarized as including
receiving a first form in a first format, wherein the first form is an
electronic form
1
CA 02737734 2011-04-19
that is electronically fillable; electronically converting the first form to a
second
format to generate a second form in the second format, wherein the second form
is an electronic form that is not electronically fillable; in response to
receiving a
client request, electronically communicating the second form to be displayed
within a user interface of a client associated with the client request instead
of
electronically communicating the first form in the first format to be
displayed within
the user interface, wherein the second form as displayed within the user
interface
is substantially visually indistinguishable from the first form were the first
form to
be displayed within the user interface, and wherein the second format is a
format
such that an image file in the second format is able to have other images
visually
placed over an image stored in the image file in the second format within the
user
interface in a manner that data indicating a position of the other images
relative to
the image stored in the image file in the second format on which the other
images
are placed is able to be captured and stored using functionality of the client
or a
service accessed by the client; receiving data indicating a position of an
overlay
image overlaid on the second form, wherein the overlay image is stored in an
electronic file with the overlay image ultimately to be overlaid on an image
stored
by an electronically fillable form; and generating a third form in the first
format,
wherein the third form is an electronic form that is electronically fillable,
the
generating including incorporating the overlay image on an image stored by the
third form at a location on the image stored by the third form corresponding
to the
data indicating the position of the overlay image on the second form. The
first
format may be a format such that an image file in the first format is not able
to
have other images visually placed over an image stored in the image file in
the
first format within the user interface in such said manner relative to the
image
stored in the image file in the first format. The first format may be portable
document format and the second format is Joint Picture Expert Group format.
The method may further include at least partially electronically filling
the first form before electronically converting the first form. The first,
second and
third forms may be insurance policy forms.
2
CA 02737734 2011-04-19
The method may further include receiving insurance policy form
data; and automatically determining a list of insurance policy forms based on
the
insurance policy form data, wherein the first form is one of the insurance
policy
forms on the determined list.
The method wherein the first form, the second form and the third
form may be insurance policy forms may further include electronically
attaching
the third form to an insurance policy; and electronically communicating an
access
mechanism to the insurance policy to a user for insurance policy verification
by
the user. The overlay image may be an image of a state specific stamp for
placement on insurance policy forms.
The method may further include receiving a plurality of files storing
overlay images; and in response to receiving the client request,
electronically
communicating the plurality of files storing overlay images. the overlay
images to
be displayed within the user interface.
A system may be summarized as including a computer processor;
and a non-transitory memory communicatively coupled to the computer processor
having computer-executable instructions stored thereon that when executed by
the computer processor cause the computer processor to: receive a first form
in a
first format, wherein the first form is an electronic form that is
electronically fillable;
electronically convert the first form to a second format to generate a second
form
in the second format, wherein the second form is an electronic form that is
not
electronically fillable; in response to receiving a client request,
electronically
communicate the second form to be displayed within a user interface of a
client
associated with the client request instead of electronically communicating the
first
form in the first format to be displayed within the user interface; receive
data
indicating a position of an overlay image overlaid on the second form, wherein
the
overlay image is stored in an electronic file with the overlay image
ultimately to be
overlaid on an image stored by an electronically fillable form; and generate a
third
form in the first format, wherein the third form is an electronic form that is
electronically fillable, by incorporating the overlay image on an image stored
by
the third form at a location on the image stored by the third form
corresponding to
3
CA 02737734 2011-04-19
the data indicating the position of the overlay image on the second form. The
second form as displayed within the user interface may be substantially
visually
indistinguishable from the first form were the first form to be displayed
within the
user interface. The second format may be a format such that an image file in
the
second format may be able to have other images visually placed over an image
stored in the image file in the second format within the user interface in
such a
manner that data indicating a position of the other images relative to the
image
stored in the image file in the second format on which the other images are
placed
may be able to be captured and stored using functionality of the client or a
service
being accessed by the client. The first, second and third forms may be
insurance
policy forms.
The computer-executable instructions, when executed by the
computer processor, may further cause the computer processor to: receive
insurance policy form data; and automatically determine a list of insurance
policy
forms based on the insurance policy form data, wherein the first form is one
of the
insurance policy forms on the determined list.
The computer-executable instructions, when executed by the
computer processor, may further cause the computer processor to:
electronically
attach the third form to an insurance policy; and electronically communicate
an
access mechanism to the insurance policy to a user for insurance policy
verification by the user. The first format may be portable document format.
The
second format may be Joint Picture Expert Group format.
A non-transitory computer readable storage medium, may have
computer computer-executable instructions stored thereon that when executed by
a computer processor may cause the computer processor to perform: receiving a
selection of a first form from a plurality of forms in a first format, wherein
the
plurality of forms are electronic forms and are electronically fillable in the
first
format; displaying within a user interface of a client a second form in a
second
format, wherein the second form is the first form converted to an electronic
form
that is not electronically fillable in the second format; displaying at least
one
overlay image on the user interface, wherein the overlay image is stored in an
4
CA 02737734 2011-04-19
electronic file with the overlay image ultimately to be overlaid on an image
stored
by an electronically fillable form, the at least one overlay image available
to be
visually placed over the second form within the user interface on which the
second
form is displayed; receiving an indication of a location corresponding to a
location
on the second form on which the overlay image was visually placed within the
user interface; and electronically communicating the indication of the
location to
enable generation a third form in the first format incorporating the overlay
image
on an image stored by the third form at a location on the image stored by the
third
form corresponding to the indication of the location. The second form as
displayed in the user interface may be substantially visually
indistinguishable from
the first form, were the first form to be displayed within the client. The
first format
may be portable document format and the second format may be Joint Picture
Expert Group format.
A computer-implemented method may be summarized as including
receiving a first electronic form of a first file type that is electronically
fillable, the
first electronic form including data and fields and a having a first format,
the fields
of the first electronic form electronically fillable; generating a second
electronic
form of a second file type that is not electronically fillable, the second
electronic
form replicating the data, the fields and the format of the first electronic
form, the
fields of the second electronic form not electronically fillable, the second
file type
such that when the second electronic form is displayed by an element of a user
interface, an image represented by an image file is selectively visually
representable by the element of the user interface overlying at least a
portion of
the second electronic form at a number of end user selectable positions; in
response to receiving a client request, electronically communicating the
second
electronic form to be displayed by at least one element of a client user
interface of
a client associated with the client request instead of communicating the first
electronic form; receiving via the client data indicative of user selected
image and
a user indentified position for the image with respect to at least one element
of the
second electronic form; and generating a third electronic form of the first
file type
that is electronically fillable, the third electronic form replicating the
data, the fields
5
CA 02737734 2011-04-19
and the format of the first electronic form and including the user selected
image at
the user identified position, the fields of the first electronic form
electronically
fillable.
BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS
In the drawings, identical reference numbers identify similar
elements or acts. The sizes and relative positions of elements in the drawings
are
not necessarily drawn to scale. For example, the shapes of various elements
and
angles are not drawn to scale, and some of these elements are arbitrarily
enlarged and positioned to improve drawing legibility. Further, the particular
shapes of the elements as drawn are not intended to convey any information
regarding the actual shape of the particular elements, and have been solely
selected for ease of recognition in the drawings.
Figure 1 is a system diagram of a networked environment, in which
systems, devices and methods for overlaying of images in automated insurance
policy form generation may be a part, or in which they may be implemented,
according to one illustrated embodiment.
Figure 2 is a schematic diagram of an example computer system of
any one of the entities or systems of Figure 1, suitable for implementing
overlaying of images in automated insurance policy form generation, according
to
one illustrated embodiment.
Figure 3 is a flow diagram illustrating an automated process of
insurance policy quoting of which overlaying images in automated insurance
policy form generation may be a part, according to one illustrated embodiment.
Figure 4 is a flow diagram illustrating an automated process of
insurance policy issuance of which overlaying images in automated insurance
policy form generation may be a part, according to one illustrated embodiment.
Figure 5 is a flow diagram illustrating an automated process of
insurance policy endorsement of which overlaying images in automated insurance
policy form generation may be a part, according to one illustrated embodiment.
6
CA 02737734 2011-04-19
Figure 6 is a block diagram showing the flow of data between
components of a policy issuance system which implements overlaying of images
in automated insurance policy form generation, according to one illustrated
embodiment.
Figure 7 is a flow diagram illustrating a process of overlaying images
in automated insurance policy form generation, according to one illustrated
embodiment.
Figure 8 is a flow diagram illustrating an automated process for
generating PDF images of forms on which an image had been placed on a JPEG
version of the form, according to one illustrated embodiment.
Figure 9 is a screenshot of an example graphical user interface
within a Web browser wherein a user may search existing or create new image
sets which can be placed on forms, according to one illustrated embodiment.
Figure 10 is a screenshot of an example graphical user interface
within a Web browser wherein a user may edit a new or an existing image set by
adding different images for specific states, according to one illustrated
embodiment.
Figure 11 is a screenshot of an example graphical user interface
within a Web browser wherein a user may add an image to or modify existing
images on a form, according to one illustrated embodiment.
Figure 12 is a screenshot of an example graphical user interface
within a Web browser showing a list of the images overlaid on a particular
form.
Figure 13 is a screenshot of an example graphical user interface
within a Web browser wherein a user may drag a selected image on the form and
apply settings, according to one illustrated embodiment.
Figure 14 is a screenshot of the example graphical user interface of
Figure 13, wherein a user has selected a different image from the image set,
according to one illustrated embodiment.
7
CA 02737734 2011-04-19
DETAILED DESCRIPTION
In the following description, certain specific details are set forth in
order to provide a thorough understanding of various disclosed embodiments.
However, one skilled in the relevant art will recognize that embodiments may
be
practiced without one or more of these specific details, or with other
methods,
components, materials, etc. In other instances, well-known structures
associated
with computing systems including client and server computing systems, as well
as
networks, including various types of telecommunications networks, have not
been
shown or described in detail to avoid unnecessarily obscuring descriptions of
the
embodiments.
Unless the context requires otherwise, throughout the specification
and claims which follow, the word "comprise" and variations thereof, such as
"comprises" and "comprising," are to be construed in an open, inclusive sense,
that is, as "including, but not limited to."
Reference throughout this specification to "one embodiment" or "an
embodiment" means that a particular feature, structure or characteristic
described
in connection with the embodiment is included in at least one embodiment.
Thus,
the appearances of the phrases "in one embodiment" or "in an embodiment" in
various places throughout this specification are not necessarily all referring
to the
same embodiment. Furthermore, the particular features, structures, or
characteristics may be combined in any suitable manner in one or more
embodiments.
As used in this specification and the appended claims, the singular
forms "a," "an," and "the" include plural referents unless the content clearly
dictates otherwise. It should also be noted that the term "or" is generally
employed in its sense including "and/or" unless the content clearly dictates
otherwise.
The headings and Abstract of the Disclosure provided herein are for
convenience only and do not interpret the scope or meaning of the embodiments.
Figure 1 is a system diagram of a networked environment, in which
systems, devices and methods for overlaying images in automated insurance
8
CA 02737734 2011-04-19
policy form generation may be a part, or in which they it be implemented,
according to one illustrated embodiment.
The networked environment 100 may include one or more general
agent (e.g., insurance agent) systems, such as general agent system 1 102,
general agent system 2 104, and general agent system m 106; one or more
insurance carrier systems, such as insurance carrier system x 108 and
insurance
carrier system y 110; and a policy (e.g., insurance policy) issuance server
112.
General agent system 1 102, general agent system 2 104, general agent system
m 106, insurance carrier system x 108, insurance carrier system y 110, and the
policy issuance server 112 may all be communicatively coupled via a network
116. Alternatively, one or more of the systems or devices may be located on a
single system and/or at a single physical location. Additional systems and
devices
may also be present, but are not illustrated for clarity of presentation.
A general agent system, e.g., general agent system 102, may
include an agency information management (AIM) database 124 that stores
insurance customer or property data included, or that may be included, on an
insurance policy. Other insurance policy information may also be stored on the
AIM database 124. One or more AIM clients, such as AIM client 1 118, AIM
client
2 120 and AIM client n 122, may be communicatively connected to the AIM
database 124 such that the insurance customer data or property data can be
collected and stored in the AIM database 124 and subsequently accessed,
modified or deleted via the one or more AIM clients 118, 120, 122. For
example,
in some cases a server installation of the AIM database is shared to the AIM
clients 118, 120, 122. This may be implemented using Citrix networking
software provided by Citrix Systems, Inc. located in Fort Lauderdale, Florida.
However, other networking software may instead or also be used. The AIM
clients 118, 120, 122 retrieve raw policy data from the AIM database 124 and
convert that data into a standardized format such as Association for
Cooperative
Operations Research and Development Extensible Markup Language (ACORD
XML). That XML is sent to the policy issuance server 112 over network 116.
9
CA 02737734 2011-04-19
However, the raw data may be converted into other standardized formats
including other declarative programming language formats, among others.
The policy issuance server 112 may provide the general agent
systems 102, 104, 106 the ability to process and issue insurance policies and
policy endorsements using a policy issuance Web service of the policy issuance
server 112. The policy issuance and policy endorsement process may include
customized automated compiling, completion, validation and/or verification,
and
generation of various policy forms and forms packages originating from or
provided by the one or more insurance carriers 108, 110. This policy issuance
and policy endorsement process may be performed using insurance customer or
property data information gathered by the one or more general agent systems
102, 104, 106 and/or provided by the one or more general agent systems 102,
104, 106 to the policy issuance server 112. For example, general agent system
1
102 may electronically collect data from an insurance customer and provide
such
data to the policy issuance server 112 in a specified format. The policy
issuance
server 112 will then compile that data and automatically complete the
applicable
insurance policy forms for the particular insurance carrier (e.g., insurance
carrier
110) based on form templates generated by the policy issuance server 112,
insurance carrier 110 and/or the general agent system 102. The policy issuance
server 112 may then communicate the completed insurance policy package back
to the general agent system 102 for further verification and/or validation
before
ultimately issuing the policy. Also, the policy issuance server 112 may
provide the
ability for the user at the general agent system 102 to customize the forms
including electronically placing and overlaying state specific stamps or other
images on the applicable forms to be attached to the policy.
The network 116 may be any computer network,
telecommunications network or combination of telecommunications and computer
networks that enables communication between the various systems and entities
connected to the network 116 shown in Figure 1. General agent system 1 102,
general agent system 2 104, general agent system m 106, insurance carrier
system x 108, insurance carrier system y 110, and the policy issuance server
112
CA 02737734 2011-04-19
may be additionally or optionally linked by one or more other communication
links
or networks that comprise network 116. For example, a communications network
of network 116 may include a local area network that uses wireless fidelity
(Wi-Fi)
high frequency radio signals to transmit and receive data over distances of a
few
hundred feet. The local area network may be a wireless local area network
(WLAN) based on the Institute of Electric and Electronic Engineers (IEEE)
802.11
standards. However, other wired and wireless communications networks and
protocols may be used to link the various entities and systems shown in Figure
1.
The network 116 may comprise connections to the general agent
system 1 102, general agent system 2 104, general agent system m 106,
insurance carrier system x 108, insurance carrier system y 110, and the policy
issuance server 112 such that the policy issuance server 112 may provide the
general agent systems 102, 104, 106 the ability to process and issue insurance
policies and policy endorsements using the policy issuance Web service of the
policy issuance server 112, and may itself represent multiple interconnected
networks. For instance wired and wireless enterprise-wide computer networks,
intranets, extranets, and/or the Internet may be included in or comprise a
part of
network 116. Embodiments may include various types of communication
networks including other telecommunications networks, cellular networks, and
other mobile networks. There may be any variety of computers, switching
devices, routers, bridges, firewalls, edge devices, multiplexers, phone lines,
cables, telecommunications equipment and other devices within network 116
and/or in the communications paths between the systems and entities of Figure
1.
In accordance with an aspect of the disclosure, the systems and/or
systems shown in Figure 1 may contain discrete functional program modules that
might make use of an application programming interface (API), or other object,
software, firmware and/or hardware, to request or provide services of one or
more
of the other entities or systems within or connected to the network 116. For
example, communication can be provided over a communications medium, e.g.,
client and server systems running on any one of the systems or systems of the
entities shown in Figure 1.
11
CA 02737734 2011-04-19
These client and server systems may be communicatively coupled
to one another via transmission control protocol/internet protocol (TCP/IP)
connection(s) for high-capacity communication. The "client" is a member of a
class or group that uses the services of another class or group to which it is
not
related. In computing, a client is a process, i.e., roughly a set of
instructions or
tasks, executed by hardware that requests a service provided by another
program. Generally, the client process utilizes the requested service without
having to "know" any working details about the other program or the service
itself.
In a client/server architecture, particularly a networked system, a client is
usually a
computer or device that accesses shared network resources provided by another
computer or device, e.g., a server. Any system in Figure 1, including the
general
agent system 1 102, general agent system 2 104, general agent system m 106,
insurance carrier system x 108, insurance carrier system y 110, the policy
issuance server 112, the AIM database 124 and the one or more AIM clients 118,
120, 122, can be considered a client, a server, or both, depending on the
circumstances.
Although the physical environment of the network 116 may have
connected devices such as computers, the physical environment may
alternatively
have or be described as comprising various digital devices such as personal
digital assistants (PDAs), televisions, MP3 players, etc., software objects
such as
interfaces, Component Object Model (COM) objects and the like.
There are a variety of systems, components, and network
configurations that may also support distributed computing environments within
the network 116. For example, computing systems may be connected together
within the network 116 by wired or wireless systems, by local networks or by
widely distributed networks. Currently, many networks are coupled to the
Internet,
which provides an infrastructure for widely distributed computing and
encompasses many different networks. Any such infrastructures, whether
coupled to the Internet or not, may be used in conjunction with, be connected
to,
or comprise part of the network 116.
12
CA 02737734 2011-04-19
Figure 2 is a schematic diagram of an example computer system of
any one of the entities or systems of Figure 1, suitable for implementing
overlaying images in automated insurance policy form generation, according to
one illustrated embodiment.
The computer system 200 is suitable for implementing systems,
devices and methods for overlaying images in automated insurance policy form
generation, according to one illustrated embodiment. The computer system 200
will at times be referred to in the singular herein, but this is not intended
to limit the
embodiments to a single device since in typical embodiments, there may be more
than one computer system or devices involved. Unless described otherwise, the
construction and operation of the various blocks shown in Figure 2 are of
conventional design. As a result, such blocks need not be described in further
detail herein, as they will be understood by those skilled in the relevant
art.
The computer system 200 may include one or more processing units
212a, 212b (collectively 212), a system memory 214 and a system bus 216 that
couples various system components including the system memory 214 to the
processing units 212. The processing units 212 may be any logic processing
unit,
such as one or more central processing units (CPUs) 212a, digital signal
processors (DSPs) 212b, application-specific integrated circuits (ASICs),
programmable gate arrays such as field programmable gate arrays (FPGAs), etc.
The system bus 216 can employ any known bus structures or architectures,
including a memory bus with memory controller, a peripheral bus, and a local
bus.
The system memory 214 includes read-only memory ("ROM") 218 and random
access memory ("RAM") 220. A basic input/output system ("BIOS") 222, which
can form part of the ROM 218, contains basic routines that help transfer
information between elements within the computer system 200, such as during
start-up.
The computer system 200 may include a hard disk drive 224 for
reading from and writing to a hard disk 226, an optical disk drive 228 for
reading
from and writing to removable optical disks 232, and/or a magnetic disk drive
230
for reading from and writing to magnetic disks 234. The optical disk 232 can
be a
13
CA 02737734 2011-04-19
CD-ROM, while the magnetic disk 234 can be a magnetic floppy disk or diskette.
The hard disk drive 224, optical disk drive 228 and magnetic disk drive 230
may
communicate with the processing unit 212 via the system bus 216. The hard disk
drive 224, optical disk drive 228 and magnetic disk drive 230 may include
interfaces or controllers (not shown) coupled between such drives and the
system
bus 216, as is known by those skilled in the relevant art. The drives 224, 228
and
230, and their associated computer-readable storage media 226, 232, 234, may
provide nonvolatile and non-transitory storage of computer readable
instructions,
data structures, program modules and other data for the computer system 200.
Although the depicted computer system 200 is illustrated employing a hard disk
224, optical disk 228 and magnetic disk 230, those skilled in the relevant art
will
appreciate that other types of computer-readable storage media that can store
data accessible by a computer may be employed, such as magnetic cassettes,
flash memory, digital video disks ("DVD"), Bernoulli cartridges, RAMs, ROMs,
smart cards, etc. For example, computer-readable storage media may include,
but is not limited to, random access memory (RAM), read-only memory (ROM),
electrically erasable programmable read-only memory (EEPROM), flash memory,
compact disc ROM (CD-ROM), digital versatile disks (DVD) or other optical disk
storage, magnetic cassettes, magnetic tape, magnetic disk storage or other
magnetic storage devices, solid state memory or any other medium which can be
used to store the desired information and which may be accessed by processing
unit 212a.
Program modules can be stored in the system memory 214, such as
an operating system 236, one or more application programs 238, other programs
or modules 240 and program data 242. Application programs 238 may include
instructions that cause the processor(s) 212 to provide overlaying images in
automated insurance policy form generation such as, for example, overlaying
images in automated insurance policy form generation performed during the
policy
issuance service provided by the policy issuance server 112 based on data
received by the general agent system 102 including indications of where on a
form
an image is to be placed. The generated forms are generally printable and
14
CA 02737734 2011-04-19
include documents and printable images. Other program modules 240 may
include instructions for handling security such as password or other access
protection and communications encryption. The system memory 214 may also
include communications programs, for example, a Web client or browser 244 for
permitting the computer system 200 to access and exchange data with sources
such as Web sites of the Internet, corporate intranets, extranets, or other
networks
and devices as described herein, as well as other server applications on
server
computing systems. The browser 244 in the depicted embodiment is markup
language based, such as Hypertext Markup Language (HTML), Extensible
Markup Language (XML) or Wireless Markup Language (WML), and operates with
markup languages that use syntactically delimited characters added to the data
of
a document to represent the structure of the document. A number of Web clients
or browsers are commercially available such as those from Mozilla, Google, and
Microsoft of Redmond, Washington.
While shown in Figure 2 as being stored in the system memory 214,
the operating system 236, application programs 238, other programs/modules
240, program data 242 and browser 244 can be stored on the hard disk 226 of
the
hard disk drive 224, the optical disk 232 of the optical disk drive 228 and/or
the
magnetic disk 234 of the magnetic disk drive 230. For example, a data of
policy
forms may be stored on the hard disk drive 224, the optical disk 232 of the
optical
disk drive 228 and/or the magnetic disk 234 of the magnetic disk drive 230, as
well as one or more images which may be placed on the forms.
An operator can enter commands and information into the computer
system 200 through input devices such as a touch screen or keyboard 246 and/or
a pointing device such as a mouse 248, and/or via a graphical user interface.
Other input devices can include a microphone, joystick, game pad, tablet,
scanner, etc. These and other input devices are connected to one or more of
the
processing units 212 through an interface 250 such as a serial port interface
that
couples to the system bus 216, although other interfaces such as a parallel
port, a
game port or a wireless interface or a universal serial bus ("USB") can be
used. A
monitor 252 or other display device is coupled to the system bus 216 via a
video
CA 02737734 2011-04-19
interface 254, such as a video adapter. The computer system 200 can include
other output devices, such as speakers, printers, etc.
The computer system 200 can operate in a networked environment
using logical connections to one or more remote computers and/or devices as
described above with reference to Figure 1. For example, the computer system
200 can operate in a networked environment using logical connections to one or
more mobile devices, landline telephones and other service providers or
information servers. Communications may be via a wired and/or wireless network
architecture, for instance wired and wireless enterprise-wide computer
networks,
intranets, extranets, telecommunications networks, cellular networks, paging
networks, and other mobile networks.
Although not required, the embodiments will be described in the
general context of computer-executable instructions, such as program
application
modules, objects, or macros stored on computer- or processor-readable storage
media and executed by a computer or processor. Those skilled in the relevant
art
will appreciate that the illustrated embodiments as well as other embodiments
can
be practiced with other system configurations and/or other computing system
configurations, including hand-held devices, multiprocessor systems,
microprocessor-based or programmable consumer electronics, personal
computers ("PCs"), network PCs, mini computers, mainframe computers, and the
like. The embodiments can be practiced in distributed computing environments
where tasks or modules are performed by remote processing devices, which are
linked through a communications network such as network 116. In a distributed
computing environment, program modules may be located in both local and
remote memory storage devices.
AIM systems may offer the user built-in options to issue insurance
policies. These built-in options vary from internally generating the document
directly from policy data, to sending policy data to word processing utilities
which
generate the actual document using templates. External policy issuance
utilities
may also follow this model, and accept policy data which is then placed in pre-
defined locations and eventually produce a printable policy document in a
similar
16
CA 02737734 2011-04-19
manner. Although each of these approaches addresses certain difficulties
inherent to issuing insurance policies, there still exists the potential of
user error
surrounding the issuance process and may also involve an excessive amount of
time to maintain these systems.
Advantageously, the embodiments of the general agent system
described herein instead or additionally provide an integration library and
associated programs that produce policy data in a standardized declarative
language format (e.g., in Association for Cooperative Operations Research and
Development Extensible Markup Language (ACORD XML)), which is then
transmitted to the policy issuance server 112. Note that the transmitted XML
need
not communicate to the policy issuance server 112 where to place the data on
any
particular policy document or form, and the user (e.g., the general agent)
need not
have seen the policy form templates nor its endorsement forms prior to using
the
system. This substantially reduces potential of user error surrounding the
policy
issuance process and also reduces the amount of time to maintain the general
agent systems.
Figure 3 is a flow diagram illustrating an automated process 300 of
insurance policy quoting of which overlaying images in automated insurance
policy form generation may be a part, according to one illustrated embodiment.
The process 300 starts at 302, wherein the basic policy data is
received by the policy issuance server (e.g., in ACORD XML format). For
example, the general agent or other user may enter basic policy data into the
general agent system, and then send a request that includes the basic policy
data
to the policy issuance server for a list of required and optional policy forms
based
on the received basic policy data.
At 304, based on the received policy data, the policy issuance server
automatically determines and sends the list of required and optional policy
forms
to the general agent system. The policy issuance server may use the received
policy data to determine the listed optional forms, and those that are marked
as
required for the particular policy. The policy issuance server may
automatically
apply custom business rules for each individual insurance carrier to compile
policy
17
CA 02737734 2011-04-19
documents, automating an otherwise typically error-prone and time consuming
process. The policy issuance server may also provide the general agent the
ability to overlay or place their own images within a Web browser interface on
top
of a carrier's forms. This need may arise in instances where the general agent
wants to include state specific stamps on policy forms in accordance with
state
specific insurance laws and regulations. The policy issuance server may
automatically generate the insurance policy form templates based on forms
previously received corresponding to the applicable insurance carrier and any
customized insurance carrier forms on which stamps have been placed by the
general agent, and then populate the forms with the appropriate received basic
policy data. Alternatively, the forms may be populated with the appropriate
received basic policy data and then the general agent may customize the forms
by
electronically placing their own images within a Web browser interface on top
of
the completed forms.
At 306, for example, the general agent may select forms from the list
of required and optional policy forms and optionally overlay any state
specific
desired stamps or other images on the selected forms within a graphical user
interface of a Web browser. The forms may be accessed at the policy issuance
server, general agent system, or any other system or database in which the
forms
are stored. This process is detailed further in Figures 7-14 and the
accompanying
description.
At 308, the general agent system selects forms from the required
and optional policy forms to include on an insurance quote document. Such may
be performed via the user interface.
At 310, the policy issuance server may send a list of all forms for a
particular carrier to the general agent if requested for an additional
endorsement
to the policy being quoted. For example, if the user decides that an
endorsement
form that is not listed needs to be attached to the policy, the user can
request a
list of all of the forms the corresponding carrier has made available to the
general
agent. At this point, the general agent may again select forms from the list
of all of
the forms the corresponding carrier has made available to the general agent
and
18
CA 02737734 2011-04-19
optionally overlay any state specific desired stamps or other images on the
selected forms within a graphical user interface of a Web browser.
At 312, the general agent system electronically attaches the
selected electronic endorsement forms to the electronically stored policy. For
example, the general agent system may include the selected electronic
endorsement forms in the same folder or object in which the electronically
stored
policy is stored or associated, or may otherwise electronically associate the
selected electronic endorsement forms to the electronically stored policy.
Figure 4 is a flow diagram illustrating an automated process 400 of
insurance policy issuance of which overlaying images in automated insurance
policy form generation may be a part, according to one illustrated embodiment.
At 402, after the policy has been bound, the general agent system
may then submit the completed policy's data, exported to ACORD XML, to the
policy issuance server.
At 404, the policy issuance server automatically validates the policy
data to ensure the policy is valid. This validation may include electronically
automatically checking the policy data against formatting rules, checking for
data
integrity and checking that the data complies with applicable insurance
regulations
and policy issuance procedures.
At 406, if the policy is valid, the policy issuance server sends a
policy issuance policy identifier (policy ID) to enable the policy issuance
workflow
to be completed by the general agent. For example, this new ID is used to
generate a uniform resource locator (URL) to a Web page on the policy issuance
server that will allow the user to complete the service's issuance workflow.
At 408, based on the received policy data, the policy issuance server
automatically generates completed policy forms (e.g., in Adobe portable
document format (PDF)) when the policy workflow is completed. For example, the
policy issuance server may automatically generate the insurance policy form
templates based on forms received from the corresponding insurance carrier,
including electronically placing state specific stamps or other images on the
PDF
forms as previously indicated by the general agent system. The policy issuance
19
CA 02737734 2011-04-19
server may then populate the forms with the applicable received policy data.
Alternatively, the policy issuance server may first populate the forms with
the
applicable received policy data and then generate the final forms by
electronically
placing the state specific stamps or other images on the populated forms as
indicated by the general agent system. In another embodiment, the PDF forms
may have already had the state specific stamps or other images electronically
placed or incorporated into the PDF forms as previously indicated by the
general
agent system before policy issuance validation.
At 410, the completed policy forms are made available to the user
for verification and the policy is automatically marked issued once verified.
For
example, the general agent system polls another generated URL, again using the
policy ID, until a link to the issued policy's PDF URL is available. Once the
PDF's
link is retrieved, the PDF is downloaded, saved to the general agent system's
attachment directory, logged to the general agent system's activity log and
displayed to the user for validation. The policy can be modified and re-
issued,
and different images overlaid as needed on the various policy forms, until the
policy has been marked as issued on policy issuance server. After the policy
has
been issued and verified, the general agent can then mail out the policy
(e.g.,
physically mailing a paper form of the policy). This also marks the policy as
completed on the policy issuance server. Once the policy has been mailed out,
it
may be modified by an endorsement.
Figure 5 is a flow diagram illustrating an automated process 500 of
insurance policy endorsement of which overlaying images in automated insurance
policy form generation may be a part, according to one illustrated embodiment.
At 502, the policy issuance server receives modified policy data after
the policy is issued. For example, the general agent system may electronically
communicate updates or changes in the policy data (e.g., insured or
beneficiary
name changes, coverage changes, etc.) to the policy issuance server.
At 504, the policy issuance server automatically identifies policy
changes and validates policy data. For example, the policy issuance server may
compare the received modified policy data to the existing policy data to
identify
CA 02737734 2011-04-19
particular changes. The policy issuance server may perform the validation on
the
identified changes. The validation may include electronically automatically
checking the policy data against formatting rules, checking for data integrity
and
checking that the data complies with applicable insurance regulations and
policy
issuance procedures.
At 506, based on the received modified policy data, the policy
issuance server automatically identifies and generates completed applicable
policy endorsement forms. For example, the policy issuance server may
automatically generate the insurance policy endorsement form templates based
on forms received from the corresponding insurance carrier, including
electronically placing state specific stamps or other images on the pdf forms
as
previously indicated by the general agent system. The policy issuance server
may then populate the forms with the applicable received policy data.
Alternatively, the policy issuance server may first populate the forms with
the
applicable received policy data and then generate the final forms by
electronically
placing the state specific stamps or other images on the populated forms as
indicated by the general agent system. In another embodiment, the PDF forms
may have already had the state specific stamps or other images electronically
placed or incorporated into the pdf forms as previously indicated by the
general
agent system before modified policy data has been received or before policy
changes have been identified.
At 508, the policy issuance server automatically electronically
attaches the completed endorsement forms to the electronically stored policy.
For
example, the policy issuance server may include the completed endorsement
forms in the same folder or object in which the electronically stored policy
is stored
or associated, or may otherwise electronically associate the completed
endorsement forms to the electronically stored policy.
At 510, the completed policy forms including endorsement forms are
made available to the user for verification (e.g., by the policy issuance
server
automatically posting a link to the completed endorsement forms or sending a
link
to the completed endorsement forms to the general agent system).
21
CA 02737734 2011-04-19
Figure 6 is a block diagram showing the flow of data 600 between
components of a policy issuance system which implements overlaying of images
in automated insurance policy form generation, according to one illustrated
embodiment.
Internally, the general agent system may use mapping files 610 to
export policy data 604 retrieved from the AIM database 602 as valid ACORD XML
612. These mapping files 610 may also be formatted as XML and are distributed
with the AIM client 606 software (e.g., AIM.exe). These mapping files 610 can
be
broken into parts, which are compiled into a full map file before being
processed
by AIM client software 606. The appropriate mapping files are loaded based on
the policy's line(s) of business that are currently being exported. Before the
mapping files are processed, the raw policy data 604 is loaded into policy
objects
608 and it is these policy objects 608 that are directly mapped to ACORD XML.
The policy data may also include information indicating the location on
particular
forms of the policy on which to overlay particular images (e.g., state
specific
stamps) as well as the size of the image to be overlaid on the form.
In the mapping files 610, each of the policy objects 608 are
represented as data sources and the pieces of data held by the object are
represented as fields. The AIM client software 606 processes the map files
sequentially, allowing the map files to dictate how the policy's objects are
accessed and what data is being exported. The mapping files 610 takes these
data sources and fields, and places them into ACORD XML nodes 612. The latter
part of this process is also performed sequentially, allowing the AIM client
software 606 to adhere to the ordering of the mapped ACORD XML nodes 612.
This ACORD XML 612 is then communicated to the policy issuance Web service
614 such that policy issuance server may automatically generate the insurance
policy form templates, including incorporating any state specific stamps on
the
forms. this form generation may be based on the information indicating the
location on particular forms of the policy on which to overlay particular
images or
stamps and based on forms received from the corresponding insurance carrier or
22
CA 02737734 2011-04-19
other sources. The policy issuance Web service 614 may then populate the forms
with the applicable policy data of the received ACORD XML 612.
Figure 7 is a flow diagram illustrating a process 700 of overlaying
images in automated insurance policy form generation, according to one
illustrated embodiment.
Referring also again to Figure 1, the general agent system 102 may,
for example, use a Web browser interface to access the policy issuance server
112 and view insurance policy form templates, which are often in PDF format.
However, traditionally there has not been a way to view a PDF file in a Web
browser with the ability to overlay an image (e.g., a state specific stamp)
with
mouse control directly on top of the PDF and incorporate the overlay image
into
the PDF at the corresponding location. The process 700 described below
provides a solution to this problem that enables a general agent to use the
general
agent system 102 to visually place the image on the insurance form template
within the Web browser. In particular, the user selects the desired image to
be
placed on the form template by positioning the selected image on the form
template by clicking a mouse button while the cursor is pointing at the image
on
the image and dragging the image across the screen to the desired position on
the form template. The process 700 of overlaying images provides one
embodiment of overlaying images within a Web browser as part of or separate
from the automated policy issuance process described herein.
At 702, the applicable policy forms are received by the policy
issuance server. These may be received from the insurance carrier, general
agent or other party and may be in PDF format, for example.
At 704, the policy issuance server converts the one or more received
electronic forms stored in an electronic file from the received file type into
another
file type, e.g., from PDF format to Joint Picture Expert Group (JPEG or JPG).
For
example, the received file type format may support an electronically fillable
form
(e.g., the form stored in the file having the received file type format has
included
form related tags or metadata having to do with particular form fields
included in
the file) and the file type format into which the form is converted stores an
image
23
CA 02737734 2011-04-19
of the original electronic form, but is not electronically fillable. The
particular file
type format to which the forms are being converted, for example, is one in
which
images in such a format may have other images visually placed over them within
a graphical user interface of a Web browser, or of a Web page displayed in the
Web browser, in such a manner that the position of the other image relative to
the
image on which it is placed is captured and stored using the functionality of
the
Web browser or application being accessed by the Web browser. Also, if a
client
other than a Web browser is being used to access the forms, the particular
format
to which the forms are being converted, for example, is one in which images in
such a format may have other images visually placed over them within the
particular type of client being used in such a manner that the position of the
other
image relative to the image on which it is placed is stored using
functionality of the
particular client or application being accessed by the client.
At 706, the converted forms are displayed in the Web browser or
other client. For example, the policy issuance server responds to a request
received via the Web browser and displays the converted image or images (e.g.,
JPEG images) corresponding to a particular form received in a different format
(e.g., PDF format). In one embodiment, the general agent uses the general
agent
system to access various forms or form templates on the policy issuance server
and the policy issuance server responds by displaying the converted form or
group of forms requested within the Web browser of the general agent system.
Alternatively, the policy issuance server may wait to convert the form or form
template (e.g., from PDF to a JPEG image) until the request is received from
the
general agent system to access the particular form or form template on the
policy
issuance server. In various other embodiments, these converted forms or form
templates may be stored at the policy issuance server, general agent system,
or
any other third party system or database.
At 708, one or more of the various images (e.g., state specific
stamps) that are available to be placed on or overlaid on one or more of the
displayed converted forms are also displayed. For example, the policy issuance
server responds to a request received via the Web browser and displays images
24
CA 02737734 2011-04-19
that are available to be placed on or overlaid on one or more of the displayed
converted forms. These various images may be received from the insurance
carrier, general agent or other party and may be in various formats, for
example,
and may have also been previously converted to JPEG or other format (e.g.,
from
PDF to a JPEG image). In various other embodiments, these images may be
stored at the policy issuance server, general agent system, or any other third
party
system or database.
At 710, an indication of a location on which the overlay image is to
be overlaid on a particular form or form template is received. For example,
within
the Web browser of the general agent system, the general agent selects (e.g.,
clicks on) a particular displayed state specific stamp icon and drags the
selected
icon to a location on a particular form or form template displayed within the
Web
browser on which the general agent wants the stamp to be placed. Since the
particular form or form template displayed within the Web browser is in JPEG
format (e.g., as opposed to its original PDF format), the Web browser has the
ability to overlay an image (e.g., the state specific stamp) with mouse
control
directly on top of the form or form template displayed within the Web browser.
Thus, displaying the JPEG image of each PDF page of the form or form template
within the Web browser instead of the original PDF of the form or form
template
gives the user the impression that they are placing the overlay image directly
on
the PDF document. The size of the overlay image, color of the overlay image,
and orientation of the overlay image may also be selected and indicated within
the
Web browser.
Other embodiments may include various other ways of selecting the
overlay image using various applicable GUI controls. Also, other embodiments
may include various other ways of indicating the location on which the overlay
image is to be placed on a particular form and the size of the overlay image
including, but not limited to: entering a name or a tag of the overlay image,
directly
entering coordinates and dimensions of the overlay image, dragging a corner of
a
selection box which indicates the size and location of the overlay image, etc.
CA 02737734 2011-04-19
Figure 8 is a flow diagram illustrating an automated process for
generating PDF images of forms on which an image had been placed on the
JPEG version of the form using the process of Figure 7, according to one
illustrated embodiment.
At 802, the coordinates on the PDF form or form template on which
to place an overlay image are determined from the received indicated location
at
which the overlay image was placed on the JPEG image of the form. For
example, once the general agent had, using a mouse, selected, dragged and
dropped the overlay image on the JPEG image, the Web browser or image
application accessed by the Web browser captures the specific coordinates of
the
JPEG image underneath the overlay image and on which the overlay image is
located. These are then translated into the corresponding coordinates of the
original PDF form version of the underlying JPEG image. This translation may
be
performed by the policy issuance server or the general agent system. If
performed by the general agent system, the corresponding coordinates of the
original PDF form version of the underlying JPEG image may then be
communicated to the policy issuance server.
At 804, a new PDF form or form template corresponding to the
underlying JPEG image is generated including the overlay image placed on the
new PDF form or form template at the determined corresponding coordinates. For
example, the policy issuance server may use the corresponding coordinates of
the
original PDF version of the underlying JPEG image to use a PDF form generation
or editing tool to automatically generate the new PDF including the overlay
image
placed on the new PDF form or for template at the determined corresponding
coordinates. Alternatively, this form generation may be performed by the
general
agent system and then the general agent system may send the generated form to
the policy issuance server.
At 806, the policy issuance server then attaches the new PDF form
to the policy. In other embodiments, the electronic forms or form templates
generated from the underlying image and overlay image may be in various other
formats instead of PDF. Also, in other embodiments, instead of JPEG, the
26
CA 02737734 2011-04-19
particular format of the underlying image may be other formats which are also
formats in which images in such formats may have other images visually placed
over them within a graphical user interface of a Web browser in such a manner
that the position of the other image relative to the image on which it is
placed is
stored using the functionality of the Web browser or application being
accessed by
the Web browser. Also, if a client other than a Web browser is being used to
access the forms, the particular format of the underlying image, for example,
is
one in which images in such a format may have other images visually placed
over
them within the particular type of client being used in such a manner that the
position of the other image relative to the image on which it is placed is
stored
using functionality of the particular client or application being accessed by
the
client.
Figure 9 is a screenshot 900 of an example graphical user interface
(GUI) within a Web browser wherein a user may search existing or create new
image sets which can be placed on forms, according to one illustrated
embodiment. For example, the screenshot 900 may be of an example graphical
user interface (GUI) within a Web browser of the general agent system that is
accessing the policy issuance server. The policy issuance server may serve a
Web page shown in the screen shot 900 that is providing the GUI displayed
within
the Web browser of the general agent system. The GUI shows an image library
902 including various image sets 906. The image sets 906 may include various
images which may be overlaid (i.e., overlay images) on forms or form templates
available from the policy issuance server. For example, image sets 906 may
include state specific insurance policy form stamps organized in various
manners
such as by state. Also, shown is GUI control 904 on which the user may select
(e.g., click or otherwise) to search the image sets 906 by keyword or name and
a
GUI control 908 on which the user may select (e.g., click or otherwise) to
create a
new image set to add to the image library 902.
Figure 10 is a screenshot 1000 of a GUI within a Web browser
wherein a user may edit a new or an existing image set by adding different
images
for specific states, according to one illustrated embodiment. The GUI shows an
27
CA 02737734 2011-04-19
image set 1002 with two images, each represented by a thumbnail image 1004,
1006. A user of the GUI may add additional images by selecting the new button
1008 and uploading them accordingly. The images may be assigned by the user
to different states and shown categorized according to the different assigned
states as shown by the state column 1010 on the GUI of screenshot 1000.
Figure 11 is a screenshot 1100 of an example GUI within a Web
browser wherein a user may add an image to or modify existing images on a
particular form, according to one illustrated embodiment. The GUI includes a
view
form section 1102 which displays various editions 1104 of the form. Using the
mouse, the user may select an edit images interface control 1106 associated
with
the form for which the user is going to add an overlay image to or modify an
existing overlay image.
Figure 12 is a screenshot 1200 of an example GUI within a Web
browser showing a list of the images overlaid on a particular form. For
example,
the GUI of screenshot 1200 may be invoked when the user selects the edit
images interface control 1106 for the particular form shown in figure 11.
Image list
section 1202 of the GUI shows the list of overlay images (e.g., state specific
stamps) or image sets on or otherwise associated with the particular form
(e.g.,
form CG 22 version 0798). Also shown is an attach button 1204 which the user
may select to attach or overlay particular images of the image sets on the
underlying form. Other GUI controls may be used in addition to or instead of
those shown to indicate or invoke the corresponding actions described herein.
Figure 13 is a screenshot 1300 of an example graphical user
interface within a Web browser wherein a user may drag a selected image on the
form and apply settings, according to one illustrated embodiment. For example,
the GUI shown in screenshot 1300 may be invoked when the user selects the
attach button or icon shown in Figure 12. Shown on the GUI of screenshot 1300
is an edit area or field 1302 displaying the underlying form 1308 and is
designated
by a title indicating which underlying form is currently being edited (e.g.,
form CG
22 version 0798). Also shown are a settings panel 1314, a save button or icon
1316 and thumbnail images 1304, 1306 of corresponding overlay images
28
CA 02737734 2011-04-19
indicating that the corresponding overlay images are available to be placed on
the
underlying form 1308. The underlying form 1308 is displayed in JPEG format
such that the user may select the applicable thumbnail image indicating the
desired overlay image (e.g., state specific stamp), which will then cause the
corresponding overlay image 1310 to appear at a default location on the
underlying form 1308.
The underlying form 1308 being displayed in JPEG format within the
Web browser also allows the user to drag, with the mouse cursor 1312, the
overlay image 1310 to the desired location on the underlying form 1308 within
the
Web browser. Using the mouse cursor, the user may also resize the overlay
image 1310 by selecting (e.g., clicking) and dragging on a corner or side of
the
overlay image 1310. Alternatively, the user may select (e.g., click) and drag
the
thumbnail image 1304 itself onto the underlying form 1308 to indicate the
desired
location of the corresponding overlay image 1310. Although the underlying form
1308 displayed is actually a JPEG version of the original PDF form, it appears
to
the user that they are placing the overlay image directly on the original PDF
version of the underlying form 1308.
Figure 14 is a screenshot 1400 of the example graphical user
interface of Figure 13, wherein the user has selected a different image from
the
image set, according to one illustrated embodiment. Note that the user used
the
mouse to select the thumbnail 1306 to indicate selection of the corresponding
overlay form 1402. This is indicated by the mouse cursor 1312 on the thumbnail
image 1306. Once the user selects the different overlay image 1402 from the
image set by clicking on the corresponding thumbnail image 1306, the overlay
image 1402 replaces the previous overlay image 1310 shown selected in Figure
13 initially at the same location on the underlying form 1308 as the previous
overlay image 1310. Also, the overlay image 1402 initially has the same
selected
size as the previously selected overlay image 1310.
The settings panel 1316 on the left of the screenshot 1314 displays
the current dimensions of the overlay image 1402 and the current location of
the
overlay image 1402 on the underlying form 1308. A user may also directly enter
29
CA 02737734 2011-04-19
in the fields of the settings panel 1314 the particular desired dimensions of
the
overlay image 1402 and the desired location on the underlying form 1308 on
which to place the overlay image 1402. Also shown is a save button or icon
1316
on the settings panel 1314 which the user may select to save the current
settings.
Once the user selects the save button or icon 1316, the current settings are
saved
and the corresponding coordinates are ultimately used by the policy issuance
server to generate the final PDF version of the underlying form including the
overlay form integrated on the PDF version of the form according to the saved
settings.
The foregoing detailed description has set forth various
embodiments of the devices and/or processes via the use of block diagrams,
schematics, and examples. Insofar as such block diagrams, schematics, and
examples contain one or more functions and/or operations, it will be
understood
by those skilled in the art that each function and/or operation within such
block
diagrams, flowcharts, or examples can be implemented, individually and/or
collectively, by a wide range of hardware, software, firmware, or virtually
any
combination thereof. In one embodiment, the present subject matter may be
implemented via Application Specific Integrated Circuits (ASICs). However,
those
skilled in the art will recognize that the embodiments disclosed herein, in
whole or
in part, can be equivalently implemented in standard integrated circuits, as
one or
more computer programs running on one or more computers (e.g., as one or more
programs running on one or more computer systems), as one or more programs
running on one or more controllers (e.g., microcontrollers) as one or more
programs running on one or more processors (e.g., microprocessors), as
firmware, or as virtually any combination thereof, and that designing the
circuitry
and/or writing the code for the software and or firmware would be well within
the
skill of one of ordinary skill in the art in light of this disclosure.
In addition, those skilled in the art will appreciate that the
mechanisms taught herein are capable of being distributed as a program product
in a variety of forms, and that an illustrative embodiment applies equally
regardless of the particular type of signal bearing media used to actually
carry out
CA 02737734 2011-04-19
the distribution. Examples of non-transitory signal bearing media include, but
are
not limited to, the following: recordable type media such as floppy disks,
hard disk
drives, CD ROMs, digital tape, and computer memory including registers.
The various embodiments described above can be combined to
provide further embodiments. To the extent that they are not inconsistent with
the
specific teachings and definitions herein, all of the U.S. patents, U.S.
patent
application publications, U.S. patent applications, foreign patents, foreign
patent
applications and non-patent publications referred to in this specification are
incorporated herein by reference, in their entirety, including U.S.
Provisional
Patent Application No. 61/422,090, filed December 10, 2010. Aspects of the
embodiments can be modified, if necessary, to employ systems, circuits and
concepts of the various patents, applications and publications to provide yet
further embodiments.
These and other changes can be made to the embodiments in light
of the above-detailed description. In general, in the following claims, the
terms
used should not be construed to limit the claims to the specific embodiments
disclosed in the specification and the claims, but should be construed to
include
all possible embodiments along with the full scope of equivalents to which
such
claims are entitled. Accordingly, the claims are not limited by the
disclosure.
31
