> 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/logicnets-software-component-details/healthcare-integration-interoperability-suite/fhir-questionnaire-export-module-ln-fqe.md).

# FHIR Questionnaire Export Module (LN-FQE)

### License: Per LogicNets Installation

Notes:

1. Requires minimum LN Base System (B) capacity of 5 named users or 2 concurrent users.
2. Does not require additional runtime licensed components when the intent is to process LogicNets-authored content using external systems
3. Can be also used in conjunction with the FHIR Runtime Module described below
4. Customers creating FHIR-based applications in LogicNets should consider the automated test and validation capabilities of Test Manager (LN-TEM)

### LN FQE Description

The FHIR Questionnaire Export Module allows clinical guidelines and healthcare pathways modeled in LogicNets to be made available via an API to external runtime systems capable of independently processing FHIR Questionnaire-formatted data. For instance, this might be an EHR system already deployed by a healthcare provider. The LogicNets output supports most, but not all, common questionnaire elements such as radio lists, checklists, etc. It also captures the FHIR-compatible logical relationships between elements that define the decision pathway logic. Other elements not necessarily supported by FHIR Questionnaire are packaged as extensions that the rendering client can process to deliver functionality beyond the standard capabilities of the FHIR Questionnaire format. Content can be identified and exported via the API as a single data file for asynchronous downstream processing by the external client. Or, the external system can establish and maintain a persistent interactive session with the LogicNets server, processing the FHIR Questionnaire content in a “step-by-step” mode. In both cases, the rendering software fully controls how information is presented to users and there is no need to embed a LogicNets runtime client in order have users or systems interact with the content. Both approaches have unique benefits. The single step export provides complete independence of processing, but means that the client bears the full processing burden. Step-by-step is capable of supporting more sophisticated server-side processing and is often preferred for superior performance, support of greater content sophistication, and less client-side development.

The FHIR Questionnaire Export module comes with a LogicNets browser-based “Test Client” component capable of processing and displaying the modeled content, but without relying on the LogicNets standard runtime system. This component allows users to validate that the content has been successfully generated in the generic format and thereby ensures that the content should be executable by any FHIR-compatible runtime application.

### Services and Deployment Considerations

LogicNets offers training services (LN-TS) to assist designer users in creating and managing FHIR-formatted content for external use.

LogicNets offers Design and Deployment services (LN-DS) to implement FHIR data export and exchange functionality beyond the scope of the standard FHIR Questionnaire format.

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

PG-FH1-250101


---

# 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/logicnets-software-component-details/healthcare-integration-interoperability-suite/fhir-questionnaire-export-module-ln-fqe.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.