TECHNICAL FIELD

[0001] Embodiments of the disclosure relate to information sharing.

Embodiments relate more particularly to a method and system for accessing and sharing health related information.

BACKGROUND

[0002] Relationships begin between people with a face to face interaction or while socially hanging out, etc. Some relationships eventually grow intimate and involve dating and sexual engagement. Nowadays, there are even various online platforms that aid in establishing various kinds of relationships between individuals. Such platforms include social networking platforms, online dating platforms, etc. Based on the nature of the relationships that people may seek to initiate and maintain, they may use suitable interaction facilitating platforms.

[0003] Relationships involve information sharing between partners. Even in online dating platforms, a database stores numerous profiles corresponding to different users. Online dating platforms allow people to interact and communicate with each other based on a variety of matching criteria depending on their profiles. When a user is seeking a suitable match, the user can specify the gender preference, age range, location, etc., that he/she would prefer. Thereafter, various profiles on the database are searched to pull up suitable matches. Offline dating involves sharing each other's likes, dislikes and preferences, among others. What is not shared among users in conventional dating (online and offline) is the health profile of the partners.

[0004] For individuals looking for sexual relationships, one of the dangers of initiating interactions with strangers or acquaintances in both online and offline dating is that there is little assurance on the credibility of information provided by the partners. One potential issue for both online and offline dating is that a percentage of the general population is infected by one or more sexually transmitted diseases (STDs) such as including but not limited to Human Immunodeficiency Virus (HIV), chlamydia, genital herpes, genital warts, gonorrhea, hepatitis B, and syphilis. Without screening for the infection of STDs, conventional dating could, unwillingly or unknowingly, pose a risk of the spread of any of the STDs to the partners involved in the sexual relationship.

[0005] Hence, there is a need for a secure and a reliable system for facilitating a platform for information sharing on STD profiles of users between them while maintaining confidentiality of the users.

SUMMARY

[0006] Various embodiments of the present disclosure provide systems and methods for sharing of sexually transmitted disease profiles among users.

[0007] An embodiment provides a method for facilitating sharing of STD profiles among users. The method includes accessing a database, by a server system, the database storing a plurality of STD profiles. The method includes receiving, by the server system, an authentication input of a first user, through an application on a first user device of the first user, the authentication input of the first user comprising at least one of a unique identifier and a biometric data associated with the first user. The method further includes receiving, by the server system, a first share request through the application for sharing a STD profile of the first user with a second user, the first share request comprising a contact information of a second user. The method further includes electronically sharing, by the server system, the STD profile to the contact information of the second user based on based on a verification of the authentication input, the STD profile fetched from the plurality of STD profiles stored in the database.

[0008] Another embodiment provides a server system comprising a processor. The processor is configured to access the database storing the plurality of STD profiles. The processor receives an authentication input of a first user, through an application on a first user device of the first user. The authentication input of the first user comprising at least one of a unique identifier and a biometric data associated with the first user. The processor receives a first share request through the application for sharing a STD profile of the first user with a second user, the first share request including contact information of a second user. The processor further shares the STD profile to the contact information of the second user based on based on a verification of the authentication input.

[0009] Another embodiment provides a method. The method includes accessing a database, by a server system, wherein the database stores a plurality of STD profiles. The method includes receiving authentication input of a first user through an application on a second user device. The method includes verifying the authentication input of the first user. The method further includes displaying a STD profile of the first user in the application, the STD profile fetched from the plurality of STDs.

[0010] Another embodiment provides a method. The method includes initializing an application, by a processor on a user device of a first user. The method includes receiving an authentication input in the application and a share request for sharing a STD profile, the share request comprising contact information of a second user. The method includes sending the authentication input and the share request to a server system. The method includes share the STD profile to the contact information of the second user upon performing a verification of the authentication input.

BRIEF DESCRIPTION OF THE FIGURES

[0011] For a more complete understanding of example embodiments of the present technology, reference is now made to the following descriptions taken in connection with the accompanying drawings in which:

[0012] FIG. 1 is an illustration of an environment, in which a server system for facilitating sharing of STD profiles among users is deployed, related to at least some embodiments;

[0013] FIG. 2 is a flowchart illustrating a method for facilitating sharing of STD profiles among users, related to at least some embodiments;

[0014] FIG. 3 is a flowchart illustrating another method for facilitating mutual sharing of STD profiles amongst two users , related to at least some embodiments; [0015] FIG. 4 is a flowchart illustrating another method for facilitating sharing of STD profiles between two users using a single user device, related to at least some embodiments;

[0016] FIG. 5 is a simplified illustration of a user interface available at a user device displaying a profile of a first user in an application;

[0017] FIGS. 6 A and 6B are illustrations of user interfaces for providing authentication input of the user;

[0018] FIG. 7 is an illustration of a user interface for providing a share request;

[0019] FIG. 8 is an illustration of a user interface for displaying the STD profile of either the user;

[0020] FIG. 9 is a block diagram of a user device which may be an example of the first user device or the second user device; and

[0021] FIG. 10 is a simplified block diagram of the server system, in accordance with one embodiment.

[0022] The drawings referred to in this description are not to be understood as being drawn to scale except if specifically noted, and such drawings are only exemplary in nature.

DETAILED DESCRIPTION

[0023] In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the present disclosure. It will be apparent, however, to one skilled in the art that the present disclosure can be practiced without these specific details. In other instances, systems and methods are shown in block diagram form only in order to avoid obscuring the present disclosure.

[0024] Reference in 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 disclosure. The appearance of the phrase "in one embodiment" in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. Moreover, various features are described which may be exhibited by some embodiments and not by others. Similarly, various requirements are described which may be requirements for some embodiments but not for other embodiments.

[0025] Moreover, although the following description contains many specifics for the purposes of illustration, anyone skilled in the art will appreciate that many variations and/or alterations to said details are within the scope of the present disclosure.

Similarly, although many of the features of the present disclosure are described in terms of each other, or in conjunction with each other, one skilled in the art will appreciate that many of these features can be provided independently of other features. Accordingly, this description of the present disclosure is set forth without any loss of generality to, and without imposing limitations upon, the present disclosure.

OVERVIEW

[0026] Various example embodiments of the present disclosure provide methods and systems for facilitating sharing of STD profiles among users.

[0027] Embodiments provide systems and methods for facilitating sharing of STD profiles among users. The system includes a server system, at least one user device and a database. The database stores a plurality of STD profiles corresponding to a plurality of users who may have tested for STD profiles by registering with a clinic or a test sample collection centre. A processor of the server system is capable of accessing the plurality of STD profiles from the database. A user may resister with the clinic or a test sample collection centre by submitting a Government issued ID card and biometric data and providing the test samples. A testing laboratory associated with the clinic may conduct one or more medical tests for generating the STD profile of the user. The database stores the STD profile of the user upon receipt of the STD profile from the testing laboratory. The STD profile is made available in an application in the user device from where the user can access his/her STD profile. The server system notifies an availability of the STD profile to the users. The user may choose to share his/her STD profile with a partner who may or may not be registered with the clinic and may or may not have tested for the STD profile.

[0028] The server system receives an authentication input of the user, through the application in the user device. The authentication input of the user comprises at least one of a unique identifier, (such as an ID card number or a mobile phone number) and a biometric data (such as a fingerprint) associated with the user. A share request is sent through the application along with the authentication input. The share request comprises contact information of the partner with whom the user wishes to share his/her STD profile. Based on verification of the authentication input at the server system, the STD profile of the user is electronically shared to the contact information of the partner as a text message, email, or a push notification, etc. In some cases, the user may use the application in the user device associated with the partner. The STD profile of the user is fetched from the plurality of STD profiles stored in the database and upon receipt of the authentication input of the user in the user device of the partner, the STD profile of the user is displayed within the application of the user device of the partner.

[0029] FIG. 1 is a simplified illustration of an example environment 100 related to at least some embodiments disclosed herein. The environment 100 includes a server system 102 and user devices exemplarily shown as user devices 104a and 104b, and a database 106. The database 106 stores a plurality of STD profiles corresponding to a plurality of users. A processor of the server system 102 can access the plurality of STD profiles from the database 106.

[0030] The user devices 104a and 104b may be associated with two respective users, who may want to engage into a mutual relationship. The two users of the user devices 104a and 104b may operate their respective user devices 104a and 104b in order to share each user's STD profiles with one another. Examples of the first user device 104a and the second user device 104b include, but are not limited to, a personal computer (PC), a tablet device, a personal digital assistant (PDA), a smart phone and a laptop. The first user device 104a and the second user device 104b may include biometric sensors, such as a finger print sensor and/or iris scanner integrated in the hardware, to capture a fingerprint. [0031] The user device 104a may be a first user device 104a associated with a first user 108a. The first user 108a may be a user who has tested for the STD profile. The user device 104b may be a second user device 104b associated with a second user 108b. The second user 108b may be a partner of the first user 108a and may be romantically involved with the first user 108a. The second user 108b may or may not have tested for the STD profile. The first user device 104a and the second user device 104b may be collectively referred to as "user devices" throughout the disclosure. Each of the first user 108a and the second user 108b may be referred to as a "user" and both of the first user 108a and the second user 108b may be collectively referred to as "users" throughout the disclosure.

[0035] The server system 102 may be a remote virtual server such as a cloud server. The server system 102 may be an applications server hosted by a third party entity. The server system 102 communicates with the first user device 104a, the second user device 104b, a first entity 114, a second entity 116, and a compliance entity 118. The third party entity may be associated with the first entity 114. The server system 102 may be hosted by the first entity 114, in another example embodiment.

[0036] The user devices 104a and 104b and other entities can communicate among themselves or to the server system 102 through a communication network 110. The communication network 110 represents any distributed communication network (wired, wireless or otherwise) for data transmission and receipt between/among two or more points. The communication network 110 may as an example, include standard and/or cellular telephone lines, LAN or WAN links, broadband connections (ISDN, Frame Relay, ATM), wireless links, and so on. Preferably, the communication network 110 can carry TCP/IP protocol communications, and HTTP/HTTPS requests made by the user device 104 and the connection between the user devices 104a and 104b and the server system 102 can be communicated over such communication networks 110. In some implementations, the communication network 110 includes various cellular data networks such as 2G, 3G, 4G, and others. The type of communication network 110 is not limited, and the communication network 110 may include any suitable form of communication. Typical examples of the communication network 110 includes a wireless or wired Ethernet-based intranet, a local or wide-area network (LAN or WAN), and/or the global communications network known as the Internet, which may accommodate many different communications media and protocols.

[0037] The processor of the server system 102 enables an application 112 for facilitating sharing of STD profile corresponding to a user with one or more other users including a partner of the user. In an example embodiment, the first user device 104a and the second user device 104b are equipped with the instances of the application 112 installed therein. The processor of the server system 102 makes the application 112 available for installation at the first user device 104a and the second user device 104b. The application 112 may be available for download at Google play store and app store, among others. The application 112 facilitates user interfaces at the first user device 104a and the second user device 104b to enable several workflows by the processor of the server system 102 and the user devices 104a and 104b.

[0038] The application 112 is a set of computer executable codes. Instances of the set of computer executable codes may be stored in a memory/storage of the user devices 104a and 104b, wherein the computer executable codes are executed by a processor of the user devices 104a and 104b to perform one or more methods as disclosed herein. The application 112 may facilitate one or more buttons or actionable icons, selection (by a pressing/click or touch) of which enables display of one or more pages or user interfaces (UI) at the user devices 104a and 104b. The application 112 may be a mobile application or a web application.

[0039] The server system 102 facilitates registration of users such as the first user 108a and the second user 108b with the first entity 114. The first entity 114 may, as an example, be a clinic, a medical facility or a center, where test samples for generating STD profiles may be collected. Examples of the first entity 114 may include, but not limited to, PreP/HIV/STD/Planned Parenthood clinic. One or both of the first user 108a and the second user 108b can be registered with the first entity 114 and can get tested for the respective STD profiles.

[0040] Registration of a user with the first entity 114 includes the user providing one or more Government issued identification card (ID card) details to the server system 102 through the application 112. The user can shown the ID card to the first entity 114, which upon verification can allow the user to provide test samples (e.g., blood, urine, etc.). Examples of Government issued identification card details may include a passport number and a social security number, among others. Additionally, the user may also be allowed to provide contact information (e.g. a phone number) or an email address associated with the user. Registration further includes providing, by the user, to the server system 102, biometric data (such as fingerprint) of the user. The first entity 114 may electronically verify the Government issued identification card (ID card) details, the contact number and the biometric data of the user by communicating with one or more central servers, which may be responsible for maintaining the information corresponding to the Government issued identification card (ID card) details, the contact number and the biometric data of the user. As an example, the central server(s) may be Government data centers, police headquarters' data centers, etc.

[0041] The second entity 116 may be an entity associated with the first entity 114. The second entity 116 may be responsible for conducting one or more medical tests associated with one or more STDs for a user (e.g., the first user 108a and/or the second user 108b). Examples of the second entity 116 may include diagnostic centers and laboratories such as Quest, LabCorp, etc. The one or more STDs may include Human Immunodeficiency Virus (HIV), Syphilis and Gonorrhea, among others. Upon conducting respective medical tests associated with the STD, an STD profile is generated and the second entity 116 makes the STD profile available to the user for whom the medical tests have been conducted. The STD profile may include the dates on which the medical test is conducted, the date on which the test sample are collected, and the status of the STD. A status may, as an example, include an indication as to whether the user has been tested positive or negative with a particular STD. In an example, the first entity 114 and the second entity 116 can be same. For instance, sample collection and testing for the STDs can be done by the same entity.

[0042] The server system 102 communicates and shares the STD profiles of the users with the compliance entity 118. The compliance entity 118, as an example, may be an entity compliant with the Health Insurance Portability and Accountability Act (HIPAA). In a non- limiting example, the server system 102 may be hosted by the HIP A A complaint compliance entity 118.

[0043] The STD profile of a user is stored at the database 106 upon receipt of the STD profile from the second entity 116. The STD profile of the user can be further made available at the application 112 in the respective user device. Notifications regarding the availability of the STD profile, at the database 106, upon receipt of the STD profile from the second entity 116 may be sent to the user device. As an example, notification about the availability of the STD profile of the first user 108a is sent to the first user in the application 112 in the first user device 104a. The first user 108a may subsequently share the STD profile with the second user 108b or one or more other users.

[0044] The database 106 is further configured to store one or more educational information related to STD, which may be shared or made available in the application 112 in the user devices (e.g. user devices 104a and 104b). Various educational features may include STD Guideline and STD Forums are aimed to promote awareness among users. The STD Guideline and STD Forums will benefit users to make secure informed decisions on consensual sexual practices, including with the use of protection.

[0045] The users, for example, the first user 108a and the second user 108b may sign in with the application 112 by providing details such as a name, a phone number, an email address and a postal address associated with the first user 108a and the second user 108b, respectively. Further, the users 108a and 108b may be instructed to provide a password so that the server system 102 can associate the email addresses of the users with the passwords. The first user 108a and the second user 108b may later log into the application 112 with the email address and the password.

[0046] The application 112 may be initiated in a user device to share his STD profile with another user. For instance, if one of the users say the first user 108a wants to share his STD profile with a partner (e.g. second user 108b), the first user 108a can access the application 112 in the first user device 104a, and after providing authentication (explained later), can share his/her STD profile with the second user 108b.

[0047] In a scenario where both the first user 108a and the second user 108b wish to share the STD profiles with one another, the first user 108a and the second user 108b, by way of using their respective user devices 104a, 104b, respectively, can share their STD profiles with one another.

[0048] Let's consider, in a first scenario the application 112 is initiated in both of the first user device 104a and the second user device 104b. In this scenario, the first user 108a operates the first user device 104a and the second user 108b operates the second user device 104b. The first user 108a and the second user 108b may be away from one another or may be together at a location. The first user 108a may request the second user 108b to share the second user's STD profile with the first user 108a. Likewise, the second user 108b may request the first user 108b to share the first user's STD profile with the second user 108b.

[0032] In an alternate use case, only one user (e.g. user of the user device 104a) may be interested in sharing or may be asked to share his/her STD profile with the other user (e.g. user of the user device 104b). This may be a case when only one of the users in the mutual relationship has tested for the STD profile, and the other user may not have tested for the STD profile.

[0049] An example representation of a flowchart for sharing STD profile by one user (e.g., the first user 108a) with another user ( e.g., the second user 108b) is shown in a method 200 in FIG. 2. One or more operations of the method 200 are carried out at the server system 102. The sequence of operations of the method 200 need not be necessarily executed in the same order as they are presented. Further, one or more operations may be grouped together and performed in form of a single step, or one operation may have several sub-steps that may be performed in parallel or in sequential manner.

[0050] At operation 202, the server system 102 accesses the database 106 storing a plurality of STD profiles. The plurality of STD profiles may correspond to a plurality of users who have tested for their STD profiles by registering with the first entity 114. One of the plurality of the STD profiles may correspond to the first user 108a and another one of the plurality of the STD profiles may correspond to the second user 108b. These STD profiles may have been sent from the second entity 116 upon completion of the one or more medical tests associated with the STD profiles. The database 106 may receive the STD profiles from the second entity 116.

[0051] The server system 102 further notifies the first user 108a regarding the availability of the STD profile at the database 106 by sending a text message at the contact information (e.g. phone number) of the first user 108a or by sending an email notification at the email address of the first user 108a. Additionally, the first user 108a may be notified through a push notification in the application 112 in the first user device 104a.

[0052] At operation 204, the server system 102 receives an authentication input of the first user 108a, through the application 112 on the first user device 104a. The authentication input of the first user 108a includes at least one of a unique identifier and a biometric data associated with the first user 108a. The first user 108a uses the application 112 in the first user device 104a to communicate an authentication input of the first user 108a to the server system 102. The unique identifier may be an

identification card number/code of a Government issued identification card that the first user 108a may have provided during registration with the first entity 114. The biometric data may be a fingerprint provided in the first user device 104a through a fingerprint sensor of the first user device 104a. Other forms of biometric data such as iris scanning may also be used for the authentication. The biometric data may be verified with the biometric data that the first user 108a may have provided during registration with the first entity 114.

[0053] At operation 206, the server system 102 receives a first share request through the application 112 for sharing the STD profile of the first user 108a with a second user 108b. The first share request includes contact information of the second user 108b. The contact information includes a phone number or an email address associated with the second user 108b.

[0054] At operation 208, the server system 102 electronically shares the STD profile of the first user 108a to the contact information of the second user 108b based on a verification of the authentication input. The server system 102 fetches the STD profile from the database 106. Verification of the authentication input includes authenticating the unique identifier and the biometric data associated with the first user 108a against the Government issued identification card details and the biometric data provided by the first user 108a during registration with the first entity 114. Electronically sharing the STD profiles may include sharing the STD profile of the first user 108a at the contact information of the second user 108b. Further, the STD profile of the first user 108a may be shared in the application 112 in the second user device 104b. In an embodiment, the second user device 104b may get a notification in the application 112, so that the second user 108b becomes aware of the shared STD profile. [0055] Similarly, the second user 108b may also share the STD profile with the first user 108a. Referring to FIG. 3 a method 300 for facilitating mutual sharing of STD profiles amongst two users (the first user 108a and the second user 108b) is illustrated. One or more operations of the method 300 are carried out at the server system 102. The sequence of operations of the method 300 need not be necessarily executed in the same order as they are presented. Further, one or more operations may be grouped together and performed in form of a single step, or one operation may have several sub-steps that may be performed in parallel or in sequential manner.

[0056] As already explained with reference to FIG. 2, the operations 202, 204, 206 and 208 are performed for facilitating sharing of the STD profile of the first user 108a with the second user 108b. Further, at operation 302, the server system 102 receives an authentication input of the second user 108b, through the application 112 on the second user device 104a. The authentication input of the second user 108b includes at least one of a unique identifier and a biometric data associated with the second user 108a. The unique identifier may be an identification card number/code of a Government issued identification card that the second user 108a may have provided during registration with the first entity 114. The biometric data may be a fingerprint provided in the second user device 104b through a fingerprint sensor of the second user device 104b. The biometric data may be verified with the biometric data that the second user 108b may have provided during registration with the first entity 114. At operation 306, the server system 102 receives a second share request through the application 112 for sharing the STD profile of the second user 108b with a first user 108a. The second share request includes contact information of the first user 108a. The contact information includes a phone number or an email address associated with the first user 108a. At operation 308, the server system 102 electronically shares the STD profile of the second user 108b to the contact information of the second first user 108a based a verification of the authentication input.

[0057] Electronically sharing the STD profiles may include facilitating display of the STD profiles including the date on which the one or more medical tests are conducted, the date on which the test sample are collected, and the status of the STD. However, electronically sharing the STD profile does not facilitate sharing any personal identifier of a user such as a photo and a name to prevent the privacy. The user may be at least one of the first user 108a and the second user 108b.

[0058] In another scenario, the first user 108a and the second user 108b may be together at the same location and may use a single device for example the second user device 104b for sharing the STD profiles. The second user 108b may request the first user 108a to share the first user's STD profile with the second user 108b.

[0033] An example of the first user 108a sharing the STD profile with the second user 108b using the application 112 in the second user device 104b is shown in an example method 400 of FIG. 4. One or more operations of the method 400 are carried out at the server system 102. The sequence of operations of the method 400 need not be necessarily executed in the same order as they are presented. Further, one or more operations may be grouped together and performed in form of a single step, or one operation may have several sub-steps that may be performed in parallel or in sequential manner.

[0059] At operation 402, the server system 102 accesses the database 106 storing the plurality of STD profiles associated with a plurality of users including the first user 108a and the second user 108b. At operation 404, the server system 102 receives the authentication input of the first user 108a through the application 112 in the second user device 104b. At operation 406, the server system 102 verifies the authentication input of the first user 108a by comparing against the Government issued ID card and the biometric data provided by the first user 108a during registration with the first entity 114.

[0060] At operation 408, the server system 102 displays the STD profile of the first user 108a in the application 112 in the second user device 104b. The STD profile of the first user 108a is fetched from the plurality of STD profiles. The second user 108b may be logged into the application 112 in the second user device 104b with a profile of the second user 108b. Displaying the STD profile at the application 112 in the second user device 104b may include sharing the STD profile of the first user 108a with the profile of the second user 108b with which the second user 108b may be logged into to the application 112.

[0061] The second user 108b may already have access to his/her STD profile using the application 112 on the second user device 104b. Accordingly, once, the second user 108b has seen the STD profile of the first user 108a, the second user 108b can also fetch the STD profile of the second user 108b from the database 106 by using the application 106, and show the fetched STD profile to the first user.

[0062] Electronically sharing the STD profiles as described with reference to FIGS. 1 to 4, may include facilitating display of the STD profiles including the date on which the one or more medical tests are conducted, the date on which the test sample are collected, and the status of the STD without displaying any personal identifier of a user such as a photo and a name to maintain the privacy of the user.

[0063] The application 112 facilitates one or more user interfaces that include one or more buttons or actionable icons that enable workflows associated with the methods 200, 300 and 400. Some example representation of UIs of the application 112 are shown in FIGS. 5 to 8.

[0064] FIG. 5 is an example user interface 500 of the application displaying to a user (e.g. user 108a or 108b), in accordance with an example embodiment. Let's consider the user interface 500 is facilitated at a user device (e.g. the user device 104a or 104b) in the application 112. In an example, the user interface 500 may be a home page of the application 112 displayed in the user device. The user interface 500 may include a plurality of actionable icons 502, 504, 506, 508, 510, 512, 514, 516 and 518. The actionable icon 502 may indicate a status verification icon. Selection of the actionable icon 502 may open one or more pages that enable sharing of the STD profile of the user (e.g. user 108a) with a partner (e.g. user 108b). In an embodiment, selection (by clicking or tapping) of the actionable icon 502 may open a user interface that includes one or more fields that facilitate providing the authentication input in the application 112 by the user.

[0065] The actionable icon 504 may be a "My Account" icon. Selection of the actionable icon 504 may open one or more pages or user interfaces displaying account details including a name, postal address, a phone number, an email address, etc., of the user. A user interface is displayed upon selection of the actionable icon 504, within which is provided an option that allows editing the account information of the user. Selection of the actionable icon 506 may enable the user to view and access the user's own STD profile upon receipt of the user's STD profile from the second entity 116. Alternatively or additionally, selection of the actionable icon 506 may enable the user to view and access the STD profile of the partner, when the server system 102 has electronically shared the STD profile of the partner in the application 112 in the user device of the user.

[0066] The actionable icons 508 and 514 may be the STD guidelines and the STD forum icons respectively. Selection of each of the actionable icons 508 and 514 may open pages with educational materials associated with STD prevention and measures.

[0067] Selection of the actionable icon 510 enables the user to find at least one of the empanelled first entities 114. The first entities 114 may be displayed on a map based on their locations and their distance from the postal address of the user. It shall be noted that other well known formats (list, grid, etc.) in which the first entities 114 may be displayed to may be implemented with the present disclosure. The display of the first entities 114 may further enable selection of one or more first entities 114 from the display.

[0068] Selection of the actionable icon 512 opens one or more pages containing information corresponding to a drug (e.g., named 'TRUVADA') used for treating a STD, such as HIV. Likewise, selection of the actionable icon 516 opens one or more pages containing information corresponding to the third party entity (e.g., names 'GILEAD') hosting the server system 102 which facilitates the application 112. The actionable icon 518 allows the user to go to one or more pages containing information corresponding to the terms for using the application 112 in the user device of the user.

[0069] FIGS. 6 A and 6B are example user interfaces 600 and 610, respectively, enabling providing by a user the authentication input. Let's assume the user interfaces 600 and 610 are facilitated at a user device (e.g., the user device 104a or 104b) by the application 112. The user interface 600 may include a field 602 for providing the unique identifier of a user (e.g., users 108a or 108b). The unique identifier as disclosed earlier, may, as an example, be a passport number or a social security card number of the user. The user interface 600 may include a field 604 for providing a contact information associated with the user. The contact information may be a phone number or an email address associated with the user. Providing the contact information may be optional. In another embodiment, the user interface 600 may include an additional field (not shown) selection of which may activate a biometric sensor of the user and at the same time instruct the user to provide his/her biometric data utilizing the biometric sensor of the user device.

[0070] The user interface 610 may enable activation of a biometric sensor of the user device. An instruction may be displayed (not shown) on the user interface 610 for the user to tap or press the user's thumb against the biometric sensor of the user device 104a. Upon tapping or pressing the thumb against the biometric sensor, the biometric sensor scans the user's thumb and eventually a thumb print 612 is displayed on the user interface 610. The application 112 receives the biometric data associated with the user and communicates the same along with the unique identifier and the contact information to the server system 102. The server system verifies the authentication input against the data (Government issued identification card number and biometric data) provided by the user while registering with the fist entity 114. In a scenario, where one user device (e.g. user device 104a or 104b) is involved, the user may be asked by a partner of the user to provide the user's finger print at the user device of the partner.

[0071] Referring to FIG. 7, the application 112 facilitates a user interface 700 on a user device, the user device being the first user device 108a or the second user device 108b. User interface 700 displays an image 702 showing that two user devices are communicating and sharing information. The image 702 indicates that a user (e.g. the first user 108a) is sharing information (e.g. the STD profile corresponding to the user) with a partner (e.g. the second user 108b). User interface 700 includes a field 704 for entering the share request. The share request is a contact information (e.g.

+7777777777) of the user.

[0072] In an example, if the user interface 700 is displayed at the second user device 104b, then the share request may correspond to the first user 108a and vice versa. In another example, if only one user device (e.g. second user device 104b) is involved, share request may correspond to the user who has been requested by a partner to share his/her STD profile with the partner. User interface 700 further includes an actionable icon 706, wherein selection of the actionable icon 706 may trigger the processor of the server system 102 to share the STD profile with the user associated with the contact information provided in the field 704. [0064] Referring to FIG. 8, a user interface 800 is displayed. The user interface 800 may be a STD profile of a user, the user being the first user 108a or the second user 108b. The STD profile as shown in FIG. 8 may include the STD status including the date and time at which the medical test associated with the respective STD was conducted at the second entity 116. As seen in FIG. 8, the user interface 800 includes a status field 802, where the names and respective time at which the status of the STD was last checked is displayed. The field 802 shows statuses of three STD namely, HIV, Gonorrhea and Syphilis are displayed. The status is shown next to the names of the STD as an indication as to whether the particular STD is tested positive or negative. A field 804 may display a testing status in terms of how old or up to date the status of the test is. User interface 800 further enables a display 806 of the biometric data (e.g. the fingerprint, thumb impression) and an indication, such as the check mark 808, whether the biometric data has been successfully verified.

[0054] FIG. 9 shows a simplified block diagram of a user device 900 such as the first user device 104a and the second user device 104b. User device 900, as an example, may be a mobile phone 900 capable of implementing the various embodiments of the present disclosure. In an embodiment, the various operations related to methods 200, 300 and 400 can be facilitated using an application 906, such as the application 112 installed in the mobile phone 900.

[0055] It should be understood that the mobile phone 900 as illustrated and hereinafter described is merely illustrative of one type of device and should not be taken to limit the scope of the embodiments. As such, it should be appreciated that at least some of the components described below in connection with that the mobile phone 900 may be optional and thus in an example embodiment may include more, less or different components than those described in connection with the example embodiment of the FIG. 9. As such, among other examples, the mobile phone 900 could be any of a mobile electronic devices or may be embodied in any of the electronic devices, for example, cellular phones, tablet computers, laptops, mobile computers, personal digital assistants (PDAs), mobile televisions, mobile digital assistants, or any combination of the aforementioned, and other types of communication or multimedia devices.

[0056] The illustrated mobile phone 900 includes a controller or a processor 902 (e.g. , a signal processor, microprocessor, ASIC, or other control and processing logic circuitry) for performing such tasks as signal coding, data processing, image processing, input/output processing, power control, and/or other functions. An operating system 904 controls the allocation and usage of the components of the mobile phone 900 and support for one or more applications programs (see, STD profile sharing application 906).

[0057] The illustrated mobile phone 900 includes one or more memory components, for example, a non-removable memory 908 and/or removable memory 910. The non-removable memory 908 and/or removable memory 910 may be collectively known as database in an embodiment. The non-removable memory 908 can include RAM, ROM, flash memory, a hard disk, or other well-known memory storage technologies. The removable memory 910 can include flash memory, smart cards, or a Subscriber Identity Module (SIM). The one or more memory components can be used for storing data and/or code for running the operating system 904 and the virtual agent system application 906. The mobile phone 900 may further include a user identity module (UIM) 912. The UIM 912 may be a memory device having a processor built in. The UIM 912 may include, for example, a subscriber identity module (SIM), a universal integrated circuit card (UICC), a universal subscriber identity module (USIM), a removable user identity module (R-UIM), or any other smart card.

[0058] The mobile phone 900 can support one or more input devices 920 and one or more output devices 930. Examples of the input devices 920 may include, but are not limited to, a touch screen / a display screen 922 (e.g. , capable of capturing finger tap inputs, finger gesture inputs, multi-finger tap inputs, multi-finger gesture inputs, or keystroke inputs from a virtual keyboard or keypad), a microphone 924 (e.g. , capable of capturing voice input), a camera module 926 (e.g. , capable of capturing still picture images and/or video images) and a physical keyboard 928. Examples of the output devices 930 may include, but are not limited to a speaker 932 and a display 934. Other possible output devices can include piezoelectric or other haptic output devices. Some devices can serve more than one input/output function. For example, the touch screen 922 and the display 934 can be combined into a single input/output device.

[0059] A wireless modem 940 can be coupled to one or more antennas (not shown in the FIG. 9) and can support two-way communications between the processor 902 and external devices, as is well understood in the art. The wireless modem 940 is shown generically and can include, for example, a cellular modem 942 for

communicating at long range with the mobile communication network, a Wi-Fi compatible modem 944 for communicating at short range with an external Bluetooth- equipped device or a local wireless data network or router, and/or a Bluetooth- compatible modem 946. The wireless modem 940 is typically configured for communication with one or more cellular networks, such as a GSM network for data and voice communications within a single cellular network, between cellular networks, or between the mobile phone 900 and a public switched telephone network (PSTN).

[0060] The mobile phone 900 can further include one or more input/output ports 950, a power supply 952, one or more sensors 954 for example, an accelerometer, a gyroscope, a compass, or an infrared proximity sensor for detecting the orientation or motion of the mobile phone 900, a transceiver 956 (for wirelessly transmitting analog or digital signals) and/or a physical connector 960, which can be a USB port, IEEE 1294 (Fire Wire) port, and/or RS-232 port. The illustrated components are not required or all- inclusive, as any of the components shown can be deleted and other components can be added.

[0065] The disclosed system and methods with reference to FIGS. 1 to 8, or one or more operations of the flow diagram 200, 300 and 400 may be implemented using software including computer-executable instructions stored on one or more computer- readable media (e.g., non-transitory computer-readable media, such as one or more optical media discs, volatile memory components (e.g., DRAM or SRAM), or nonvolatile memory or storage components (e.g., hard drives or solid-state non-volatile memory components, such as Flash memory components) and executed on a computer (e.g., any suitable computer, such as a laptop computer, net book, Web book, tablet computing device, smart phone, or other mobile computing device). Such software may be executed, for example, on a single local computer or in a network environment (e.g., via the Internet, a wide-area network, a local-area network, a remote web-based server, a client-server network (such as a cloud computing network), or other such network) using one or more network computers. Additionally, any of the intermediate or final data created and used during implementation of the disclosed methods or systems may also be stored on one or more computer-readable media (e.g., non- transitory computer- readable media) and are considered to be within the scope of the disclosed technology. Furthermore, any of the software-based embodiments may be uploaded, downloaded, or remotely accessed through a suitable communication means. Such suitable

communication means include, for example, the Internet, the World Wide Web, an intranet, software applications, cable (including fiber optic cable), magnetic

communications, electromagnetic communications (including RF, microwave, and infrared communications), electronic communications, or other such communication means.

[0066] FIG. 10 is a simplified block diagram of a server system 1000, in accordance with one embodiment of the present disclosure. The server system 1000 is an example of a server system 102 shown in FIG. 1. The server system 1000 includes computer system 1002 and database 1004.

[0067] The computer system 1002 includes a processor 1006 for executing instructions. Instructions may be stored in, for example, but not limited to, a memory 1008. The processor 1006 may include one or more processing units (e.g., in a multi- core configuration).The processor 1006 is operatively coupled to a communication interface 1008 such that computer system 1002 is capable of communicating with a remote device such as the user device (e.g. user device 104a and 104b) (shown in FIG. 1)

[0068] The processor 1006 may also be operatively coupled to the database 1004. The database 1004 is any computer-operated hardware suitable for storing and/or retrieving data. The database 1004 may include multiple storage units such as hard disks and/or solid-state disks in a redundant array of inexpensive disks (RAID) configuration. The database 1004 may include a storage area network (SAN) and/or a network attached storage (NAS) system. In some alternate embodiments, the database 604 may also include magnetic storage devices (such as hard disk drives, floppy disks, magnetic tapes, etc.), optical magnetic storage devices (e.g., magneto-optical disks), semiconductor memories (such as mask ROM, PROM (programmable ROM), EPROM (erasable PROM), Phase-change memory, flash ROM, RAM (random access memory)), etc.

[0069] In some embodiments, the database 1004 is integrated within computer system 1002. For example, computer system 1002 may include one or more hard disk drives as database 1004. In other embodiments, database 1004 is external to computer system 1002 and may be accessed by the computer system 1002 using a storage interface 1012. The storage interface 1012 is any component capable of providing the processor 1006 with access to the database 1004. The storage interface 1012 may include, for example, an Advanced Technology Attachment (ATA) adapter, a Serial ATA (SAT A) adapter, a Small Computer System Interface (SCSI) adapter, a RAID controller, a SAN adapter, a network adapter, and/or any component providing processor 1006 with access to the database 1004. In some alternate embodiments, the database 604 may also include magnetic storage devices (such as hard disk drives, floppy disks, magnetic tapes, etc.), optical magnetic storage devices (e.g., magneto-optical disks), semiconductor memories (such as mask ROM, PROM (programmable ROM), EPROM (erasable PROM), Phase-change memory, flash ROM, RAM (random access memory)), etc.

[0070] Although the invention has been described with reference to specific exemplary embodiments, it is noted that various modifications and changes may be made to these embodiments without departing from the broad spirit and scope of the invention. For example, the various operations, blocks, etc., described herein may be enabled and operated using hardware circuitry (for example, complementary metal oxide semiconductor (CMOS) based logic circuitry), firmware, software and/or any combination of hardware, firmware, and/or software (for example, embodied in a machine-readable medium). For example, the apparatuses and methods may be embodied using transistors, logic gates, and electrical circuits (for example, application specific integrated circuit (ASIC) circuitry and/or in Digital Signal Processor (DSP) circuitry).

[0071] Particularly, the server system 1000 and its various components such as the computer system 1002 and the database 1004 may be enabled using software and/or using transistors, logic gates, and electrical circuits (for example, integrated circuit circuitry such as ASIC circuitry). Various embodiments of the invention may include one or more computer programs stored or otherwise embodied on a computer-readable medium, wherein the computer programs are configured to cause a processor or computer to perform one or more operations. A computer-readable medium storing, embodying, or encoded with a computer program, or similar language, may be embodied as a tangible data storage device storing one or more software programs that are configured to cause a processor or computer to perform one or more operations. Such operations may be, for example, any of the steps or operations described herein. In some embodiments, the computer programs may be stored and provided to a computer using any type of non-transitory computer readable media. Non-transitory computer readable media include any type of tangible storage media. Examples of non-transitory computer readable media include magnetic storage media (such as floppy disks, magnetic tapes, hard disk drives, etc.), optical magnetic storage media (e.g. , magneto- optical disks), CD-ROM (compact disc read only memory), CD-R (compact disc recordable), CD-R/W (compact disc rewritable), DVD (Digital Versatile Disc), BD (BLU-RAY® Disc), and semiconductor memories (such as mask ROM, PROM

(programmable ROM), EPROM (erasable PROM), flash memory, RAM (random access memory), etc.). Additionally, a tangible data storage device may be embodied as one or more volatile memory devices, one or more non- volatile memory devices, and/or a combination of one or more volatile memory devices and non- volatile memory devices. In some embodiments, the computer programs may be provided to a computer using any type of transitory computer readable media. Examples of transitory computer readable media include electric signals, optical signals, and electromagnetic waves. Transitory computer readable media can provide the program to a computer via a wired communication line (e.g. electric wires, and optical fibers) or a wireless communication line.

[0072] The present disclosure is described above with reference to block diagrams and flowchart illustrations of method and system embodying the present disclosure. It will be understood that various block of the block diagram and flowchart illustrations, and combinations of blocks in the block diagrams and flowchart illustrations, respectively, may be implemented by a set of computer program instructions. These set of instructions may be loaded onto a general purpose computer, special purpose computer, or other programmable data processing apparatus to cause a device, such that the set of instructions when executed on the computer or other programmable data processing apparatus create a means for implementing the functions specified in the flowchart block or blocks. Although other means for implementing the functions including various combinations of hardware, firmware and software as described herein may also be employed. [0073] Various embodiments described above may be implemented in software, hardware, application logic or a combination of software, hardware and application logic. The software, application logic and/or hardware may reside on at least one memory, at least one processor, an apparatus or, a non-transitory computer program product. In an example embodiment, the application logic, software or an instruction set is maintained on any one of various conventional computer-readable media. In the context of this document, a "computer-readable medium" may be any non-transitory media or means that can contain, store, communicate, propagate or transport the instructions for use by or in connection with an instruction execution system, apparatus, or device, such as a computer, with one example of a system described and depicted in FIG. 10. A computer-readable medium may comprise a computer-readable storage medium that may be any media or means that can contain or store the instructions for use by or in connection with an instruction execution system, apparatus, or device, such as a computer.

[0074] The foregoing descriptions of specific embodiments of the present disclosure have been presented for purposes of illustration and description. They are not intended to be exhaustive or to limit the present disclosure to the precise forms disclosed, and obviously many modifications and variations are possible in light of the above teaching. The embodiments were chosen and described in order to best explain the principles of the present disclosure and its practical application, to thereby enable others skilled in the art to best utilize the present disclosure and various embodiments with various modifications as are suited to the particular use contemplated. It is understood that various omissions and substitutions of equivalents are contemplated as circumstance may suggest or render expedient, but such are intended to cover the application \or implementation without departing from the spirit or scope of the claims.