RELEVANCE ENGINE
Menu
00AI workflow · clearly disclosed prototype

Which information reaches the simulated HCP Inbox?

Relevance Engine demonstrates Information Triage for healthcare professionals (HCPs): a complete Newsletter is compared with a compact HCP Relevance Profile. The result is a reasoned push-or-do-not-push decision.

View the workflowUnderstand the boundaries
Several blank paper lanes converge into one ordered lane on a blue surface.
InputProfileDecision
English · ApprovedENHCP Information Triage prototype
01How the demonstration works

From the complete Newsletter to a reasoned relevance decision.

The workflow keeps the source, profile, decision, and output visibly separate.

One continuous blank paper loop is shown in full on a blue surface.

Complete Newsletter / 01

Newsletter

The demonstration uses a prepared Newsletter in full, without altering it, as the information source.

  1. 01

    Use the complete Newsletter as the source

    The demonstration uses a prepared Newsletter in full, without altering it, as the information source.

  2. 02

    Remove direct identifiers

    Direct identifiers are removed for the demonstration. This is a demo safeguard, not production-grade de-identification.

  3. 03

    Choose a compact HCP Relevance Profile

    A synthetic profile summarizes selected clinical traits and clinical domains.

  4. 04

    Compare the Newsletter and profile

    The complete Newsletter is compared with the selected profile. The same Newsletter can be evaluated differently for distinct synthetic profiles.

  5. 05

    Show the decision and rationale

    The decision is “push” or “do not push.” For a push, a short Relevance Summary remains linked to its source.

Blank paper and acrylic surfaces pass beneath dark shutters while neutral shapes continue along their path.
Demo anonymization / data boundary
Loose paper and acrylic strips pass through a paper comb and become one compact woven band.
Compact synthetic HCP Relevance Profile
02Same source, different context

One Newsletter. Different synthetic HCP profiles.

The same Newsletter can produce different demo decisions for distinct profiles. The demonstration shows the comparison without establishing clinical validity.

A blank source sheet and compact woven band meet at a clear registration seam.
Newsletter / profile comparison
The same blank paper lane passes through three differently arranged settings.
One Newsletter / different contexts
03Decision

A binary decision makes the path visible.

The output is intentionally limited to “push” or “do not push” and includes a short rationale.

A blank paper lane splits into an open mint route and a stopped dark route.
  1. A

    Push

    A short Relevance Summary can appear in the simulated HCP Inbox and remains linked to the complete Newsletter as its source.

  2. B

    Do not push

    The information does not enter the simulated HCP Inbox.

A blank slip remains connected by a cord to a larger blank source sheet.

Source-linked output

HCP Inbox

04Boundaries and transparency

The boundary is part of the demonstration.

The prototype shows an information workflow and makes clear what its output is not intended for.

  1. 01

    Fictitious data

    All Newsletters and profiles shown are fictitious; all results are generated solely within the demonstration.

  2. 02

    Information Triage

    The output classifies information. It does not provide clinical advice, diagnosis support, or treatment recommendations.

  3. 03

    Demo safeguard

    The removal of direct identifiers shown is not production-grade or regulatorily validated de-identification.

Language approval

All language versions have documented approval.

German remains the default language. The English and French language versions are approved for this publication. Language is not forced based on IP address or browser settings.

Outside the demonstrated boundary

Not claimed or demonstrated

  • Processing of real patient or HCP data
  • Clinical accuracy, efficacy, or validated scores
  • Production readiness, regulatory compliance, or availability
05Contact

Discuss the prototype in the right context.

Describe the information workflow you want to examine. Do not send patient or HCP data, or any other confidential information.

05 / Enquiry form

Prototype enquiry

All visible fields are required. Do not submit confidential information.