> 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-format-adding-content-references.md).

# FHIR Questionnaire Format - Adding Content References

This topic contains information on how and where you can capture content references, including update notes, for FHIR Questionnaire applications.

### Purpose of Content References in relation to FHIR Questionnaire

Owners of medical guidelines may want to communicate two types of information in support of their FHIR questionnaire formatted guideline:

1. Footnotes associated with various "levels" of the protocol, relating to a word, diagnostic question, treatment option, or larger texts, including Principles or Guideline Board members.
2. Updates made to the guideline, including what changed and why.

When modeling medical guidelines, you can create both types of notes as content references and associate them with a node, answer option, logicnet or project. You can also organize them within folders relevant for the version, year, and other details.

See the detailed document attached to this topic for an example approach for documenting changes at the logicnet, node. and option level. The document also shows the resulting impact on the FHIR export.

## Attachments

* [FHIR Questionnaire Applications - Use of Content References.pdf](https://github.com/logicnets/community-portal/tree/release-9/docs/.gitbook/assets/80wl2f-FHIR-Questionnaire-Applications---Use-of-Content-References.pdf)


---

# 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-format-adding-content-references.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.