2nd DSTU Draft For Comment

This page is part of the FHIR Specification (v0.4.0: DSTU 2 Draft). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3 R2

4.27 Resource Questionnaire - Content

This resource maintained by the Patient Care Work Group

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.

4.27.1 Scope and Usage

A Questionnaire is an organized collection of questions intended to solicit information from patients, providers or other individuals involved in the healthcare domain. They may be simple flat lists of questions or can be hierarchically organized in groups and sub-groups, each containing questions. The Questionnaire defines the questions to be asked, how they are ordered and grouped and what the constraints are on the allowed answers. The results of a Questionnaire can be communicated using the QuestionnaireAnswer resource.

Questionnaires cover the need to communicate data originating from forms used in medical history examinations, research questionnaires and sometimes full clinical specialty records. In many systems this data is collected using user-defined screens and forms. Questionnaires define specifics about data capture - exactly what questions were asked, in what order, what choices for answers were, etc. Each of these questions is part of the Questionnaire, and as such the Questionnaire is a separately identifiable Resource, whereas the individual questions are not.

Examples of Questionnaires include:

  • Past medical history (PMH)
  • Family diseases
  • Social history
  • Research questionnaires/Clinical research forms (CRFs)
  • Quality and evaluation forms
  • Patient intake form (e.g. clipboard)
  • Insurance claim form

This resource is limited in scope to support the characteristics of simple questionnaires. However, common extensions have been defined to allow more sophisticated behavior. This includes:

  • Questionnaire core extensions which defines the additional descriptive characteristics for questionnaires and their groups and questions
  • Element extensions which can describe additional constraints on allowed answers for questionnaires such as string length and date and numeric ranges

Additional profiles such as the Structured Data Capture Questionnaire profile may provide additional capabilities for defining more sophisticated questionnaires and forms.

4.27.2 Boundaries and Relationships

Questionnaires differ from Lists because Lists group existing resources, while Questionnaires group arbitrary questions. In theory, a Questionnaire could be expressed as a List or Composition containing DataElement resources. However, the former would disregard the "wholeness" associated with a questionnaire where questions must generally be maintained as a single structure. The latter would focus on rendering of the data elements rather than organizing the capture of information.

4.27.3 Background and Context

Groups and questions that make up a Questionnaire can be explicitly coded to refer to externally defined numbering or identification of questions and sections on formally defined questionnaires. This allows extraction of the data on a form and post-processing of the data contained in a Questionnaire. Such coding is not required however and Questionnaires may be quite loosely defined. The section Questionnaire versus Resources below discusses the issues of collecting data in such loosely defined Questionnaires versus collecting data as well-defined separate Resources.

This resource is referenced by [QuestionnaireAnswers]

4.27.4 Resource Content

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. Questionnaire IDomainResourceA structured set of questions
The link ids for groups and questions must be unique within the questionnaire
... identifier Σ0..*IdentifierExternal Ids for this questionnaire
... version Σ0..1stringLogical id for this version of Questionnaire
... status M Σ1..1codedraft | published | retired
QuestionnaireStatus (Required)
... date Σ0..1dateTimeDate this version was authored
... publisher Σ0..1stringOrganization/individual who designed the questionnaire
... telecom Σ0..*ContactPointContact information of the publisher
... group I1..1ElementGrouped questions
Groups may either contain questions or groups but not both
.... linkId 0..1stringTo link questionnaire with questionnaire answers
.... title 0..1stringName to be displayed for group
.... concept 0..*CodingConcept that represents this section on a questionnaire
.... text 0..1stringAdditional text for the group
.... required 0..1booleanMust group be included in data results?
.... repeats 0..1booleanWhether the group may repeat
.... group I0..*see groupNested questionnaire group
.... question I0..*ElementQuestions in this group
..... linkId 0..1stringTo link questionnaire with questionnaire answers
..... concept 0..*CodingConcept that represents this question on a questionnaire
..... text 0..1stringText of the question as it is shown to the user
..... type 0..1codeboolean | decimal | integer | date | dateTime +
AnswerFormat (Required)
..... required 0..1booleanMust question be answered in data results?
..... repeats 0..1booleanCan question have multiple answers?
..... options 0..1ValueSetValueset containing the possible options
..... group 0..*see groupNested questionnaire group

UML Diagram

Questionnaire (DomainResource)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)identifier : Identifier 0..*The version number assigned by the publisher for business reasons. It may remain the same when the resource is updatedversion : string 0..1The lifecycle status of the questionnaire as a whole (this element modifies the meaning of other elements)status : code 1..1 « Lifecycle status of the questionnaireQuestionnaireStatus »The date that this questionnaire was last changeddate : dateTime 0..1Organization or person responsible for developing and maintaining the questionnairepublisher : string 0..1Contact details to assist a user in finding and communicating with the publishertelecom : ContactPoint 0..*GroupAn identifier that is unique within the questionnaire allowing linkage to the equivalent group in a QuestionnaireAnswers resourcelinkId : string 0..1The human-readable name for this section of the questionnairetitle : string 0..1Identifies a how this group of questions is known in a particular terminology such as LOINCconcept : Coding 0..*Additional text for the group, used for display purposestext : string 0..1If 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 questionnairerequired : boolean 0..1Whether the group may occur multiple times in the instance, containing multiple sets of answersrepeats : boolean 0..1QuestionAn identifier that is unique within the questionnaire allowing linkage to the equivalent group in a [[[QuestionnaireAnswers]]] resourcelinkId : string 0..1Identifies a how this question is known in a particular terminology such as LOINCconcept : Coding 0..*The actual question as shown to the user to prompt them for an answertext : string 0..1The expected format of the answer, e.g. the type of input (string, integer) or whether a (multiple) choice is expectedtype : code 0..1 « The expected format of an answerAnswerFormat »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 questionnairerequired : boolean 0..1If true, the question may have more than one answerrepeats : boolean 0..1Reference to a valueset containing the possible optionsoptions : Reference(ValueSet) 0..1A sub-group within a group. The ordering of groups within this group is relevantgroup0..*Nested group, containing nested question for this question. The order of groups within the question is relevantgroup0..*Set of questions within this group. The order of questions within the group is relevantquestion0..*A collection of related questions (or further groupings of questions)group1..1

XML Template

<Questionnaire xmlns="http://hl7.org/fhir"> doco
 <!-- from Resource: id, meta, implicitRules, and language -->
 <!-- from DomainResource: text, contained, extension, and modifierExtension -->
 <identifier><!-- 0..* Identifier External Ids for this questionnaire --></identifier>
 <version value="[string]"/><!-- 0..1 Logical id for this version of Questionnaire -->
 <status value="[code]"/><!-- 1..1 draft | published | retired -->
 <date value="[dateTime]"/><!-- 0..1 Date this version was authored -->
 <publisher value="[string]"/><!-- 0..1 Organization/individual who designed the questionnaire -->
 <telecom><!-- 0..* ContactPoint Contact information of the publisher --></telecom>
 <group>  <!-- 1..1 Grouped questions -->
  <linkId value="[string]"/><!-- 0..1 To link questionnaire with questionnaire answers -->
  <title value="[string]"/><!-- 0..1 Name to be displayed for group -->
  <concept><!-- 0..* Coding Concept that represents this section on a questionnaire --></concept>
  <text value="[string]"/><!-- 0..1 Additional text for the group -->
  <required value="[boolean]"/><!-- 0..1 Must group be included in data results? -->
  <repeats value="[boolean]"/><!-- 0..1 Whether the group may repeat -->
  <group><!-- ?? 0..* Content as for Questionnaire.group Nested questionnaire group --></group>
  <question>  <!-- ?? 0..* Questions in this group -->
   <linkId value="[string]"/><!-- 0..1 To link questionnaire with questionnaire answers -->
   <concept><!-- 0..* Coding Concept that represents this question on a questionnaire --></concept>
   <text value="[string]"/><!-- 0..1 Text of the question as it is shown to the user -->
   <type value="[code]"/><!-- 0..1 boolean | decimal | integer | date | dateTime + -->
   <required value="[boolean]"/><!-- 0..1 Must question be answered in data results? -->
   <repeats value="[boolean]"/><!-- 0..1 Can question  have multiple answers? -->
   <options><!-- 0..1 Reference(ValueSet) Valueset containing the possible options --></options>
   <group><!-- 0..* Content as for Questionnaire.group Nested questionnaire group --></group>
  </question>
 </group>
</Questionnaire>

JSON Template

{doco
  "resourceType" : "Questionnaire",
  // from Resource: id, meta, implicitRules, and language
  // from DomainResource: text, contained, extension, and modifierExtension
  "identifier" : [{ Identifier }], // External Ids for this questionnaire
  "version" : "<string>", // Logical id for this version of Questionnaire
  "status" : "<code>", // R! draft | published | retired
  "date" : "<dateTime>", // Date this version was authored
  "publisher" : "<string>", // Organization/individual who designed the questionnaire
  "telecom" : [{ ContactPoint }], // Contact information of the publisher
  "group" : { // R! Grouped questions
    "linkId" : "<string>", // To link questionnaire with questionnaire answers
    "title" : "<string>", // Name to be displayed for group
    "concept" : [{ Coding }], // Concept that represents this section on a questionnaire
    "text" : "<string>", // Additional text for the group
    "required" : <boolean>, // Must group be included in data results?
    "repeats" : <boolean>, // Whether the group may repeat
    "group" : [{ Content as for Questionnaire.group }], // C? Nested questionnaire group
    "question" : [{ // C? Questions in this group
      "linkId" : "<string>", // To link questionnaire with questionnaire answers
      "concept" : [{ Coding }], // Concept that represents this question on a questionnaire
      "text" : "<string>", // Text of the question as it is shown to the user
      "type" : "<code>", // boolean | decimal | integer | date | dateTime +
      "required" : <boolean>, // Must question be answered in data results?
      "repeats" : <boolean>, // Can question  have multiple answers?
      "options" : { Reference(ValueSet) }, // Valueset containing the possible options
      "group" : [{ Content as for Questionnaire.group }] // Nested questionnaire group
    }]
  }
}

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. Questionnaire IDomainResourceA structured set of questions
The link ids for groups and questions must be unique within the questionnaire
... identifier Σ0..*IdentifierExternal Ids for this questionnaire
... version Σ0..1stringLogical id for this version of Questionnaire
... status M Σ1..1codedraft | published | retired
QuestionnaireStatus (Required)
... date Σ0..1dateTimeDate this version was authored
... publisher Σ0..1stringOrganization/individual who designed the questionnaire
... telecom Σ0..*ContactPointContact information of the publisher
... group I1..1ElementGrouped questions
Groups may either contain questions or groups but not both
.... linkId 0..1stringTo link questionnaire with questionnaire answers
.... title 0..1stringName to be displayed for group
.... concept 0..*CodingConcept that represents this section on a questionnaire
.... text 0..1stringAdditional text for the group
.... required 0..1booleanMust group be included in data results?
.... repeats 0..1booleanWhether the group may repeat
.... group I0..*see groupNested questionnaire group
.... question I0..*ElementQuestions in this group
..... linkId 0..1stringTo link questionnaire with questionnaire answers
..... concept 0..*CodingConcept that represents this question on a questionnaire
..... text 0..1stringText of the question as it is shown to the user
..... type 0..1codeboolean | decimal | integer | date | dateTime +
AnswerFormat (Required)
..... required 0..1booleanMust question be answered in data results?
..... repeats 0..1booleanCan question have multiple answers?
..... options 0..1ValueSetValueset containing the possible options
..... group 0..*see groupNested questionnaire group

UML Diagram

Questionnaire (DomainResource)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)identifier : Identifier 0..*The version number assigned by the publisher for business reasons. It may remain the same when the resource is updatedversion : string 0..1The lifecycle status of the questionnaire as a whole (this element modifies the meaning of other elements)status : code 1..1 « Lifecycle status of the questionnaireQuestionnaireStatus »The date that this questionnaire was last changeddate : dateTime 0..1Organization or person responsible for developing and maintaining the questionnairepublisher : string 0..1Contact details to assist a user in finding and communicating with the publishertelecom : ContactPoint 0..*GroupAn identifier that is unique within the questionnaire allowing linkage to the equivalent group in a QuestionnaireAnswers resourcelinkId : string 0..1The human-readable name for this section of the questionnairetitle : string 0..1Identifies a how this group of questions is known in a particular terminology such as LOINCconcept : Coding 0..*Additional text for the group, used for display purposestext : string 0..1If 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 questionnairerequired : boolean 0..1Whether the group may occur multiple times in the instance, containing multiple sets of answersrepeats : boolean 0..1QuestionAn identifier that is unique within the questionnaire allowing linkage to the equivalent group in a [[[QuestionnaireAnswers]]] resourcelinkId : string 0..1Identifies a how this question is known in a particular terminology such as LOINCconcept : Coding 0..*The actual question as shown to the user to prompt them for an answertext : string 0..1The expected format of the answer, e.g. the type of input (string, integer) or whether a (multiple) choice is expectedtype : code 0..1 « The expected format of an answerAnswerFormat »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 questionnairerequired : boolean 0..1If true, the question may have more than one answerrepeats : boolean 0..1Reference to a valueset containing the possible optionsoptions : Reference(ValueSet) 0..1A sub-group within a group. The ordering of groups within this group is relevantgroup0..*Nested group, containing nested question for this question. The order of groups within the question is relevantgroup0..*Set of questions within this group. The order of questions within the group is relevantquestion0..*A collection of related questions (or further groupings of questions)group1..1

XML Template

<Questionnaire xmlns="http://hl7.org/fhir"> doco
 <!-- from Resource: id, meta, implicitRules, and language -->
 <!-- from DomainResource: text, contained, extension, and modifierExtension -->
 <identifier><!-- 0..* Identifier External Ids for this questionnaire --></identifier>
 <version value="[string]"/><!-- 0..1 Logical id for this version of Questionnaire -->
 <status value="[code]"/><!-- 1..1 draft | published | retired -->
 <date value="[dateTime]"/><!-- 0..1 Date this version was authored -->
 <publisher value="[string]"/><!-- 0..1 Organization/individual who designed the questionnaire -->
 <telecom><!-- 0..* ContactPoint Contact information of the publisher --></telecom>
 <group>  <!-- 1..1 Grouped questions -->
  <linkId value="[string]"/><!-- 0..1 To link questionnaire with questionnaire answers -->
  <title value="[string]"/><!-- 0..1 Name to be displayed for group -->
  <concept><!-- 0..* Coding Concept that represents this section on a questionnaire --></concept>
  <text value="[string]"/><!-- 0..1 Additional text for the group -->
  <required value="[boolean]"/><!-- 0..1 Must group be included in data results? -->
  <repeats value="[boolean]"/><!-- 0..1 Whether the group may repeat -->
  <group><!-- ?? 0..* Content as for Questionnaire.group Nested questionnaire group --></group>
  <question>  <!-- ?? 0..* Questions in this group -->
   <linkId value="[string]"/><!-- 0..1 To link questionnaire with questionnaire answers -->
   <concept><!-- 0..* Coding Concept that represents this question on a questionnaire --></concept>
   <text value="[string]"/><!-- 0..1 Text of the question as it is shown to the user -->
   <type value="[code]"/><!-- 0..1 boolean | decimal | integer | date | dateTime + -->
   <required value="[boolean]"/><!-- 0..1 Must question be answered in data results? -->
   <repeats value="[boolean]"/><!-- 0..1 Can question  have multiple answers? -->
   <options><!-- 0..1 Reference(ValueSet) Valueset containing the possible options --></options>
   <group><!-- 0..* Content as for Questionnaire.group Nested questionnaire group --></group>
  </question>
 </group>
</Questionnaire>

JSON Template

{doco
  "resourceType" : "Questionnaire",
  // from Resource: id, meta, implicitRules, and language
  // from DomainResource: text, contained, extension, and modifierExtension
  "identifier" : [{ Identifier }], // External Ids for this questionnaire
  "version" : "<string>", // Logical id for this version of Questionnaire
  "status" : "<code>", // R! draft | published | retired
  "date" : "<dateTime>", // Date this version was authored
  "publisher" : "<string>", // Organization/individual who designed the questionnaire
  "telecom" : [{ ContactPoint }], // Contact information of the publisher
  "group" : { // R! Grouped questions
    "linkId" : "<string>", // To link questionnaire with questionnaire answers
    "title" : "<string>", // Name to be displayed for group
    "concept" : [{ Coding }], // Concept that represents this section on a questionnaire
    "text" : "<string>", // Additional text for the group
    "required" : <boolean>, // Must group be included in data results?
    "repeats" : <boolean>, // Whether the group may repeat
    "group" : [{ Content as for Questionnaire.group }], // C? Nested questionnaire group
    "question" : [{ // C? Questions in this group
      "linkId" : "<string>", // To link questionnaire with questionnaire answers
      "concept" : [{ Coding }], // Concept that represents this question on a questionnaire
      "text" : "<string>", // Text of the question as it is shown to the user
      "type" : "<code>", // boolean | decimal | integer | date | dateTime +
      "required" : <boolean>, // Must question be answered in data results?
      "repeats" : <boolean>, // Can question  have multiple answers?
      "options" : { Reference(ValueSet) }, // Valueset containing the possible options
      "group" : [{ Content as for Questionnaire.group }] // Nested questionnaire group
    }]
  }
}

 

Alternate definitions: Schema/Schematron, Resource Profile (XML, JSON), Questionnaire

4.27.4.1 Terminology Bindings

PathDefinitionTypeReference
Questionnaire.status Lifecycle status of the questionnaireFixedhttp://hl7.org/fhir/questionnaire-status
Questionnaire.group.concept Codes for questionnaires and groupings of questionnaire questionsUnknownNo details provided yet
Questionnaire.group.question.type The expected format of an answerFixedhttp://hl7.org/fhir/answer-format

4.27.4.2 Constraints

  • que-1: On Questionnaire.group: Groups may either contain questions or groups but not both (xpath on f:Questionnaire/f:group: not(exists(f:group) and exists(f:question)))
  • que-2: The link ids for groups and questions must be unique within the questionnaire (xpath: count(descendant::f:linkId/@value)=count(distinct-values(descendant::f:linkId/@value)))

4.27.5 Notes:

  • Questionnaires may be used to represent predefined forms, named using Questionnaire.name.
  • A Questionnaire's contents are placed inside its single nested Group, which may contain Questions or subgroups with Questions.
  • Groups and Questions may have linkIds allowing groups and question answers captured in a QuestionnaireAnswers to be associated with their corresponding group or question.
  • Questionnaire allows for flexible naming and structuring of its contents to reflect the flexible and varying nature of forms and questionnaires. It explicitly does not try to standardize or streamline exchange of its contents outside its context of use, although exchanging partners may further constrain its structure and flexibility using profiles to define standardized, reusable forms.
  • Because of the lack of explicit support for Questionnaires in HL7v3, HL7 CDA Documents frequently used named sections with Observations to model Questionnaires. Such use cases should now utilize the Questionnaire Resource instead.
  • The order of questions within groups, groups within groups and groups within questions is relevant and must be retained for display and capture.

4.27.5.1 Using Questionnaires versus using Resources

There is considerable overlap between the information covered by Questionnaires and other Resources (especially FamilyHistory, MedicationStatement, Observation, Procedure, etc.): Questionnaire's flexible structure can easily be misused to capture any data, even data that should be captured as separate Resources. The choice between using Questionnaires or separate Resources may be dictated by the procedure of collection and recording. E.g. if the data is captured as a physician-agreed (electronic) form, it might be impossible or undesirable to distill separate resources from it and capturing the data in a Questionnaire would be most appropriate.

However, data captured only in Questionnaires can be difficult to query after-the-fact. Queries against other Resources will not return data captured only in Questionnaires, and querying against Questionnaires directly may not find all desired data, depending on how the questions may have been phrased or encoded over time or by different clinicians. Moreover, interoperability of such Questionnaires is limited as interpretation of its contents is only known to the circle of parties that were involved in its definition: encoding data from such Questionnaires using other, more specific, Resources increases the ability and consistency with which it can be understood and queried.

4.27.5.2 Structure of the Questionnaire

A Questionnaire is built out of three components:

  • The main component is Questionnaire, which holds information about the Questionnaire, like the identifier, publisher, date authored, etc. The Questionnaire contains one "root" Group, which contains all the content of the questionnaire. This "root" group contains elements that apply to the entire questionnaire - the title for the questionnaire, the concept that represents the meaning of the overall questionnaire (e.g. a code for "family history"), the text to display at the top of the questionnaire, etc. (In most cases, required would be 'true' and repeats would be false for the root group
  • This Group can contain either nested Groups (to represent sections and subsections on a questionnaire form) or Questions. This way, any form containing sections or subsections can be represented, down to the actual questions.
  • The Questions themselves may be simple questions with a prompt text and one expected answer, but they may also contain nested groups, each containing sets of nested questions. This way, one can model "panels" of questions which would only be relevant (and thus would only be displayed) depending on the answers of a parent question. E.g. a question "Did the patient receive treatment in the past six months?" would contain a nested group of questions asking for further details about the treatment. See an example from the Australian New South Wales blue book
  • Specific controls on dynamic display of groups, questions, etc. based on the answers to other questions is outside the scope of the base resource and are expected to be introduced as extensions.

4.27.5.3 Question Definitions

Questionnaires can be crafted using any questions the author can conceive phrased in whatever manner is appropriate or convenient. However, standardization of questions and the constraints enforced on the accompanying answers increases the ability to compare data gathered across questionnaires. There are two mechanisms defined in the specification for linking a Question (or Group) to a standardized definition:

  • The concept element on both Group and Question allows an individual question, a group of questions or even the questionnaire as a whole to be associated with a pre-defined terminology of questions and question groups such as LOINC
  • The deReference extension allows a question or group to be associated with the DataElement (DE) resource that formally defines the data element.

Linking to formal definitions of a question allows data captured by distinct questionnaires to be compared. If systems have the necessary mappings to the formal definition, linkages to formal definitions may also be used to automatically pre-populate or extract data from a corresponding QuestionnaireAnswers resource.

NOTE: Even if standard question definitions are referenced using concept or the deReference extension, information such as the question text, data type and value set SHOULD still be declared for the question. Systems processing the questionnaire may not have access to or support the ability to look up the question definitions from external sources. If the information is not included in-line within the questionnaire, other systems may not be able to to render or use the Questionnaire.

If an external reference (concept or deReference extension) is included along with question information such as question text, data type or value set, it is expected that the content for the question and the referenced definition would be in alignment. However, FHIR does not dictate what degree of alignment is required. E.g. Does the question text need to match exactly? Is it legitimate for a question to constrain the allowed value set of possible answers? These rules will need to be established within implementation environments.

4.27.5.4 Question types

The codes for the data type for each question is slightly different than the data types allowed in the QuestionnaireAnswers resource. Where the names are the same (ignoring case), the "answer" must use the specified type. Where the names are different, the mappings are as follows:

Questionnaire AnswerFormat code QuestionnaireAnswers data type
text string
url uri
choice Coding
open-choice Coding

4.27.5.5 Extensions for Additional capabilities

The core elements defined in the questionnaire resource are sufficient for simple questionnaires. For more sophisticated capabilities, a number of "common" extensions are defined in the Questionnaire Core extensions and the Element extensions profiles. For example, strict control over allowed number of conditions, conditional display of questionnaire content, etc.

4.27.6 Search Parameters

Search parameters for this resource. The common parameters also apply. See Searching for more information about searching in REST, messaging, and services.

NameTypeDescriptionPaths
codetokenA code that corresponds to the questionnaire or one of its groupsQuestionnaire.group.concept
datedateWhen the questionnaire was last changedQuestionnaire.date
identifiertokenAn identifier for the questionnaireQuestionnaire.identifier
publisherstringThe author of the questionnaireQuestionnaire.publisher
statustokenThe status of the questionnaireQuestionnaire.status
titlestringAll or part of the name of the questionnaire (title for the root group of the questionnaire)
versionstringThe business version of the questionnaireQuestionnaire.version