A post-life forward planning system and method of use thereof

Abstract

A system and method for post-life forward planning is provided. In one form, the system includes: at least one remotely accessible server for receiving a user's post-life information data and the user's nominee information data for release of the post-life information data upon death of the user; at least one database operatively associated with the at least one remotely accessible server for storing a plurality of post-life information data and a plurality of nominee information data; and at least one external processing device programmed to: receive input from the user corresponding to the post-life information data and the nominee information data. Responsive to the death of the user, the at least one remotely accessible server is configured to retrieve the post-life information data from the plurality of post-life information data and the nominee information data from the plurality of nominee information data from the at least one database and transmit, or share, the post-life information data to or with at least one nominee based on the nominee information data retrieved. Embodiments of the disclosure also monitor a life status of the user.

Description

A POST-LIFE FORWARD PLANNING SYSTEM AND METHOD OF USE THEREOFPriority Claim

[0001] This application claims priority from Australian provisional application no 2024900072, the entire content of which is hereby incorporated by reference.Technical Field

[0002] The present disclosure pertains to a post-life forward planning system and method of use thereof.Background

[0003] Any discussion of the prior art throughout the specification should in no way be considered as an admission that such prior art is widely known or forms part of the common general knowledge in the field.

[0004] Initiating a conversation about an individual’s wishes and arrangements for when they have passed can be challenging. A common issue with organising post-life forward planning is that many individuals are hesitant to discuss, let alone consider, their plans for such events due to the perceived morbidity or discomfort it brings.

[0005] Indeed, individuals often avoid discussing their post-life forward planning preferences due to the awkwardness surrounding the topic. Generally, there is a tendency to be in denial about life expectancy, with the belief that such discussions are unnecessary because the event seems improbable or not given priority, despite its inevitability. Indeed, many individuals do not engage in post-life forward planning until late in life or not at all. However, the reality is that we can pass away at any time, and it may happen suddenly.

[0006] Some individuals are private and may hesitate to engage with a funeral home or third- party service when discussing their post-life forward planning arrangements because it makes them uncomfortable to disclose personal and private information about their death. If an individual desires to maintain confidentiality about their post-life arrangements and preferences, conventional options include handwritten documentation, digital recording on a personal device, utilising paid online storage, or engaging the services of an attorney or estate planner. Nevertheless, the individual is still required to inform a trusted individual about the storage location of these details. Challenges may arise if the deceased has sharedthis information, or if the trusted individual forgets or fails to document the precise location or accesses this information prematurely.

[0007] Consequently, close family or friends usually bear the responsibility of organising and bearing the cost of post-life arrangements. So, when a deceased person has not made postlife forward planning and preferences, it places undue emotional distress and financial burden on bereaved family and / or friends. Indeed, the planning and arranging of post-life services may become a substantial burden and distraction.

[0008] Another issue arises when the deceased has not organised or paid for their interment arrangements, such as, e.g., a burial plot, which may not be available when needed. This situation also places strain on loved ones who may feel compelled to hastily select an option.

[0009] Accordingly, family and friends left behind face the challenge of recalling and reconstructing the life and preferences of the departed for post-life forward planning. In many instances, they find themselves sifting through the individual's possessions, photo albums and personal belongings in an effort to determine what to include. Moreover, in other instances, individuals may only communicate their preferences for sentimental and emotional personal possessions verbally to their loved ones. However, this leaves the loved ones to recall these conversations, often spanning their entire life. This can lead to confusion and disagreements when recollections vary.

[0010] Disagreements among bereaved family members and / or friends may further compound emotional difficulties during this period. Decisions on the deceased’s funeral or memorial service content and presentation may be challenging, with family members attempting to discern the deceased's preferences, which can sometimes lead to emotional disagreements.

[0011] In some instances, challenges may arise if an individual chooses to place their preferences in a safety deposit box or a locked safe. This is because family or friends may encounter challenges when making arrangements during weekends or holidays, or when attempting to locate a key required to open the box; they might not even know about it or where it is located.

[0012] In some instances, challenges may arise in scenarios when an individual is approaching the end of their life due to a terminal illness and is unable to organisearrangements for a post-life service, such as, e.g., funeral or memorial service, because they are in palliative care, nursing homes, hospitals, or lack family and friends.

[0013] Moreover, some issues may arise when individuals lack the ability to write or use software to record and save post-life forward planning preferences. In these instances, a family member or friend may be asked to assist or undertake these tasks.

[0014] Further, over time, an individual may change their mind about preferred post-life forward planning preferences. Conventional methods, such as, e.g., a traditional funeral home, will, public trust, estate planner or solicitor, do not enable an individual to readily change their preferences, without incurring additional cost.

[0015] Guidance provided by funeral service providers in arranging funerals may be profit- driven rather than centred on the individual's preferences. Their guidance may prioritise financial considerations over the personalised needs of the person involved, placing their bottom line ahead of the individual's priorities. This approach may exploit the vulnerability of individuals experiencing heightened emotions and bereavement. Funeral homes may not always provide transparent pricing or adequately explain the breakdown of costs, leaving families confused or unaware of what they are paying for.

[0016] Challenges emerge when incorporating post-life planning preferences into a Will, as Wills typically do not encompass post-life planning preferences. Wills commonly focus on asset and financial management, and not everyone has a will. Moreover, even when an individual possesses a will or advanced health directive, these documents may not adequately address or encompass arrangements for post-life forward planning preferences.

[0017] The general populace typically possesses limited awareness regarding the expenses associated with post-life forward planning preferences, such as but not limited to; funeral, burial, memorial or remembrance arrangements. Frequently, their initial acquaintance with these costs occurs when a beloved individual passes away and they find themselves at a funeral home. At this point, they may become inundated by the myriad choices and layered expenses associated with these arrangements. This can lead to unexpected financial strain as they navigate post-life financial commitments, potentially making decisions under pressure and emotional distress.

[0018] Issues also arise when individuals prepay funeral planning services with a funeral home, prompting questions about the treatment of interest realised on prepaid funds placedinto a trust account. Concerns also emerge regarding the protection of individuals if the funeral home they have engaged enters administration or ceases trading.

[0019] Similarly, issues may arise with funeral homes when cancelling the contract and obtaining a full refund in the event of a change of mind. Additionally, uncertainties surround situations, such as, e.g., the relocation or passing away while away from home - some prepaid funeral plans may allow a transfer, albeit often at additional cost.

[0020] Generally speaking, many funeral contracts have rigid terms, making it challenging for families or friends to cancel or modify plans if circumstances change, which, in turn, leads to frustration and dissatisfaction. Further, funeral homes may have limited flexibility in accommodating unique requests or personalisation, which can be disheartening for families seeking a more personalised and meaningful farewell.

[0021] The lack of awareness within an individual’s family about the existence of a prepaid funeral plan may result in unfulfilled wishes, as the family may not be informed of the plan's existence, let alone the details. Consequently, the family may inadvertently end up paying for the same arrangements with a different funeral home.

[0022] Miscommunication or lack of communication between the family and the funeral home may result in misunderstandings, potentially impacting the execution of the funeral plans. This can lead to unintentional deviations from what the individual may have desired.

[0023] Eulogies are frequently crafted and expressed based on the perspective of the speaker or loved one, sharing their narratives about the departed and their own perception of the deceased. In general, such a delivery style can sometimes place more emphasis on the speaker rather than capturing the true essence of the deceased. However, this may not always correspond with the way the deceased desires to be remembered.

[0024] Hidden fees or unexpected charges may arise with traditional funeral homes, contributing to financial stress for the family.

[0025] Families may feel pressured to acquire the costliest funeral planning items, such as caskets, urns and other funeral extras, while in a state of mourning. Such impulsive spending can have an unnecessary impact on the financial well-being of loved ones after the individual has passed away.

[0026] Some individuals may possess an insurance policy that covers all funeral-related expenses. However, family members frequently lack knowledge about the existence let alone the whereabouts of this policy or the process for accessing it following the individual's demise. Additionally, uncertainties may arise regarding the policy's validity, particularly if the individual ceased paying premiums.

[0027] Accordingly, there is a need for a means to record and store an individual’s post-life forward planning preferences, enable the individual to routinely update them as desired and ensure the individual’s preferences are known to family and friends upon their passing.Summary

[0028] Embodiments of the present disclosure provide a post-life forward planning system and method of use thereof, which may at least partially address one or more of the issues, challenges, problems or deficiencies mentioned above or which may provide the public with a useful or commercial choice.

[0029] In a first embodiment, there is provided a post-life forward planning system including: at least one remotely accessible server for receiving a user’s post-life information data and the user’s nominee information data for release of the post-life information data upon death of the user; at least one database operatively associated with the at least one remotely accessible server for storing a plurality of post-life information data and a plurality of nominee information data; and at least one external processing device programmed to: receive input from the user corresponding to the post-life information data and the nominee information data; and optionally, monitor a life status of the user, wherein, responsive to the death of the user, the at least one remotely accessible server retrieves the post-life information data from the plurality of post-life information data and the nominee information data from the plurality of nominee information data from the at least one database and transmits, or shares, the post-life information data to or with at least one nominee based on the nominee information data retrieved.

[0030] Advantageously, the present disclosure provides a post-life forward planning system and method for a user to prepare and record post-life arrangements in advance, and wellbefore the actual need arises. The system provides a private platform for a user to plan without the morbidity or uncomfortableness that arises from otherwise speaking about it with family, friends and / or third party services. Moreover, embodiments of the system periodically prompt a user to update their post-life information to ensure the information remain up to date. By monitoring the life status of the user and releasing the post-life information upon the user’s death, the nominee recipients of the information can be sure that they have the deceased user’s actual post-life information and not the incorrect posthumous plans of a well meaning family member or friend.

[0031] As indicated, the post-life forward planning system of the present disclosure is designed for individuals to convey post-life information to at least one nominee upon the death of the user. It will therefore be convenient to describe the system with reference to this example application. However, a person skilled in the art will appreciate its versatility for broader applications. This innovative system has the potential to be utilised for various purposes, including data recording and management, health status monitoring, and designation notification.

[0032] Embodiment of the present disclosure offer an alternative approach to conventional funeral planning, allowing users to independently and privately record their post-life forward planning data, bypassing the conventional reliance on funeral homes or planning services. Nevertheless, it can also serve as a valuable source of information for engaging with such services either before the user’s death or posthumously via the at least one nominee.

[0033] As also indicated, the system stores and releases the post-life information of a user to the at least one nominee upon the death of the user. The at least one nominee can then use this information for post-life services and planning. Advantageously, this alleviates the at least one nominee, who is often a close loved one, from the unnecessary stress or burden of recalling these considerations during a difficult time, providing them with comprehensive answers regarding the deceased’s preferences.

[0034] As used herein, the term “post-life information” may refer to information that a user wishes to convey to the at least one nominee upon their passing.

[0035] The information may include post-life service information, including any one of funeral service preferences, memorial service preferences, service venue preferences, funeral service provider preferences, interment preferences, burial plot preferences, casket preferences, including open or closed casket preferences, urn preferences, burialpreferences, cremation preferences, location preferences, symbolic release preferences, service music preferences, preferences for service reading and / or speeches, officiate preferences, liturgy preferences, eulogy preferences, pall bearer preferences, religious preferences, cultural preferences, theme preferences, a preferred invitation list, preferred floral arrangements, preferred clothing, preferred wearables (e.g., jewellery, accessories, make-up, nails and adornments), and transport preferences.

[0036] In some embodiments, the post-life service information may include information about prepayment or any allocated funds for a service. This may include prepaid funeral planning, prepaid burial plot, insurances policies, and / or allocated funds in an account for postlife considerations.

[0037] The information may include post-life interment preferences, including any one of burial preferences, cremation preferences, location preferences, scattering preferences if cremated, information concerning any pre-purchased burial plot or place of interment, preferences for the type, style and material of casket or urn, headstone or marker preferences and epitaph preferences. The location preferences may include any one of burial plot, a scattering location, a mausoleum location, a columbarium niche location, a monument or other interment space. In some embodiments, the post-life interment preferences may include a preference as to whether the user wants to donate their body and / or parts thereof to medical or scientific research.

[0038] The information may include post-life eulogy information including memories and themes that the user desires to share. The memories may include photographs, and video and audio clips. The post-life eulogy information may include information that the user wishes to share at a post-life service. The post-life eulogy information may include personal information, history, contributions, achievements, messages of gratitude and comfort, memories, themes, photographs, videos and / or audio clips.

[0039] The information may include post-life message information for desired recipients, including any one of video messages, text-based messages and audio messages for a group, a selection or individual desired recipients.

[0040] The information may include journal and / or diary entries of the user.

[0041] The journal entries may provide a record of the user’s personal and emotional experiences. The journal entries may be structured for input from the user. For example,the journal entries may provide information concerning self-reflection, goal setting and progress tracking, going beyond personal experiences to include ideas and plans. The journal entries may provide an insight of the user’s personal growth.

[0042] The diary entries may chronicle a user’s daily occurrences, emotions and experiences. The diary entries may provide a snapshot of the user’s life with detailed and informal accounts.

[0043] The information may include post-life cadaver, organ or tissue donation information, including any one of the user’s donation preferences, information on a location of a user’s registered organ donation registration, and recipient donee preferences.

[0044] The information may include post-life possessions information, including a listing of sentimental and emotional possessions and intended recipients. Depending on the laws in a particular jurisdiction, these possessions may not be explicitly listed in a will.

[0045] The information may include post-life asset information, including a listing of assets and intended recipients. Depending on the laws of a particularly country, the listing of assets may in some cases function as a will. However, it is always important to ensure compliance with the laws of any particular jurisdiction.

[0046] The information may include post-life portfolio information, including a listing, details and / or location of banks accounts, superannuation policies, insurance policies, investment accounts, real estate holdings and accounts, including service and utility subscriptions / accounts.

[0047] The information may include post-life legal document information, including a location of any one of the last will and testament, advanced health care directive, care arrangements for dependents and power of attorneys.

[0048] The information may include post-life pet care information, including a listing of pets, pet care products, pet ownership documents, pet insurance information and intended recipients.

[0049] As indicated, the post-life forward planning system includes at least one remotely accessible server for receiving the post-life information data for release upon the death of the user.

[0050] The at least one remotely accessible server may be any appropriate server computer, distributed server computer, cloud-based server computer, server computer cluster or the like. The server may include one or more processors and one or more memory units containing executable instructions / software to be executed by the one or more processors, such as, e.g., a data processing operation.

[0051] The remotely accessible server may be configured to transmit communications to and receive communications from the at least one external processing device over a communications network, which may include, amongst others, the Internet, LANs, WANs, GPRS network, a mobile communications network, a radio network (UHF-band), etc., and may include wire and / or wireless communication links, preferably the latter.

[0052] In some embodiments, the communications may be received and transmitted via a private network connection established between the at least one remotely accessible server and the at least one external processing device.

[0053] For example, in some embodiments, the private network connection may be a secure communication session across an encrypted communication channel such as Hypertext Transfer Protocol Secure (HTTPS), Transport Layer Security / Secure Sockets Layer (TLS / SSL) or some other secure channel.

[0054] In other embodiments, the private network connection may be a VPN connection established using an encrypted layered tunnelling protocol and authentication methods, including identifiers, passwords and / or certificates.

[0055] For example, in some such embodiments, the at least one external processing device may be assigned a unique identifier that may be registered with the server. In use, the server may establish a VPN connection with the at least one external processing device upon authenticating the identifier assigned to the at least one external processing device.

[0056] In other embodiments, communications between the at least one remotely accessible server and the at least one external processing device may require authentication, such as, e.g., identifiers, passwords, captcha and / or two-factor (2FA) authentication.

[0057] As indicated, the system further includes at least one database for storing the plurality of post-life information data and the plurality of nominee information data, preferably at leastone remotely accessible database. The at least one database may further include a plurality of user data.

[0058] The plurality of post-life information data may refer to all post-life information data for all users.

[0059] The user data may include the name, address, age and contact details for an individual user. Before use, the user may need to create a profile by inputting their user data.

[0060] The user may further be asked to verify one or more components of their user data, such as, e.g., their email address, before the profile is created by the system.

[0061] The plurality of user data may refer to data corresponding to a plurality of records of individual users.

[0062] Each user may be assigned a unique identifier, such as, e.g., a profile name or number. The unique identifier may be selected by the user or may be assigned by the system.

[0063] The nominee information data may include the names and contact details of one or more nominees nominated by the user to be notified and given access to the user’s post-life information data upon the user’s death.

[0064] The nominees may be a trusted person of the user, typically selected from friends and family members of the user. However, the nominee may also be a solicitor, a doctor, a notary or other professional service, for example.

[0065] The nominee information data may further include a preferred communication method of contacting the nominee, such as, e.g., by email or text message.

[0066] In some embodiments, the nominee information data may include the name and contact details for a single nominee.

[0067] In other embodiments, the nominee information data may include the names and contact details of two or more nominees.

[0068] Generally, inputting the details of the one or more nominees, the system may transmit a confirmation message to each of the one or more nominees based on the contact details inputted requesting each of the nominees verify their confirmation to be acting as nominees.Preferably, the confirmation message may be transmitted to each of the nominees based on their preferred communication method.

[0069] Responsive to the nominee positively confirming their willingness to act as a nominee, the system may notify the user that the nominee has accepted the role.

[0070] Conversely, responsive to the nominee rejecting the role, the system may notify the user that the nominee is unwilling to act as a nominee and invite the user to input details for a substitute nominee.

[0071] In some embodiments, upon receiving the confirmation message and verifying their confirmation, the nominee may be invited to confirm or input their preferred contact details, including their preferred communication method.

[0072] In other embodiments, and upon receiving the confirmation message and verifying their confirmation, the nominee may be invited to register with the system and create a profile.

[0073] The plurality of nominee information data may refer to all the nominee information data for all users.

[0074] Each user’s nominee information data may be assigned to the unique identifier of the corresponding user.

[0075] Generally, the at least one remotely accessible server may be in communication with the at least one database.

[0076] For example, in some embodiments, the server may be linked to or may maintain all data within the at least one database. The server may collect and store post-life information data and nominee information data in the at least one database.

[0077] In some embodiments, the at least one database associated with the system may incorporate regular backup and recovery procedures as part of its operational framework. This may involve systematic measures designed to safeguard against potential data loss and mitigate the impact of unforeseen system failures.

[0078] In some embodiments, the at least one database may integrate suitable monitoring tools to proactively track database performance and generate alerts for potential issues.These monitoring mechanisms may be instrumental in maintaining the overall health and efficiency of the database.

[0079] As indicated, the system includes at least one external processing device enabling a user to interact with the system, optionally monitor a life status of the user, and, responsive to the death of the user, instruct the at least one remotely accessible server to retrieve and release the post-life information data to the one or more nominees based on the retrieved nominee information data.

[0080] The external processing device may include a computer, a tablet, a smart phone, a smart watch or a PDA, for example.

[0081] As previously mentioned, the external processing device may connect to the at least one remotely accessible server by a wired connection or a wireless connection via a wireless network (e.g., Wi-Fi (WLAN) communication, RF communication, infrared communication, or Bluetooth™), preferably the latter.

[0082] The at least one external processing device and / or the at least one remotely accessible server may include software configured to be run on the external processing device and / or the server for interacting with the system. The software may preferably be interactive.

[0083] In some embodiments, the software may include an app configured to be run on a mobile external processing device, such as, e.g., a smart phone.

[0084] In other embodiments, the software may be a software program, browser extension and / or plug-in extension configured to be run on the external processing device.

[0085] In other embodiments, the remotely accessible server may include a web server providing a graphical user interface (“GUI”) through which a user may interact with the system and the remotely accessible server via their external processing device.

[0086] The web server may accept requests, such as HTTP responses, along with optional data content, such as web pages (e.g., HTML documents) and linked objects. Generally, the web server, upon authentication, may enable the user to receive and transmit communications and commands with the remotely accessible server.

[0087] As indicated, the at least one external processing device may be programmed to receive input from a user corresponding to the post-life information data and the nominee information data.

[0088] The programming of the at least one external processing device to receive input from the user may involve implementing a user-friendly interface and establishing a secure and efficient data input process.

[0089] In some embodiments, the user-friendly interface may use a GUI with clear navigation and well-organised sections.

[0090] In some such embodiments, the software run on the external processing device may provide a question and answer form configured to elicit responses from the user to base questions to compile post-life information data, such as, e.g., any one of burial or cremation; type of post-life service (traditional, memorial celebration of life, etc.); preferred location for the post-life service; preferences for the type, style, and material and type of casket or urn; preferred rituals, prayers, and / or ceremonies in the service; preferred floral arrangements, preferred clothing, preferred transportation, and a preferred location for burial of coffin and / or scattering of ashes. In some such embodiments, the question and answer form may include a multiple-choice answer format.

[0091] In other such embodiments, the software run on the external processing device may provide one or more input fields for a user to input post-life information preferences, such as, e.g., for music, readings, and / or speeches during the funeral and / or memorial service; a preferred invitation list; and any specific wishes regarding post-funeral matters, such as, e.g., the distribution of assets, estate management, etc. Likewise, the software may provide one or more input fields for input of nominee information data, including nominee name, contact information and preferred means of contact.

[0092] In some embodiments, the software run on the external processing device may provide a guided input process that guides the user through each step of entering post-life information and nominee details. For example, in some such embodiments, the software may provide a chat bot / artificial intelligence bot configured to systematically receive, compile and input post-life information and nominee details. Specifically, it is envisaged that the chat bot may advantageously assist in compiling post-life service information data, such as, e.g., preparing a cohesive eulogy script by prompting the user to recollect essential life details.

[0093] In some embodiments, the software run on the external processing device may have an error identification function configured to identify errors in detail inputted by the user. For example, the error identification function may identify misspellings and incorrect contact details and highlight the errors for correction by the user.

[0094] In some embodiments, the software run on the external processing device may have a verification function configured to reminder users to verify details inputted by the user. For example, the verification function may require the user to verify that they have requested permission from the one or more nominees to act as nominees. Likewise, the verification function may require the user to verify the availability of a preferred burial plot or interment location, for example. Lastly, the verification function may require a user to verify any prepurchased post-life service items, such as, e.g., caskets, coffins, urns or plots.

[0095] In some embodiments, the software run on the external processing device may have an update reminder function configured periodically remind or prompt a user to check and update the post-life information data and / or nominee information data inputted. For example, the function may be configured to remind or prompt the user to check the data weekly, fortnightly, monthly, quarterly, biannually, annually or even once every two years.

[0096] In some embodiments, the software run on the external processing device may have a voice note recording function configured to record post-life notes and / or posthumous messages for people. In some such embodiments, the voice note recording function may enable the user to record a eulogy audio message.

[0097] In some embodiments, the software run on the external processing device may have a video note recording function configured to utilise at least one camera of the external processing device for recording post-life notes and / or posthumous video messages for people. In some such embodiments, the video note recording function may enable the user to record a eulogy video.

[0098] In some such embodiments, the software run on the external processing device and / or the at least one remotely accessible server may generate a written, verbal or video eulogy based on stored post-life eulogy information data. In some such embodiments, the software may utilise third-party artificial intelligence software to assist in generating the written, verbal or video eulogy.

[0099] In some embodiments, the software run on the external processing device may interact with a digital assistant provided on the device, such as, e.g., Siri, to facilitate in the inputting and / or updating of post-life information.

[0100] As indicated, in some embodiments, the at least one external processing device may monitor a life status of the user. This may be achieved in any suitable way.

[0101] In some embodiments, the at least one external processing device may include, or be in communication with, one or more sensors capable of monitoring vital signs, such as, e.g., a user’s heart rate and / or body temperature.

[0102] For example, in some such embodiments, the software running on the external processing device may periodically retrieve health data, such as, information produced by an associated devices ("wearable" or "wearables"), i.e., fitness trackers, smartwatches, smart glasses, wearable cameras, location trackers, or hearing devices.

[0103] The system may further include health monitoring devices, such as the wearables, to monitor the life status of the user. The wearables may comprise sensors to monitor health data of the user.

[0104] Upon retrieving the health data, the software may determine the life status of the user. For example, an abrupt termination in health data may be indicative that the user has died. However, in some embodiments, the software may include a wait period before determining the life status of the user to counter scenarios in which the user may not be in proximity of his or her external processing device or wearing the one or more sensors or wearable(s). The wait period may be about 3 hours, about 6 hours, about 9 hours, about 12 hours, about 15 hours, about 18 hours, about 21 hours, about 24 hours, about 27 hours, about 30 hours, about 33 hours, about 36 hours, about 39 hours, about 42 hours, about 45 hours or even about 48 hours.

[0105] In some embodiments, where analysis of the health data is indicative that the user has died, the system may prompt the user to confirm that they are alive, and may set a prescribed period for the user to respond with that confirmation before providing nominee(s) with access to the post-life information data.

[0106] In other embodiments, the at least one external processing device may track and record various user health metrics over time. Such metrics may include historical data onphysical activity, sleep patterns, and other relevant health indicators. The software running on the external processing device may implement data mining or machine learning algorithms to analyse the collected health metrics and identify patterns associated with a life status of the user.

[0107] In yet other embodiments, the external processing device or the at least one remotely accessible server may be in communication with electronic health care records and / or death records and the software running on at least one of the external processing device and the at least one remotely accessible server may cross-check user records against electronic health care records and / or death records to determine a life status of the user.

[0108] In further embodiments, the software running on the external processing device may periodically prompt a user to indicate that they are alive by acknowledging the prompt. The user may be given a prescribed period to acknowledge the prompt, such as, e.g., about 30min, about 1 hour, about 2 hours, about 3 hours, about 6 hours, about 9 hours, about 12 hours, about 15 hours, about 18 hours, about 21 hours, about 24 hours, about 27 hours, about 30 hours, about 33 hours, about 36 hours, about 39 hours, about 42 hours, about 45 hours or even about 48 hours.

[0109] Responsive to receiving a positive acknowledgment, the software may determine the user as being alive.

[0110] Conversely, responsive to not receiving an acknowledgment within the prescribed period, the software may determine the user as being deceased.

[0111] In other embodiments, the at least one remotely accessible server may receive an access request from one or more of the nominees to access the post-life information data. Responsive to receiving the request, the at least one remotely accessible server may send notification of the access request to the external processing device of the user and invite the user to reject the access request within a prescribed period. The notification of the access request may be sent by email, text message or push notification from the software running on the user’s external processing device.

[0112] Responsive to the user rejecting the access request, the software running on the external processing device may determine the user as being alive. In such scenarios, the software may block the nominee to protect the user from a data breach. The user may remove the block or re-invite the nominee to be a nominee again.

[0113] Conversely, responsive to user not rejecting the access request within the prescribed period, the software running on the external processing device may determine the user as being deceased.

[0114] Again, the prescribed period may be any suitable period of time. For example, the prescribed period may include about 30min, about 1 hour, about 2 hours, about 3 hours, about 6 hours, about 9 hours, about 12 hours, about 15 hours, about 18 hours, about 21 hours, about 24 hours, about 27 hours, about 30 hours, about 33 hours, about 36 hours, about 39 hours, about 42 hours, about 45 hours, about 48 hours, about 51 hours, about 54 hours, about 57 hours or even about 60 hours.

[0115] In some embodiments, the at least one remotely accessible server may receive an access request from one or more of the nominees to access the post-life information data together with uploaded proof of the death of the user, such as, e.g., an uploaded death certificate. Responsive to receiving the request and the proof, the at least one remotely accessible server may optionally seek verification of authenticity of the proof, before retrieving the post-life information data and the nominee information data from the at least one database and transmitting the post-life information data to the one or more nominees as determined from the nominee information data.

[0116] In embodiments in which the one or more nominees are unavailable or deceased prior to the user, the system may enable a third party to request access to the post-life information data of the user by providing proof of the user’s death and proof of their right to access the post-life information. For example, it is envisaged that the third party may gain access to the information by uploading a death certificate for the user and a copy of the will of the user indicating their role as the executor of the user’s will, if available. In other instances, the third party may satisfy their right to access the post-life information by uploading information evidencing their relationship to the user, e.g., next of kin, spouse, sibling, son or daughter.

[0117] As indicated, upon the death of the user, the at least one external processing device may instruct the remotely accessible server to retrieve the post-life information data and the nominee information data from the at least one database and transmit the post-life information data to the one or more nominees as determined from the nominee information data. Preferably, the data may be transmitted according to the one or more nominees’preference as determined from the nominee information data, such as, e.g., by email or text message.

[0118] When instructing, the external device may establish a connection to the at least one remotely accessible server. As previously mentioned, this connection may be established through secure communication protocols over the internet or another network. Then the external device may send a sequence of instructions to the remotely accessible server, specifically indicating the instructions to retrieve the post-life information data and the nominee information data. These instructions may include the unique identifier of the user or other relevant parameters for accurate data retrieval.

[0119] To ensure secure access, the external device may undergo an authentication process with the at least one remotely accessible server. This process may verify the device's identity.

[0120] The server may initiate the process of retrieving the user's post-life information data and nominee information data based on the provided instructions.

[0121] In some embodiments, the external processing device or the at least one remotely accessible server may utilise secure channels for transmitting the post-life information data to the one or more nominees. This may involve encrypted communication methods to protect the confidentiality of the data during transmission. Further, and / or alternatively, the system may implement authentication and authorisation procedures to ensure that only authorised nominees have access to the post-life information data. Typically, these procedures may involve the use of secure login credentials, multi-factor authentication, or other secure verification methods.

[0122] In some such embodiments, the software running on the external processing device may enable a user to transmit a customised selection of the post-life information data to a selected nominee of the one or more nominees. For example, the software may enable the user to transmit a video or sound message to the selected nominee, whereas the other nominees may not receive or have access to the video or sound message.

[0123] In some embodiments, the nominees may receive a unique URL to access the data. Alternatively, the nominees may be provided a shared URL but a unique password or code to access the URL. It is envisaged that the URL and password or code may only be valid for a limited period of time, adding an extra layer of security and control to the access process.The limited period of time may be any suitable period, such as, e.g., 1 week, 2 weeks, 3 weeks, 4 weeks and so on.

[0124] In some embodiments, it is envisaged that the system may provide access to, or share, the post-life information data for a period of about 12 months after the death of the user.

[0125] After the period, the post-life information data may be deleted.

[0126] The URL may serve as a direct link to the dedicated location on the remotely accessible server where the data is stored, while the password or code may act as an authentication factor, ensuring that only authorised nominees with the correct credentials may retrieve the data.

[0127] Once notified, authorised nominees may access the post-life information data by downloading it directly from the at least one remotely accessible server using the URL. This secure download process may ensure that the one or more nominees have convenient and controlled access to the relevant information, allowing them to retrieve comprehensive details about the user's post-life information.

[0128] The remotely accessible server may serve as a central repository, and the download functionality may be designed to be user-friendly while maintaining the necessary security measures to safeguard the confidentiality and integrity of the transmitted data.

[0129] In some embodiments, nominees may access the post-life information data by requesting to receive a storage media that contains the user funeral information data. In such embodiments, nominees who prefer an offline or physical copy of the information may opt to receive a storage media, such as, e.g., a USB drive, a CD or DVD, through a secure and controlled process.

[0130] In such embodiments, upon receiving a request from a nominee, the system may initiate the preparation and dispatch of the storage media. This approach may cater to nominees preferring a tangible form of documentation or who may have limited access to accessing digital content directly from the remotely accessible server.

[0131] The storage media may be packaged and sent to the designated nominee's specified address, maintaining confidentiality and adhering to privacy considerations.

[0132] Once the one or more nominees have access to the corresponding user’s post-life information data, they may commence preparations for post-life service in accordance with the user’s preferences.

[0133] In some embodiments, the post-life information data may be shared with funeral service providers via the at least one nominee. The post-life information data shared may provide a comprehensive profile of the now deceased user thereby streamlining and simplifying the funeral services offered by the funeral home.

[0134] In some embodiments, the accessed post-life information data may be used to generate and manage post-life events, including sending electronic invitations, attendee status and push notifications to invitees.

[0135] In some embodiments, the system may enable a user to link their account with third party online will storage services. The link to the user’s will may be stored in the post-life information data and may be made accessible to the one or more nominees upon the death of the user.

[0136] In some embodiments, the system may provide a link to online third party will drafting tools thereby prompting and enabling a user to draft a will when inputting post-life information data. Once the will has been drafted, the system may store a link to the will in the post-life information data as described in the preceding paragraph.

[0137] In some embodiments, the software run on the external processing device may provide links to third party services, including funeral directors, crematoriums, florists, transportation services, funeral crowdfunding services and platforms, cemeteries, catering and other service-related services.

[0138] In some embodiments, the software run on the external processing device may enable a user to instantly share their post-life information data with the at least one nominee before the user is deceased. For example, in scenarios in which the user is at least partially incapacitated or unable to use their external processing device, the at least one nominee may assist in inputting the post-life information based on the user’s input. Once the post-life information has been input, the user may or may not withdraw the nominee’s access until their death.

[0139] In some embodiments, the user may download, or obtain, a copy of their post-life information data. In some such embodiments, the user may be provided with a unique URL to download the data, as previously described. In other such embodiments, the user may request a storage medium be provided with a copy of the post-life information data stored thereon.

[0140] In some embodiments, and responsive to the user terminating their account, the software run on the external processing device may enable a user to download, or obtain, a copy of their post-life information data. As previously described, in some such embodiments, the user may be provided with a unique URL to download the data. In other such embodiments, the user may request a storage medium be provided with a copy of the postlife information data stored thereon.

[0141] According to another embodiment of the present disclosure, there is provided a postlife forward planning system including: at least one remotely accessible server for receiving a user’s post-life information data and the user’s nominee information data for release of the post-life information data upon death of the user; at least one database operatively associated with the at least one remotely accessible server for storing a plurality of post-life information data and a plurality of nominee information data; at least one sensor to monitor health data for the user; and at least one external processing device programmed to: receive input from the user corresponding to the post-life information data and the nominee information data; and receiving input from the at least one sensor to determine a life status of the user, wherein, responsive to the death of the user, the at least one remotely accessible server retrieves the post-life information data from the plurality of post-life information data and the nominee information data from the plurality of nominee information data from the at least one database and transmits, or shares, the post-life information data to or with at least one nominee based on the nominee information data retrieved.

[0142] According to another embodiment of the present disclosure, there is provided a postlife forward planning method including:receiving, by a remotely accessible server, post-life information data and nominee information data for a user; storing, by the remotely accessible server, the post-life information data and nominee information data in a database operatively associated with the remotely accessible server; monitoring, by an external processing device, the life status of the user; and responsive to the death of the user, transmitting, or sharing, the post-life information data from the database to or with at least one nominee based on the nominee information data retrieved.

[0143] According to another embodiment of the present disclosure, there is provided a method of post-life forward planning, said method including: providing the post-life forward planning system of the previously described embodiment; inputting post-life information and nominee information for a user on at least one external processing device; transmitting the post-life information and the nominee information to at least one database via at least one remotely accessible server; optionally, monitoring a life status of the user with the at least one external processing device; and responsive to the user being determined to be deceased, authorising the at least one remotely accessible server to retrieve the post-life information and the nominee information for the user from the at least one database and transmit, or share, the postlife information to or with at least one nominee as determined based on the nominee information retrieved.

[0144] The method may include one or more features or characteristics of the post-life forward planning system as hereinbefore described.

[0145] The user may input post-life information and the nominee information via the user interface of the at least one external processing device. In general, the device may be capable of recording various information, including text, audio and video of the user’s choice in predefined forms.

[0146] A user may have the flexibility to input information in multiple formats. For example, the external processing device may accommodate traditional text input, audio and video recording, and a selection of predefined templates or forms.

[0147] A user may also have the capability to modify or supplement their post-life information and nominee information through the user interface on the external processing device.

[0148] The post-life information, whether provided initially or amended, along with the nominee information, may be transmitted to a database located on, or associated with, the remotely accessible server.

[0149] As indicated, the external processing device may optionally monitor a life status of the user by gathering relevant data to infer the user's life status.

[0150] When a user has been determined to be deceased, the post-life forward planning system may initiate a response process by sending a sequence of instructions to the remotely accessible server to retrieve the post-life information of the user and the nominee information for the user.

[0151] The system may send notifications to the designated nominees using their contact information. The content of the notification may include access instructions.

[0152] Once notified, authorised nominees may access the post life information data by downloading it directly from the at least one remotely accessible server or through any other suitable method.

[0153] Any of the features described herein can be combined in any combination with any one or more of the other features described herein within the scope of the invention. It will be appreciated that, unless otherwise stated, details and variations described for one embodiment equally apply to other embodiments.

[0154] The following provides a detailed description of one or more embodiments, along with figures that illustrate their principles by example. Although these embodiments are described below, the overall scope is not limited to any one embodiment. Instead, the scope is defined the appended claims, which include various alternatives, modifications, and equivalents. To illustrate this, specific details are to give a comprehensive understanding of the disclosure.

[0155] The embodiments described below may be practised according to the claims without some or all these specific details. For clarity, technical material that is known in the technical fields related to this disclosure has not been described in detail so that the present invention is not unnecessarily obscured.Brief Description of the Drawings

[0156] Various embodiments will now be described by way of example only with reference to the accompanying drawings.

[0157]

[0158] Figure 1 a schematic showing a post-life forward planning system according to an embodiment;

[0159] Figure 2 is a schematic showing a post-life forward planning system according to another embodiment of the present disclosure;

[0160] Figure 3 is a flowchart showing steps in a post-life forward planning method according to an embodiment of the present disclosure;

[0161] Figure 4 is a flowchart showing steps in registering a user with the post-life forward planning system according to an embodiment of the present disclosure;

[0162] Figure 5 is a flowchart showing steps in inputting one or more nominees into the postlife forward planning system according to an embodiment of the present disclosure;

[0163] Figure 6 is a flowchart showing steps in accepting nomination as a nominee in the post-life forward planning system according to an embodiment of the present disclosure;

[0164] Figure 7 is a flowchart showing steps in releasing post-life information upon death of a user in the post-life forward planning system according to an embodiment of the present disclosure; and

[0165] Figure 8 is flowchart showing steps in releasing post-life information upon death of a user in the post-life forward planning system according to another embodiment of the present disclosure.

[0166] Figures 9 to 19 are flowcharts showing, in more detail, steps involved in storing and releasing post-life information in accordance with embodiments of the present disclosure.Description

[0167] Figure 1 shows an embodiment of a post-life forward planning system (100).

[0168] Referring to Figure 1 , the system (100) includes a remotely accessible server (110) for receiving a user’s (105) post-life information data and nominee information data for release upon the death of the user (105); at least one database (120) operatively associated with the at least one remotely accessible server (110) for storing a plurality of post-life information data records and a plurality of nominee information data records; and an external processing device (130).

[0169] The external processing device (130) in the form of a smartphone is programmed to: receive input from the user (105) corresponding to the user’s (105) post-life information data and nominee information data; monitor a life status of the user (105); and responsive to the death of the user (105), instruct the server (110) to retrieve the user’s (105) post-life information data from the plurality of post-life information data records and the user’s (105) nominee information data from the plurality of nominee information data records from the database (120) and share the user’s (105) post-life information data with the nominees (140) based on the user’s (105) nominee information data retrieved.

[0170] The server (110) is any one of an appropriate server computer, distributed server computer, cloud-based server computer, server computer cluster or the like. The server (110) includes one or more processors and one or more memory units containing executable instructions / software to be executed by the one or more processors, such as, e.g., a data processing operation.

[0171] The server (110) is configured to transmit communications to and receive communications from the external processing device (130) of the user (105) over a wireless communications network, including the Internet.

[0172] Communications between the at least one remotely accessible server (110) and the external processing device (130) require authentication to ensure secure communications.

[0173] As mentioned, the system (100) further includes a database (120) for storing a plurality of post-life information data records and a plurality of nominee information data records as well as a plurality of user data records.

[0174] The user data includes at least the the name, address, age and contact details for an individual user (105).

[0175] Each user (105) is assigned a unique identifier, such as, e.g., a profile name or number.

[0176] The user’s (105) post-life information data refers to information that the user (105) wises to convey to the nominees (140) - nominated trusted people of the user (105).

[0177] The post-life information data includes any one of: post-life service information; postinterment information; post-life eulogy information; post-life message information; post-life cadaver, organ or tissue donation information; post-life possession information; post-life asset information; post-life portfolio information; post-life legal document information; and post-life pet care information, as hereinbefore described.

[0178] Each individual user’s (105) post-life information data is assigned to the unique identifier of the user (105).

[0179] The user’s (105) nominee information data includes the names and contact details of the nominees (140) nominated by the user (105) to be notified and given access to the user’s (105) post-life information upon the user’s (105) death.

[0180] The nominees (140) will typically be friends, family members, a solicitor, a doctor, a notary or other professional service provider selected by the user (105).

[0181] The user’s (105) nominee information data further includes a preferred communication method of contacting the nominee (140), such as, e.g., by email or text message.

[0182] The plurality of nominee information data may refer to all the nominee information data for all users (105).

[0183] Like the post-life information data, the user’s (105) nominee information data is assigned to the unique identifier of the user (105).

[0184] The server (110) is in communication with the database (120) and is linked to or may maintain all data within the database (120). The server (110) collects and stores users’ postlife information data and users’ nominee information data in the database (120).

[0185] As indicated, the external processing device (130) enables the user (105) to interact with the system (100), monitor a life status of the user (105), and, responsive to the death of the user (105), instruct the server (110) to retrieve and release the user’s (105) post-life information data to the nominees (140) based on the retrieved user’s (105) nominee information data.

[0186] In this embodiment the external processing device (130) is a smartphone. However, the external processing device may also be a computer, a tablet, a smart watch or a PDA, for example.

[0187] As previously mentioned, the external processing device (130) connects to the server (110) by a wireless connection over a wireless network.

[0188] The external processing device (130) includes software for interacting with the system (100).

[0189] In this embodiment, the software includes an app configured to run on the external processing device (130) of the user (105), i.e., the smart phone. However, in other embodiments, the software may be a software program, browser extension and / or plug-in extension configured to be run on a computer or tablet, for example.

[0190] In yet other embodiments, the remotely accessible server (110) may include a web server providing a graphical user interface (“GUI”) through which the user (105) may interact with the system (100) and the server (110) via their external processing device (130).

[0191] As indicated, the external processing device (130) is programmed to receive input from the user (105) corresponding to the user’s (105) post-life information data and the user’s (105) nominee information data.

[0192] For some basic input, the software run on the external processing device (130) provides a question and answer form configured to elicit responses from the user (105) to base questions, such as, e.g., any one of burial or cremation; type of post-life service (traditional, memorial celebration of life, etc.); preferred location for the post-life service; preferences for the type, style, and material and type of casket or urn; preferred rituals,prayers, and / or ceremonies in the service; preferred floral arrangements, preferred clothing, preferred transportation, and a preferred location for burial of coffin and / or scattering of ashes.

[0193] For more detailed input, the software run on the external processing device (130) provides one or more input fields for the user (105) to input preferences, such as, e.g., for music, readings, and / or speeches during the post-life service; a preferred invitation list; and any specific wishes regarding post-funeral matters, such as, e.g., the distribution of assets, estate management, etc.

[0194] Likewise, the software provides one or more input fields for input of the user’s (105) nominee information data, including nominee name, contact information and preferred method of communication.

[0195] The software run on the external processing device (130) further includes an update reminder function configured periodically remind or prompt the user (105) to check and update the user’s (105) post-life information data and / or the user’s (105) nominee information data inputted.

[0196] The software has voice note recording function configured to record audio post-life notes, eulogy notes and / or posthumous audio messages for people.

[0197] Similarly, the software has a video note recording function configured to utilise a camera of the user’s (105) external processing device (130) for recording video post-life notes, video eulogy notes and / or posthumous video messages for people.

[0198] As indicated, the external processing device (130) monitors a life status of the user (105), albeit in an indirect manner in this embodiment. This is achieved by way of an access request to the server (110) from one of the nominees (140) and the server (110) in turn sending notification of the access request to the external processing device (130) of the user (105) and inviting the user (105) to reject the access request within a prescribed period.

[0199] Responsive to the user (105) rejecting the access request, the software running on the external processing device (130) determines the user (105) as being alive.

[0200] Conversely, responsive to user (105) not rejecting the access request within the prescribed period, the software determines the user (105) as being deceased.

[0201] The prescribed period will typically be a period of time ranging from 24 hours to 48 hours but may be more or less.

[0202] Upon determining that the user (105) is deceased, the external processing device (130) is programmed to instruct the server (110) to retrieve the user’s (105) post-life information data and the user’s (105) nominee information data from the database (120) and release the user’s (105) post-life information data to the nominees (140) as determined from the user’s (105) nominee information data.

[0203] In some embodiments, the software running on the external processing device (130) may enable the user (105) to transmit a customised selection of the post-life information data to a selected nominee (140A) of the nominees (140). For example, and in the embodiment illustrated, the software may release a personal video or sound message to the selected nominee (140A), whereas the other nominees (140B) may not have access to the personal video or sound message.

[0204] Generally, when sharing the user’s (105) post-life information data, the nominees (140) receive a unique URL with a password or code only valid for a limited period of time to access the data by the nominees’ preferred communication method. In this instance, nominee (140A) receives the URL via email on her computer (150A) and nominee (140B) receives the URL via text message on his smartphone (150B).

[0205] The URL serves as a direct link to the dedicated location on the server (110) where the data is stored, while the password or code acts as an authentication factor, ensuring that only authorised nominees (140) with the correct credentials can access the data.

[0206] Once notified, the nominees (140) can access the user’s (105) post-life information data by downloading it directly from the server (110) using the U RL to their respective devices (150).

[0207] In use, the server (110) serves as a central repository, and the download functionality is designed to be user-friendly while maintaining the necessary security measures to safeguard the confidentiality and integrity of the transmitted data.

[0208] Once the nominees (140) have access to the user’s (105) post-life information data, they may commence preparations for the post-life service in accordance with the user’s (105) prearranged plan.

[0209] Figure 2 shows another embodiment of a post-life forward planning system (100). For convenience, features that are similar or correspond to features of the first embodiment will be referenced with the same reference numerals.

[0210] Referring to Figure 2, the system (100) includes a cloud-based database management system (210) hosted by a remotely accessible sever associated with at least one database for receiving a user’s (105) post-life information data and nominee information data for release upon the death of the user (105) and an external processing device (130).

[0211] As shown, the external processing device (130) may be in the form of a smartphone (130A), a desktop computer (130B), a tablet (130C), a laptop computer (130D) or smartwatch (130E).

[0212] Depending on the type of external processing device (130), the device (130) can either run software in the form of an app (220) or be used to interact with a web server (230) hosted by the remotely accessible sever for interacting with the cloud-based database management system (210). The external processing device (130) may itself include sensors for monitoring health data or activity data of the user, which can be used to monitor the life status of the user. Alternatively, the external processing device (130) may be in communication with other devices, in particular wearable devices, which can monitor vital signs / health data of the user. This health data may include heart rate data, activity or movement data such as step counts, blood pressure data, body temperature data, etc.

[0213] The app (220) or web server (230) can be used to receive input from the user (105) corresponding to the user’s (105) post-life information data and nominee information data; monitor a life status of the user (105); and responsive to the death of the user (105), instruct the cloud-based database management system (210) to retrieve the user’s (105) post-life information data and the user’s (105) nominee information data and share the user’s (105) post-life information data with the nominees (140; not shown) based on the user’s (105) nominee information data retrieved.

[0214] The cloud-based database management system (210) is configured to transmit communications to and receive communications from the external processing device (130) of the user (105) over a wireless communications network, including the Internet.

[0215] Application programming interfaces (240) are provided between the cloud-based database management system (210) and the app (220) or web server (230) and betweenthe app (220) or web server (230) and the external processing device (130) for facilitating communication.

[0216] A method (300) of using the system (100) as shown in Figure 1 to post-life forward plan will now be described in detail with reference to Figure 3.

[0217] At step 310, the user (105) inputs her post-life information data and nominee information data using her external processing device (130).

[0218] The data is input via interactive app running on the external processing device (130).

[0219] Some basic information is input via a question and answer form on the app configured to elicit responses from the user (105) to base questions.

[0220] Other data is input through one or more input fields provided by the app for the user (105) to input more detailed preferences.

[0221] Lastly, some data may be input as audio or video messages recorded on the external processing device (130) and uploaded using the app.

[0222] At step 320, the user’s (105) post-life information data and nominee information data is transmitted to the server (110) via a secure connection and stored on the associated database (120).

[0223] Upon registering the nominee information data, the server (110) transmits a notification to the nominees (140) advising them that they have been designated as nominees and instructing them how the system (100) works.

[0224] At step 330, the life status of the user (105) is indirectly monitored by her external processing device (130).

[0225] The user’s (105) life status is monitored through active rejection of access requests by the nominees (140).

[0226] The monitoring works on the premise that if at least one of the nominees (140) become concerned about the user (105), or learns that the user (105) has recently deceased, they can send an access request to the server (120), which in turn will send notification of the access request to the external processing device (130) of the user (105) inviting the user (105) to reject the access request within a prescribed period.

[0227] If the user (105) is deceased and fails to reject the access request with her external processing device (130), the system (100) determines the user (105) as being deceased.

[0228] Conversely, if the nominee’s (140) concern is misplaced, and the user (105) is alive and well, the user (105) can reject the access request using her external processing device (130) and the system (100) will determine the user (105) as being alive.

[0229] Alternatively, in different embodiments, the external processing device (130) can monitor the user's life status by accessing health data of the user - either obtained directly from sensors on the external processing device (130) or obtain from external sensors devices (e.g. wearables) with which the external processing device (130) is communicating. If there is an abrupt termination of the health data, or another change indicative of death of the user (e.g. a drop in recorded body temperature), the external processing device (130) may determine that the user has died, and take subsequent steps to notify nominee(s) as outline below. Alternatively, as an interim step, the external processing device (130) may - upon receiving sensor data indicative of the user's death - prompt the user to confirm whether they are still alive (e.g. by text message, email, or push notification from the app). If the user does not reply within a prescribed period (e.g. about 3 hours, about 6 hours, about12 hours, about 24 hours, about 36 hours, about 48 hours), the system may only then consider this sufficient confirmation of the user's death and take steps to notify nominee(s). The combination of sensor data tracking physical life signs of a user, with electronic prompts and notifications, helps provide necessary checks to avoid false detections of a user's death, but still detecting or verifying a user's death in a timely manner, to simplify and help nominees manage the process, in the difficult time following a user's death.

[0230] At step 340, and responsive to the user (105) failing to reject a nominee (140) access request, the system (100) authorises the server (110) to retrieve the user’s (105) post-life information data and nominee information data and releases the data to the nominees (140) based on the nominee information data.

[0231] The nominees (140) receive a unique URL with a password or code only valid for a limited period of time to access the data by the nominees’ preferred communication method. In this instance, and as previously discussed, nominee (140A) receives the URL via email on her computer (150A) and nominee (140B) receives the URL via text message on his smartphone (150B).

[0232] The nominees (140) can access the user’s (105) post-life information data by downloading it directly from the server (110) using the URL to their respective device (150).

[0233] A method (400) of registering a user (105) with the system (100) will now be described with reference to Figure 4.

[0234] Having launched the app (210) or accessed the web server (230) on their external processing device (130), the user (105) at step 410 is presented with the option of either logging into their account or signing up.

[0235] At step 420, the user (105) agrees to the terms and conditions before inputting their name, password and email address.

[0236] At step 430, the user (105) is prompted that a confirmation email has been sent with a verification link verifying the email address entered at step 420.

[0237] At step 440, the user clicks the link in the confirmation email thereby verifying the email address.

[0238] At step 450, the app (210) or the web server (230) confirms that the email address has been successfully verified.

[0239] At step 460, the app (210) or the web server (230) prompts the user (105) to start a free trial of the system (100).

[0240] At step 470, the app (210) or the web server (230) prompts the user (105) to input a payment method for use upon conclusion of the free trial.

[0241] At step 480, the app (210) or the web server (230) confirms that a payment method has been successfully inputted.

[0242] At step 490, the app (210) or the web server (230) prompts the user (105) to input personal details before inputting two nominees (140).

[0243] A method (500) of inputting two nominees (140) with the system (100) will now be described with reference to Figure 5.

[0244] At step 510, and either through the app (210) or the web server (230), the user (105) is prompted to input the name, date of birth, email address and mobile phone number for two nominees (140).

[0245] At step 520, the app (210) or the web server (230) alerts the user (105) that the two nominees (140) have been successfully added. The app (210) further alerts the user (105) that an invitation has been sent to the nominees (140) via email to accept.

[0246] At step 530, the nominees (140) are alerted either through the app (210) if they have already downloaded the app (210) or via email that the user (105) has appointed them as a nominee and requests that they click a link to accept or deny the nomination.

[0247] A method (600) of accepting or rejecting nominee (140) appointment by a user (105) with the system (100) will now be described with reference to Figure 6.

[0248] At step 610, the nominee (140) is prompted to either accept or reject the appointment through the app (210) or the web server (230).

[0249] At step 620A and responsive to accepting the nomination, the nominee (140) is prompted through the app (210) or the web server (230) to either register as a nominee (140) through the app (210) or confirm their appointment as a nominee (140) outside the app (210).

[0250] At step 620B and responsive to rejecting the nomination, the nominee (140) is prompted through the app (210) or the web server (230) to confirm that they reject the nomination.

[0251] If the nominee (140) confirms the rejection, a notification is sent to the user (105) either through the app (210) or via email.

[0252] At step 630 and following step 620A, the nominee (140) is prompted to enter their contact details through the web server (230).

[0253] Following the entering of their details through the web server (230), a notification is sent to the user (105) either through the app (210) or via email alerting the user (105) that the nominee (140) has accepted the nomination.

[0254] A method (700) of requesting release of the post-life information upon the death of the user (105) with the system (100) will now be described with reference to Figure 7.

[0255] At step 710, the nominee (140) through the app (210) or the web server (230) inputs that they wish to unlock and release the user’s (105) post-life information.

[0256] At step 720, the app (210) or the web server (230) prompts the nominee (140) to confirm that they wish to unlock the user’s (105) post-life information.

[0257] At step 730 and responsive to the nominee (140) confirming that the wish to unlock the user’s (105) post-life information, the nominee (140) is alerted through either the app (210) or the web server (230) that a deny access request has been sent to the user (105) and that the user (105) has 48 hours to deny access to the nominee (140), otherwise the user (105) is presumed deceased and the post-life information is released to the nominee (140).

[0258] At step 740 and simultaneous with step 730, the deny access request is sent to the user (105) by email, text message and by push notification through the app (210).

[0259] Failing a response from the user (105), the deny access request is re-sent to the user (105) by email, text message and by push notification through the app (210) at 12 hours and 24 hours following the initial request from the nominee (140).

[0260] At step 750A and responsive to the user (105) denying access to the nominee (140), the user (105) and the nominee (140) are alerted by text message, email and by push notification through the app (210) that access to the post-life information is denied and that the nominee (140) has breached the terms and conditions and has been removed as a nominee (140).

[0261] At step 750B and responsive to the user (105) being deceased and incapable of denying access to the nominee (140) within the 48 hour period, an unlock authentication link is sent to the nominee (140) by email and text message.

[0262] A method (800) of requesting release of post-life information with a death certificate using the system (100) will now be described with reference to Figure 8.

[0263] At step 810, the nominee (140) through the app (210) or the web server (230) inputs that they wish to unlock and release the user’s (105) post-life information.

[0264] At step 820, the app (210) or the web server (230) prompts the nominee (140) to confirm that they wish to unlock the user’s (105) post-life information.

[0265] At step 830, the nominee (140) is prompted through the app (210) or the web server (230) to upload proof of the death of the user (105), such as, e.g., a death certificate.

[0266] At step 840 and responsive to the nominee (140) successfully uploading proof of the death of the user (105), the nominee (140) is prompted through the app (210) or the web server (230) that the upload was success and that the subsequent review of the proof can take between 12-24 hours.

[0267] In some embodiments, the uploaded proof of death may be verified by the system. For example, a death certificate may be verified by cross-checking with government databases, for recording deaths within a society. In some embodiments, the system may communicate directly with a government server to verify the death of the user, although this may not always be possible in all jurisdictions.

[0268] The format of the proof of death may vary. For example, in some embodiments, digital death certificates may be issued that can be readily parsed by the system, and may be digitally signed for authenticity. However, in many embodiments, the uploaded proof of death will be a scan or photograph of the death certificate. In that case, the death certificate may (in some embodiments) be verified by an optical character recognition (OCR) process. The scan may be pre-processed to enhance the scanned image, by for instance converting to grayscale, removing noise, or adjusting brightness or contrast. The OCR process can then be used to extract text from the certificate. The extracted text can then be parsed to segment it into identifiable fields. Fields of a death certificate, identified by the present system, may include: registration number; family name; given name; other given name(s); date of death; date of birth; cause of death; name of certifying medical practitioner or coroner, or official certifications by a Justice of the Peace (for example, statements such as "This is to certify that this is a true and complete copy of the original, which I have sighted", along with Justice of the Peace name and registration number.

[0269] If all fields of the death certificate are present and verifiable the system may determine that the proof of death is authenticated and begin to take susbsequent steps to provide postlife information data to the nominee(s). The remote processing server may immediately send a confirmation to the nominee that the proof of death has been verified and nominee access is granted. Alternatively, the remote processing server may nevertheless seek confirmation of the death by contacting the user and / or other nominees.

[0270] Parts of the verification step may be performed by either the remote server or the user external processing device.

[0271] If the death certificate cannot be verified using automatic or OCR processes, a manual process may be initiated to allow an authorised administrator to manually review the uploaded proof of death (i.e. a manual system support process). The system may send a notification to an authorised administrator to prompt them to review and verify the uploaded proof of death.

[0272] At step 850 and responsive to a successful review of the proof of death of the user (105), an unlock authentication link is sent to the nominee (140) by email and text message.

[0273] Figures 9 to 19 show, in more detail, steps according to additional embodiments of the present disclosure. Brief discussion of additional features shown in these steps is set out below.

[0274] Figures 9 to 11 depict how a particularly trusted nominee may be assigned a direct access key "DAK" enabling them to immediately access the post-life information for the user. This allows them to be pre-authorised to access the user's post-life information, upon request and entry of the DAK, thereby bypassing the ordinary proof of death requirements. This provides a fast and simple mechanism to enable a particularly trusted nominee to access necessary information, in the event of a user's death. Alternatively, all nominees may be notified of such a request.

[0275] Figures 12 and 13 depict more detail about how death certificate verification can be used to enable a nominee to upload proof of death, to allow access to the post-life information. In particular, Figure 13 provides details of a death certificate OCR analysis, allowing the system to verify the authenticity of an uploaded death certificate.

[0276] Figure 14 provides more details of the proof of life process that user's can enable, to reqularly provide proof of life via their external processing device.

[0277] Figure 15 provides steps that the system can take to send heartfelt messages, from the user to important people in their life. Of particular note, these can be set up so that they are sent without interaction from any nominee (noting many recipients of heartfelt messages may not be nominees themselves). In these embodiments, nominees are not privy to theheartfelt messages themselves, which may be in various text or multi-media forms, and may be sent or shared across various formats.

[0278] Figures 16 and 17 depict how a user may manage their nominees, and for instance toggle a nominee's access to a DAK (see Figure 16) or set up shared nominee access to all post-life information. The system may enable a user to toggle authorisations for many of the options described throughout this specification. For example, a user may specify whether any nominees receive a DAK, whether wearable devices are used to monitor the user's life status, whether regular prompts / invitations are sent for the user to verify that they are currently alive (and how often such invitations may be sent), and the ways in which nominees can access post-life information and verify the user's death.

[0279] Figure 18 provides more details in the case a nominee is notified of another nominee's request to unlock, and rejects the request. The system may handle this in different ways, for example by then requesting proof of death to be uploaded.

[0280] Figure 19 provides additional details regarding the request to unlock post-life information by a nominee, according to an embodiment of the present disclosure.

[0281] Finally, it will be appreciated that accounts within the system may be associated with people who are users in the sense used throughout this specification, but also nominees - for example, multiple members of a family may be using the system, and may be each others' nominees. The system preferably allows people, when accessing their account, to switch between viewing and managing their own post-life information, and tracking their nominee status for other users.

[0282] 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 of the present invention. Thus, the appearance 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 combinations.

[0283] Concerning the computing devices used in various embodiments described in the present disclosure, each computing device will typically include a processor in communication with a memory. The computing device can also include one or morecommunication interfaces, in communication with the processor and / or memory, capable of sending and receiving data. In several embodiments, the memory is any form of storage storing a variety of data, including, but not limited to, instructions, transaction data, blockchain data, user data and / or machine classifiers. In many embodiments, instructions, the data may be stored using an external server system and received by the computing device using the communications interface.

[0284] The processor can include one or more physical processors communicatively coupled to memory devices, input / output devices, and the like. In one illustrative example, a processor may implement a Von Neumann architectural model and may include an arithmetic logic unit (ALU), a control unit, and a plurality of registers. In many aspects, a processor may be a single core processor that is typically capable of executing one instruction at a time (or process a single pipeline of instructions) and / or a multi-core processor that may simultaneously execute multiple instructions. In a variety of aspects, a processor may be implemented as a single integrated circuit, two or more integrated circuits, and / or may be a component of a multi-chip module in which individual microprocessor dies are included in a single integrated circuit package and hence share a single socket. Memory, typically provided on each device, can include a volatile or non-volatile memory device, such as RAM, ROM, EEPROM, or any other device capable of storing data. Communication devices can include network devices (e.g., a network adapter or any other component that connects a computer to a computer network).

[0285] In an embodiment, the system is a tangible, non-transitory, machine-readable medium storing instructions that when executed by one or more processors effectuate operations as described in this specification.

[0286] Although specific architectures for computing devices per embodiments of the invention are described above, any of a variety of architectures, including those that store data or applications on disk or some other form of storage and are loaded into memory at runtime, can also be utilised. Additionally, any of the data utilised in the system can be cached and transmitted once a network connection (such as a wireless network connection via the communications interface) becomes available. In several aspects, each computing device provides an interface, such as an API or web service, which provides some or all the data to other computing devices for further processing. Access to the interface can be open and / or secured using any of a variety of techniques, such as by using client authorisation keys, as appropriate to the requirements of specific applications of the disclosure. In a variety ofembodiments, a memory includes circuitry such as, but not limited to, memory cells constructed using transistors, that store instructions. Similarly, a processor can include logic gates formed from transistors (or any other device) that dynamically perform actions based on the instructions stored in the memory. In several embodiments, the instructions are embodied in a configuration of logic gates within the processor to implement and / or perform actions described by the instructions. In this way, the systems and methods described herein can be performed utilising both general-purpose computing hardware and by single-purpose devices.

[0287] The foregoing provides one example of an embodiment of the present disclosure. However, numerous variations are possible. The present disclosure can also be implemented in numerous ways, including as processes, apparatus, systems, or (non-transitory) computer readable media.

[0288] Throughout this specification and the claims that follow unless the context requires otherwise, the words 'comprise' and 'include' and variations such as 'comprising' and 'including' will be understood to imply the inclusion of a stated integer or group of integers but not the exclusion of any other integer or group of integers.

Claims

Claims1. A post-life forward planning system including: at least one remotely accessible server for receiving a user’s post-life information data and the user’s nominee information data for release of the post-life information data upon death of the user; at least one database operatively associated with the at least one remotely accessible server for storing a plurality of post-life information data and a plurality of nominee information data; and at least one external processing device programmed to: receive input from the user corresponding to the post-life information data and the nominee information data; wherein, responsive to the death of the user, the at least one remotely accessible server retrieves the post-life information data from the plurality of post-life information data and the nominee information data from the plurality of nominee information data from the at least one database and transmits, or shares, the post-life information data to or with at least one nominee based on the nominee information data retrieved.

2. The system of claim 1, wherein the at least one external processing device is further programmed to monitor a life status of the user.

3. The system of claim 2, wherein the at least one external processing device includes, or is in communication with, one or more sensors capable of monitoring vital signs of the user.

4. The system of claim 3, wherein the one or more sensors include one or more associated wearables of the user, and the external processing device periodically retrieves health data produced by the one or more wearables to determine the life status of the user from the health data.

5. The system of claim 4, wherein the external processing device is configured, upon retrieving health data indicating that the user has died, to provide a wait period before determining that the user has died and before taking any action responsive to the death of the user.

6. The system of claim 5, wherein the wait period is about 3 hours, about 6 hours, about 9 hours, about 12 hours, about 15 hours, about 18 hours, about 21 hours,about 24 hours, about 27 hours, about 30 hours, about 33 hours, about 36 hours, about 39 hours, about 42 hours, about 45 hours or about 48 hours.

7. The system of any preceding claim, wherein the external processing device or the at least one remotely accessible server is in communication with electronic health care records and / or death records and is configured to cross-check user records against the electronic health care records and / or the death records to determine a life status of the user.

8. The system of any one of claims 2 to 7, wherein the external processing device is configured to periodically prompt a user to indicate that they are alive by acknowledging the prompt, and the external processing device determines the life status of the user based responsive to whether receiving a positive acknowledgement, or no acknowledgement, received within a prescribed period.

9. The system of any preceding claim, wherein the at least one remotely accessible server is configured to receive an access request from one or more of the nominees to access the post-life information data.

10. The system of claim 9, wherein the at least one remotely accessible server is configured, responsive to receiving the request, to send notification of the access request to the external processing device of the user; and invite the user to reject the access request within a prescribed period.

11. The system of claim 10, wherein the notification of the access request is sent by email, text message or push notification from software running on the external processing device.

12. The system of claim 9, wherein the at least one remotely accessible server is configured to receive the access request together with uploaded proof of death of the user, and is further configured to determine the life status of the user based on the uploaded proof of death.

13. The system of claim 12, wherein the remotely accessible server is further configured to verify the authenticity of the uploaded proof of death before retrievingthe post-life information data and the nominee information data from the at least one database and transmitting the post-life information data to the one or more nominees as determined from the nominee information data.

14. The system of claim 13, wherein the remotely accessible server is configured to verify the authenticity of the uploaded proof of death by cross-checking with electronic health care and / or death records.

15. The system of claim 13, wherein the remotely accessible server is configured to verify the authenticity of the uploaded proof of death by OCR analysis of the uploaded proof of death.

16. The system of any preceding claim, wherein the post-life information data includes post-life service information, including at least one of funeral service preferences, memorial service preferences, service venue preferences, funeral service provider preferences, interment preferences, burial plot preferences, casket preferences, including open or closed casket preferences, urn preferences, burial preferences, cremation preferences, location preferences, symbolic release preferences, service music preferences, preferences for service reading and / or speeches, officiate preferences, liturgy preferences, eulogy preferences, pall bearer preferences, religious preferences, cultural preferences, theme preferences, a preferred invitation list, preferred floral arrangements, preferred clothing, preferred wearables (e.g., jewellery, accessories, make-up, nails and adornments), and transport preferences.

17. The system of claim 16, wherein the post-life service information includes information at least one of prepaid funeral planning, prepaid burial plot, insurances policies, and / or allocated funds in an account for post-life considerations.

18. The system of claim 16 or 17, wherein the post-life service information includes post-life interment preferences, including at least one of burial preferences, cremation preferences, location preferences, scattering preferences if cremated, information concerning any pre-purchased burial plot or place of interment, preferences for the type, style and material of casket or urn, headstone or marker preferences and epitaph preferences.

19. The system of claim 18, wherein the post-life service information includes location preferences, and the location preferences include at least one of burial plot, a scattering location, a mausoleum location, a columbarium niche location, a monument or other interment space.

20. The system of any one of claims 16 to 19, wherein the post-life service information includes post-life eulogy information, including at least one of personal information, history, contributions, achievements, messages of gratitude and comfort, memories, themes, photographs, videos and / or audio clips.

21. The system of any one of the preceding claims, wherein the post-life information data includes post-life message information for desired recipients, including any one of video messages, text-based messages and audio messages for a group, a selection or individual desired recipients.

22. The system of any one of the preceding claims, wherein the post-life information data includes post-life cadaver, organ or tissue donation information, including any one of the user’s donation preferences, information on a location of a user’s registered organ donation registration, and recipient donee preferences.

23. The system of any one of the preceding claims, wherein the post-life information data includes post-life asset information, including a listing of assets and intended recipients.

24. The system of any one of the preceding claims, wherein the post-life information data includes post-life possessions information, including a listing of sentimental and emotional possessions and intended recipients.

25. The system of any one of the preceding claims, wherein the post-life information data includes post-life legal document information, including a location of any one of the last will and testament, advanced health care directive, care arrangements for dependents and power of attorneys.

26. The system of any preceding claim, wherein the remotely accessible server is configured to transmit communications to and receive communications from the at least one external processing device over a communications network.

27. The system of any preceding claim, wherein the at least one database further includes a plurality of user data, for a plurality of users.

28. The system of any preceding claim, wherein one or more of the nominees comprise a professional service provider, such as a solicitor, a doctor, or a notary.

29. The system of any preceding claim, wherein the nominee information data includes a preferred communication method of contacting the nominee.

30. The system of any preceding claim, wherein responsive to receiving details of the one or more nominees, the remotely accessible server is configured to: transmit a confirmation message to each of the one or more nominees requesting each of the nominees verify their confirmation to be acting as nominees; and responsive to the nominee confirming or rejecting the role, notify the user of the nominee response.

31. The system of any preceding claim, wherein a user interface on the external processing device provides a question and answer form configured to elicit responses from the user to base questions to compile post-life information data.

32. The system of any preceding claim, wherein the remotely accessible server or the external processing device further provide access to a chat bot configured to systematically receive, compile and input post-life information and nominee details.

33. The system of any preceding claim, wherein the remotely accessible server or the external processing device provides access to an artificial intelligence bot to assist in compiling a cohesive eulogy script by prompting the user to recollect essential life details.

34. The system of any preceding claim, wherein the external processing device is configured to enable a user to instantly share their post-life information data with the at least one nominee before the user is deceased.

35. A post-life forward planning system including: at least one remotely accessible server for receiving a user’s post-life information data and the user’s nominee information data for release of the post-life information data upon death of the user; at least one database operatively associated with the at least one remotely accessible server for storing a plurality of post-life information data and a plurality of nominee information data; at least one sensor to monitor health data for the user; and at least one external processing device programmed to: receive input from the user corresponding to the post-life information data and the nominee information data; and receiving input from the at least one sensor to determine a life status of the user, wherein, responsive to the death of the user, the at least one remotely accessible server retrieves the post-life information data from the plurality of post-life information data and the nominee information data from the plurality of nominee information data from the at least one database and transmits, or shares, the post-life information data to or with at least one nominee based on the nominee information data retrieved.

36. A post-life forward planning method including: receiving, by a remotely accessible server, post-life information data and nominee information data for a user; storing, by the remotely accessible server, the post-life information data and nominee information data in a database operatively associated with the remotely accessible server; monitoring, by an external processing device, the life status of the user; and responsive to the death of the user, transmitting, or sharing, the post-life information data from the database to or with at least one nominee based on the nominee information data retrieved.

37. A method of post-life forward planning, said method including:providing the post-life forward planning system of any one of the preceding claims; inputting post-life information and nominee information for a user on at least one external processing device; transmitting the post-life information and the nominee information to at least one database via at least one remotely accessible server; and responsive to the user being determined to be deceased, authorising the at least one remotely accessible server to retrieve the post-life information and the nominee information for the user from the at least one database and transmit, or share, the postlife information to or with at least one nominee as determined based on the nominee information retrieved.

Images