The disclosure relates generally to a pet insurance system and method.
Pet insurance has existed for a very long time since pets often have health problems that require major surgeries, treatment and the like. However, most current pet insurance systems are very cumbersome and do not allow a pet owner to rapidly obtain the insurance. Furthermore, most of the existing systems do not provide a veterinarian or pet hospital with an easy to view status of any particular pet so that the veterinary may not know, at the time of a major surgery or treatment, if the pet is going to be covered by insurance which would be desirable. In addition, most existing pet insurance systems take so long to process a claim that both the pet owner and the veterinarian or pet hospital are unhappy with the delay.
Thus, it is desirable to provide a pet insurance system and method that overcomes the above limitations and it is to this end that the disclosure is directed.
The disclosure is particularly applicable to a client server architecture pet insurance system and it is in this context that the disclosure will be described. It will be appreciated, however, that the system and method has greater utility.
The communication path 108 may be a wired or wireless network that may be unsecure or secure and uses typical protocols for the exchange of data between the computing devices 102, 104 and the backend component 106. For example, the communication path 108 may be an Ethernet network, the Internet, a wireless cellular network, a wireless digital data network and the like and the system is not limited to any particular communication path 108. In the implementation in which the communication path 108 is the Internet, the communication path 108 may use the known HTTP or HTTPS protocol for data communications.
The backend component 106 may be implemented as one or more computing resources or hardware devices. In one implementation, the backend component 106 may be one or more server computers, one or more cloud computing resources and the like and each resource has one or more processors, memory, persistent storage and the like. The backend component 106 may further comprise a web server 106a, a pet insurance management component 106B and a storage device 110 that are coupled together as shown in
The pet insurance component 204 may be provided by the pet insurance backend system 106 and may be installed in the computing device 104 of the veterinary practice or pet hospital. The pet insurance component 204, that may be known as the Trupanion Express service (TES), is a system which integrates with these varied systems to provide added value and operational simplicity for both veterinarians and pets. The service component of TES is responsible for retrieving and mapping data from any PIMS, communicating with Trupanion Central Services (TCS) 210 about claims or certificates and communicating with Trupanion Express Client (TREX) 200. TES 204 employs various technological mechanisms to reduce the amount of traffic between TCS and TREX, as well as the PIMS creating efficient correspondence. TES 204 may include an abstracted engine that allows communication with various PIMS systems on market today, as well as the ability to integrate with more in the future in a plug-and-play fashion.
The client 200, that may be known as Trupanion Express Client (TREX), is the user interface for Trupanion Express. It communicates with TES 204 with the aim to exchange information between the hospital and the backend component 106. The client allows submitting claims, issuing certificates, searching PIMS data for pet insurance clients and appointments, mapping clients between systems, and displaying all of the information for these activities in a digestible way for hospital staff. Additionally, TREX 200 is a catalyst for better workflows and communications for hospital staff—resulting in significantly improved patient care.
The backend component 106 may further comprise a services component 210, that may be known as Trupanion Central Services, the storage device 110, known as Trupanion database system, an enrollment processing system 212 and a claim processing system 214 that are coupled to each other as shown in
In one implementation, each of the components of the backend component 106 may be a plurality of lines of computer code that are executed by a processor of the computing device 106. The services component 210 integrated with the storage device. The enrollment processing system 212 and a claim processing system 214 may interact with the storage 110 allowing certificates to be issued and activated and claims to be processed. The services component 210 is a service inside Trupanion's network that receives TES requests and passes the appropriately-formed requests on to the Trupanion Database System (TruDat) 110. The Trupanion Database System (TruDat) is any location where transactional data for Trupanion's various IT systems is stored. The Enrollment Processing System is the system that issues certificates to pet owners interested in potentially becoming a Trupanion policyholder and the claim Processing System (PO) is the system that catalogs the collection of medical records that enables claims adjudicators to manage and process pet owner claims. Trupanion Express is revolutionary in that one of its purposes is to allow claims to be adjudicated very quickly—allowing the pet owner to not pay out-of-pocket expenses at the veterinary hospital. Said another way, Trupanion Express allows Trupanion to pay veterinarians directly with PO while the customer is standing at checkout, similar to the concept of a “co-pay” in human health care. Trupanion Express allows for near real time claims submission and claims processing enabling claim adjudication at point of sale at the veterinary clinic. Versus typical channels such as fax or mail that support a delayed reimbursement model for veterinary practices or pet hospitals and/or pet owners. For additional details, see Claim A.
In addition to the process above, the system also allows the veterinary practice or pet hospital, when they want to perform a procedure or treatment, to pre-approve a pet for the treatment or procedure using a pre-approval request made through the client 200 and the express service 204 that communicates the pre-approval request to the backend component 106. In this pre-approval, the Paw Print has not been generated for the pet so it is not typically used during the pre-approval process.
Returning to
While the foregoing has been with reference to a particular embodiment of the invention, it will be appreciated by those skilled in the art that changes in this embodiment may be made without departing from the principles and spirit of the disclosure, the scope of which is defined by the appended claims.
This application is a continuation application of U.S. application Ser. No. 14/210,079, filed Mar. 13, 2014, which claims priority to and the benefit under 35 USC 119(e) and 120 of U.S. Application No. 61/801,404, filed on Mar. 15, 2013 and entitled “PET INSURANCE SYSTEM AND METHOD”, the entire contents of each are incorporated herein by reference.
Number | Name | Date | Kind |
---|---|---|---|
5720502 | Cain | Feb 1998 | A |
6117526 | Marks | Sep 2000 | A |
6966064 | Schneidewend et al. | Nov 2005 | B1 |
7155405 | Petrovich | Dec 2006 | B2 |
7266770 | Onbe et al. | Sep 2007 | B2 |
D572717 | Loehr et al. | Jul 2008 | S |
7496583 | Moore et al. | Feb 2009 | B2 |
D605653 | Danton | Dec 2009 | S |
8341547 | Ingman et al. | Dec 2012 | B2 |
8359605 | Ross | Jan 2013 | B2 |
D777737 | Marshall et al. | Jan 2017 | S |
1001353 | Marshall et al. | Jul 2018 | A1 |
20030004740 | Dickey et al. | Jan 2003 | A1 |
20040254816 | Myers | Dec 2004 | A1 |
20050060344 | Pawlick | Mar 2005 | A1 |
20050091606 | Sauermann | Apr 2005 | A1 |
20060074724 | Schwartz | Apr 2006 | A1 |
20060075724 | Kammler et al. | Apr 2006 | A1 |
20060196436 | Nichols | Sep 2006 | A1 |
20060251775 | Anderson et al. | Nov 2006 | A1 |
20070084099 | Sarbo et al. | Apr 2007 | A1 |
20070203758 | Stephens | Aug 2007 | A1 |
20080172617 | Takeda et al. | Jul 2008 | A1 |
20080307339 | Boro et al. | Dec 2008 | A1 |
20090106678 | Chase et al. | Apr 2009 | A1 |
20090182586 | Cohane | Jul 2009 | A1 |
20090289844 | Palsgrove et al. | Nov 2009 | A1 |
20090300540 | Russell | Dec 2009 | A1 |
20100017234 | Stephens et al. | Jan 2010 | A1 |
20100293487 | Schoenberg | Nov 2010 | A1 |
20110131507 | Butcher | Jun 2011 | A1 |
20120060105 | Brown et al. | Mar 2012 | A1 |
20120110453 | Ma et al. | May 2012 | A1 |
20120265702 | Maher | Oct 2012 | A1 |
20130218592 | Hashmat | Aug 2013 | A1 |
20140155785 | Haas | Jun 2014 | A1 |
20140278551 | Marshall et al. | Sep 2014 | A1 |
Number | Date | Country |
---|---|---|
2002073802 | Mar 2002 | JP |
2013022984 | Feb 2013 | JP |
WO-2006036316 | Apr 2006 | WO |
WO-2014152179 | Sep 2014 | WO |
WO-2017075207 | May 2017 | WO |
Entry |
---|
Co-pending U.S. Appl. No. 16/023,624, filed Jun. 29, 2018. |
European search report dated Dec. 9, 2016 for EP Application No. 14770490. |
International search report with written opinion dated Nov. 29, 2016 for PCT/US2016/059095. |
Notice of allowance dated May 17, 2018 for U.S. Appl. No. 14/924,606. |
Notice of allowance dated May 29, 2018 for U.S. Appl. No. 14/924,606. |
PCT/US2014/27042 International Search Report and Written Opinion dated Oct. 1, 2014. |
U.S. Appl. No. 14/210,079 Final Office Action dated Sep. 5, 2017. |
U.S. Appl. No. 14/210,079 Non-Final Office Action dated Dec. 7, 2016. |
U.S. Appl. No. 14/210,079 Non-Final Office Action dated Mar. 21, 2018. |
U.S. Appl. No. 14/924,606 Final Office Action dated Jul. 22, 2016. |
U.S. Appl. No. 14/924,606 Final Office Action dated Oct. 12, 2017. |
U.S. Appl. No. 14/924,606 Non-Final Office Action dated Jan. 12, 2017. |
U.S. Appl. No. 14/924,606 Non-Final Office Action dated Mar. 10, 2016. |
U.S. Appl. No. 29/449,619 Final Office Action dated Jul. 17, 2015. |
U.S. Appl. No. 29/449,619 Non-Final Office Action dated Oct. 3, 2014. |
U.S. Appl. No. 29/449,619 Notice of Allowance dated Sep. 13, 2016. |
Number | Date | Country | |
---|---|---|---|
20180374574 A1 | Dec 2018 | US |
Number | Date | Country | |
---|---|---|---|
61801404 | Mar 2013 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 14210079 | Mar 2014 | US |
Child | 16115446 | US |