Patent Description:
Additionally, given the possibility of messages being sent from a recipient to a blood donor being sensitive in nature, human approval during communication between receivers and providers may be needed prior to delivery of the communication.

<CIT> discloses a method for providing anonymity in a Voice-over IP (VoIP) telephony network for calls established between a calling endpoint and a called endpoint. The calling and called endpoints have respective IP addresses and can be under the control of a single IP call server or separate IP call servers. An IP address is obtained from a network address translator that is operatively connected to the IP call server. The IP call server then substitutes the IP address of the calling endpoint with the IP address obtained from the network address translator in all call signaling messages intended for the called endpoint. Conversely, the IP call server substitutes the IP address obtained from the network translator with the IP address of the calling endpoint in all call signaling messages intended for the calling endpoint. The end result is the setup and establishment of a VoIP call between the endpoints in which the actual IP address of each endpoint is unknown to the other.

Objects and features of the present invention will be more fully disclosed or rendered obvious by the following detailed description of the invention, which is to be considered together with the accompanying drawings wherein like numbers refer to like parts, and further wherein:.

Generally, providers of certain products would like to remain anonymous to a final receiver. In some cases, the final receiver of the product would like to communicate with the provider while still protecting the provider's anonymity. Given the possibility of communication being sensitive in nature, human approval during such communication may be needed prior to delivery of the communication.

Optional features are defined by the dependent claims. Viewed from a first aspect the present invention provides one or more non-transitory computer readable medium storing a set of computer executable instructions for running on one or more processors of a communication system that when executed by the one or more processors cause the communication system to establish communication from a receiver to a donor by: receiving at least one communication and an identifier from a receiver system, the receiver system being used by the receiver who received an accommodation that was donated to an intermediary from the donor, the intermediary being used by an intermediary system, the donor having contact information that remains confidential to the receiver and the receiver system and that is known to the intermediary, the identifier configured to provide identifying characteristics of the accommodation from the donor, analyzing the identifier to determine the at least one intermediary system related to the accommodation, providing the identifier to the intermediary system, receiving the contact information of the donor from the intermediary system, and transmitting the at least one communication to the donor using the contact information from the intermediary system.

Viewed from a further aspect, there is provided an automated method performed by at least one processor running computer executable instructions stored on at least one non-transitory computer readable medium, comprising receive at least one communication intended for a donor of a donated accommodation and an identifier of the donated accommodation from a receiver of the donated accommodation, analyze the identifier to determine an intermediary system having contact information for the donor, providing the identifier to the intermediary system, receiving the contact information of the donor from the intermediary system, and, transmit the at least one communication to the donor using the contact information received wherein the contact information of the donor and identity of the donor remains confidential to the receiver.

An accomodation is anything that fulfills a need or want of the receiver, such as bodily tissue (e.g., blood or organ(s)), entertainment (e.g., a play, a movie, a park), lodging, food, medication, healthcare, advice and/or assistance, or the like. The receiver may have the ability to create and/or send the communication to the provider via an online-interface with a back-end receiver look-up application program interface (API), for example. Additionally, an administrator review process may be included for review of the communication prior to delivery to the anonymous provider. In some embodiments, a repository of communications provided by the receiver may be collected and/or stored. One or more Internet servers may provide one or more graphical user interfaces (GUI), for example, for creation of one or more communications by a receiver of an accomodation from a provider. Additionally, one or more images of one or more identifying characteristics of the accomodation (e.g., encoded product information) from the provider, may be collected. In some embodiments, an administrator review process may also be used to review one or more submitted communications, communicate information regarding such communication(s) (e.g., forward approved communications to the provider), and/or archive communications (e.g., approved communications, denied communication). In some embodiments, provider information (e.g., first name, last name, e-mail, unique identifier) may be retrieved and/or requested, for example, via one or more API.

As used herein, the terms "comprises," "comprising," "includes," "including," "has," "having," or any other variation thereof, are intended to cover a non-exclusive inclusion. For example, a process, method, article, or apparatus that comprises a list of elements is not necessarily limited to only those elements but may include other elements not expressly listed or inherently present therein.

The term "and combinations thereof" as used herein refers to all permutations or combinations of the listed items preceding the term. For example, "A, B, C, and combinations thereof" is intended to include at least one of: A, B, C, AB, AC, BC, or ABC, and if order is important in a particular context, also BA, CA, CB, CBA, BCA, ACB, BAC, or CAB. A person of ordinary skill in the art will understand that typically there is no limit on the number of items or terms in any combination, unless otherwise apparent from the context.

In addition, use of the "a" or "an" are employed to describe elements and components of the embodiments herein. This is done merely for convenience and to give a general sense of the inventive concepts. This description should be read to include one or at least one and the singular also includes the plural unless it is obvious that it is meant otherwise.

The use of the terms "at least one" and "one or more" will be understood to include one as well as any quantity more than one, including but not limited to each of, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, and all integers and fractions, if applicable, therebetween. The terms "at least one" and "one or more" may extend up to <NUM> or <NUM> or more, depending on the term to which it is attached; in addition, the quantities of <NUM>/<NUM> are not to be considered limiting, as higher limits may also produce satisfactory results.

Further, as used herein any reference to "one embodiment" or "an embodiment" means that a particular element, feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment.

As used herein qualifiers such as "about," "approximately," and "substantially" are intended to signify that the item being qualified is not limited to the exact value specified, but includes some slight variations or deviations therefrom, caused by measuring error, manufacturing tolerances, stress exerted on various parts, wear and tear, and combinations thereof, for example.

Software may include one or more computer readable instructions that when executed by one or more components cause the component to perform a specified function. It should be understood that algorithms or process instructions described herein may be stored on one or more non-transitory computer readable medium. Exemplary non-transitory computer readable medium may include random access memory, read only memory, flash memory, and/or the like. Such non-transitory computer readable mediums may be electrically based, optically based, and/or the like.

Circuitry, as used herein, may be analog and/or digital components, or one or more suitably programmed processors (e.g., microprocessors) and associated hardware and software, or hardwired logic. Also, "components" may perform one or more functions. The term "component," may include hardware, such as a processor (e.g., microprocessor), an application specific integrated circuit (ASIC), field programmable gate array (FPGA), a combination of hardware and software, and/or the like. The term "processor" as used herein means a single processor or multiple processors working independently or together to collectively perform a task.

Additionally, it is to further be understood that the provider and receiver as described herein are not limited to human beings, and may comprise, an animal, a thing, a computer, a server, a website, a business entity, a human, a group of humans, a virtual computer, combinations thereof, and the like, for example.

Certain exemplary embodiments of the invention will now be described with reference to the drawings. In general, such embodiments relate to communication between a receiver and an anonymous provider of an accomodation.

Referring to the Figures, and in particular <FIG>, shown therein is a block diagram of an exemplary communication system <NUM> configured to provide one or more communications <NUM> between one or more receivers <NUM> and one or more anonymous providers <NUM> of an accomodation, which is depicted by way of example in <FIG>, as product <NUM>. Communications <NUM> may be verbal communications, written communications, and/or non-verbal communications. Additionally, communications <NUM> may be provided via text, video, audio, and/or the like. For example, the communication <NUM> may be a video of the receiver <NUM> of the accomodation saying "Thank you". In another example, the communication <NUM> may be a text message from the receiver <NUM> of the product <NUM> describing alterations in their health, death, or even inappropriate comments.

In some embodiments, one or more intermediaries <NUM> may be configured to provide a review process for the one or more communications <NUM> via one or more administrators <NUM> prior to receipt by the one or more providers <NUM> of the accomodation, such as the product <NUM>.

For simplicity in description, the following disclosure uses the exemplary communication system <NUM> in relation to blood product donors. However, as one skilled in the art will recognize, the communication system <NUM> may relate to any method wherein communications <NUM> may be intended between the receiver <NUM> and the anonymous provider <NUM> of the accomodation. For example, in charitable giving, identity of donors providing gifts to recipients may be kept anonymous (e.g., Salvation Army Angel Tree). The gifts may be made to third parties, such as municipalities or charitable organizations who provide the accomodation to the receiver(s) <NUM>. For example the anonymous provider <NUM> may make a cash donation to a charitable organization who funds and/or takes care of a park for receiver(s) <NUM>. Receiver(s) <NUM> may want to provide a communication <NUM> for the gift to the anonymous donor(s) (i.e., providers <NUM>).

Referring again to <FIG>, in the communication system <NUM> as it relates to blood product donors, the provider <NUM> may be the donor of blood product <NUM>. Generally, blood collection centers may keep personal health information when blood product <NUM> is donated. Such information may include identification information, safeguards for blood supply, testing and follow-up activities of the blood, matching information for blood product and recipients, and other donation-related activities that may be necessary for medical purposed or required by law. However, identifying characteristics of providers <NUM> of the blood products <NUM> (e.g., e-mail, home address, name) may be kept confidential (e.g., from receivers <NUM> and/or other entities). In some embodiments, the blood collection center may be the intermediary <NUM>. In some embodiments, the intermediary <NUM> may serve as an aggregate for several blood collection centers.

The provider <NUM> may donate and/or give the product <NUM>. The terms blood product <NUM> and product <NUM> may be used interchangeably herein to describe an exemplary use for the system <NUM>. The product <NUM> may be any blood product capable of being donated and/or given, such as, for example, white blood cells, red blood cells, plasma, and/or all other forms or formations of blood and/or plasma. In another example, the product <NUM> may be organ, tissue material, or other donated items.

The product <NUM> may include one or more identifiers <NUM> having one or more identifying characteristics configured to track and/or identify the product <NUM>. The identifier <NUM> may be attached, fastened to or otherwise associated with the product <NUM> for delivery from the intermediary <NUM> to the receiver <NUM>. For example, when the accomodation is a park, a movie or the like, the identifier <NUM> may be attached to a sign located on or near the park, or on a ticket or other item associated with the movie. Each identifier <NUM> may be individualized to each product <NUM>. The identifier <NUM> may include, but is not limited to, a bar code, near field communication (NFC) tag, radio frequency identification (RFID) tag, quick response (QR) code, a numeric code, an alphabetical code, an alphanumeric code and/or the like. For example, blood products <NUM> may be labelled using the ISBT <NUM> donation identification number (DIN), the global standard for identification of medical products of human origin (e.g., blood, cells, tissue, and the like). The donation identification number may be thirteen characters long, for example, and provide identifying characteristics composed of three parts: (<NUM>) Facility Identification Number (FIN) - a <NUM> character identification number assigned to a blood collection center (e.g., the intermediary <NUM>); (<NUM>) a <NUM> digit number indicating the year in which the DIN was assigned; and (<NUM>) a <NUM>-digit sequence number controlled and maintained by the blood collection center (e.g., the intermediary <NUM>). The sequence number controlled by the blood collection center (e.g., the intermediary <NUM>) may include identifying characteristics of the product <NUM> including, but not limited to, blood screeners, phlebotomists, shipping preferences, and/or the like. The identifying characteristics, however, do not provide direct contact information for the provider <NUM> (e.g., e-mail, home address, and name).

Generally, once the blood product <NUM> is collected from the provider <NUM>, and the identifier <NUM> is fastened or attached to the blood product <NUM>, the blood product <NUM> may be transferred to the receiver <NUM>. The receiver <NUM> is generally a person, animal or thing in receipt of the product <NUM>. For example, the receiver <NUM> may be a person receiving the blood product <NUM> (e.g., via a blood transfusion). Alternatively, the receiver <NUM> may be a person associated with the person, animal or thing in receipt of the blood product <NUM> (e.g., a friend or family member).

Referring to <FIG> and <FIG>, the receiver <NUM> may desire to send one or more communications <NUM> to the provider <NUM> regarding the product <NUM>. In some embodiments, the receiver <NUM> may only send one or more communications <NUM> to the provider <NUM> regarding the product <NUM>, without having any indication of their identity (including an anonymous name, a name of an avatar associated with the receiver <NUM> or the like) being disclosed to the provider <NUM>, or contracting with the provider <NUM> for the physical shipment of any item(s) or the provision of services. Contact information for the provider <NUM>, however, is to remain confidential to the receiver <NUM>, at least, and may remain confidential to other entities outside of the intermediary <NUM> and/or affiliates of the intermediary <NUM>.

Generally, the receiver <NUM> contacts the communication system <NUM> and provides the one or more communications <NUM> to the communication system <NUM>. The communication system <NUM> may then analyze the identifier <NUM> to determine the intermediary <NUM>, or affiliate of the intermediary, the provider <NUM> who may have donated or given blood product <NUM>. The identifier <NUM>, however, may not provide contact information of the provider <NUM>, or any financial information including amounts of money, credit card information, bank account information, bank routing numbers or the like. The communication system <NUM> may communicate the communication <NUM> to the intermediary <NUM> to determine contact information for the provider <NUM>. In some embodiments, the communication system <NUM> may coordinate transfer of the one or more communications <NUM> from the receiver <NUM> to the intermediary <NUM>. The intermediary <NUM>, having the contact information of the provider <NUM>, may then provide the one or more communications <NUM> to the provider <NUM>. In some embodiments, the intermediary <NUM> may provide contact information of the provider <NUM> to the communication system <NUM>. The communication system, having contact information of the provider <NUM> may then coordinate transfer of the one or more communications <NUM> from the receiver <NUM> to the provider <NUM>. In some embodiments, the intermediary <NUM> only facilitates providing the one or more communications <NUM> from the receiver <NUM> to the provider <NUM>. In some embodiments, the intermediary <NUM> does not provide financial or payment services between the receiver <NUM> and the provider <NUM>. In some embodiments, the intermediary <NUM> neither facilitates the contracting nor the delivery of one or more physical items or services from the provider <NUM> to the receiver <NUM>.

Referring to <FIG>, the receiver <NUM> may use one or more receiver systems <NUM> to communicate the one or more communications <NUM> to the communication system <NUM>. The one or more receiver systems <NUM> may include one or more processors. In some embodiments, the one or more processors may be partially or completely network-based or cloud-based. The one or more processors may or may not be located in a single physical location. Additionally, multiple processors may or may not be located in a single physical location.

In some embodiments, the receiver system <NUM> may include one or more image capturing devices capable of receiving information from a user and/or processor, and transmitting such information to the communication system <NUM>. The one or more image capturing input devices may include, but are not limited to, a cellular phone camera,.

The communication system <NUM> may be a system or systems that are able to embody and/or execute the logic of the processes described herein. Logic embodied in the form of software instructions and/or firmware may be executed on appropriate hardware. For example, logic embodied in the form of software instructions or firmware may be executed on a dedicated system or systems, a distributed processing system, and/or the like. In some embodiments, logic may be implemented in a stand-alone environment operating on a single computer system and/or logic may be implemented in a networked environment, such as a distributed system using multiple computers and/or processors. For example, a subsystem of the communication system <NUM> may be located within at and/or within the intermediary <NUM>, and another subsystem of the communication system <NUM> may be located in a data center having multiple computers, servers, and/or processors networked together.

In some embodiments, the communication system <NUM> may include one or more processors configured to communicate with the receiver system <NUM> and an intermediary system <NUM> enabling the transfer of the one or more communications <NUM> from the receiver system <NUM> to the intermediary system <NUM> for delivery to the provider <NUM>. The communication system <NUM> as shown in <FIG> has an application server <NUM> and a database server <NUM>. It should be noted that a single server or additional servers may be included. In some embodiments, one or both of the application server <NUM> and/or the database server <NUM> may be network-based, cloud-based, and variations thereof. As used herein, the terms "network-based", "cloud based", and any variations thereof, may include the provision of configurable computational resources on demand via interfacing with a computer and/or computer network, with software and/or data at least partially located on the computer and/or computer network, by pooling processing power of two or more networked processors.

The communication system <NUM> may be capable of interfacing and/or communicating with the receiver system <NUM> and/or the intermediary system <NUM> via a network <NUM>. Additionally, the application server <NUM> and the database server <NUM> may be capable of communicating with each other via the network <NUM>.

The network <NUM> may be almost any type of network. For example, the network <NUM> may interface by optical and/or electronic interfaces, and/or may use a plurality of network topographies and/or protocols including, but not limited to, Ethernet, TCP/IP, circuit switched paths, and/or combinations thereof. For example, in some embodiments, the network <NUM> may be implemented as the World Wide Web (or Internet), a local area network (LAN), a wide area network (WAN), a metropolitan network, a wireless network, a cellular network, a Global System for Mobile Communications (GSM) network, a code division multiple access (CDMA) network, a <NUM> network, a <NUM> network, a satellite network, a radio network, an optical network, a cable network, a public switched telephone network, an Ethernet network, combinations thereof, and/or the like. Additionally, the network <NUM> may use a variety of network protocols to permit bi-directional interface and/or communication of data and/or information. It is conceivable that in the near future, embodiments of the present disclosure may use more advanced networking topologies.

In some embodiments, the network <NUM> may be the Internet and/or other network. For example, if the network <NUM> is the Internet, a primary user interface of the donor communication delivery software may be delivered through a series of web pages. It should be noted that the primary user interface of the donor communication delivery software may be replaced by another type of interface, such as, for example, a Windows-based application.

The application server <NUM> and the database server <NUM> may be capable of reading and/or executing processor executable code and/or capable of creating, manipulating, retrieving, altering and/or storing data structures into one or more memories. The one or more memories may be capable of storing processor executable code. Additionally, the one or more memories may be implemented as a conventional non-transitory memory, such as, for example, random access memory (RAM), a CD-ROM, a hard drive, a solid state drive, a flash drive, a memory card, a DVD-ROM, a floppy disk, an optical drive, combinations thereof, and/or the like, for example.

In some embodiments, the one or more memories may be located in the same physical location. Alternatively, one or more memories may be located in a different location as the communication system <NUM> and communicating via a network, such as the network <NUM>. Additionally, one or more of the memories may be implemented as a "cloud memory" (i.e., one or more memories may be partially or completely based on or accessed using a network, such as network <NUM>, for example).

The one or more memories may store processor executable code and/or information comprising one or more databases and program logic. In some embodiments, the processor executable code may be stored as a data structure, such as a part of database and/or data table, for example. In some embodiments, one of the databases may be an identifier database storing identifying characteristics analyzed and determined from the identifier <NUM> of the product <NUM>. In some embodiments, one of the databases may be a communication database storing one or more communications <NUM> received from the receiver system <NUM>. In some embodiments, one of the databases may be an image database storing images of one or more identifiers <NUM>. In some embodiments, one of the databases may be an archive communication database, storing one or more archived communications <NUM>. In some embodiments, one of the databases may be a rejected communication database, storing one or more rejected communications <NUM>. In some embodiments, one of the databases may be a receiver database, storing one or more characteristics of receivers <NUM>.

Generally, program logic of the communication system <NUM> may decode one or more identifiers <NUM> associated with the product <NUM> to identify one or more intermediaries <NUM>. For example, using the <NUM>-digit code from the identifier <NUM>, the communication system <NUM> may extract the first <NUM> digits to determine the intermediary <NUM>. Through identification of the one or more intermediaries <NUM>, the communication system <NUM> may contact the intermediary <NUM> and, in some embodiments, query the intermediary <NUM> for information regarding the provider <NUM> by using the remaining <NUM> digits of the identifier <NUM>. The intermediary <NUM> may use the identifier <NUM> to determine further information related the provider <NUM>, including contact information. In some embodiments, the intermediary <NUM> may transmit the additional information to the communication system <NUM>. In some embodiments, the administrator <NUM> associated with the intermediary <NUM> may have access to the communication system <NUM> for review of the one or more communications <NUM> prior to transmission of the communications <NUM> to the provider <NUM>.

In some embodiments, the communication system <NUM> may communicate with the intermediary system <NUM> via a representational state transfer (Restful Service) API <NUM>. To that end, the Restful Service API may communicate with the intermediary system <NUM>. The intermediary system <NUM>, in some embodiments, may include an intermediary API <NUM> for communicating with one or more processors <NUM> of the intermediary system <NUM>. In some embodiments, a firewall <NUM> may exist between the Restful Service API <NUM> and the intermediary system <NUM>. In some embodiments, the intermediary system <NUM> may be safeguarded behind the firewall <NUM>. It should be noted that the communication system <NUM> may communicate with the intermediary system <NUM> via other methods including, but not limited to, simple object access protocol (SOAP), direct communication, and/or the like.

The intermediary system <NUM> may include one or more processors <NUM> and/or computer systems. In some embodiments, the one or more processors <NUM> and/or computer systems may be partially or completely network-based or cloud-based. The one or more processors <NUM> and/or computer systems may or may not be located in a single physical location. Additionally, multiple processors may or may not be located in a single physical location.

In some embodiments, the administrator <NUM> may be associated with the intermediary <NUM>. As such, the administrator <NUM> may use one or more processors associated with the intermediary <NUM> to communicate with the communication system <NUM> for administrative review of the one or more communications <NUM> as discussed in further detail herein. In some embodiments, the administrator <NUM> may use the communication system <NUM> for administrative review of the one or more communications <NUM>. Alternatively, the administrator <NUM> may use a third party processor to communicate with the communication system <NUM> for administrative review of the one or more communications <NUM>.

<FIG> illustrates a flow chart <NUM> of an exemplary method for submittal of the one or more communications <NUM> by the receiver <NUM> to the communication system <NUM>. <FIG> illustrate exemplary screen shots of the method described in relation to <FIG>.

Referring to <FIG> and <FIG>, in a step <NUM>, the process of submission may begin by the receiver <NUM> accessing the communication system <NUM>. In some embodiments, the communication system <NUM> may provide one or more network servers with one or more graphical user interfaces (GUI), for example, for creation of one or more communications <NUM> at the receiver system <NUM>. A screenshot <NUM> on <FIG> illustrates an exemplary landing page for entry.

Referring to <FIG> and <FIG>, in a step <NUM>, the receiver <NUM> may be directed to enter receiver data information and have fields including, but not limited to, first name <NUM>, last name <NUM>, e-mail <NUM>, and/or the like, as illustrated in a screen shot <NUM>. Other information may be collected related to the receiver <NUM> such as medical data, personal information, contact information, and/or the like. Additionally, in some embodiments, the receiver <NUM> may be prompted to upload one or more images of the receiver <NUM> or other relevant images associated with the receiver <NUM>.

In a step <NUM>, the receiver <NUM> may be prompted to select sharing preferences related to messaging (e.g., appreciation) as illustrated in the screen shot <NUM>. For example, the receiver <NUM> may select sharing preferences for the provider <NUM>, the intermediary <NUM>, affiliates to the intermediary <NUM>, social media, and/or the like.

Referring to <FIG> and <FIG>, in a step <NUM>, the receiver <NUM> may enter the one or more communications <NUM>. The receiver <NUM> may select from predefined messages, as indicated in step <NUM>, or may create messages, as indicated in step <NUM>. As illustrated in the screen shot <NUM> of <FIG>, the receiver <NUM> may be prompted to create a message by either entering text into a message field <NUM> or selecting a portion <NUM> of the screen having one or more check boxes, option buttons, and/or toggle buttons. For example, the receiver <NUM> may select a predefined message stating "Thank you for giving the blood donation that was used to care for mv family member today" (selection underlined).

Referring to <FIG> and <FIG>, in steps <NUM>-<NUM>, the receiver <NUM> may be prompted to provide the identifier <NUM> to the communication system <NUM>. In some embodiments, the receiver <NUM> may have the option of providing one or more images of the identifier <NUM>, as in step <NUM>. Alternatively, the receiver <NUM> may manually enter the identifier <NUM>, as in step <NUM>.

<FIG> illustrate screenshots <NUM>-<NUM> of a tutorial for the receiver <NUM>. The tutorial provides information on how to provide the identifier <NUM> to the communication system <NUM> for decoding. Generally, the receiver <NUM> may be prompted to locate the identifier <NUM> (e.g., barcode) on the product <NUM> as shown in screen shot <NUM>. In screenshot <NUM>, the receiver <NUM> may be prompted to click a camera icon to take an image of the identifier <NUM> as shown in <FIG>. In screenshot <NUM>, shown in <FIG>, the receiver <NUM> may be prompted to rotate the captured image if there are scanning issues. In screenshot <NUM>, shown in <FIG>, the receiver <NUM> may be prompted to crop the image of the identifier <NUM> using a cropping box such that the identifier <NUM> is within borders of the cropping box. In screenshot <NUM>, shown in <FIG>, the receiver <NUM> may be informed that image capture of the identifier <NUM> may be unavailable, and as such, the receiver <NUM> may need to manually enter the identifier <NUM> into a field. <FIG> illustrates a screenshot <NUM> wherein the receiver may provide the identifier <NUM> via image <NUM> or manually entry via an alphanumeric field <NUM>.

Referring to <FIG> and <FIG>, in a screenshot <NUM>, the receiver <NUM> may be informed that the one or more communications will be reviewed, as illustrated in step <NUM>, and submitted to the provider <NUM>, as illustrated in step <NUM>.

<FIG> illustrates a flow chart <NUM> of an exemplary administrator review process for the one or more communications <NUM>. <FIG> illustrate exemplary screenshots <NUM>-<NUM> for the administrator review process shown in <FIG>.

Referring to <FIG>, in a step <NUM>, the administrator review process may begin by the administrator <NUM>, shown in <FIG>, communicating with the communication system <NUM>. In a step <NUM>, the administrator <NUM> may be authenticated by entering one or more credentials, as shown in step <NUM>. If the credentials are validated, as shown in step <NUM>, the administrator <NUM> may be directed to a display dashboard. An exemplary display dashboard is shown in the screenshot <NUM> of <FIG>. The display dashboard illustrates, for example, a text message <NUM> indicating a number of appreciations (i.e., communications <NUM>) needing review, a graphical representation <NUM> of a total number of communications <NUM> received, a graphical representation <NUM> of a total number of communications <NUM> approved, a graphical representation <NUM> of a total number of communications <NUM> denied, and/or the like.

Referring to <FIG>, in a step <NUM>, the administrator <NUM> may have the option of viewing pending communications <NUM> for review or past-reviewed (i.e., completed) communications <NUM>. In a step <NUM>, the administrator <NUM> may select to show pending communications <NUM> for review. In some embodiments, the communications system <NUM> may retrieve contact information of the provider <NUM> from the intermediary system <NUM>, as shown in step <NUM>. In some embodiments, the communications system <NUM> may communicate the identifier <NUM> to the intermediary system <NUM> and indicate that the intermediary system <NUM> may release contact information of the provider <NUM> to the administrator <NUM>. If the contact information of the provider <NUM> is successfully acquired, as indicated in step <NUM>, the administrator may be able to view the one or more communications <NUM> including information of the provider <NUM> and the receiver <NUM> as shown in a screenshot <NUM> in <FIG>. In addition, the identifier <NUM> may be shown to the administrator <NUM>. If the contact information of the provider <NUM> is not acquired, information of the receiver <NUM> may be shown, or the administrator <NUM> may view a message indicating "No Data to Display" as shown in step <NUM> of <FIG>.

Steps <NUM>-<NUM> of <FIG> illustrate an exemplary message review process shown in screenshots <NUM> and <NUM> of <FIG> and <FIG> respectively. In steps <NUM> and <NUM>, the administrator <NUM> may review the one or more communications <NUM> and approve, reject or flag each communication. Communications <NUM> may be rejected for use of inappropriate language or topics, for example. If the one or more communications <NUM> is rejected or flagged, the communications <NUM> may be archived as illustrated in step <NUM>. If the one or more communications <NUM> is approved, the communication <NUM> may be transmitted to the provider <NUM>. Such communications <NUM> may be transmitted to the provider <NUM> via e-mail message, text message, phone message, postal service, video recording, audio recording, and/or the like.

Claim 1:
One or more non-transitory computer readable medium storing a set of computer executable instructions for running on one or more processors of a communication system (<NUM>) that when executed by the one or more processors cause the communication system (<NUM>) to establish communication from a receiver (<NUM>) to a donor (<NUM>) by:
receiving at least one communication (<NUM>) and an identifier (<NUM>) from a receiver system (<NUM>), the receiver system (<NUM>) being used by the receiver (<NUM>) who received an accommodation (<NUM>) that was donated to an intermediary (<NUM>) from the donor (<NUM>), the donor (<NUM>) having contact information that remains confidential to the receiver (<NUM>) and that is known to the intermediary (<NUM>) , the identifier (<NUM>) configured to provide identifying characteristics of the accommodation (<NUM>) from the donor (<NUM>);
analyzing the identifier (<NUM>) to determine an intermediary system (<NUM>) related to the accommodation (<NUM>) ;
providing the identifier (<NUM>) to the intermediary system (<NUM>);
receiving the contact information of the donor (<NUM>) from the intermediary system (<NUM>); and
transmitting the at least one communication (<NUM>) to the donor (<NUM>) using the contact information from the intermediary system (<NUM>).