> 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/fhir-support/fhir-questionnaire-system-overview.md). # FHIR Questionnaire System Overview The LogicNets system suppurts FHIR Questionnaire export functionality with several components. ## LogicNets Components These components are available with the purchase of the *LN-FQR* license. ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-61094680744485732836f716a597fa1c5e9c36cf%2F629c94d7-fa22-4bf5-b901-2a0b4c25d951.png?alt=media) | Component | Developed by | Description | | --------------------------------- | ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Designer** | LogicNets | The LogicNets Designer is an authoring tool that can SMEs can use to create and maintain guideline content. | | **Guideline Projects** | Customer | A Guideline project is a project that contains the guideline content. The SME uses the **Designer** to create and maintain the guideline projects. | | **Guideline Packages** | Generated | When a Guideline project is ready for testing or for production, you publish the project. The result of the publishing step is a Guideline package. | | **Guideline FHIR Questionnaires** | Generated | You can convert guideline projects and packages to FHIR Questionnaires that can be executed inside the FhirTestHarness or using the LogicNets FHIR Questionnaire runtime or a runtime developed by another supplier. | | **FhirTestHarness** | LogicNets (customizable) | The FhirTestHarness is a tool that is integrated with the Designer and SMEs can use it to test the modeled content directly from the Designer. The FhirTestHarness converts the current state of the content to a FHIR Questionnaire format and executes the content using the LogicNets FHIR Questionnaire runtime. You can also customize the FhirTestHarness. | | **ExportAPI** | LogicNets | This is a REST API that allows clients to query and retrieve available FHIR Questionnaires. The documentation of the API is located at the following URL: *https\:////ApiDoc*. | | **FHIR Questionnaire Runtime** | LogicNets/Customer | This is a runtime that can render/execute an FHIR Questionnaire. LogicNets delivers an implementation of this runtime, but you can also use runtimes developed by other vendors. | | **LogicNets Runtime** | LogicNets | This is the LogicNets server-side runtime used by the LogicNets tools. | | **(Test-)Client** | LogicNets/Customer | This (test-)client connects to the ExportAPI to retrieve an FHIR Questionnaire and uses an FHIR Questionnaire runtime to execute/render the Questionnaire. LogicNets delivers a test/demo test client, which can be retrieved via the ExportAPI, but customers can also implement an own client. | --- # 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/fhir-support/fhir-questionnaire-system-overview.md?ask=&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.