Patent ID: 12254489

DETAILED DESCRIPTION OF THE INVENTION

In a following description, reference is made to the accompanying drawings, which form a part hereof, and in which is shown by way of illustration a specific example in which the invention may be practiced. It is to be understood that other embodiments may be utilized and structural changes may be made without departing from the scope of the present invention.

General Overview:

It should be noted that the descriptions that follow, for example, in terms of an HCP Consent Management Framework system are described for illustrative purposes and the underlying system can apply to any number and multiple types of website providers. In one embodiment of the present invention, the HCP Consent Management Framework system can be configured using consent codes. The HCP Consent Management Framework system can be configured to include an overall consent forms and can be configured to include a granular consent form using the present invention.

Message utilization poses another significant challenge for publishers. Matching and aligning the appropriate commercial message with the right HCP is a complex and time-consuming endeavor. For instance, extensive research is conducted to identify the HCPs, ensuring that an advertisement with cardiology-related medical product content information reaches an HCP specialized in cardiology rather than one specialized in a different medical field, such as dentistry or orthopedics. In the future, there will be a growing need for healthcare and life sciences marketers to access information about recent and innovative medical solutions and effectively reach the corresponding HCPs and medical practitioners on a large scale.

Publishers are also under considerable pressure to conceive, design, and establish their own customized HCP Consent Management Frameworks. This is essential for expanding HCP identities and, in turn, driving more targeted traffic to their digital advertising spaces.

Additionally, a significant volume of medical product content information, authored by experts in the medical field, is intended solely for consumption by specialist medical practitioners. In such cases, a consent management mechanism plays a pivotal role in restricting public access to this medical product content information. Moreover, publishers may limit access to detailed medical product content information on their websites exclusively to pre-identified HCPs, often tailoring the experience for HCPs who visit specific sections or pages.

FIG.1shows for illustrative purposes only an example of a publisher website consent management of one embodiment.FIG.1shows a publisher #1 website100having a publisher-partner #1101selecting rules set #1102and #1 consent form parameters103. The publisher #2 website112has a publisher-partner #2104selecting rules set #2105with #2 consent form parameters106. Each publisher-partner provides consent form parameters based on their website medical product content information and geographical compliance requirements. In one embodiment the #1 consent form parameters103are converted into code to implement consent #1 code110. The consent code is converted in at least one consent #1 form120. For example, consent #1 form120is converted into an overall #1 consent122to cover all medical product content information of the publisher-partner #1101. In addition, consent #1 form120is converted into multiple granular #1 consent121forms. Each granular #1 consent121form covers specific aspects of the publisher-partner #1101medical product content information.

As discussed in U.S. application Ser. No. 18/116,290, which is incorporated by reference herein, the medical products graphical user interface is configured to display medical product content information122on electronic health records medical provider and patient interaction segment screens during an appointment. A healthcare professional (HCP) end user140may only consent to medical product content information or another offering listed on the granular #1 consent121form. The healthcare professional (HCP) end user140will receive the consent forms upon access to the publisher's website142. The HCP218ofFIG.2may #1 accept/reject150one or more consent forms. The election by the HCP218ofFIG.2is recorded on the consent database170of the publisher #1 website100. In this example, the HCP218ofFIG.2has elected one of the granular #1 consent121form selections.

In another embodiment, the #2 consent form parameters106are converted into implement consent #2 code111. At least one consent #2 form130into a granular #2 consent131and an overall #2 consent132form. The HCP upon access to the publisher website142selects the overall #2 consent132form and responds to the #2 accept/reject160accept. The accepted overall #2 consent132form is recorded in the consent database170of the publisher #1 website100of one embodiment. Message utilization is another great challenge that publishers need to address on their end. It is a massive and time-consuming endeavor for publishers to just match and map the suitable commercial message with the correct HCP218ofFIG.2. For example, much research goes into HCP218ofFIG.2identification so that an advertisement with a context related to cardiology reaches an HCP218ofFIG.2who specializes in cardiology rather than reaching an HCP218ofFIG.2who specializes in another medical specialty, for example dentistry or orthopedics.

There is a requirement for marketers in the healthcare and life sciences domain to get information about recent and innovative medical solutions to reach the corresponding HCPs and medical practitioners at the earliest and with the best possible means to reach HCPs and that too at scale.

There is a high demand on the publisher210ofFIG.2side to conceptualize, design, and develop their bespoke HCP218ofFIG.2Consent Management Frameworks to scale HCP218ofFIG.2identities and thereby drive more targeted traffic to their respective digital advertisement spaces.

Moreover, there is a growing body of medical product content information that is created by experts in the medical field and is meant to be consumed by none other than specialist medical practitioners. In such a scenario, a consent management mechanism plays a significant role in preventing the general public from accessing such medical product content information. Furthermore, publishers may restrict access to granular medical product content information on their websites only to previously identified HCPs, to the point of generating custom-made experiences for HCPs landing on particular sections or pages.

DETAILED DESCRIPTION

FIG.2shows for illustrative purposes only an example of the HCP Consent Management Framework (CMF)200of one embodiment.FIG.2shows an HCP Consent Management Framework200to collect consent from HCP218users of a publisher #1 website100. The Publisher210has a publisher development team211to establish an HCPCMF consent matrix212on the publisher #1 website100. Access216from an HCP218is authenticated referencing consents granted by the HCP218stored in the consent database170. No consent recorded, triggers consent form parameters230implemented in consent code250in the form of access to consent forms240converted into one or more consent forms260. Consent forms refers to medical product content information that can be accessed by the HCP based on the explicit consent they have provided to the Publisher on a specific website. The HCP218user may accept/reject270from a selection of consent forms and add the HCP218selection into the consent collection280of one embodiment.

The HCP Consent Management Framework200promotes the concept of consent granularity, ensuring that healthcare professionals (HCPs) have the autonomy to select the specific types of data processing and online marketers with whom they are willing to share their data. This level of granularity empowers HCPs to exercise greater control over the data they provide to publishers. Once consent is obtained, the data is processed by the HCPs' agreed-upon terms.

HCPs may be required to provide consent for various activities, which can vary among different publishers based on their unique business needs. The list of activities for which HCP218consent is required is presented to the HCP218in a digital format, often as a pop-up window when they visit the publisher's website. The consent form is designed to be clear and straightforward, ensuring that HCPs can easily understand and provide their consent.

The said form would mention the activities for which explicit consent is being sought and the language used in the form would be straightforward for the HCP218to understand.

The HCP Permission Management Framework provides the publishers with a template for developing and specifying the portions of the consent form they wish to display to the HCPs. The form design template also allows the publishers to include their consent statements. The template will also enable publishers to develop a consent form that is not only concise but also simple enough for HCPs to easily understand and grant their approval accordingly.

Activities for which consent is being sought are presented as a list of items with a corresponding checkbox for each of the listed activities that the HCP218can tick/select. The goal is to offer the information to the HCP218in such a way that they can freely select required statements or settings expressing their permission for the selected information to be processed and used by the publisher210to conduct the indicated activities.

The HCP Permission Management Framework's design and development both promote end-user rights because the consent form does not provide pre-selected options to the user or a mechanism by which publishers can create a form in which inactivity of the HCP218is in any way considered consent. In doing so, the publisher210never violates any authorized data processing provisions of regulatory frameworks, which solely considers willfully granted consent.

Additionally, publishers may easily show this consent form, as valid documentary proof or evidence, to the data regulatory authorities of their various regions that the consent was obtained voluntarily and without any compulsion or using any unfair means, from the concerned HCPs.

Based on the content that is taken from HCPs, the corresponding publishers would then apply the consent to the entire website (site-level consent ramifications); or the consent would be applied at the web page level (HCPs can be provided or denied access to certain pages of the website based on the received HCP218content), or the consent could be enforced for certain sections of the website's page (for example, a section dedicated to a content snippet meant for cutting edge research in oncology would not be exposed to an HCP218that is a specialist in dermatology or say nephrology) based on the attributes shared by the concerned HCP218.

Consent Collection Form:

FIG.3shows for illustrative purposes only an example of a consent collection form of one embodiment.FIG.3shows an example of a consent collection form300content. In one example an overall consent301the HCP218ofFIG.2user may accept/reject322. Another example is a selection of granular consent310forms. In one embodiment, the granular consent310form may include cookies320that display using a graphical user interface (GUI) to list what medical product content information the cookie form includes that the HCP218ofFIG.2user may accept or reject322. Other examples of a granular consent310form include attribute 1330of the HCP218ofFIG.2user being specialization332to accept/reject322. Another attribute 2340may include a geographical location342to accept/reject322. medical product content information consent varies by geographical location and the granular consent310form will include specific content consents based on geographical compliance regulations. Another issue is third-party350content and the manner the vendor data processed352for display. The HCP218ofFIG.2may accept/reject322based on location compliance restrictions. Cookies consent320is subject to acceptance based on the medical product content information of the cookie displayed to select accept/reject322responses. Any of the consent responses received is stored in the consent database170of one embodiment.

The HCP Consent Management Framework200ofFIG.2would store/document consent details of the HCPs for the respective publisher210ofFIG.2within a consent database. The consent collected from the HCPs would also be accompanied by the corresponding attributes they share, for example, specialization, location, etc. Moreover, the attributes collected from the HCPs are configurable, which means that the HCPs can freely select the specific consent they want to provide and would subsequently be used for the stated data processing and for receiving messages and medical product content information accordingly.

The HCPs would be asked to provide specific attributes around their nature of work, that is, with which medical specialty they are aligned. They could also be asked to provide information about their location or specifically the location of their workplace, that is, where the hospital, clinic, or healthcare facility they are associated with is located. The HCP218ofFIG.2could also be asked to provide consent for any specific academic objective that they would like to pursue or any specific publication they would like to subscribe to.

These attributes would vary from one publisher210ofFIG.2to another and even differ from one country to another within a specific geographically demarcated market. Nonetheless, the publishers would only seek the information from the HCPs that is legal within their specific market/country/location. In doing so, publishers do not infringe on any compliance parameters and adhere to the prescribed medical and legal injunctions of their respective regions or countries.

Bespoke User Experience:

FIG.4shows for illustrative purposes only an example of a bespoke user experience of one embodiment.FIG.4shows bespoke user experience400claimed by consent granularity parameter/attribute selection410. An HCP218ofFIG.2consent yes420response to a premium bundle of consented medical product content information430for the publisher #1 website100creates a better user experience450by consenting to all publisher medical product content information. An HCP218ofFIG.2consent no460response to a generic consent470publisher #1 website100generates a message to HCP218ofFIG.2mapping optimized490to avoid consent-required medical product content information of one embodiment.

Based on the consent provided by consenting to all publisher medical product content information or only HCP selected portions of the publisher medical product content information, an HCP can be shown or debarred from accessing medical product content information on a specific website. This means HCPs excelling in a particular healthcare domain get to see medical product content information associated with their specific areas of expertise only and not just any other generic medical product content information. For HCPs who do not provide explicit consent, the website though providing them access to the generic medical product content information would restrict such users from accessing specific premium medical product content information present and available on the site. This means the consent provided by the HCP218ofFIG.2would determine what type of medical product content information or message they would get to see on the publisher's website.

Opt-Out Review:

FIG.5shows for illustrative purposes only an example of an opt-out review of one embodiment.FIG.5shows an opt-out review500of an HCP218publisher website100selection. The HCPCMF consent matrix212records the opt-out response with a consent database updated540.

Opt-Out Management: The HCP Consent Management Framework200ofFIG.2allows HCPs to withdraw their consent whenever they see fit, respecting the rights of data subjects, i.e., the HCPs. The option to opt out is a fundamental aspect of data subject rights and is a standard practice mandated by privacy regulatory authorities worldwide of one embodiment.

Access and Transparency:

FIG.6shows for illustrative purposes only an example of access and transparency of one embodiment.FIG.6shows access and transparency600from a publisher210on the publisher #1 website100. Further, as discussed in U.S. application Ser. No. 18/116,290, incorporated above, a medical products provider computer110ofFIG.1stored the medical product content information and graphical displays on network platform databases and memory devices132coupled to network platform servers, communication devices, processors, graphic devices and other digital devices130. The HCPCMF consent matrix212uses a platform having a plurality of servers and processors to analyze patterns and make decisions640related to HCP218ofFIG.2user privacy and consent matters of one embodiment. HCPs are asked to provide specific attributes related to their professional background, including their medical specialty, workplace location, academic objectives, or publication preferences. The specific attributes may vary between publishers and even from one country to another within a geographically segmented market. Importantly, publishers only request information that is legally permissible in their specific market or country, ensuring compliance with medical and legal regulations.

The HCP Consent Management Framework200ofFIG.2offers easy access for publishers, providing them with a dashboard to review their HCP218ofFIG.2consent-related data. This facilitates a deeper understanding of consent data, enabling publishers to derive valuable insights and make informed business decisions. The HCP Consent Management Framework200ofFIG.2is easy to access, and publishers can seamlessly review their respective HCP218ofFIG.2consent-related data. For a better understanding of the consent data, to derive apt business acumen from consent data, and to make informed business decisions, publishers are provided with a dashboard.

Compliance:

FIG.7shows for illustrative purposes only an example of compliance of one embodiment.FIG.7shows compliance700by the publisher210using the HCPCMF consent matrix212to meet regulatory compliance with at least GDPR, CCPA, and HIPAA730. Where in the compliance agencies include at least GDPR (General Data Protection Regulation), CCPA (California Consumer Privacy Act) and HIPAA (Health Insurance Portability and Accountability Act) are some of the popular and cited regulatory frameworks, that govern data privacy and data protection procedures and process in the EU (European Union) region and the US, respectively.

The consent database170ofFIG.1includes consent form records740, HCP references750, and audit trails760to verify to any compliance agency that the publisher210and publisher #1 website100ofFIG.1are in compliance of one embodiment.

AdTech organizations, for example advertisers or publishers operate in a complex legal framework, with national laws, medical laws, and restrictions imposing strict data processing obligations. The HCP Consent Management Framework200ofFIG.2aids publishers in remaining compliant with these rules and regulations at all times. Compliance needs are met within the framework by transparently maintaining HCP218ofFIG.2consent records, managing consent preferences, and giving audit trails to publishers. All of this enables publishers to give verifiable evidence of compliance to data compliance authorities in their specific geography.

Based on the content taken from HCPs, publishers can apply consent at different levels. This includes applying consent at the site level, web page level, or for specific sections of a webpage, depending on the attributes shared by the HCPs.

The HCP Consent Management Framework200ofFIG.2ensures bespoke user experiences. HCPs are shown medical product content information related to their specific areas of expertise based on their consent. Those who do not provide explicit consent can access generic medical product content information but are restricted from accessing premium medical product content information.

The framework also prioritizes managing opt-outs, allowing HCPs to withdraw their consent as needed. This is vital for respecting the rights of data subjects, and the HCPs, and aligns with privacy regulations globally.

Respecting user rights is a core principle of the HCP Consent Management Framework200ofFIG.2. HCPs can change their consent preferences or withdraw consent without any hindrance. When an HCP218ofFIG.2opts out or withdraws consent, the publisher210ofFIG.2ceases to process their data, ensuring full compliance with data subject rights and privacy regulations.

The HCP Consent Management Framework200ofFIG.2has been designed such that the rights of data subjects, that is, HCPs, are upheld both by design and by development. HCPs can withdraw their consent and even change their consent preferences as and when they require it, and they can do so without any prior obligation or hindrance. Once an HCP218ofFIG.2has opted out or withdrawn their consent from a website, the concerned publisher210ofFIG.2stops processing the data of that particular HCP218ofFIG.2.

Trust Building:

FIG.8shows for illustrative purposes only an example of trust building of one embodiment.FIG.8shows trust building800between the HCP218and publisher #1 website100that provides healthcare medical product content information specific to healthcare professional specialty830. The HCP218subscriptions840allow for paper consent850for relevant advertisements and medical product content information, information release messages860including commercial messages, and review consent870of medical publications and research papers by the HCP218of one embodiment.

The HCP Consent Management Framework200ofFIG.2enables publishers to create trust with the HCPs they serve through their websites. This is accomplished through HCP218-focused consent. This means that end users can only access healthcare-related material after providing explicit agreement that they are in the healthcare or life sciences domain.

Furthermore, by using consent granularity, publishers can offer HCPs messages that are specifically tailored to their needs. When HCPs are fully aware that they control their consent preferences and how their consent data is used by publishers who are providing them with relevant advertisements, commercial messages, and content, they are more likely to interact with these messages and niche content (specific medical publications, research papers, subscription requests to medical journals, etc.) favorably.

Third-Party Relationships:

FIG.9shows a block diagram of an overview of third-party relationships of one embodiment.FIG.9shows building trust based third-party relationships900with the HCP218and publisher #1 website100. The HCPCMF consent matrix212user consent codes940generate consent forms for the third-party vendor950and advertisers960to seek consent from their users to maintain regulatory compliance.

Whenever HCPs provide their consent, these consented parameters, within the HCP CMF are automatically generated into what is known as ‘User Consent Codes’ that the respective Publishers can share with third-party entities, further building the trust/relationship between the concerned Publisher with their respective third-party relations, that is, vendors. Thus HCP CMF enables Publishers within the Ad Tech space to expand their scope of third-party relations, based on transparency, compliance, and thereby augment their trustworthiness in the business domain/industry.

The HCPCMF consent matrix212also stores the HCP218consent form responses on the consent database170of one embodiment.

To meet specific criteria, publishers frequently must collaborate with third-party suppliers and vendors. The HCP Consent Management Framework200ofFIG.2also supports ensuring that HCP218consent is applied to these third parties, as well as that those business organizations adhere to the specified privacy and data protection rules. For example, if an HCP218withdraws its consent, the consequences are applied to any third party with whom the publisher210ofFIG.2shared HCP218data. Furthermore, processing of HCP218data ceases immediately in such a circumstance, and neither the publisher210ofFIG.2nor any of their third-party vendors or data processors can thereafter process that HCP's data.

Consent Synchronization:

FIG.10shows for illustrative purposes only an example of consent synchronization of one embodiment.FIG.10shows consent synchronization1000using a consent signal1010when an HCP218ofFIG.2user accesses the publisher #1 website100. The HCPCMF consent matrix212sends through the wireless communications the consent signal1010to advertisers960and an advertisement exchange1060to determine if advertising medical product content information is within compliance and covered by HCP218ofFIG.2user consent of one embodiment.

The HCP Consent Management Framework200ofFIG.2supports the synchronization of permission signals between publishers, advertisers, and ad exchanges to assure compliance. This is also the more crucial advertisement delivery in a programmatic advertising ecosystem where advertising impressions and placement of these ads take place in the blink of an eye.

Consent Matrix:

FIG.11shows a block diagram of an overview of the consent matrix of one embodiment.FIG.11shows the HCPCMF consent matrix212consent components1110. The consent components1110include third-party vendor consent1120selection for third-party data process consent1121. The consent components1110include consent form parameters1111and consent settings status1112.

The consent settings status1112may show an HCP218ofFIG.2opt-out response1130. The consent component1110includes any new consent type1113, for example, that was published by a regulatory agency. The consent components1110include consent patterns1114. In one embodiment a consent pattern1114may include a bundled overall consent1140wherein the HCP218ofFIG.2user accepts all medical product content information. In another embodiment, consent patterns1114provide consent granularity1150wherein a granular consent1151form may include cookies consent1152and specific user attributes1153.

In one embodiment user attributes1153include specialization1154, geographical location1155, and vendor data1156. The HCPCMF consent matrix212maintains consent audit trails1160for registered compliance1170. Different geographical locations have differing compliance regulations. However, the HCPCMF consent matrix212maintains consent audit trails1160, for example, a publisher1(USA) website1180and a publisher2(EU) website1190of one embodiment.

The HCP Consent Management Framework200ofFIG.2provides a one-stop destination for publishers where they can manage all of their HCP218ofFIG.2consent-related components and that too form a single consent management repository and dashboard. Publishers can access the framework to review their current consent settings, which they are offering to their respective HCPs, review these consent-related choices that they offer, and make required changes to these choices as per their specific needs.

Cookie Consent/Tracking Mechanism:

FIG.12shows for illustrative purposes only an example of the cookie consent/tracking mechanism of one embodiment.FIG.12shows a cookie consent/tracking mechanism1200. The cookie consent/tracking mechanism1200maintains vigilant HCP218privacy on a publisher #1 website100. HCP Consent Management Framework user privacy1230is a main concern of the publisher210. The HCP Consent Management Framework user privacy1230uses the platform to optimize ad slots/cookie offered/subscription offered/premium cookie1250of one embodiment.

Cookie Consent Management: If cookies or similar tracking mechanisms are used for profiling end-users and sending messages and advertisements based on collected information, publishers must obtain consent from HCPs and transparently explain the tracking purposes to them.

The foregoing has described the principles, embodiments, and modes of operation of the present invention. However, the invention should not be construed as being limited to the particular embodiments discussed. The above-described embodiments should be regarded as illustrative rather than restrictive, and it should be appreciated that variations may be made in those embodiments by workers skilled in the art without departing from the scope of the present invention as defined by the following claims.