A structured set of questions intended to guide the collection of answers. The questions are ordered and grouped into coherent subsets, corresponding to the structure of the grouping of the underlying 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.

May be used to represent additional information that is not part of the basic definition of the resource. 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 base URL for the server to which questionnaire response associated with this questionnaire should be submitted.

Indicates that the form has been designed with an expectation that it will be submitted to the specified URI. If multiple endpoints are specified, expectation is that answers are submitted to all endpoints.

If no end-point is specified, then the form is not exclusively designed to be submitted to a specific site. If and where the form needs to be submitted or how the form should be internally processed must be inferred from external context or system business rules.

If true, indicates that QuestionnaireResponse instances created against this questionnaire must have an associated Provenance record.

Systems may choose to require that the QuestionnaireResponse and referencing Provenance instance be submitted together as a single transaction using Bundle.

Indicates that the style extensions in this resource are essential to the interpretation of the styled text and that it cannot be rendered without the style without losing essential information.

If set to true, all systems that claim to support this extension and which render elements of the resource containing this extension SHALL either render the content as required by the style extensions defined by this profile that are present in the resource or shall (if safe to do so based on their own rules), omit entirely the styled content they cannot render in accordance with the extensions.

A code that identifies the questionnaire as falling into a particular group of like questionnaires. E.g. "Pediatric", "Admissions", "Research", "Demographic", "Opinion Survey", etc.

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.

Identifies when this version of the form was created. Changes whenever the form is updated.

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).

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

A label for a particular group or question within the questionnaire.

These are generally unique within a questionnaire, though this is not guaranteed. Some questionnaires may have multiple questions with the same label with logic to control which gets exposed.

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

Identifies how the specified element should be rendered when displayed.

This extension would be equivalent to setting the HTML "style" attribute on the root element for the element containing the extension.

This is an equivalent of the string on which the extension is sent, but includes additional XHTML markup, such as bold, italics, styles, tables, etc.

Source of the definition for the extension code - a logical name or a URL.

The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition should be version specific. This will ideally be the URI for the Resource Profile defining the extension, with the code for the extension after a #.

Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list).

The text provides instructions intended to be rendered with the element explaining how the content of the element is to be completed. This should be rendered in-line before the question or group.

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

Identifies how the specified element should be rendered when displayed.

This extension would be equivalent to setting the HTML "style" attribute on the root element for the element containing the extension.

This is an equivalent of the string on which the extension is sent, but includes additional XHTML markup, such as bold, italics, styles, tables, etc.

Source of the definition for the extension code - a logical name or a URL.

The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition should be version specific. This will ideally be the URI for the Resource Profile defining the extension, with the code for the extension after a #.

Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list).

The text describes specific security and/or privacy considerations associated with the element. E.g. retention rules, data access control expectations, etc.

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

Identifies how the specified element should be rendered when displayed.

This extension would be equivalent to setting the HTML "style" attribute on the root element for the element containing the extension.

This is an equivalent of the string on which the extension is sent, but includes additional XHTML markup, such as bold, italics, styles, tables, etc.

Source of the definition for the extension code - a logical name or a URL.

The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition should be version specific. This will ideally be the URI for the Resource Profile defining the extension, with the code for the extension after a #.

Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list).

The content is intended for display if a user selects an icon or performs some other action seeking help about the element.

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

Identifies how the specified element should be rendered when displayed.

This extension would be equivalent to setting the HTML "style" attribute on the root element for the element containing the extension.

This is an equivalent of the string on which the extension is sent, but includes additional XHTML markup, such as bold, italics, styles, tables, etc.

Source of the definition for the extension code - a logical name or a URL.

The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition should be version specific. This will ideally be the URI for the Resource Profile defining the extension, with the code for the extension after a #.

Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list).

The content is intended for use in a fly-over or similar display mechanism - primarily intended for online form entry.

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

Identifies how the specified element should be rendered when displayed.

This extension would be equivalent to setting the HTML "style" attribute on the root element for the element containing the extension.

This is an equivalent of the string on which the extension is sent, but includes additional XHTML markup, such as bold, italics, styles, tables, etc.

Source of the definition for the extension code - a logical name or a URL.

The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition should be version specific. This will ideally be the URI for the Resource Profile defining the extension, with the code for the extension after a #.

Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list).

The text should be displayed after all of the other the content of the group or question.

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

Identifies how the specified element should be rendered when displayed.

This extension would be equivalent to setting the HTML "style" attribute on the root element for the element containing the extension.

This is an equivalent of the string on which the extension is sent, but includes additional XHTML markup, such as bold, italics, styles, tables, etc.

If set to true, it means that the system displaying the form (or the individual encoding the form for data capture) can choose to omit the question from display to the user.

If a group or question that contains other groups or questions is marked as "optional", all of its contents are automatically also treated as optional.

Source of the definition for the extension code - a logical name or a URL.

The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition should be version specific. This will ideally be the URI for the Resource Profile defining the extension, with the code for the extension after a #.

Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list).

If true, indicates that the containing group or question should not be displayed to the user for data entry.

If a group is hidden, all descendant content of the group is automatically hidden.

The minimum number of times the group must appear or the minimum number of answers for a question - when greater than 1.

Default assumption for "required" elements is minOccurs=1.

The maximum number of times the group must appear or the minimum number of answers for a question - when greater than 1 and not unlimited.

Only relevant if the element has repeats=true and there's a need to constrain the number of allowed repetitions.

If specified, indicates that the group should be rendered as a repeating header or footer on each "page" of the questionnaire.

When omitted, sections are presumed to be "regular" sections.

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.

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 resource. 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

Identifies how the specified element should be rendered when displayed.

This extension would be equivalent to setting the HTML "style" attribute on the root element for the element containing the extension.

This is an equivalent of the string on which the extension is sent, but includes additional XHTML markup, such as bold, italics, styles, tables, etc.

The actual value

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.

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 resource. 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

Identifies how the specified element should be rendered when displayed.

This extension would be equivalent to setting the HTML "style" attribute on the root element for the element containing the extension.

This is an equivalent of the string on which the extension is sent, but includes additional XHTML markup, such as bold, italics, styles, tables, etc.

The actual value

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 minimum number of times the group must appear or the minimum number of answers for a question - when greater than 1.

Default assumption for "required" elements is minOccurs=1.

The maximum number of times the group must appear or the minimum number of answers for a question - when greater than 1 and not unlimited.

Only relevant if the element has repeats=true and there's a need to constrain the number of allowed repetitions.

A label for a particular group or question within the questionnaire.

These are generally unique within a questionnaire, though this is not guaranteed. Some questionnaires may have multiple questions with the same label with logic to control which gets exposed.

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

Identifies how the specified element should be rendered when displayed.

This extension would be equivalent to setting the HTML "style" attribute on the root element for the element containing the extension.

This is an equivalent of the string on which the extension is sent, but includes additional XHTML markup, such as bold, italics, styles, tables, etc.

Source of the definition for the extension code - a logical name or a URL.

The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition should be version specific. This will ideally be the URI for the Resource Profile defining the extension, with the code for the extension after a #.

Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list).

The text provides instructions intended to be rendered with the element explaining how the content of the element is to be completed. This should be rendered in-line before the question or group.

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

Identifies how the specified element should be rendered when displayed.

This extension would be equivalent to setting the HTML "style" attribute on the root element for the element containing the extension.

This is an equivalent of the string on which the extension is sent, but includes additional XHTML markup, such as bold, italics, styles, tables, etc.

Source of the definition for the extension code - a logical name or a URL.

The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition should be version specific. This will ideally be the URI for the Resource Profile defining the extension, with the code for the extension after a #.

Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list).

The text describes specific security and/or privacy considerations associated with the element. E.g. retention rules, data access control expectations, etc.

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

Identifies how the specified element should be rendered when displayed.

This extension would be equivalent to setting the HTML "style" attribute on the root element for the element containing the extension.

This is an equivalent of the string on which the extension is sent, but includes additional XHTML markup, such as bold, italics, styles, tables, etc.

Source of the definition for the extension code - a logical name or a URL.

The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition should be version specific. This will ideally be the URI for the Resource Profile defining the extension, with the code for the extension after a #.

Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list).

The content is intended for display if a user selects an icon or performs some other action seeking help about the element.

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

Identifies how the specified element should be rendered when displayed.

This extension would be equivalent to setting the HTML "style" attribute on the root element for the element containing the extension.

This is an equivalent of the string on which the extension is sent, but includes additional XHTML markup, such as bold, italics, styles, tables, etc.

Source of the definition for the extension code - a logical name or a URL.

The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition should be version specific. This will ideally be the URI for the Resource Profile defining the extension, with the code for the extension after a #.

Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list).

The content is intended for use in a fly-over or similar display mechanism - primarily intended for online form entry.

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

Identifies how the specified element should be rendered when displayed.

This extension would be equivalent to setting the HTML "style" attribute on the root element for the element containing the extension.

This is an equivalent of the string on which the extension is sent, but includes additional XHTML markup, such as bold, italics, styles, tables, etc.

Source of the definition for the extension code - a logical name or a URL.

The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition should be version specific. This will ideally be the URI for the Resource Profile defining the extension, with the code for the extension after a #.

Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list).

The text should be displayed after all of the other the content of the group or question.

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

Identifies how the specified element should be rendered when displayed.

This extension would be equivalent to setting the HTML "style" attribute on the root element for the element containing the extension.

This is an equivalent of the string on which the extension is sent, but includes additional XHTML markup, such as bold, italics, styles, tables, etc.

Source of the definition for the extension code - a logical name or a URL.

The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition should be version specific. This will ideally be the URI for the Resource Profile defining the extension, with the code for the extension after a #.

Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list).

Identifies the units in which the question's answer should be captured.

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

Identifies how the specified element should be rendered when displayed.

This extension would be equivalent to setting the HTML "style" attribute on the root element for the element containing the extension.

This is an equivalent of the string on which the extension is sent, but includes additional XHTML markup, such as bold, italics, styles, tables, etc.

Source of the definition for the extension code - a logical name or a URL.

The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition should be version specific. This will ideally be the URI for the Resource Profile defining the extension, with the code for the extension after a #.

Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list).

If present, indicates that the group or question containing the extension should only be enabled (allow an answer to be present and, in most circumstances, even be visible to the user) when the specified condition is true.

If multiple repetitions of this extension are present, the question or group should be displayed when the condition for any of the repetitions is true. I.e. Treat "enableWhen"s as being joined by an "or" clause.

If set to true, it means that the system displaying the form (or the individual encoding the form for data capture) can choose to omit the question from display to the user.

If a group or question that contains other groups or questions is marked as "optional", all of its contents are automatically also treated as optional.

If true, indicates that the containing group or question should not be displayed to the user for data entry.

If a group is hidden, all descendant content of the group is automatically hidden.

The type of data entry control that should be exposed to the user when capturing the answer to the question.

Different controls may be appropriate for different question data types. It is up to the system rendering a questionnaire as to what controls it will support and for which data types.

Identifies the desired orientation when rendering a list of choices (typically radio-box or check-box lists).

Systems may choose to wrap answers rather than attempting to display them all in one row or column. Language conventions may determine the order in which the choices are listed (left-to-right or right-to-left, etc.).

This is the value that should be pre-populated when rendering the questionnaire for user input.

If true, the value cannot be changed by a human respondant to the Questionnaire.

The value of readOnly elements can be established by asserting extensions for defaultValues, linkages that support pre-population and/or extensions that support calculation based on other answers.

The minimum number of characters that must be present in the simple data type to be considered a "valid" instance.

For base64binary, reflects the number of characters representing the encoded data, not the number of bytes of the binary data.

The maximum number of characters that must be present in the simple data type to be considered a "valid" instance.

For base64binary, reflects the number of characters representing the encoded data, not the number of bytes of the binary data.

A regular expression that defines the syntax for the data element to be considered valid.

A syntax intended for display to the user to guide their input (i.e. a human readable version of a regular expression). For example "nnn-nnn-nnn".

The inclusive lower bound on the range of allowed values for the data element.

Data type specified must be the same as the data type for the data element.

The inclusive upper bound on the range of allowed values for the data element.

Data type specified must be the same as the data type for the data element.

Identifies the maximum number of decimal places that may be specified for the data element.

A reference to the Data Element that corresponds to the question text and answer constraints for this question.

If a code applies to a question, that code should still be conveyed on the question, even if the same code is also referenced as a DataElement.code in the referenced data element. This extension must not be used in place of specifying the Questionnaire.group.question.concept element.

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.

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 resource. 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

Identifies how the specified element should be rendered when displayed.

This extension would be equivalent to setting the HTML "style" attribute on the root element for the element containing the extension.

This is an equivalent of the string on which the extension is sent, but includes additional XHTML markup, such as bold, italics, styles, tables, etc.

The actual value

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.

Time is handled using "string". File is handled using Attachment. (Content can be sent as a contained binary).

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.