> 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/example-gallery/example-projects-for-parts/fhir-questionnaire-example-with-informatics.md).

# FHIR Questionnaire Example with Informatics

Download this project to your Designer, and test it using the *FHIRQuestionnaire* test harness by following Steps 1 through 3 below.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-375f2cc3fd95caf8d36480dad553b78f3d35d90c%2F191f3213-4237-4910-93e1-64a21d1bf78e.jpg?alt=media)

1. From the menu at the bottom-left of the screen, click the *Test* tab.
2. Select *FhirQuestionnaireTestHarness* from the *Test harness* dropdown menu.
3. Click ***Test Project***.

The system opens the application screen. To see that the system includes the specific Informatics meta data in the FHIRQuestionnaireResponse, select options in the radio lists and click ***Show questionnaire response***.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-eb83c5b364a66885369c567162339ddf35a8f264%2Fe62906ce-3302-4d73-8a1b-f2af611d512e.jpg?alt=media)

Go to the specific questions in the Designer and click on the *Informatics* tab to add, edit, and/or remove the Informatics valueCoding.

## Attachments

* [InformaticsExample.zip](https://github.com/logicnets/community-portal/tree/release-9/docs/.gitbook/assets/m22t1c-InformaticsExample.zip)


---

# 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/example-gallery/example-projects-for-parts/fhir-questionnaire-example-with-informatics.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.