A CQIF questionnaire is a questionnaire with the added ability to describe behavior associated with questions. For example, whether or not to display a particular question or group of questions, or automatically calculating the value of an answer based on the answers to previous questions.

The logical id of the resource, as used in the url for the resource. Once assigned, this value never changes.

The only time that a resource does not have an id is when it is being submitted to the server using a create operation. Bundles always have an id, though it is usually a generated UUID.

The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content may not always be associated with version changes to the resource.

A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content.

Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element as much as possible.

The base language in which the resource is written.

Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).

A human-readable narrative that contains a summary of the resource, and may be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.

Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative.

These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope.

This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again.

The content of the module, if any. If this is a library, this would be the CQL or ELM representation of the library contents.

May be used to represent additional information that is not part of the basic definition of the resource, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

This records identifiers associated with this question set that are defined by business processed and/ or used to refer to it when a direct URL reference to the resource itself is not appropriate (e.g. in CDA documents, or in written / printed documentation).

Need to allow connection to a wider workflow.

The version number assigned by the publisher for business reasons. It may remain the same when the resource is updated.

In some cases, separate resource instances might be created for each version (if an older version can be maintained once a new version exists).

The lifecycle status of the questionnaire as a whole.

The date that this questionnaire was last changed.

Organization or person responsible for developing and maintaining the questionnaire.

Conveys responsibility for the questions and their organization and also helps evaluate the questionnaire's "authority".

Contact details to assist a user in finding and communicating with the publisher.

Identifies the types of subjects that can be the subject of the questionnaire.

If none are specified, then the subject is unlimited.

A collection of related questions (or further groupings of questions).

Need to be able to logically group answers to grouped questions.

The Questionnaire itself has one "root" group with the actual contents of the Questionnaire. Information on this root group applies to the questionnaire as a whole.

unique id for the element within a resource (for internal references).

The name of an expression in a referenced library that describes the logic for a particular context.

May be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

An identifier that is unique within the questionnaire allowing linkage to the equivalent group in a QuestionnaireResponse resource.

QuestionnaireResponse does not require omitted groups to be included and may have some groups that repeat, so linkage based on position alone is not sufficient.

May be omitted if there is no expectation to link answers back to a questionnaire. This can be a meaningful id (e.g. a LOINC code) but is not intended to have any meaning. GUIDs or sequential numbers are appropriate here.

The human-readable name for this section of the questionnaire.

When including text for the questionnaire with the answers, sections may have a section header.

The title of the "root" group is the title for the questionnaire.

Identifies a how this group of questions is known in a particular terminology such as LOINC.

Allows linking of groups of questions (and complete questionnaires) to formal terminologies.

The code(s) for the "root" group apply to the questionnaire as a whole.

Additional text for the group, used for display purposes.

When including text for the questionnaire, each section may contain additional explanations are background text.

Common extensions are defined for more specialized types of display text.

If true, indicates that the group must be present and have required questions within it answered. If false, the group may be skipped when answering the questionnaire.

Whether the group may occur multiple times in the instance, containing multiple sets of answers.

Groups may be used to create set of (related) questions that can be repeated to give multiple answers to such a set.

A sub-group within a group. The ordering of groups within this group is relevant.

Reports can consist of complex nested groups.

Set of questions within this group. The order of questions within the group is relevant.

Must register answers to questions.

unique id for the element within a resource (for internal references).

May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

• unordered
• Open
• discriminators: url

The name of an expression in a referenced library that describes the logic for a particular context.

The name of an expression in a referenced library that describes the logic for a particular context.

May be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

An identifier that is unique within the questionnaire allowing linkage to the equivalent group in a QuestionnaireResponse resource.

QuestionnaireResponse does not require omitted groups to be included and may have some groups that repeat, so linkage based on position alone is not sufficient.

May be omitted if there is no expectation to link answers back to a questionnaire. This can be a meaningful id (e.g. a LOINC code) but is not intended to have any meaning. GUIDs or sequential numbers are appropriate here.

Identifies a how this question is known in a particular terminology such as LOINC.

Allows linking of questions (and their answers) to formal terminologies.

The actual question as shown to the user to prompt them for an answer.

When including text for the questionnaire, each question may contain its actual question display text.

Common extensions are defined for more specialized types of display text.

The expected format of the answer, e.g. the type of input (string, integer) or whether a (multiple) choice is expected.

Defines the format in which the user is to be prompted for the answer.

Additional constraints on the type of answer can be conveyed by extensions.

If true, indicates that the question must be answered and have required groups within it also present. If false, the question and any contained groups may be skipped when answering the questionnaire.

If true, the question may have more than one answer.

Used for "check all that apply" types of questions or "list your top 3", etc.

Whether the question itself will be displayed for each answer is a rendering choice typically based on whether there are nested groups.

Reference to a valueset containing the a list of codes representing permitted answers for the question.

LOINC defines many useful value sets for questionnaire response. See LOINC Answer Lists.

For a "choice" question, identifies one of the permitted answers for the question.

Nested group, containing nested question for this question. The order of groups within the question is relevant.

It is useful to have "sub-questions", questions which normally appear when certain answers are given and which collect additional details.