EHR
Health System
Resources
BlogsCase Studies
Login
Request Demo

Ad Placement PolicyEffective Date: 28th November 2025

1. Introduction

This Ad Placement Policy (“Policy”) governs the participation of all publishers (“Publishers”) in the Doceree Spark program (“Program”) as delivered through the Spark Platform, Doceree’s AI-powered, clinical-context–aware communication framework that enables the delivery of real-time, patient-led, contextually triggered messages (“Spark Messages”), including Co-Pay Spark, Trial Spark, and Drug Spark. This Policy constitutes a binding legal framework between you (“you” or “your”) and Doceree Inc., a Delaware corporation with its principal place of business in the United States, together with its affiliates, subsidiaries, and related global entities (“Doceree,” “we,” “us,” or “our”). By participating in the Program, you acknowledge and agree to comply with all terms set forth in this Policy, as well as all applicable laws, regulations, and healthcare advertising standards governing contextual messaging, digital content delivery, privacy, data usage, and clinical workflow safety.

For purposes of this Policy, “Publisher Property” or “Publisher Properties” refers to any electronic health record (“EHR”) system, health system digital environment, clinical workflow module, secured healthcare application, or other Doceree-approved interface that you operate or control and within which Spark Messages may be displayed. As a Publisher, you are responsible for ensuring that all Spark Message surfaces and contextual-trigger placements within your environment comply with this Policy, including adherence to clinical-workflow appropriateness, trigger integrity requirements, and non-interference with patient care. Doceree reserves the right, at its sole discretion, to disable Spark Message delivery on any Publisher Property, suspend Program participation, or terminate your account for any violation of this Policy. Accounts suspended or terminated for non-compliance may not be eligible for reinstatement.

Publishers must ensure that Spark Messages appear only in professional, clinically suitable, and workflow-safe environments. Spark Messages may not be displayed on any screen, module, or workflow surface deemed clinically inappropriate, disruptive, misleading, or inconsistent with accepted healthcare standards. Spark Messages must not appear in locations where their presence could interfere with clinical judgment, impede patient care, confuse healthcare professionals, or create an impression that Spark Messages are clinical guidance or medical decision-support content. This suitability requirement replaces traditional consumer-web “adult/mature content” restrictions, as Spark operates exclusively within regulated healthcare environments.

Doceree reserves the right to amend this Policy at any time to reflect operational needs, evolving clinical-workflow standards, regulatory obligations, or enhancements to the Spark Platform. Your continued participation in the Program following any amendment constitutes acceptance of the updated Policy. The Program is part of Doceree’s proprietary contextual-messaging and analytics ecosystem, including the Spark Platform, integration toolkits, reporting interfaces, and associated resources (collectively, the “Services”), which facilitate compliant, precise, and contextually appropriate delivery of Spark Messages across Publisher Properties.

2. General Guidelines

  1. Legal, Regulatory, and Clinical Compliance: Publishers must ensure that all EHR environments, health system modules, and other approved Publisher Properties in which Spark Messages are delivered comply with all applicable laws, healthcare regulations, professional advertising standards, and institutional policies governing contextual messaging, patient-safety workflows, data privacy, and digital content delivery. Spark Messages may not be displayed in any environment that promotes, facilitates, or is associated with unlawful activities or clinically inappropriate practices. Publishers must also ensure that no Spark Message placement violates jurisdiction-specific healthcare advertising regulations, pharmaceutical marketing requirements, or institutional medical-governance standards.

  2. Clinical Content Suitability, and Workflow Safety: Publishers are responsible for maintaining a clinically appropriate, professional, and workflow-safe environment for Spark Message placement. Spark Messages must not appear alongside, adjacent to, or within content that is misleading, clinically unverified, contradictory to medical standards of care, or inappropriate for healthcare professionals. Publisher Properties must not incorporate exaggerated claims, non-evidence-based health information, or any surrounding content that could interfere with clinical interpretation or decision-making. All Spark Message placements must preserve context clarity and workflow safety within the clinical environment.

  3. Respect, Professionalism, and Non-Discrimination: Publishers must not deliver Spark Messages on any surfaces, modules, or workflows containing discriminatory, offensive, harassing, stigmatizing, or culturally insensitive content. Prohibited material includes any content targeting or demeaning individuals or groups based on race, ethnicity, religion, gender, gender identity, sexual orientation, disability status, socioeconomic background, age, health condition, or any other protected personal characteristic. All Publisher Properties must uphold high standards of professionalism, clinical integrity, and inclusivity consistent with healthcare-industry expectations.

  4. Brand, Clinical, and Workflow Quality Standards: Doceree reserves the right, in its sole discretion, to restrict or disallow Spark Message serving within Publisher Properties that may compromise Doceree’s brand, clinical integrity, or user trust. This includes environments featuring low-quality or clinically dubious content, unmoderated user-generated information, inappropriate or distracting visual elements, or any material inconsistent with Spark’s role as a contextual, workflow-safe messaging platform. Spark Messages must only appear in surfaces that maintain the professional, clinical, and operational standards of EHR systems and health system environments.

3. Ad Placement Restrictions and Prohibitions

For the purpose of this Policy, “Spark Messages” means all promotional, informational, contextual, or patient-led message formats delivered by Doceree through the Spark Platform, including Co-Pay Spark, Trial Spark, Drug Spark, and any derivative or adapted versions created or configured by Doceree. Spark Messages may only be displayed in approved, clinically appropriate, workflow-safe environments and may not be placed in any context that exposes Doceree, its clients, or healthcare professionals to legal, regulatory, operational, or clinical-safety risks.

  • Prohibited Clinical Modules and High-Sensitivity Surfaces
    Spark Messages must not appear in any clinical module, screen, or workflow surface where the presence of promotional messaging may interfere with clinical judgment, patient care, or regulatory expectations. Prohibited surfaces include, but are not limited to:
    • Medication prescribing, ordering, or eRx workflows
    • Diagnosis entry, ICD/SNOMED selection, or problem-list screens
    • Clinical Decision Support (CDS) alerts or interruptive clinical prompts
    • Lab or imaging results displays
    • Clinical documentation or patient-chart note editors
    • Vital signs, clinical assessment, or triage screens
    • Patient-identifier headers or personally identifiable patient-information sections
    • Emergency, critical care, or high-acuity care modules
    • Consent forms, privacy warnings, or legal disclosure screens

    Spark Messages must never appear in locations where they could be mistaken for clinical guidance or medical advice.

  • Prohibited Screen Types
    Spark Messages may not be displayed on:
    • Login, authentication, logout, or session-timeout screens
    • Admin, configuration, or IT system-management interfaces
    • Error messages, downtime notices, or connectivity warnings
    • Transitional screens with no clinical content
    • Public-facing, patient-facing, kiosk, or shared-consumption screens
    • Mobile or browser modes not used by authenticated healthcare professionals

    Spark is intended exclusively for authenticated HCP-only professional workflows.

  • Contextual Trigger Integrity Restrictions
    • To preserve clinical neutrality and system integrity:
    • Clinical-context triggers must originate from authentic workflow events.
    • Publishers may not simulate, manipulate, or artificially generate triggers.
    • Spark Messages must not be refreshed, repeated, or forced outside natural workflow conditions.
    • Trigger timing, sequence, and eligibility criteria may not be modified by the Publisher.
    • Publishers may not alter, intercept, or enrich contextual signals with any PHI or behavioral data.

    All contextual data must comply with Spark integration specifications.

  • HIPAA, PHI, and Sensitive Data Restrictions
    To maintain strict legal and privacy boundaries:
    • No PHI may be transmitted to Doceree under any circumstances.
    • Spark does not require, store, or process identifiable patient data.
    • Publishers must ensure Spark Messages never display over, obscure, or interact with patient identifiers.
    • Contextual workflow data used for triggering Spark Messages must be anonymized or de-identified.
    • UI overlap or rendering issues that expose PHI beneath or around Spark Messages are strictly prohibited.

    Any breach or suspected breach must be reported immediately.

  • Healthcare Regulatory, Pharmaceutical, and FDA Compliance
    Spark Messages relating to pharmaceuticals, therapies, or clinical trials must not be placed in any environment or configuration that:
    • misrepresents product claims
    • violates FDA promotional rules or labeling requirements
    • omits required fair-balance elements (where applicable)
    • misleads HCPs regarding safety, efficacy, or indications
    • conflicts with institutional advertising or medical-governance rules

    Publishers may not modify, truncate, or reposition Spark Messages to alter regulatory intent.

  • Workflow Interference and UI/UX Disruption Restrictions
    Spark Messages must be delivered in a manner that does not:
    • obscure, overlap, or impede critical clinical actions
    • slow down EHR performance or screen-loading times
    • interfere with data entry, navigation, or task completion
    • mimic alert styles, icons, or urgency indicators used by the EHR
    • create repetitive or disruptive experiences that affect clinical efficiency

    Spark must always remain subordinate in visual priority to clinical functions.

  • Professionalism, Respect, and Non-Discrimination
    Spark Messages may not appear adjacent to or within any environment containing:
    • discriminatory or stigmatizing content
    • harassment, hate, or culturally insensitive material
    • unverified or unsafe medical claims
    • inflammatory or misleading commentary
    • inappropriate professional communication

    Publisher Properties must reflect professional conduct consistent with clinical standards.

  • Brand Safety, Reputational Risk, and Environmental Suitability
    Doceree may restrict Spark Message delivery in any environment that:
    • conflicts with medical, ethical, or clinical standards of care
    • includes unmoderated or unreliable medical information
    • hosts content that could cause reputational, legal, or safety risk
    • undermines trust in the healthcare system or clinical content
    • contains fraudulent, misleading, conspiratorial, or harmful material
    • presents low-quality, outdated, or clinically unsafe content

    Doceree may require environmental pre-approval, implement allowlists/blocklists, or disable Spark Message delivery without notice.

  • Clinical Mimicry and Medical Advice Prohibition
    Spark Messages must not simulate, resemble, or be easily confused with:
    • clinical alerts, CDS prompts, or medication warnings
    • treatment recommendations or medical directives
    • risk notifications, contraindication notes, or safety flags
    • clinician-to-clinician or system-to-clinician communications

    Spark Messages must never be interpreted as clinical direction.

  • Publisher Modification Restrictions
    Publishers may not:
    • alter Spark Message layout, font, structure, or labeling
    • wrap messages in custom UI elements
    • restyle messages to look like EHR-native cards
    • add or remove interactive elements not provided by Doceree
    • resize, relocate, hide, or visually manipulate Spark Messages

    Spark Message design must remain exactly as provided by Doceree.

  • Workflow Change Notification Requirement
    Publishers must notify Doceree at least 30 days in advance of:
    • EHR UI redesigns
    • layout changes affecting Spark placements
    • DOM or component-structure changes
    • clinical module upgrades or version changes
    • workflow sequencing adjustments
    • migration to new rendering engines or frameworks

    Doceree may pause Spark delivery until compatibility is verified.

  • Security & Access-Control Requirements
    Spark Messages must only be displayed in:
    • authenticated, role-based, secure HCP environments
    • access-controlled clinical systems
    • TLS-encrypted communication channels

    Spark must not appear in:
    • shared or public workstations without login
    • unsecure browser sessions
    • environments where HCP identity cannot be validated
  • System Performance, Stability, and Latency Safeguards
    Publishers must ensure Spark delivery does not:
    • degrade clinical system performance
    • generate excessive rendering latency
    • impair patient-chart loading
    • interfere with network-sensitive modules
    • cause CPU or memory bottlenecks

    Performance regressions must be resolved immediately.

  • Prohibited Adjacent Content (Healthcare-Specific)
    Spark Messages must not appear next to:
    • non-evidence-based medical content
    • anti-science narratives
    • misleading drug or therapy claims
    • unapproved supplements or unsafe products
    • political, religious, or controversial commentary
    • peer-to-peer clinician discussions or sensitive notes
  • Emergency and High-Acuity Scenario Exclusions
    Spark Messages must not appear during:
    • emergency department workflows
    • code/rapid response events
    • critical-care workflows
    • high-acuity inpatient workflows
    • trauma or urgent-care modules

    Ensures Spark never appears during time-sensitive care.

  • Third-Party Integration Restrictions
    Publishers may not:
    • pass Spark Messages to third-party mediation layers
    • commingle Spark placements with other ad networks
    • allow reselling, sublicensing, or sub-syndication
    • expose Spark Messages through unsupported integrations

    Spark must remain within the Doceree-approved environment only.

4. Publisher Responsibility for Content

Publishers acknowledge and agree that they are solely responsible for all content, data, workflows, user interfaces, and system environments within their Publisher Properties, including but not limited to all clinical modules, administrative interfaces, informational content, and any third-party materials integrated or displayed within such environments. Publishers further acknowledge that the accuracy, appropriateness, and compliance of all content within their systems, including contextual signals used to trigger Spark Messages, are the full responsibility of the Publisher.

Publishers must ensure that all content, screens, workflows, and contextual triggers within their Publisher Properties comply with this Policy, all Spark Platform integration requirements, applicable healthcare laws and regulations, institutional clinical-content standards, and all relevant data privacy obligations. Content within Publisher Properties must not:

  • contain misleading, inaccurate, unverified, or clinically unsafe information;
  • conflict with evidence-based medical standards or institutional clinical governance;
  • expose or render visible Protected Health Information (“PHI”) in violation of HIPAA or applicable privacy laws;
  • include malware, scripts, tracking tools, or code that could compromise system security or interfere with Spark Message delivery;
  • misrepresent affiliation with Doceree, healthcare institutions, or clinicians;
  • facilitate or depict illegal, unethical, unsafe, or fraudulent behavior within clinical or administrative workflows.

Doceree does not review, verify, moderate, or assume responsibility for any content, workflow, or interface displayed within Publisher Properties, including clinical content, patient information, or third-party integrations. Publishers remain fully responsible for ensuring that all content and all areas where Spark Messages are displayed comply with legal, regulatory, clinical, and institutional standards. Publishers agree to indemnify, defend, and hold harmless Doceree, its affiliates, and its clients from any claims, damages, regulatory actions, losses, or liabilities arising out of or relating to the content, workflows, clinical modules, or contextual signals within Publisher Properties.

5. Additional Requirements

For the purpose of delivering Spark Messages through the Spark Platform, Publishers must ensure that their Publisher Properties do not host, display, generate, transmit, or allow any content, workflows, user interfaces, or contextual signals that create legal, regulatory, clinical, reputational, security, or safety risks for Doceree, its clients, or healthcare professionals. Spark Messages may not be delivered on any surface, module, or workflow containing or associated with content, data, or activities that:

  • Violate Laws, Regulations, or Institutional Policies
    • contravene applicable healthcare, advertising, privacy, or data-protection regulations (including HIPAA, HITECH, GDPR, CCPA, or local equivalents);
    • violate medical-governance, compliance, or content-standards established by the EHR vendor or health system;
    • infringe upon intellectual property, data rights, or proprietary material belonging to third parties.
  • Present Clinical Inappropriateness, Inaccuracy, or Safety Risk
    • contain misleading, unverified, unsubstantiated, or clinically unsafe information;
    • conflict with evidence-based medical practice or institutional guidelines;
    • introduce clinical misinformation or pseudo-scientific content;
    • could confuse healthcare professionals regarding diagnosis, treatment, or clinical workflow.
  • Include Discriminatory, Harassing, or Unprofessional Material
    • contain content that is discriminatory, harassing, inflammatory, or stigmatizing toward any individual or group on the basis of race, ethnicity, religion, gender, sexual orientation, disability, socioeconomic status, age, veteran status, or other protected characteristics;
    • undermine professional conduct or clinical decorum expected in healthcare environments.
  • Facilitate Illegal, Unethical, or Fraudulent Behavior
    • promote, depict, or facilitate unlawful acts or unethical behavior within clinical, administrative, or operational workflows;
    • misrepresent the identity, affiliations, or credentials of users, healthcare institutions, or clinical professionals;
    • mislead, deceive, impersonate, or otherwise distort the origin, accuracy, or intent of clinical or non-clinical content.
  • Pose Data Security, System Integrity, or Technical Risks
    • contain malicious code, unauthorized scripts, or software that could compromise system security, interfere with Spark delivery, or disrupt EHR/health system performance;
    • introduce data exfiltration risks, unauthorized data capture, or third-party tracking technologies not permitted in clinical systems;
    • alter or manipulate contextual signals or workflow data in ways inconsistent with Spark Platform requirements.
  • Create Reputational, Compliance, or Environmental Risk for Doceree or its Clients
    Spark Messages must not appear in environments that:
    • undermine the credibility or neutrality of clinical information;
    • conflict with standards of care or institutional values;
    • display content that is medically inappropriate, ethically sensitive, or inconsistent with professional healthcare expectations;
    • contain commentary, materials, or third-party integrations that could reflect adversely on Doceree, its clients, or the health system.

    • Publishers remain solely responsible for monitoring, moderating, and ensuring the ongoing compliance of all content, workflows, and contextual signals presented within their Publisher Properties, regardless of whether such content originates from the Publisher, a clinical partner, a vendor integration, or any third party. Doceree bears no responsibility for the accuracy, integrity, appropriateness, or legality of any Publisher Property content and shall be indemnified and held harmless from any claims or liabilities arising from such content.

6. User Experience, Workflow Integrity, and Viewability Standards

Publishers must ensure that Spark Messages are delivered in a manner that upholds the highest standards of usability, workflow safety, and clinical clarity within their Publisher Properties. Spark Messages must not interfere with navigation, obscure clinical information, interrupt user tasks, or degrade the functionality or performance of any EHR or health-system workflow. Spark Message placement must preserve full visibility and access to all clinical modules, actions, and decision points at all times.

  • Spark Messages must be:

    • non-interruptive and subordinate to all clinical content and system components;
    • clearly distinguished from clinical alerts, system notifications, CDS messages, or other clinical decision-support elements;
    • visually identifiable as sponsored or informational messaging;
    • presented in a stable, predictable location that does not move, overlay, float, or reposition automatically;
    • rendered reliably without affecting page load times, system responsiveness, or workflow continuity.

    • Publishers must ensure that Spark Messages remain sufficiently visible to the intended authenticated healthcare professional without requiring additional scrolling, interaction, or workflow modifications. Spark Messages must never be displayed in a manner that simulates urgency, mimics clinical warnings, or encourages clinicians to alter medical decision-making.

    Doceree may issue additional UX, placement, or viewability specifications tailored to specific clinical environments or proprietary EHR designs. Publishers must comply with all such specifications and must verify that Spark Message placement preserves consistent, safe, and non-disruptive user experience standards throughout all supported workflows.

    7. Tracking, Reporting, and Analytics

    For the purpose of delivering Spark Messages through the Spark Platform, Publishers must permit Doceree to implement and maintain the technical instrumentation necessary to validate contextual triggers, measure Spark Message delivery, monitor system performance, and ensure compliance with Spark Platform integration requirements. Tracking for Spark is performed through server-to-server signals, SDK integration events, workflow triggers, and other Doceree-approved technical mechanisms, and does not involve cookies, browser-based pixels, or consumer ad-network tracking technologies.

    Publishers must not remove, modify, suppress, intercept, or otherwise interfere with any Spark Platform instrumentation, including contextual trigger events, impression confirmations, delivery logs, or diagnostic signals. Publishers must ensure that all workflow, UI, and module-level behaviors necessary for accurate Spark measurement remain functional and unaltered. Any system changes that may affect trigger accuracy, data flows, or reporting must be communicated to Doceree in advance.

    Publishers shall provide Doceree, upon request, with accurate workflow, placement, or system-level data reasonably necessary to validate Spark Message delivery, contextual suitability, performance metrics, and overall integration compliance. All reporting and tracking data exchanged between the parties must adhere to applicable privacy, regulatory, and clinical-governance requirements and may not contain PHI.

    8. Spark Message Review and Approval Process

    Doceree reserves the right, at its sole discretion, to review, approve, modify, suspend, or reject any Spark Message prior to, during, or after its display within a Publisher Property. Publishers may not deploy, enable, or display any Spark Message, including Co-Pay Spark, Trial Spark, Drug Spark, or any variant thereof, unless such content has been expressly approved by Doceree and complies with all Spark Platform requirements, regulatory obligations, and applicable healthcare industry standards.

    Doceree may immediately restrict or suspend Spark Message delivery on any Publisher Property that fails to meet placement, workflow, safety, or clinical appropriateness requirements. This includes improper trigger behavior, module-level misplacement, UI misuse, or any deviation from the approved Spark implementation.

    Publishers may request clarification, submit remediation evidence, or seek reinstatement of Spark Message delivery; however, Doceree’s determinations regarding clinical suitability, regulatory compliance, technical compatibility, brand and reputational risk shall be final and binding.

    9. Compliance with Laws, Healthcare Regulations, Industry Standards, and Consent Requirements

    Publishers must ensure full compliance with all applicable local, national, and international laws, healthcare regulations, and professional advertising standards governing the delivery of Spark Messages through the Spark Platform. This includes, without limitation, strict adherence to all privacy and data-protection laws such as the Health Insurance Portability and Accountability Act (“HIPAA”), the Health Information Technology for Economic and Clinical Health Act (“HITECH”), the General Data Protection Regulation (“GDPR”), the California Consumer Privacy Act (“CCPA/CPRA”), and any other relevant data-protection frameworks applicable in the jurisdictions where Spark Messages are delivered. Publishers must ensure that no Protected Health Information (“PHI”) is transmitted to Doceree under any circumstances, and that all clinical-context signals used to trigger Spark Messages are properly anonymized or de-identified in accordance with applicable law.

    Publishers are further required to comply with all healthcare and pharmaceutical advertising regulations, including but not limited to the promotional, labeling, and fair-balance requirements enforced by the U.S. Food and Drug Administration (“FDA”), truth-in-advertising standards promulgated by the Federal Trade Commission (“FTC”), and all applicable national or regional rules governing medical-product communications. Publishers must also comply with institutional clinical-content governance rules and medical-ethics standards that apply to healthcare systems and electronic health-record environments. Spark Messages may not be placed or displayed in any manner that could violate or create ambiguity under these regulatory requirements, misrepresent the intent of the message, or confuse healthcare professionals regarding its clinical relevance.

    In addition, Publishers must comply with all technical, operational, cybersecurity, and interoperability standards applicable to clinical systems, including secure role-based access control, authenticated-user requirements, privacy-by-design principles, least-privilege access, data-minimization expectations, and relevant industry security frameworks such as NIST and ISO/IEC 27001. Publishers are responsible for obtaining all consents, permissions, approvals, and institutional authorizations necessary for the use of contextual workflow signals, the integration and operation of the Spark Platform, and the transmission of any non-PHI operational, analytical, or diagnostic data to Doceree for the purpose of validating trigger behavior or measuring Spark Message performance. Publishers must maintain accurate records of all such consents and authorizations and make them available to Doceree upon reasonable request.

    Spark Messages must not be delivered within any Publisher Property, environment, clinical module, or workflow that violates applicable laws, healthcare regulations, privacy requirements, medical-governance guidelines, advertising rules, or ethical standards of clinical practice. Doceree reserves the right to restrict, suspend, or discontinue Spark Message delivery immediately where Publisher Properties fail to satisfy these compliance obligations or present a material legal, regulatory, or reputational risk.

    10. Prohibited Practices

    For the purpose of delivering Spark Messages through the Spark Platform, the following practices are strictly prohibited. Publishers may not manipulate, generate, simulate, or artificially trigger Spark Messages or related contextual events, including any attempt to create false, duplicated, or mechanized workflow signals that do not originate from legitimate clinical activity. Publishers must not alter, obscure, mask, restyle, wrap, rebrand, or modify Spark Messages, their appearance, labeling, or placement in any manner, nor may they attempt to integrate Spark Messages into custom user-interface elements in ways that could misrepresent their source or confuse healthcare professionals. Spark Messages may only be delivered through authorized, Doceree-approved integrations, and Publishers may not reroute, proxy, forward, or otherwise transmit Spark Messages through unauthorized domains, subdomains, applications, intermediaries, or third-party systems.

    Publishers are expressly prohibited from interfering with Spark Message rendering, visibility, impression measurement, or contextual-trigger reporting. This includes, but is not limited to, suppressing or manipulating impression delivery, preventing proper measurement of contextual signals, modifying SDK or API behavior, overriding integration logic, artificially delaying or accelerating message delivery, or introducing technical configurations that cause Spark Messages to appear in unintended workflows, surfaces, or modules. Any practice that seeks to deceive, mislead, inflate performance metrics, distort reporting accuracy, circumvent Spark Platform technical requirements, or compromise the integrity of Doceree’s contextual messaging framework is strictly forbidden. Doceree reserves the right to suspend or terminate Spark Message delivery immediately if any prohibited practice is detected.

    11. Disclaimer

    All Spark Messages, contextual triggers, technical integrations, analytics, reporting features, and related services provided through the Spark Platform or delivered within Publisher Properties are provided strictly on an “as is” and “as available” basis, without any representation, warranty, or assurance of any kind, whether express or implied. Without limiting the foregoing, Doceree makes no warranty regarding the accuracy, completeness, timeliness, reliability, availability, performance, or legal or regulatory compliance of Spark Messages, contextual triggers, workflow-derived signals, or any outcomes arising from their delivery within EHR or health-system environments. Doceree does not warrant that Spark Messages will be delivered without interruption, error, delay, or misplacement, nor does Doceree guarantee that Spark Messages will achieve any particular result, clinical impact, performance metric, or operational objective.

    Except to the extent expressly agreed in writing, Doceree disclaims all liability arising from the placement, display, delivery, integration, triggering, performance, or interpretation of Spark Messages within Publisher Properties, including any effects on user experience, workflow behavior, clinical perception, or system performance. Publishers acknowledge that Spark Messages are informational in nature, are not clinical guidance or medical decision support, and must not be relied upon as such. Publishers further acknowledge that they bear sole responsibility for the operation, content, and regulatory compliance of their Publisher Properties and agree that Doceree shall not be liable for any claims, losses, damages, regulatory actions, penalties, or other consequences arising out of or relating to the surrounding clinical content, contextual triggers, workflow environments, or system configurations in which Spark Messages appear.

    12. Suspension, Termination, and Remedies

    Doceree may suspend, restrict, or terminate a Publisher’s participation in the Program, in whole or in part, if the Publisher violates this Policy, fails to comply with Spark Platform integration requirements, jeopardizes the accuracy or integrity of contextual triggers, places Spark Messages in prohibited clinical environments, or otherwise engages in conduct that creates legal, regulatory, clinical, operational, or reputational risk for Doceree, its clients, or healthcare professionals. Doceree may immediately disable Spark Message delivery where non-compliance presents a risk to clinical workflow safety, data-privacy obligations, or regulatory requirements. In the event of suspension or termination, Publishers may forfeit accrued payments, and Doceree may withhold or adjust amounts owed to mitigate actual or potential losses arising from the Publisher’s non-compliance. Doceree may pursue any other remedies available under law or equity, including claims for damages resulting from improper implementation, trigger manipulation, workflow interference, or misuse of Spark Messages or related integration tools. Reinstatement, where permitted, shall occur solely at Doceree’s discretion and only after all violations have been fully remediated to Doceree’s satisfaction.

    13. Reporting Violations

    Publishers must promptly report any actual or suspected violations of this Policy, including but not limited to improper Spark Message placement in restricted clinical modules, deviations from approved workflow-trigger behavior, exposure of Spark Messages in contexts that contain PHI, unauthorized modification of Spark Message presentation, performance issues that may impact clinical workflows, or any integration defects that may compromise safety, compliance, or system integrity. Doceree reserves the right to conduct periodic reviews, audits, technical assessments, or workflow analyses of Publisher Properties to verify adherence to Spark Platform requirements, monitor contextual-trigger accuracy, evaluate message placement behavior, and detect potential violations. Publishers must cooperate fully with any such audit or investigation and must promptly implement corrective actions required by Doceree to restore compliance and ensure the ongoing safe, accurate, and compliant delivery of Spark Messages.

    14. Intellectual Property Ownership

    All intellectual property rights in Spark Messages, contextual triggers, creative assets, clinical-workflow configurations, integration materials, and all related content delivered through the Spark Platform, including, without limitation, logos, trademarks, text, images, videos, layouts, messaging templates, design elements, data structures, technical specifications, and any derivatives thereof, remain the exclusive property of Doceree or its respective clients and licensors. Publishers are granted only a limited, non-exclusive, non-transferable, non-sublicensable, and revocable license to display Spark Messages within their Publisher Properties strictly in accordance with this Policy, the applicable Program terms, and all Spark Platform integration requirements. Publishers shall not modify, alter, restyle, recreate, reproduce, distribute, disassemble, reverse engineer, decompile, translate, adapt, generate derivative works from, rebrand, or otherwise exploit Spark Messages, Spark creative assets, or any component of the Spark Platform without Doceree’s prior written consent. Nothing in this Policy grants Publishers any ownership interest, intellectual-property rights, or proprietary claims in Spark Messages, the Spark Platform, or any Doceree technology. Any unauthorized use of Spark Messages, creative elements, or integration materials constitutes a material breach of this Policy and may result in immediate suspension or termination of Spark Message delivery, in addition to any legal or equitable remedies available to Doceree.

    15. Liability and Indemnification

    Publishers acknowledge and agree that they are solely responsible for the accuracy, integrity, configuration, and compliance of all clinical workflows, contextual triggers, placement surfaces, and system environments in which Spark Messages are delivered. Publishers shall be fully liable for any legal, regulatory, financial, operational, or reputational consequences arising from improper Spark Message placement, trigger manipulation, non-compliant integrations, PHI exposure, clinical-workflow interference, or any violation of this Policy. Publishers agree to indemnify, defend, and hold harmless Doceree, its affiliates, licensors, and clients from and against any claims, damages, losses, regulatory penalties, enforcement actions, litigation costs, or reputational harm arising from Publisher conduct, including but not limited to improper implementation of the Spark Platform, breach of applicable healthcare or privacy regulations, misrepresentation of contextual data, or the surrounding content and workflows within Publisher Properties. This indemnification obligation applies regardless of whether claims are asserted by healthcare professionals, regulatory authorities, institutional partners, or third parties.

    16. Technical Requirements

    Publishers must ensure that all Publisher Properties meet the technical, architectural, and operational requirements necessary for accurate, secure, and reliable delivery of Spark Messages within EHR or health-system environments. This includes maintaining compatibility with Doceree’s Spark SDKs, APIs, server-to-server integrations, contextual-trigger specifications, rendering requirements, and workflow-event instrumentation. Publisher Properties must operate in a secure, authenticated, role-based environment and must maintain system configurations that support proper loading, display, and performance of Spark Messages without degrading clinical workflow performance, screen rendering, or system responsiveness. Publishers must promptly remediate any technical, performance, latency, integration, or UI issues that interfere with Spark Message delivery, measurement, or contextual-trigger reporting, and must not deploy system updates or workflow changes that may impact Spark functionality without prior notice to Doceree. Doceree may suspend Spark Message delivery until technical compliance has been verified.

    17. Audit and Access

    Doceree, or its authorized agents, may conduct audits, assessments, inspections, workflow evaluations, or technical reviews of Publisher Properties, including EHR modules and health-system environments, to verify adherence to this Policy, confirm contextual-trigger accuracy, assess Spark Message placement behavior, and ensure ongoing compliance with Spark Platform requirements. Publishers shall provide timely and reasonable access to technical resources, documentation, logs, integration details, workflow demonstrations, system information, and such other materials as Doceree may reasonably request to complete an audit. Publishers must fully cooperate with all audit activities, including implementing any corrective actions required by Doceree to address deficiencies, mitigate risk, or restore compliance. Failure to cooperate with an audit, or failure to remediate identified issues within a reasonable period, may result in immediate suspension or termination of Spark Message delivery and Program participation.

    18. Amendments

    Doceree reserves the right to amend, update, or modify this Policy, in whole or in part, at any time in its sole discretion in order to reflect changes in regulatory requirements, clinical-workflow standards, Spark Platform capabilities, technical specifications, operational rules, security practices, or industry expectations applicable to EHR and health-system environments. Any such amendments will become effective upon posting or notification through Doceree’s designated communication channels. Continued integration with, or delivery of, Spark Messages within Publisher Properties following the effective date of any amendment shall constitute the Publisher’s acknowledgment and acceptance of the revised Policy. Publishers are responsible for reviewing this Policy on a regular basis and ensuring ongoing compliance with the most current version, including implementing any technical, operational, or workflow changes necessary to maintain adherence to Spark Platform requirements.

    19. Grievance and Contact

    Publishers or authorized representatives who have questions, concerns, or complaints regarding this Policy, the placement or delivery of Spark Messages, integration requirements, technical behavior, or compliance matters may submit a written inquiry to Doceree’s legal team. All grievances should be submitted in writing to:

    • Email: legal@doceree.com
    • Address: Doceree Inc., 150 John F Kennedy Parkway, Suite 403, Short Hills, NJ 07078, USA

    To facilitate proper review, Publishers are encouraged to include sufficient detail regarding the concern, including the affected workflow or module, the nature of the issue, relevant system information, observed behavior, and any supporting documentation or logs. Doceree will review and respond to all submissions in a timely manner and may request additional information as needed to assess and resolve the matter. Publishers agree to cooperate fully with any follow-up inquiries, technical reviews, or compliance assessments arising from such grievances.