> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/platform-documentation/sales-materials/logicnets-support-center-framework-ln-scf.md).

# LogicNets Support Center Framework (LN-SCF)

### License basis: per user of SCF Framework-based applications

Notes:

1. Supports use of both named (NU) and concurrent user (CU) licenses
2. Includes integrated Starter App Framework
3. Commonly used options include: Knowledge Center (KC), Charting (CHA/CHR) and PDF modules

### LN-SCF Description

The Support Center Framework (SCF) is a LogicNets application designed to guide diagnostic professionals and/or their customers/patients through LogicNets-modeled diagnostic decision making. The framework is provided with the additional LogicNets Starter App framework layer, allowing users to select from a range of diagnostic guidelines, create a new session, or resume or review a pre-existing one. With this combination, the user can selectively navigate through different available topics to kick-off a guided support session for a particular topic. It then navigates the user through the modeled diagnostic steps.

With its integrated “Predictive Diagnostics” feature the SCF dynamically updates and displays the current statistical probability and confidence levels for possible diagnostic outcomes, allowing users to quickly jump to and record a probable root cause based on the aggregated history of past use across the user population. The framework also allows displayed content to be contextually linked to reference content for expanded information and guidance within each step.

The system tracks the user’s interaction through the diagnostic decision tree structure and generates a complete “case report” summarizing the questions answered and the resulting root causes identified, and any corrective actions registered during the process.

### Services and Deployment Considerations

LogicNets currently requires SCF licenses to be deployed, configured, and (if necessary) customized through engagement with LogicNets Pro Services for both training and use case-specific configurations.

Typical configuration options under these services include:

* Application-level user and role management setup and training
* Customer-specific UI styling and layout for both Starter App and Support Center Framework-based processes
* Optional Web services-based integration with external applications
* Optional customer-specific setup of PDF or other structured data report

These services usually require development and acceptance by customer of a formal SoW

PG-FR2-260217


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://community-test.logicnets.com/release-9/platform-documentation/sales-materials/logicnets-support-center-framework-ln-scf.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.