Knowledge Base

Overview

The Knowledge Base (KB) is THE primary feature of Phase 2, so gets its own page as a new feature. The KB is a fully searchable table, or collection of data, that consists of all content within the ATPG database. All articles are stored in the KB. All clinical trials are stored in the KB. Essentially, and thing that is searchable, is considered part of the KB.

Our goal is that the KB is used by visitors to solve problems. The ATPG website is not just a collection of articles and a reliable source of information. Information on PG exist throughout the internet, and with modern use of AI, is easy to find. We need to go beyond static information.

We want Phase 2 of the ATPG website to help users find and apply information specific to their needs, whether they be patients, caregivers, providers, pharmaceutical reps, or guests. The KB turns Phase 2 into something living, data with a purpose, which is much different than a set of static pages in Phase 1.

What will the knowledge base include?

The knowledge base should grow beyond simple text pages and eventually include:

• curated articles and guidance
• patient stories and community content
• provider and clinic directory entries
• facilities and locations
• images and supporting graphics
• video and other media where useful
• reference material tied to specific menu items or topics

Each content type can be published through DCMS, then surfaced in a way that makes sense for the visitor and the topic.

Why DCMS matters

DCMS lets us create menu items, content documents, and content elements in a controlled way. That means we can curate content instead of scattering it across separate static pages.

For the knowledge base, that is important because:

1. content can be organized by topic and audience
2. visibility can respect visitor type
3. search results can point users to the right menu item or document
4. content can be expanded over time without redesigning the whole site

Dynamic menus and content

Dynamic menus and content are the layer that makes the knowledge base usable in the site itself.

The knowledge base does not live by search alone. It depends on a content model that can:

• attach content to menu items
• promote content into topic tiles
• organize pages by audience or purpose
• keep related material connected as the site grows

That is why the menu system matters so much. It is not just navigation. It is part of the structure that makes the knowledge base feel coherent instead of random.

Provider directory

The provider directory is part of the knowledge base story, not a separate idea.

Right now it may be a manual list or a managed CMS entry set, but the long-term goal is to treat providers and related facilities as searchable reference data. That allows the site to grow into a practical directory as well as a documentation site.

Searchable result set

When the search experience is built, the result set should do more than return a title. It should show enough information for a visitor to decide whether to click.

A result row could include:

• result type
• title
• short description or snippet
• associated menu item or topic
• route or link
• visitor type visibility
• relevance or ranking
• last updated date

Back to top