> 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-extensions.md). # FHIR Extensions LogicNets uses additional defined FHIR extensions to map some LogicNets-supported concepts to FHIR Questionnaire concepts. These extensions are LogicNets specific, but they also support customer-specific extensions to export customer-specific attributes. ### Standard Extensions Used Besides the LogicNets- and customer-specific extensions the generated FHIRQuestionnaire also relies on standard FHIR (Questionnaire) extensions described in . The following standard extensions are used (this may change in the future): * * * * * * * * * * * * ### LogicNets Extensions Used The following chapters describe the LogicNets extensions used in this solution. #### ExtensionInResponse Extension | URL | | | -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **Description** | The FHIRQuestionnaire (items) can contain several (custom) extensions. By default, the extensions are not copied to the FHIRQuestionnaireResponse. In some cases, it may be useful to copy these extensions to the FHIRQuestionnaireResponse. For example, a conclusion item does contain extensions to describe additional attributes of the conclusion (e.g., priority). The client can create a conclusion overview by using the response, but it requires the additional attributes to order the conclusion. | | **Value-type** | uri () | | **Multiplicity** | 0..\* | | **Location** | questionnaire | | **Child-extensions** | - | | **Example** |

{
"extension": \[
{ "url": "",
"valueUri": ""
},
{ "url": "",
"valueUri": ""
}
],
"item": \[],
"name": "Example Guideline",
"resourceType": "Questionnaire",
"status": "active"
}

| #### Coding Extension | URL | | | -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Description** | The LogicNets system supports coding of questions and individual answer options. Every question can have zero or more codes (of one or more code systems) attached. Every answer option can also have zero or more codes attached. The FHIRQuestionnaire does support coding of items () and coding of answerOptions (); however, it does not support define multiple codes to one answerOption. This extension is used to express multiple codes of an individual answerOption. | | **Value-type** | coding () | | **Multiplicity** | 0..\* | | **Location** | Questionnaire.item.answerOption | | **Child-extensions** | - | | **Example** |

{
"answerOption": \[
{ "valueString": "Fever",
"extension": \[
{
"url": "",
"valueCoding": {
"code": "R50.9",
"display": "Fever, unspecified",
"system": ""
}
}
]
}]
}

| #### NodeType Extension | URL | | | -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **Description** | The LogicNets system supports multiple node types, such as form-part, conclusion, process, rule, and switch. In the Designer, the shape and styling of the nodes is based on the node type. Nodes in LogicNets are translated to questionnaire items in the export of type group. With this extension the fhirquestionnaire item is labeled with the node type of the original node. This extension can be used in the client runtime, for example, to style the questionnaire item differently. | | **Value-type** | string () | | **Multiplicity** | 0..1 | | **Location** | Questionnaire.item | | **Child-extensions** | | | **Example** |

{
"id": "6#1680~~1:node",
"item": \[],
"extension": \[ {
"url": "", "valueString": "conclusion"
}
\`\`
],
"linkId": "6#1680~~1",
"type": "group"
}

| #### Description Extension | URL | | | -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Description** | Some parts/nodes in LogicNets, such as the conclusion part, have a description field. This value of this field is exported via this extension. | | **Value-type** | string () | | **Multiplicity** | 0..1 | | **Location** | Questionnaire.item | | **Child-extensions** | | | **Example** |

{
\
` "id": "6#1680~1:node",`\
` "item": [],`\
` "extension": [ {`\
` "url": "http://logicnets.info/fhir/StructureDefinition/Description", "valueString": "conclusion description"`\
` }`\

],
"linkId": "6#1680\~1",
"type": "group"
}

| --- # 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-extensions.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.