🔗  This resource is a non-persisted resource used to pass information into and back from an [operation](http://hl7.org/fhir/R4/operations.html). It has no other use, and there is no RESTful endpoint associated with it. The parameters that may be used are defined by the OperationDefinition resource.parameters-questionnaire-assemble-out(xsd)=
	 <#base:Parameters>
	 <  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.; (xsd)id:string>?
	 <  The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.; (xsd)meta:Meta>?
	 <  A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. 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. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.; (xsd)implicitRules:uri>?
	 <  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).; (xsd)language:code>?
	[]<  A parameter passed to or received from the operation.; (xsd)parameter:parameters-questionnaire-assemble-out.parameter>+
	 <  A parameter passed to or received from the operation.; (xsd)return:parameters-questionnaire-assemble-out.return>
	 <  A parameter passed to or received from the operation.; (xsd)outcome:parameters-questionnaire-assemble-out.outcome>?

🔗  A parameter passed to or received from the operation.parameters-questionnaire-assemble-out.outcome(xsd)=
	 <#base:BackboneElement>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  The name of the parameter (reference to the operation definition). outcome; (xsd)name:string>
	 ( <valueAddress:Address>
		 | <valueAge:Age>
		 | <valueAnnotation:Annotation>
		 | <valueAttachment:Attachment>
		 | <valueBase64Binary:base64Binary>
		 | <valueBoolean:boolean>
		 | <valueCanonical:canonical>
		 | <valueCode:code>
		 | <valueCodeableConcept:CodeableConcept>
		 | <valueCoding:Coding>
		 | <valueContactDetail:ContactDetail>
		 | <valueContactPoint:ContactPoint>
		 | <valueContributor:Contributor>
		 | <valueCount:Count>
		 | <valueDataRequirement:DataRequirement>
		 | <valueDate:date>
		 | <valueDateTime:dateTime>
		 | <valueDecimal:decimal>
		 | <valueDistance:Distance>
		 | <valueDosage:Dosage>
		 | <valueDuration:Duration>
		 | <valueExpression:Expression>
		 | <valueHumanName:HumanName>
		 | <valueId:id>
		 | <valueIdentifier:Identifier>
		 | <valueInstant:instant>
		 | <valueInteger:integer>
		 | <valueMarkdown:markdown>
		 | <valueMeta:Meta>
		 | <valueMoney:Money>
		 | <valueOid:oid>
		 | <valueParameterDefinition:ParameterDefinition>
		 | <valuePeriod:Period>
		 | <valuePositiveInt:positiveInt>
		 | <valueQuantity:Quantity>
		 | <valueRange:Range>
		 | <valueRatio:Ratio>
		 | <valueRelatedArtifact:RelatedArtifact>
		 | <valueResource:Resource>
		 | <valueSampledData:SampledData>
		 | <valueSignature:Signature>
		 | <valueString:string>
		 | <valueTime:time>
		 | <valueTiming:Timing>
		 | <valueTriggerDefinition:TriggerDefinition>
		 | <valueUnsignedInt:unsignedInt>
		 | <valueUri:uri>
		 | <valueUrl:url>
		 | <valueUsageContext:UsageContext>
		 | <valueUuid:uuid>){0,0}
	 <  If the parameter is a whole resource. When resolving references in resources, the operation definition may specify how references may be resolved between parameters. If a reference cannot be resolved between the parameters, the application should fall back to it's general resource resolution methods.; (xsd)resource:OperationOutcome>?
	 <  A named part of a multi-part parameter. Only one level of nested parameters is allowed.; (xsd)part:Parameters.parameter>{0,0}

🔗  A parameter passed to or received from the operation.parameters-questionnaire-assemble-out.parameter(xsd)=
	 <#base:Parameters.parameter>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  The name of the parameter (reference to the operation definition).; (xsd)name:string>
	 ( <valueAddress:Address>
		 | <valueAge:Age>
		 | <valueAnnotation:Annotation>
		 | <valueAttachment:Attachment>
		 | <valueBase64Binary:base64Binary>
		 | <valueBoolean:boolean>
		 | <valueCanonical:canonical>
		 | <valueCode:code>
		 | <valueCodeableConcept:CodeableConcept>
		 | <valueCoding:Coding>
		 | <valueContactDetail:ContactDetail>
		 | <valueContactPoint:ContactPoint>
		 | <valueContributor:Contributor>
		 | <valueCount:Count>
		 | <valueDataRequirement:DataRequirement>
		 | <valueDate:date>
		 | <valueDateTime:dateTime>
		 | <valueDecimal:decimal>
		 | <valueDistance:Distance>
		 | <valueDosage:Dosage>
		 | <valueDuration:Duration>
		 | <valueExpression:Expression>
		 | <valueHumanName:HumanName>
		 | <valueId:id>
		 | <valueIdentifier:Identifier>
		 | <valueInstant:instant>
		 | <valueInteger:integer>
		 | <valueMarkdown:markdown>
		 | <valueMeta:Meta>
		 | <valueMoney:Money>
		 | <valueOid:oid>
		 | <valueParameterDefinition:ParameterDefinition>
		 | <valuePeriod:Period>
		 | <valuePositiveInt:positiveInt>
		 | <valueQuantity:Quantity>
		 | <valueRange:Range>
		 | <valueRatio:Ratio>
		 | <valueRelatedArtifact:RelatedArtifact>
		 | <valueResource:Resource>
		 | <valueSampledData:SampledData>
		 | <valueSignature:Signature>
		 | <valueString:string>
		 | <valueTime:time>
		 | <valueTiming:Timing>
		 | <valueTriggerDefinition:TriggerDefinition>
		 | <valueUnsignedInt:unsignedInt>
		 | <valueUri:uri>
		 | <valueUrl:url>
		 | <valueUsageContext:UsageContext>
		 | <valueUuid:uuid>)?
	 <  If the parameter is a whole resource. When resolving references in resources, the operation definition may specify how references may be resolved between parameters. If a reference cannot be resolved between the parameters, the application should fall back to it's general resource resolution methods.; (xsd)resource:Resource>?
	[]<  A named part of a multi-part parameter. Only one level of nested parameters is allowed.; (xsd)part:Parameters.parameter>*

🔗  A parameter passed to or received from the operation.parameters-questionnaire-assemble-out.return(xsd)=
	 <#base:BackboneElement>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  The name of the parameter (reference to the operation definition). return; (xsd)name:string>
	 ( <valueAddress:Address>
		 | <valueAge:Age>
		 | <valueAnnotation:Annotation>
		 | <valueAttachment:Attachment>
		 | <valueBase64Binary:base64Binary>
		 | <valueBoolean:boolean>
		 | <valueCanonical:canonical>
		 | <valueCode:code>
		 | <valueCodeableConcept:CodeableConcept>
		 | <valueCoding:Coding>
		 | <valueContactDetail:ContactDetail>
		 | <valueContactPoint:ContactPoint>
		 | <valueContributor:Contributor>
		 | <valueCount:Count>
		 | <valueDataRequirement:DataRequirement>
		 | <valueDate:date>
		 | <valueDateTime:dateTime>
		 | <valueDecimal:decimal>
		 | <valueDistance:Distance>
		 | <valueDosage:Dosage>
		 | <valueDuration:Duration>
		 | <valueExpression:Expression>
		 | <valueHumanName:HumanName>
		 | <valueId:id>
		 | <valueIdentifier:Identifier>
		 | <valueInstant:instant>
		 | <valueInteger:integer>
		 | <valueMarkdown:markdown>
		 | <valueMeta:Meta>
		 | <valueMoney:Money>
		 | <valueOid:oid>
		 | <valueParameterDefinition:ParameterDefinition>
		 | <valuePeriod:Period>
		 | <valuePositiveInt:positiveInt>
		 | <valueQuantity:Quantity>
		 | <valueRange:Range>
		 | <valueRatio:Ratio>
		 | <valueRelatedArtifact:RelatedArtifact>
		 | <valueResource:Resource>
		 | <valueSampledData:SampledData>
		 | <valueSignature:Signature>
		 | <valueString:string>
		 | <valueTime:time>
		 | <valueTiming:Timing>
		 | <valueTriggerDefinition:TriggerDefinition>
		 | <valueUnsignedInt:unsignedInt>
		 | <valueUri:uri>
		 | <valueUrl:url>
		 | <valueUsageContext:UsageContext>
		 | <valueUuid:uuid>){0,0}
	 <  A structured set of questions intended to guide the collection of answers from end-users. Questionnaires provide detailed control over order, presentation, phraseology and grouping to allow coherent, consistent data collection. When resolving references in resources, the operation definition may specify how references may be resolved between parameters. If a reference cannot be resolved between the parameters, the application should fall back to it's general resource resolution methods.; (xsd)resource:sdc-questionnaire>?
	 <  A named part of a multi-part parameter. Only one level of nested parameters is allowed.; (xsd)part:Parameters.parameter>{0,0}

🔗  This resource is a non-persisted resource used to pass information into and back from an [operation](http://hl7.org/fhir/R4/operations.html). It has no other use, and there is no RESTful endpoint associated with it. The parameters that may be used are defined by the OperationDefinition resource.parameters-questionnaire-next-question-in(xsd)=
	 <#base:Parameters>
	 <  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.; (xsd)id:string>?
	 <  The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.; (xsd)meta:Meta>?
	 <  A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. 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. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.; (xsd)implicitRules:uri>?
	 <  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).; (xsd)language:code>?
	[]<  A parameter passed to or received from the operation.; (xsd)parameter:parameters-questionnaire-next-question-in.parameter>*
	[]<  A parameter passed to or received from the operation.; (xsd)in:parameters-questionnaire-next-question-in.in>*

🔗  A parameter passed to or received from the operation.parameters-questionnaire-next-question-in.in(xsd)=
	 <#base:BackboneElement>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  The name of the parameter (reference to the operation definition). questionnaire-response; (xsd)name:string>
	 ( <valueAddress:Address>
		 | <valueAge:Age>
		 | <valueAnnotation:Annotation>
		 | <valueAttachment:Attachment>
		 | <valueBase64Binary:base64Binary>
		 | <valueBoolean:boolean>
		 | <valueCanonical:canonical>
		 | <valueCode:code>
		 | <valueCodeableConcept:CodeableConcept>
		 | <valueCoding:Coding>
		 | <valueContactDetail:ContactDetail>
		 | <valueContactPoint:ContactPoint>
		 | <valueContributor:Contributor>
		 | <valueCount:Count>
		 | <valueDataRequirement:DataRequirement>
		 | <valueDate:date>
		 | <valueDateTime:dateTime>
		 | <valueDecimal:decimal>
		 | <valueDistance:Distance>
		 | <valueDosage:Dosage>
		 | <valueDuration:Duration>
		 | <valueExpression:Expression>
		 | <valueHumanName:HumanName>
		 | <valueId:id>
		 | <valueIdentifier:Identifier>
		 | <valueInstant:instant>
		 | <valueInteger:integer>
		 | <valueMarkdown:markdown>
		 | <valueMeta:Meta>
		 | <valueMoney:Money>
		 | <valueOid:oid>
		 | <valueParameterDefinition:ParameterDefinition>
		 | <valuePeriod:Period>
		 | <valuePositiveInt:positiveInt>
		 | <valueQuantity:Quantity>
		 | <valueRange:Range>
		 | <valueRatio:Ratio>
		 | <valueRelatedArtifact:RelatedArtifact>
		 | <valueResource:Resource>
		 | <valueSampledData:SampledData>
		 | <valueSignature:Signature>
		 | <valueString:string>
		 | <valueTime:time>
		 | <valueTiming:Timing>
		 | <valueTriggerDefinition:TriggerDefinition>
		 | <valueUnsignedInt:unsignedInt>
		 | <valueUri:uri>
		 | <valueUrl:url>
		 | <valueUsageContext:UsageContext>
		 | <valueUuid:uuid>){0,0}
	 <  Sets expectations for supported capabilities for questionnaire responses for SDC-conformant systems. The QuestionnaireResponse contains enough information about the questions asked and their organization that it can be interpreted somewhat independently from the Questionnaire it is based on.  I.e. You don't need access to the Questionnaire in order to extract basic information from a QuestionnaireResponse.; (xsd)resource:sdc-questionnaireresponse-adapt>?
	 <  A named part of a multi-part parameter. Only one level of nested parameters is allowed.; (xsd)part:Parameters.parameter>{0,0}

🔗  A parameter passed to or received from the operation.parameters-questionnaire-next-question-in.parameter(xsd)=
	 <#base:Parameters.parameter>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  The name of the parameter (reference to the operation definition).; (xsd)name:string>
	 ( <valueAddress:Address>
		 | <valueAge:Age>
		 | <valueAnnotation:Annotation>
		 | <valueAttachment:Attachment>
		 | <valueBase64Binary:base64Binary>
		 | <valueBoolean:boolean>
		 | <valueCanonical:canonical>
		 | <valueCode:code>
		 | <valueCodeableConcept:CodeableConcept>
		 | <valueCoding:Coding>
		 | <valueContactDetail:ContactDetail>
		 | <valueContactPoint:ContactPoint>
		 | <valueContributor:Contributor>
		 | <valueCount:Count>
		 | <valueDataRequirement:DataRequirement>
		 | <valueDate:date>
		 | <valueDateTime:dateTime>
		 | <valueDecimal:decimal>
		 | <valueDistance:Distance>
		 | <valueDosage:Dosage>
		 | <valueDuration:Duration>
		 | <valueExpression:Expression>
		 | <valueHumanName:HumanName>
		 | <valueId:id>
		 | <valueIdentifier:Identifier>
		 | <valueInstant:instant>
		 | <valueInteger:integer>
		 | <valueMarkdown:markdown>
		 | <valueMeta:Meta>
		 | <valueMoney:Money>
		 | <valueOid:oid>
		 | <valueParameterDefinition:ParameterDefinition>
		 | <valuePeriod:Period>
		 | <valuePositiveInt:positiveInt>
		 | <valueQuantity:Quantity>
		 | <valueRange:Range>
		 | <valueRatio:Ratio>
		 | <valueRelatedArtifact:RelatedArtifact>
		 | <valueResource:Resource>
		 | <valueSampledData:SampledData>
		 | <valueSignature:Signature>
		 | <valueString:string>
		 | <valueTime:time>
		 | <valueTiming:Timing>
		 | <valueTriggerDefinition:TriggerDefinition>
		 | <valueUnsignedInt:unsignedInt>
		 | <valueUri:uri>
		 | <valueUrl:url>
		 | <valueUsageContext:UsageContext>
		 | <valueUuid:uuid>)?
	 <  If the parameter is a whole resource. When resolving references in resources, the operation definition may specify how references may be resolved between parameters. If a reference cannot be resolved between the parameters, the application should fall back to it's general resource resolution methods.; (xsd)resource:Resource>?
	[]<  A named part of a multi-part parameter. Only one level of nested parameters is allowed.; (xsd)part:Parameters.parameter>*

🔗  This resource is a non-persisted resource used to pass information into and back from an [operation](http://hl7.org/fhir/R4/operations.html). It has no other use, and there is no RESTful endpoint associated with it. The parameters that may be used are defined by the OperationDefinition resource.parameters-questionnaire-next-question-out(xsd)=
	 <#base:Parameters>
	 <  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.; (xsd)id:string>?
	 <  The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.; (xsd)meta:Meta>?
	 <  A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. 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. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.; (xsd)implicitRules:uri>?
	 <  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).; (xsd)language:code>?
	[]<  A parameter passed to or received from the operation.; (xsd)parameter:parameters-questionnaire-next-question-out.parameter>*
	[]<  A parameter passed to or received from the operation.; (xsd)out:parameters-questionnaire-next-question-out.out>*

🔗  A parameter passed to or received from the operation.parameters-questionnaire-next-question-out.out(xsd)=
	 <#base:BackboneElement>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  The name of the parameter (reference to the operation definition). return; (xsd)name:string>
	 ( <valueAddress:Address>
		 | <valueAge:Age>
		 | <valueAnnotation:Annotation>
		 | <valueAttachment:Attachment>
		 | <valueBase64Binary:base64Binary>
		 | <valueBoolean:boolean>
		 | <valueCanonical:canonical>
		 | <valueCode:code>
		 | <valueCodeableConcept:CodeableConcept>
		 | <valueCoding:Coding>
		 | <valueContactDetail:ContactDetail>
		 | <valueContactPoint:ContactPoint>
		 | <valueContributor:Contributor>
		 | <valueCount:Count>
		 | <valueDataRequirement:DataRequirement>
		 | <valueDate:date>
		 | <valueDateTime:dateTime>
		 | <valueDecimal:decimal>
		 | <valueDistance:Distance>
		 | <valueDosage:Dosage>
		 | <valueDuration:Duration>
		 | <valueExpression:Expression>
		 | <valueHumanName:HumanName>
		 | <valueId:id>
		 | <valueIdentifier:Identifier>
		 | <valueInstant:instant>
		 | <valueInteger:integer>
		 | <valueMarkdown:markdown>
		 | <valueMeta:Meta>
		 | <valueMoney:Money>
		 | <valueOid:oid>
		 | <valueParameterDefinition:ParameterDefinition>
		 | <valuePeriod:Period>
		 | <valuePositiveInt:positiveInt>
		 | <valueQuantity:Quantity>
		 | <valueRange:Range>
		 | <valueRatio:Ratio>
		 | <valueRelatedArtifact:RelatedArtifact>
		 | <valueResource:Resource>
		 | <valueSampledData:SampledData>
		 | <valueSignature:Signature>
		 | <valueString:string>
		 | <valueTime:time>
		 | <valueTiming:Timing>
		 | <valueTriggerDefinition:TriggerDefinition>
		 | <valueUnsignedInt:unsignedInt>
		 | <valueUri:uri>
		 | <valueUrl:url>
		 | <valueUsageContext:UsageContext>
		 | <valueUuid:uuid>){0,0}
	 <  Sets expectations for supported capabilities for questionnaire responses for SDC-conformant systems. The QuestionnaireResponse contains enough information about the questions asked and their organization that it can be interpreted somewhat independently from the Questionnaire it is based on.  I.e. You don't need access to the Questionnaire in order to extract basic information from a QuestionnaireResponse.; (xsd)resource:sdc-questionnaireresponse-adapt>?
	 <  A named part of a multi-part parameter. Only one level of nested parameters is allowed.; (xsd)part:Parameters.parameter>{0,0}

🔗  A parameter passed to or received from the operation.parameters-questionnaire-next-question-out.parameter(xsd)=
	 <#base:Parameters.parameter>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  The name of the parameter (reference to the operation definition).; (xsd)name:string>
	 ( <valueAddress:Address>
		 | <valueAge:Age>
		 | <valueAnnotation:Annotation>
		 | <valueAttachment:Attachment>
		 | <valueBase64Binary:base64Binary>
		 | <valueBoolean:boolean>
		 | <valueCanonical:canonical>
		 | <valueCode:code>
		 | <valueCodeableConcept:CodeableConcept>
		 | <valueCoding:Coding>
		 | <valueContactDetail:ContactDetail>
		 | <valueContactPoint:ContactPoint>
		 | <valueContributor:Contributor>
		 | <valueCount:Count>
		 | <valueDataRequirement:DataRequirement>
		 | <valueDate:date>
		 | <valueDateTime:dateTime>
		 | <valueDecimal:decimal>
		 | <valueDistance:Distance>
		 | <valueDosage:Dosage>
		 | <valueDuration:Duration>
		 | <valueExpression:Expression>
		 | <valueHumanName:HumanName>
		 | <valueId:id>
		 | <valueIdentifier:Identifier>
		 | <valueInstant:instant>
		 | <valueInteger:integer>
		 | <valueMarkdown:markdown>
		 | <valueMeta:Meta>
		 | <valueMoney:Money>
		 | <valueOid:oid>
		 | <valueParameterDefinition:ParameterDefinition>
		 | <valuePeriod:Period>
		 | <valuePositiveInt:positiveInt>
		 | <valueQuantity:Quantity>
		 | <valueRange:Range>
		 | <valueRatio:Ratio>
		 | <valueRelatedArtifact:RelatedArtifact>
		 | <valueResource:Resource>
		 | <valueSampledData:SampledData>
		 | <valueSignature:Signature>
		 | <valueString:string>
		 | <valueTime:time>
		 | <valueTiming:Timing>
		 | <valueTriggerDefinition:TriggerDefinition>
		 | <valueUnsignedInt:unsignedInt>
		 | <valueUri:uri>
		 | <valueUrl:url>
		 | <valueUsageContext:UsageContext>
		 | <valueUuid:uuid>)?
	 <  If the parameter is a whole resource. When resolving references in resources, the operation definition may specify how references may be resolved between parameters. If a reference cannot be resolved between the parameters, the application should fall back to it's general resource resolution methods.; (xsd)resource:Resource>?
	[]<  A named part of a multi-part parameter. Only one level of nested parameters is allowed.; (xsd)part:Parameters.parameter>*

🔗  This resource is a non-persisted resource used to pass information into and back from an [operation](http://hl7.org/fhir/R4/operations.html). It has no other use, and there is no RESTful endpoint associated with it. The parameters that may be used are defined by the OperationDefinition resource.parameters-questionnaire-populate-html-out(xsd)=
	 <#base:Parameters>
	 <  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.; (xsd)id:string>?
	 <  The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.; (xsd)meta:Meta>?
	 <  A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. 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. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.; (xsd)implicitRules:uri>?
	 <  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).; (xsd)language:code>?
	[]<  A parameter passed to or received from the operation.; (xsd)parameter:parameters-questionnaire-populate-html-out.parameter>+
	 <  A parameter passed to or received from the operation.; (xsd)form:parameters-questionnaire-populate-html-out.form>
	 <  A parameter passed to or received from the operation.; (xsd)issues:parameters-questionnaire-populate-html-out.issues>?

🔗  A parameter passed to or received from the operation.parameters-questionnaire-populate-html-out.form(xsd)=
	 <#base:BackboneElement>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  The name of the parameter (reference to the operation definition). form; (xsd)name:string>
	 ( <valueAddress:Address>
		 | <valueAge:Age>
		 | <valueAnnotation:Annotation>
		 | <valueAttachment:Attachment>
		 | <valueBase64Binary:base64Binary>
		 | <valueBoolean:boolean>
		 | <valueCanonical:canonical>
		 | <valueCode:code>
		 | <valueCodeableConcept:CodeableConcept>
		 | <valueCoding:Coding>
		 | <valueContactDetail:ContactDetail>
		 | <valueContactPoint:ContactPoint>
		 | <valueContributor:Contributor>
		 | <valueCount:Count>
		 | <valueDataRequirement:DataRequirement>
		 | <valueDate:date>
		 | <valueDateTime:dateTime>
		 | <valueDecimal:decimal>
		 | <valueDistance:Distance>
		 | <valueDosage:Dosage>
		 | <valueDuration:Duration>
		 | <valueExpression:Expression>
		 | <valueHumanName:HumanName>
		 | <valueId:id>
		 | <valueIdentifier:Identifier>
		 | <valueInstant:instant>
		 | <valueInteger:integer>
		 | <valueMarkdown:markdown>
		 | <valueMeta:Meta>
		 | <valueMoney:Money>
		 | <valueOid:oid>
		 | <valueParameterDefinition:ParameterDefinition>
		 | <valuePeriod:Period>
		 | <valuePositiveInt:positiveInt>
		 | <valueQuantity:Quantity>
		 | <valueRange:Range>
		 | <valueRatio:Ratio>
		 | <valueRelatedArtifact:RelatedArtifact>
		 | <valueResource:Resource>
		 | <valueSampledData:SampledData>
		 | <valueSignature:Signature>
		 | <valueString:string>
		 | <valueTime:time>
		 | <valueTiming:Timing>
		 | <valueTriggerDefinition:TriggerDefinition>
		 | <valueUnsignedInt:unsignedInt>
		 | <valueUri:uri>
		 | <valueUrl:url>
		 | <valueUsageContext:UsageContext>
		 | <valueUuid:uuid>){0,0}
	 <  If the parameter is a whole resource. When resolving references in resources, the operation definition may specify how references may be resolved between parameters. If a reference cannot be resolved between the parameters, the application should fall back to it's general resource resolution methods.; (xsd)resource:Binary>
	 <  A named part of a multi-part parameter. Only one level of nested parameters is allowed.; (xsd)part:Parameters.parameter>{0,0}

🔗  A parameter passed to or received from the operation.parameters-questionnaire-populate-html-out.issues(xsd)=
	 <#base:BackboneElement>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  The name of the parameter (reference to the operation definition). issues; (xsd)name:string>
	 ( <valueAddress:Address>
		 | <valueAge:Age>
		 | <valueAnnotation:Annotation>
		 | <valueAttachment:Attachment>
		 | <valueBase64Binary:base64Binary>
		 | <valueBoolean:boolean>
		 | <valueCanonical:canonical>
		 | <valueCode:code>
		 | <valueCodeableConcept:CodeableConcept>
		 | <valueCoding:Coding>
		 | <valueContactDetail:ContactDetail>
		 | <valueContactPoint:ContactPoint>
		 | <valueContributor:Contributor>
		 | <valueCount:Count>
		 | <valueDataRequirement:DataRequirement>
		 | <valueDate:date>
		 | <valueDateTime:dateTime>
		 | <valueDecimal:decimal>
		 | <valueDistance:Distance>
		 | <valueDosage:Dosage>
		 | <valueDuration:Duration>
		 | <valueExpression:Expression>
		 | <valueHumanName:HumanName>
		 | <valueId:id>
		 | <valueIdentifier:Identifier>
		 | <valueInstant:instant>
		 | <valueInteger:integer>
		 | <valueMarkdown:markdown>
		 | <valueMeta:Meta>
		 | <valueMoney:Money>
		 | <valueOid:oid>
		 | <valueParameterDefinition:ParameterDefinition>
		 | <valuePeriod:Period>
		 | <valuePositiveInt:positiveInt>
		 | <valueQuantity:Quantity>
		 | <valueRange:Range>
		 | <valueRatio:Ratio>
		 | <valueRelatedArtifact:RelatedArtifact>
		 | <valueResource:Resource>
		 | <valueSampledData:SampledData>
		 | <valueSignature:Signature>
		 | <valueString:string>
		 | <valueTime:time>
		 | <valueTiming:Timing>
		 | <valueTriggerDefinition:TriggerDefinition>
		 | <valueUnsignedInt:unsignedInt>
		 | <valueUri:uri>
		 | <valueUrl:url>
		 | <valueUsageContext:UsageContext>
		 | <valueUuid:uuid>){0,0}
	 <  If the parameter is a whole resource. When resolving references in resources, the operation definition may specify how references may be resolved between parameters. If a reference cannot be resolved between the parameters, the application should fall back to it's general resource resolution methods.; (xsd)resource:OperationOutcome>
	 <  A named part of a multi-part parameter. Only one level of nested parameters is allowed.; (xsd)part:Parameters.parameter>{0,0}

🔗  A parameter passed to or received from the operation.parameters-questionnaire-populate-html-out.parameter(xsd)=
	 <#base:Parameters.parameter>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  The name of the parameter (reference to the operation definition).; (xsd)name:string>
	 ( <valueAddress:Address>
		 | <valueAge:Age>
		 | <valueAnnotation:Annotation>
		 | <valueAttachment:Attachment>
		 | <valueBase64Binary:base64Binary>
		 | <valueBoolean:boolean>
		 | <valueCanonical:canonical>
		 | <valueCode:code>
		 | <valueCodeableConcept:CodeableConcept>
		 | <valueCoding:Coding>
		 | <valueContactDetail:ContactDetail>
		 | <valueContactPoint:ContactPoint>
		 | <valueContributor:Contributor>
		 | <valueCount:Count>
		 | <valueDataRequirement:DataRequirement>
		 | <valueDate:date>
		 | <valueDateTime:dateTime>
		 | <valueDecimal:decimal>
		 | <valueDistance:Distance>
		 | <valueDosage:Dosage>
		 | <valueDuration:Duration>
		 | <valueExpression:Expression>
		 | <valueHumanName:HumanName>
		 | <valueId:id>
		 | <valueIdentifier:Identifier>
		 | <valueInstant:instant>
		 | <valueInteger:integer>
		 | <valueMarkdown:markdown>
		 | <valueMeta:Meta>
		 | <valueMoney:Money>
		 | <valueOid:oid>
		 | <valueParameterDefinition:ParameterDefinition>
		 | <valuePeriod:Period>
		 | <valuePositiveInt:positiveInt>
		 | <valueQuantity:Quantity>
		 | <valueRange:Range>
		 | <valueRatio:Ratio>
		 | <valueRelatedArtifact:RelatedArtifact>
		 | <valueResource:Resource>
		 | <valueSampledData:SampledData>
		 | <valueSignature:Signature>
		 | <valueString:string>
		 | <valueTime:time>
		 | <valueTiming:Timing>
		 | <valueTriggerDefinition:TriggerDefinition>
		 | <valueUnsignedInt:unsignedInt>
		 | <valueUri:uri>
		 | <valueUrl:url>
		 | <valueUsageContext:UsageContext>
		 | <valueUuid:uuid>)?
	 <  If the parameter is a whole resource. When resolving references in resources, the operation definition may specify how references may be resolved between parameters. If a reference cannot be resolved between the parameters, the application should fall back to it's general resource resolution methods.; (xsd)resource:Resource>?
	[]<  A named part of a multi-part parameter. Only one level of nested parameters is allowed.; (xsd)part:Parameters.parameter>*

🔗  This resource is a non-persisted resource used to pass information into and back from an [operation](http://hl7.org/fhir/R4/operations.html). It has no other use, and there is no RESTful endpoint associated with it. The parameters that may be used are defined by the OperationDefinition resource.parameters-questionnaire-populate-in(xsd)=
	 <#base:Parameters>
	 <  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.; (xsd)id:string>?
	 <  The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.; (xsd)meta:Meta>?
	 <  A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. 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. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.; (xsd)implicitRules:uri>?
	 <  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).; (xsd)language:code>?
	[]<  A parameter passed to or received from the operation.; (xsd)parameter:parameters-questionnaire-populate-in.parameter>*
	 <  A parameter passed to or received from the operation.; (xsd)identifier:parameters-questionnaire-populate-in.identifier>?
	 <  A parameter passed to or received from the operation.; (xsd)questionnaire:parameters-questionnaire-populate-in.questionnaire>?
	 <  A parameter passed to or received from the operation.; (xsd)subject:parameters-questionnaire-populate-in.subject>?
	 <  A parameter passed to or received from the operation.; (xsd)context:parameters-questionnaire-populate-in.context>?
	 <  A parameter passed to or received from the operation.; (xsd)local:parameters-questionnaire-populate-in.local>?

🔗  A parameter passed to or received from the operation.parameters-questionnaire-populate-in.context(xsd)=
	 <#base:BackboneElement>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  The name of the parameter (reference to the operation definition). context; (xsd)name:string>
	 ( <valueAddress:Address>
		 | <valueAge:Age>
		 | <valueAnnotation:Annotation>
		 | <valueAttachment:Attachment>
		 | <valueBase64Binary:base64Binary>
		 | <valueBoolean:boolean>
		 | <valueCanonical:canonical>
		 | <valueCode:code>
		 | <valueCodeableConcept:CodeableConcept>
		 | <valueCoding:Coding>
		 | <valueContactDetail:ContactDetail>
		 | <valueContactPoint:ContactPoint>
		 | <valueContributor:Contributor>
		 | <valueCount:Count>
		 | <valueDataRequirement:DataRequirement>
		 | <valueDate:date>
		 | <valueDateTime:dateTime>
		 | <valueDecimal:decimal>
		 | <valueDistance:Distance>
		 | <valueDosage:Dosage>
		 | <valueDuration:Duration>
		 | <valueExpression:Expression>
		 | <valueHumanName:HumanName>
		 | <valueId:id>
		 | <valueIdentifier:Identifier>
		 | <valueInstant:instant>
		 | <valueInteger:integer>
		 | <valueMarkdown:markdown>
		 | <valueMeta:Meta>
		 | <valueMoney:Money>
		 | <valueOid:oid>
		 | <valueParameterDefinition:ParameterDefinition>
		 | <valuePeriod:Period>
		 | <valuePositiveInt:positiveInt>
		 | <valueQuantity:Quantity>
		 | <valueRange:Range>
		 | <valueRatio:Ratio>
		 | <valueRelatedArtifact:RelatedArtifact>
		 | <valueResource:Resource>
		 | <valueSampledData:SampledData>
		 | <valueSignature:Signature>
		 | <valueString:string>
		 | <valueTime:time>
		 | <valueTiming:Timing>
		 | <valueTriggerDefinition:TriggerDefinition>
		 | <valueUnsignedInt:unsignedInt>
		 | <valueUri:uri>
		 | <valueUrl:url>
		 | <valueUsageContext:UsageContext>
		 | <valueUuid:uuid>){0,0}
	 <  If the parameter is a whole resource. When resolving references in resources, the operation definition may specify how references may be resolved between parameters. If a reference cannot be resolved between the parameters, the application should fall back to it's general resource resolution methods.; (xsd)resource:Resource>{0,0}
	[]<  A named part of a multi-part parameter. Only one level of nested parameters is allowed.; (xsd)part:Parameters.parameter>{2,2147483647}
	 <  A named part of a multi-part parameter. Only one level of nested parameters is allowed.; (xsd)name:parameters-questionnaire-populate-in.context.name>
	[]<  A named part of a multi-part parameter. Only one level of nested parameters is allowed.; (xsd)content:parameters-questionnaire-populate-in.context.content>*

🔗  A named part of a multi-part parameter. Only one level of nested parameters is allowed.parameters-questionnaire-populate-in.context.content(xsd)=
	 <#base:BackboneElement>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  The name of the parameter (reference to the operation definition). content; (xsd)name:string>
	 <  If the parameter is a data type.; (xsd)value:Resource*>?
	 <  If the parameter is a whole resource. When resolving references in resources, the operation definition may specify how references may be resolved between parameters. If a reference cannot be resolved between the parameters, the application should fall back to it's general resource resolution methods.; (xsd)resource:Resource>?
	 <  A named part of a multi-part parameter. Only one level of nested parameters is allowed.; (xsd)part:Parameters.parameter>{0,0}

🔗  A named part of a multi-part parameter. Only one level of nested parameters is allowed.parameters-questionnaire-populate-in.context.name(xsd)=
	 <#base:BackboneElement>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  The name of the parameter (reference to the operation definition). name; (xsd)name:string>
	 <  If the parameter is a data type.; (xsd)value:string>
	 <  If the parameter is a whole resource. When resolving references in resources, the operation definition may specify how references may be resolved between parameters. If a reference cannot be resolved between the parameters, the application should fall back to it's general resource resolution methods.; (xsd)resource:Resource>{0,0}
	 <  A named part of a multi-part parameter. Only one level of nested parameters is allowed.; (xsd)part:Parameters.parameter>{0,0}

🔗  A parameter passed to or received from the operation.parameters-questionnaire-populate-in.identifier(xsd)=
	 <#base:BackboneElement>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  The name of the parameter (reference to the operation definition). identifier; (xsd)name:string>
	 <  If the parameter is a data type.; (xsd)value:Identifier>
	 <  If the parameter is a whole resource. When resolving references in resources, the operation definition may specify how references may be resolved between parameters. If a reference cannot be resolved between the parameters, the application should fall back to it's general resource resolution methods.; (xsd)resource:Resource>{0,0}
	 <  A named part of a multi-part parameter. Only one level of nested parameters is allowed.; (xsd)part:Parameters.parameter>{0,0}

🔗  A parameter passed to or received from the operation.parameters-questionnaire-populate-in.local(xsd)=
	 <#base:BackboneElement>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  The name of the parameter (reference to the operation definition). local; (xsd)name:string>
	 <  If the parameter is a data type.; (xsd)value:boolean>
	 <  If the parameter is a whole resource. When resolving references in resources, the operation definition may specify how references may be resolved between parameters. If a reference cannot be resolved between the parameters, the application should fall back to it's general resource resolution methods.; (xsd)resource:Resource>{0,0}
	 <  A named part of a multi-part parameter. Only one level of nested parameters is allowed.; (xsd)part:Parameters.parameter>{0,0}

🔗  A parameter passed to or received from the operation.parameters-questionnaire-populate-in.parameter(xsd)=
	 <#base:Parameters.parameter>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  The name of the parameter (reference to the operation definition).; (xsd)name:string>
	 ( <valueAddress:Address>
		 | <valueAge:Age>
		 | <valueAnnotation:Annotation>
		 | <valueAttachment:Attachment>
		 | <valueBase64Binary:base64Binary>
		 | <valueBoolean:boolean>
		 | <valueCanonical:canonical>
		 | <valueCode:code>
		 | <valueCodeableConcept:CodeableConcept>
		 | <valueCoding:Coding>
		 | <valueContactDetail:ContactDetail>
		 | <valueContactPoint:ContactPoint>
		 | <valueContributor:Contributor>
		 | <valueCount:Count>
		 | <valueDataRequirement:DataRequirement>
		 | <valueDate:date>
		 | <valueDateTime:dateTime>
		 | <valueDecimal:decimal>
		 | <valueDistance:Distance>
		 | <valueDosage:Dosage>
		 | <valueDuration:Duration>
		 | <valueExpression:Expression>
		 | <valueHumanName:HumanName>
		 | <valueId:id>
		 | <valueIdentifier:Identifier>
		 | <valueInstant:instant>
		 | <valueInteger:integer>
		 | <valueMarkdown:markdown>
		 | <valueMeta:Meta>
		 | <valueMoney:Money>
		 | <valueOid:oid>
		 | <valueParameterDefinition:ParameterDefinition>
		 | <valuePeriod:Period>
		 | <valuePositiveInt:positiveInt>
		 | <valueQuantity:Quantity>
		 | <valueRange:Range>
		 | <valueRatio:Ratio>
		 | <valueRelatedArtifact:RelatedArtifact>
		 | <valueResource:Resource>
		 | <valueSampledData:SampledData>
		 | <valueSignature:Signature>
		 | <valueString:string>
		 | <valueTime:time>
		 | <valueTiming:Timing>
		 | <valueTriggerDefinition:TriggerDefinition>
		 | <valueUnsignedInt:unsignedInt>
		 | <valueUri:uri>
		 | <valueUrl:url>
		 | <valueUsageContext:UsageContext>
		 | <valueUuid:uuid>)?
	 <  If the parameter is a whole resource. When resolving references in resources, the operation definition may specify how references may be resolved between parameters. If a reference cannot be resolved between the parameters, the application should fall back to it's general resource resolution methods.; (xsd)resource:Resource>?
	[]<  A named part of a multi-part parameter. Only one level of nested parameters is allowed.; (xsd)part:Parameters.parameter>*

🔗  A parameter passed to or received from the operation.parameters-questionnaire-populate-in.questionnaire(xsd)=
	 <#base:BackboneElement>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  The name of the parameter (reference to the operation definition). questionnaire; (xsd)name:string>
	 ( <valueQuestionnaire:Questionnaire>
		 | <valueUri:uri>)?
	 <  If the parameter is a whole resource. When resolving references in resources, the operation definition may specify how references may be resolved between parameters. If a reference cannot be resolved between the parameters, the application should fall back to it's general resource resolution methods.; (xsd)resource:Questionnaire>?
	 <  A named part of a multi-part parameter. Only one level of nested parameters is allowed.; (xsd)part:Parameters.parameter>{0,0}

🔗  A parameter passed to or received from the operation.parameters-questionnaire-populate-in.subject(xsd)=
	 <#base:BackboneElement>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  The name of the parameter (reference to the operation definition). subject; (xsd)name:string>
	 <  If the parameter is a data type.; (xsd)value:Resource*>
	 <  If the parameter is a whole resource. When resolving references in resources, the operation definition may specify how references may be resolved between parameters. If a reference cannot be resolved between the parameters, the application should fall back to it's general resource resolution methods.; (xsd)resource:Resource>{0,0}
	 <  A named part of a multi-part parameter. Only one level of nested parameters is allowed.; (xsd)part:Parameters.parameter>{0,0}

🔗  This resource is a non-persisted resource used to pass information into and back from an [operation](http://hl7.org/fhir/R4/operations.html). It has no other use, and there is no RESTful endpoint associated with it. The parameters that may be used are defined by the OperationDefinition resource.parameters-questionnaire-populate-link-out(xsd)=
	 <#base:Parameters>
	 <  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.; (xsd)id:string>?
	 <  The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.; (xsd)meta:Meta>?
	 <  A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. 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. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.; (xsd)implicitRules:uri>?
	 <  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).; (xsd)language:code>?
	[]<  A parameter passed to or received from the operation.; (xsd)parameter:parameters-questionnaire-populate-link-out.parameter>+
	 <  A parameter passed to or received from the operation.; (xsd)link:parameters-questionnaire-populate-link-out.link>
	 <  A parameter passed to or received from the operation.; (xsd)issues:parameters-questionnaire-populate-link-out.issues>?

🔗  A parameter passed to or received from the operation.parameters-questionnaire-populate-link-out.issues(xsd)=
	 <#base:BackboneElement>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  The name of the parameter (reference to the operation definition). issues; (xsd)name:string>
	 ( <valueAddress:Address>
		 | <valueAge:Age>
		 | <valueAnnotation:Annotation>
		 | <valueAttachment:Attachment>
		 | <valueBase64Binary:base64Binary>
		 | <valueBoolean:boolean>
		 | <valueCanonical:canonical>
		 | <valueCode:code>
		 | <valueCodeableConcept:CodeableConcept>
		 | <valueCoding:Coding>
		 | <valueContactDetail:ContactDetail>
		 | <valueContactPoint:ContactPoint>
		 | <valueContributor:Contributor>
		 | <valueCount:Count>
		 | <valueDataRequirement:DataRequirement>
		 | <valueDate:date>
		 | <valueDateTime:dateTime>
		 | <valueDecimal:decimal>
		 | <valueDistance:Distance>
		 | <valueDosage:Dosage>
		 | <valueDuration:Duration>
		 | <valueExpression:Expression>
		 | <valueHumanName:HumanName>
		 | <valueId:id>
		 | <valueIdentifier:Identifier>
		 | <valueInstant:instant>
		 | <valueInteger:integer>
		 | <valueMarkdown:markdown>
		 | <valueMeta:Meta>
		 | <valueMoney:Money>
		 | <valueOid:oid>
		 | <valueParameterDefinition:ParameterDefinition>
		 | <valuePeriod:Period>
		 | <valuePositiveInt:positiveInt>
		 | <valueQuantity:Quantity>
		 | <valueRange:Range>
		 | <valueRatio:Ratio>
		 | <valueRelatedArtifact:RelatedArtifact>
		 | <valueResource:Resource>
		 | <valueSampledData:SampledData>
		 | <valueSignature:Signature>
		 | <valueString:string>
		 | <valueTime:time>
		 | <valueTiming:Timing>
		 | <valueTriggerDefinition:TriggerDefinition>
		 | <valueUnsignedInt:unsignedInt>
		 | <valueUri:uri>
		 | <valueUrl:url>
		 | <valueUsageContext:UsageContext>
		 | <valueUuid:uuid>){0,0}
	 <  If the parameter is a whole resource. When resolving references in resources, the operation definition may specify how references may be resolved between parameters. If a reference cannot be resolved between the parameters, the application should fall back to it's general resource resolution methods.; (xsd)resource:OperationOutcome>
	 <  A named part of a multi-part parameter. Only one level of nested parameters is allowed.; (xsd)part:Parameters.parameter>{0,0}

🔗  A parameter passed to or received from the operation.parameters-questionnaire-populate-link-out.link(xsd)=
	 <#base:BackboneElement>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  The name of the parameter (reference to the operation definition). link; (xsd)name:string>
	 <  If the parameter is a data type.; (xsd)value:uri>
	 <  If the parameter is a whole resource. When resolving references in resources, the operation definition may specify how references may be resolved between parameters. If a reference cannot be resolved between the parameters, the application should fall back to it's general resource resolution methods.; (xsd)resource:Resource>{0,0}
	 <  A named part of a multi-part parameter. Only one level of nested parameters is allowed.; (xsd)part:Parameters.parameter>{0,0}

🔗  A parameter passed to or received from the operation.parameters-questionnaire-populate-link-out.parameter(xsd)=
	 <#base:Parameters.parameter>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  The name of the parameter (reference to the operation definition).; (xsd)name:string>
	 ( <valueAddress:Address>
		 | <valueAge:Age>
		 | <valueAnnotation:Annotation>
		 | <valueAttachment:Attachment>
		 | <valueBase64Binary:base64Binary>
		 | <valueBoolean:boolean>
		 | <valueCanonical:canonical>
		 | <valueCode:code>
		 | <valueCodeableConcept:CodeableConcept>
		 | <valueCoding:Coding>
		 | <valueContactDetail:ContactDetail>
		 | <valueContactPoint:ContactPoint>
		 | <valueContributor:Contributor>
		 | <valueCount:Count>
		 | <valueDataRequirement:DataRequirement>
		 | <valueDate:date>
		 | <valueDateTime:dateTime>
		 | <valueDecimal:decimal>
		 | <valueDistance:Distance>
		 | <valueDosage:Dosage>
		 | <valueDuration:Duration>
		 | <valueExpression:Expression>
		 | <valueHumanName:HumanName>
		 | <valueId:id>
		 | <valueIdentifier:Identifier>
		 | <valueInstant:instant>
		 | <valueInteger:integer>
		 | <valueMarkdown:markdown>
		 | <valueMeta:Meta>
		 | <valueMoney:Money>
		 | <valueOid:oid>
		 | <valueParameterDefinition:ParameterDefinition>
		 | <valuePeriod:Period>
		 | <valuePositiveInt:positiveInt>
		 | <valueQuantity:Quantity>
		 | <valueRange:Range>
		 | <valueRatio:Ratio>
		 | <valueRelatedArtifact:RelatedArtifact>
		 | <valueResource:Resource>
		 | <valueSampledData:SampledData>
		 | <valueSignature:Signature>
		 | <valueString:string>
		 | <valueTime:time>
		 | <valueTiming:Timing>
		 | <valueTriggerDefinition:TriggerDefinition>
		 | <valueUnsignedInt:unsignedInt>
		 | <valueUri:uri>
		 | <valueUrl:url>
		 | <valueUsageContext:UsageContext>
		 | <valueUuid:uuid>)?
	 <  If the parameter is a whole resource. When resolving references in resources, the operation definition may specify how references may be resolved between parameters. If a reference cannot be resolved between the parameters, the application should fall back to it's general resource resolution methods.; (xsd)resource:Resource>?
	[]<  A named part of a multi-part parameter. Only one level of nested parameters is allowed.; (xsd)part:Parameters.parameter>*

🔗  This resource is a non-persisted resource used to pass information into and back from an [operation](http://hl7.org/fhir/R4/operations.html). It has no other use, and there is no RESTful endpoint associated with it. The parameters that may be used are defined by the OperationDefinition resource.parameters-questionnaire-populate-out(xsd)=
	 <#base:Parameters>
	 <  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.; (xsd)id:string>?
	 <  The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.; (xsd)meta:Meta>?
	 <  A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. 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. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.; (xsd)implicitRules:uri>?
	 <  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).; (xsd)language:code>?
	[]<  A parameter passed to or received from the operation.; (xsd)parameter:parameters-questionnaire-populate-out.parameter>+
	 <  A parameter passed to or received from the operation.; (xsd)response:parameters-questionnaire-populate-out.response>
	 <  A parameter passed to or received from the operation.; (xsd)issues:parameters-questionnaire-populate-out.issues>?

🔗  A parameter passed to or received from the operation.parameters-questionnaire-populate-out.issues(xsd)=
	 <#base:BackboneElement>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  The name of the parameter (reference to the operation definition). issues; (xsd)name:string>
	 ( <valueAddress:Address>
		 | <valueAge:Age>
		 | <valueAnnotation:Annotation>
		 | <valueAttachment:Attachment>
		 | <valueBase64Binary:base64Binary>
		 | <valueBoolean:boolean>
		 | <valueCanonical:canonical>
		 | <valueCode:code>
		 | <valueCodeableConcept:CodeableConcept>
		 | <valueCoding:Coding>
		 | <valueContactDetail:ContactDetail>
		 | <valueContactPoint:ContactPoint>
		 | <valueContributor:Contributor>
		 | <valueCount:Count>
		 | <valueDataRequirement:DataRequirement>
		 | <valueDate:date>
		 | <valueDateTime:dateTime>
		 | <valueDecimal:decimal>
		 | <valueDistance:Distance>
		 | <valueDosage:Dosage>
		 | <valueDuration:Duration>
		 | <valueExpression:Expression>
		 | <valueHumanName:HumanName>
		 | <valueId:id>
		 | <valueIdentifier:Identifier>
		 | <valueInstant:instant>
		 | <valueInteger:integer>
		 | <valueMarkdown:markdown>
		 | <valueMeta:Meta>
		 | <valueMoney:Money>
		 | <valueOid:oid>
		 | <valueParameterDefinition:ParameterDefinition>
		 | <valuePeriod:Period>
		 | <valuePositiveInt:positiveInt>
		 | <valueQuantity:Quantity>
		 | <valueRange:Range>
		 | <valueRatio:Ratio>
		 | <valueRelatedArtifact:RelatedArtifact>
		 | <valueResource:Resource>
		 | <valueSampledData:SampledData>
		 | <valueSignature:Signature>
		 | <valueString:string>
		 | <valueTime:time>
		 | <valueTiming:Timing>
		 | <valueTriggerDefinition:TriggerDefinition>
		 | <valueUnsignedInt:unsignedInt>
		 | <valueUri:uri>
		 | <valueUrl:url>
		 | <valueUsageContext:UsageContext>
		 | <valueUuid:uuid>){0,0}
	 <  If the parameter is a whole resource. When resolving references in resources, the operation definition may specify how references may be resolved between parameters. If a reference cannot be resolved between the parameters, the application should fall back to it's general resource resolution methods.; (xsd)resource:OperationOutcome>
	 <  A named part of a multi-part parameter. Only one level of nested parameters is allowed.; (xsd)part:Parameters.parameter>{0,0}

🔗  A parameter passed to or received from the operation.parameters-questionnaire-populate-out.parameter(xsd)=
	 <#base:Parameters.parameter>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  The name of the parameter (reference to the operation definition).; (xsd)name:string>
	 ( <valueAddress:Address>
		 | <valueAge:Age>
		 | <valueAnnotation:Annotation>
		 | <valueAttachment:Attachment>
		 | <valueBase64Binary:base64Binary>
		 | <valueBoolean:boolean>
		 | <valueCanonical:canonical>
		 | <valueCode:code>
		 | <valueCodeableConcept:CodeableConcept>
		 | <valueCoding:Coding>
		 | <valueContactDetail:ContactDetail>
		 | <valueContactPoint:ContactPoint>
		 | <valueContributor:Contributor>
		 | <valueCount:Count>
		 | <valueDataRequirement:DataRequirement>
		 | <valueDate:date>
		 | <valueDateTime:dateTime>
		 | <valueDecimal:decimal>
		 | <valueDistance:Distance>
		 | <valueDosage:Dosage>
		 | <valueDuration:Duration>
		 | <valueExpression:Expression>
		 | <valueHumanName:HumanName>
		 | <valueId:id>
		 | <valueIdentifier:Identifier>
		 | <valueInstant:instant>
		 | <valueInteger:integer>
		 | <valueMarkdown:markdown>
		 | <valueMeta:Meta>
		 | <valueMoney:Money>
		 | <valueOid:oid>
		 | <valueParameterDefinition:ParameterDefinition>
		 | <valuePeriod:Period>
		 | <valuePositiveInt:positiveInt>
		 | <valueQuantity:Quantity>
		 | <valueRange:Range>
		 | <valueRatio:Ratio>
		 | <valueRelatedArtifact:RelatedArtifact>
		 | <valueResource:Resource>
		 | <valueSampledData:SampledData>
		 | <valueSignature:Signature>
		 | <valueString:string>
		 | <valueTime:time>
		 | <valueTiming:Timing>
		 | <valueTriggerDefinition:TriggerDefinition>
		 | <valueUnsignedInt:unsignedInt>
		 | <valueUri:uri>
		 | <valueUrl:url>
		 | <valueUsageContext:UsageContext>
		 | <valueUuid:uuid>)?
	 <  If the parameter is a whole resource. When resolving references in resources, the operation definition may specify how references may be resolved between parameters. If a reference cannot be resolved between the parameters, the application should fall back to it's general resource resolution methods.; (xsd)resource:Resource>?
	[]<  A named part of a multi-part parameter. Only one level of nested parameters is allowed.; (xsd)part:Parameters.parameter>*

🔗  A parameter passed to or received from the operation.parameters-questionnaire-populate-out.response(xsd)=
	 <#base:BackboneElement>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  The name of the parameter (reference to the operation definition). response; (xsd)name:string>
	 ( <valueAddress:Address>
		 | <valueAge:Age>
		 | <valueAnnotation:Annotation>
		 | <valueAttachment:Attachment>
		 | <valueBase64Binary:base64Binary>
		 | <valueBoolean:boolean>
		 | <valueCanonical:canonical>
		 | <valueCode:code>
		 | <valueCodeableConcept:CodeableConcept>
		 | <valueCoding:Coding>
		 | <valueContactDetail:ContactDetail>
		 | <valueContactPoint:ContactPoint>
		 | <valueContributor:Contributor>
		 | <valueCount:Count>
		 | <valueDataRequirement:DataRequirement>
		 | <valueDate:date>
		 | <valueDateTime:dateTime>
		 | <valueDecimal:decimal>
		 | <valueDistance:Distance>
		 | <valueDosage:Dosage>
		 | <valueDuration:Duration>
		 | <valueExpression:Expression>
		 | <valueHumanName:HumanName>
		 | <valueId:id>
		 | <valueIdentifier:Identifier>
		 | <valueInstant:instant>
		 | <valueInteger:integer>
		 | <valueMarkdown:markdown>
		 | <valueMeta:Meta>
		 | <valueMoney:Money>
		 | <valueOid:oid>
		 | <valueParameterDefinition:ParameterDefinition>
		 | <valuePeriod:Period>
		 | <valuePositiveInt:positiveInt>
		 | <valueQuantity:Quantity>
		 | <valueRange:Range>
		 | <valueRatio:Ratio>
		 | <valueRelatedArtifact:RelatedArtifact>
		 | <valueResource:Resource>
		 | <valueSampledData:SampledData>
		 | <valueSignature:Signature>
		 | <valueString:string>
		 | <valueTime:time>
		 | <valueTiming:Timing>
		 | <valueTriggerDefinition:TriggerDefinition>
		 | <valueUnsignedInt:unsignedInt>
		 | <valueUri:uri>
		 | <valueUrl:url>
		 | <valueUsageContext:UsageContext>
		 | <valueUuid:uuid>){0,0}
	 <  Sets expectations for supported capabilities for questionnaire responses for SDC-conformant systems. The QuestionnaireResponse contains enough information about the questions asked and their organization that it can be interpreted somewhat independently from the Questionnaire it is based on.  I.e. You don't need access to the Questionnaire in order to extract basic information from a QuestionnaireResponse.; (xsd)resource:sdc-questionnaireresponse>
	 <  A named part of a multi-part parameter. Only one level of nested parameters is allowed.; (xsd)part:Parameters.parameter>{0,0}

🔗  This resource is a non-persisted resource used to pass information into and back from an [operation](http://hl7.org/fhir/R4/operations.html). It has no other use, and there is no RESTful endpoint associated with it. The parameters that may be used are defined by the OperationDefinition resource.parameters-questionnaire-process-response-in(xsd)=
	 <#base:Parameters>
	 <  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.; (xsd)id:string>?
	 <  The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.; (xsd)meta:Meta>?
	 <  A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. 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. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.; (xsd)implicitRules:uri>?
	 <  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).; (xsd)language:code>?
	[]<  A parameter passed to or received from the operation.; (xsd)parameter:parameters-questionnaire-process-response-in.parameter>*
	[]<  A parameter passed to or received from the operation.; (xsd)in:parameters-questionnaire-process-response-in.in>*

🔗  A parameter passed to or received from the operation.parameters-questionnaire-process-response-in.in(xsd)=
	 <#base:BackboneElement>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  The name of the parameter (reference to the operation definition). in; (xsd)name:string>
	 ( <valueAddress:Address>
		 | <valueAge:Age>
		 | <valueAnnotation:Annotation>
		 | <valueAttachment:Attachment>
		 | <valueBase64Binary:base64Binary>
		 | <valueBoolean:boolean>
		 | <valueCanonical:canonical>
		 | <valueCode:code>
		 | <valueCodeableConcept:CodeableConcept>
		 | <valueCoding:Coding>
		 | <valueContactDetail:ContactDetail>
		 | <valueContactPoint:ContactPoint>
		 | <valueContributor:Contributor>
		 | <valueCount:Count>
		 | <valueDataRequirement:DataRequirement>
		 | <valueDate:date>
		 | <valueDateTime:dateTime>
		 | <valueDecimal:decimal>
		 | <valueDistance:Distance>
		 | <valueDosage:Dosage>
		 | <valueDuration:Duration>
		 | <valueExpression:Expression>
		 | <valueHumanName:HumanName>
		 | <valueId:id>
		 | <valueIdentifier:Identifier>
		 | <valueInstant:instant>
		 | <valueInteger:integer>
		 | <valueMarkdown:markdown>
		 | <valueMeta:Meta>
		 | <valueMoney:Money>
		 | <valueOid:oid>
		 | <valueParameterDefinition:ParameterDefinition>
		 | <valuePeriod:Period>
		 | <valuePositiveInt:positiveInt>
		 | <valueQuantity:Quantity>
		 | <valueRange:Range>
		 | <valueRatio:Ratio>
		 | <valueRelatedArtifact:RelatedArtifact>
		 | <valueResource:Resource>
		 | <valueSampledData:SampledData>
		 | <valueSignature:Signature>
		 | <valueString:string>
		 | <valueTime:time>
		 | <valueTiming:Timing>
		 | <valueTriggerDefinition:TriggerDefinition>
		 | <valueUnsignedInt:unsignedInt>
		 | <valueUri:uri>
		 | <valueUrl:url>
		 | <valueUsageContext:UsageContext>
		 | <valueUuid:uuid>){0,0}
	 <  Sets expectations for supported capabilities for questionnaire responses for SDC-conformant systems. The QuestionnaireResponse contains enough information about the questions asked and their organization that it can be interpreted somewhat independently from the Questionnaire it is based on.  I.e. You don't need access to the Questionnaire in order to extract basic information from a QuestionnaireResponse.; (xsd)resource:sdc-questionnaireresponse>?
	 <  A named part of a multi-part parameter. Only one level of nested parameters is allowed.; (xsd)part:Parameters.parameter>{0,0}

🔗  A parameter passed to or received from the operation.parameters-questionnaire-process-response-in.parameter(xsd)=
	 <#base:Parameters.parameter>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  The name of the parameter (reference to the operation definition).; (xsd)name:string>
	 ( <valueAddress:Address>
		 | <valueAge:Age>
		 | <valueAnnotation:Annotation>
		 | <valueAttachment:Attachment>
		 | <valueBase64Binary:base64Binary>
		 | <valueBoolean:boolean>
		 | <valueCanonical:canonical>
		 | <valueCode:code>
		 | <valueCodeableConcept:CodeableConcept>
		 | <valueCoding:Coding>
		 | <valueContactDetail:ContactDetail>
		 | <valueContactPoint:ContactPoint>
		 | <valueContributor:Contributor>
		 | <valueCount:Count>
		 | <valueDataRequirement:DataRequirement>
		 | <valueDate:date>
		 | <valueDateTime:dateTime>
		 | <valueDecimal:decimal>
		 | <valueDistance:Distance>
		 | <valueDosage:Dosage>
		 | <valueDuration:Duration>
		 | <valueExpression:Expression>
		 | <valueHumanName:HumanName>
		 | <valueId:id>
		 | <valueIdentifier:Identifier>
		 | <valueInstant:instant>
		 | <valueInteger:integer>
		 | <valueMarkdown:markdown>
		 | <valueMeta:Meta>
		 | <valueMoney:Money>
		 | <valueOid:oid>
		 | <valueParameterDefinition:ParameterDefinition>
		 | <valuePeriod:Period>
		 | <valuePositiveInt:positiveInt>
		 | <valueQuantity:Quantity>
		 | <valueRange:Range>
		 | <valueRatio:Ratio>
		 | <valueRelatedArtifact:RelatedArtifact>
		 | <valueResource:Resource>
		 | <valueSampledData:SampledData>
		 | <valueSignature:Signature>
		 | <valueString:string>
		 | <valueTime:time>
		 | <valueTiming:Timing>
		 | <valueTriggerDefinition:TriggerDefinition>
		 | <valueUnsignedInt:unsignedInt>
		 | <valueUri:uri>
		 | <valueUrl:url>
		 | <valueUsageContext:UsageContext>
		 | <valueUuid:uuid>)?
	 <  If the parameter is a whole resource. When resolving references in resources, the operation definition may specify how references may be resolved between parameters. If a reference cannot be resolved between the parameters, the application should fall back to it's general resource resolution methods.; (xsd)resource:Resource>?
	[]<  A named part of a multi-part parameter. Only one level of nested parameters is allowed.; (xsd)part:Parameters.parameter>*

🔗  This resource is a non-persisted resource used to pass information into and back from an [operation](http://hl7.org/fhir/R4/operations.html). It has no other use, and there is no RESTful endpoint associated with it. The parameters that may be used are defined by the OperationDefinition resource.parameters-questionnaireresponse-extract-in(xsd)=
	 <#base:Parameters>
	 <  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.; (xsd)id:string>?
	 <  The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.; (xsd)meta:Meta>?
	 <  A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. 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. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.; (xsd)implicitRules:uri>?
	 <  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).; (xsd)language:code>?
	[]<  A parameter passed to or received from the operation.; (xsd)parameter:parameters-questionnaireresponse-extract-in.parameter>*
	[]<  A parameter passed to or received from the operation.; (xsd)in:parameters-questionnaireresponse-extract-in.in>*
	 <  A parameter passed to or received from the operation.; (xsd)questionnaire:parameters-questionnaireresponse-extract-in.questionnaire>?

🔗  A parameter passed to or received from the operation.parameters-questionnaireresponse-extract-in.in(xsd)=
	 <#base:BackboneElement>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  The name of the parameter (reference to the operation definition). in; (xsd)name:string>
	 ( <valueAddress:Address>
		 | <valueAge:Age>
		 | <valueAnnotation:Annotation>
		 | <valueAttachment:Attachment>
		 | <valueBase64Binary:base64Binary>
		 | <valueBoolean:boolean>
		 | <valueCanonical:canonical>
		 | <valueCode:code>
		 | <valueCodeableConcept:CodeableConcept>
		 | <valueCoding:Coding>
		 | <valueContactDetail:ContactDetail>
		 | <valueContactPoint:ContactPoint>
		 | <valueContributor:Contributor>
		 | <valueCount:Count>
		 | <valueDataRequirement:DataRequirement>
		 | <valueDate:date>
		 | <valueDateTime:dateTime>
		 | <valueDecimal:decimal>
		 | <valueDistance:Distance>
		 | <valueDosage:Dosage>
		 | <valueDuration:Duration>
		 | <valueExpression:Expression>
		 | <valueHumanName:HumanName>
		 | <valueId:id>
		 | <valueIdentifier:Identifier>
		 | <valueInstant:instant>
		 | <valueInteger:integer>
		 | <valueMarkdown:markdown>
		 | <valueMeta:Meta>
		 | <valueMoney:Money>
		 | <valueOid:oid>
		 | <valueParameterDefinition:ParameterDefinition>
		 | <valuePeriod:Period>
		 | <valuePositiveInt:positiveInt>
		 | <valueQuantity:Quantity>
		 | <valueRange:Range>
		 | <valueRatio:Ratio>
		 | <valueRelatedArtifact:RelatedArtifact>
		 | <valueResource:Resource>
		 | <valueSampledData:SampledData>
		 | <valueSignature:Signature>
		 | <valueString:string>
		 | <valueTime:time>
		 | <valueTiming:Timing>
		 | <valueTriggerDefinition:TriggerDefinition>
		 | <valueUnsignedInt:unsignedInt>
		 | <valueUri:uri>
		 | <valueUrl:url>
		 | <valueUsageContext:UsageContext>
		 | <valueUuid:uuid>){0,0}
	 <  Defines elements that allow conversion of a QuestionnaireResponse to an Observation resource or Bundle of Observation resources using the Observation-based extraction mechanism. When resolving references in resources, the operation definition may specify how references may be resolved between parameters. If a reference cannot be resolved between the parameters, the application should fall back to it's general resource resolution methods.; (xsd)resource:( <sdc-questionnaire-extr-defn>
		 | <sdc-questionnaire-extr-obsn>
		 | <sdc-questionnaire-extr-smap>)>?
	 <  A named part of a multi-part parameter. Only one level of nested parameters is allowed.; (xsd)part:Parameters.parameter>{0,0}

🔗  A parameter passed to or received from the operation.parameters-questionnaireresponse-extract-in.parameter(xsd)=
	 <#base:Parameters.parameter>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  The name of the parameter (reference to the operation definition).; (xsd)name:string>
	 ( <valueAddress:Address>
		 | <valueAge:Age>
		 | <valueAnnotation:Annotation>
		 | <valueAttachment:Attachment>
		 | <valueBase64Binary:base64Binary>
		 | <valueBoolean:boolean>
		 | <valueCanonical:canonical>
		 | <valueCode:code>
		 | <valueCodeableConcept:CodeableConcept>
		 | <valueCoding:Coding>
		 | <valueContactDetail:ContactDetail>
		 | <valueContactPoint:ContactPoint>
		 | <valueContributor:Contributor>
		 | <valueCount:Count>
		 | <valueDataRequirement:DataRequirement>
		 | <valueDate:date>
		 | <valueDateTime:dateTime>
		 | <valueDecimal:decimal>
		 | <valueDistance:Distance>
		 | <valueDosage:Dosage>
		 | <valueDuration:Duration>
		 | <valueExpression:Expression>
		 | <valueHumanName:HumanName>
		 | <valueId:id>
		 | <valueIdentifier:Identifier>
		 | <valueInstant:instant>
		 | <valueInteger:integer>
		 | <valueMarkdown:markdown>
		 | <valueMeta:Meta>
		 | <valueMoney:Money>
		 | <valueOid:oid>
		 | <valueParameterDefinition:ParameterDefinition>
		 | <valuePeriod:Period>
		 | <valuePositiveInt:positiveInt>
		 | <valueQuantity:Quantity>
		 | <valueRange:Range>
		 | <valueRatio:Ratio>
		 | <valueRelatedArtifact:RelatedArtifact>
		 | <valueResource:Resource>
		 | <valueSampledData:SampledData>
		 | <valueSignature:Signature>
		 | <valueString:string>
		 | <valueTime:time>
		 | <valueTiming:Timing>
		 | <valueTriggerDefinition:TriggerDefinition>
		 | <valueUnsignedInt:unsignedInt>
		 | <valueUri:uri>
		 | <valueUrl:url>
		 | <valueUsageContext:UsageContext>
		 | <valueUuid:uuid>)?
	 <  If the parameter is a whole resource. When resolving references in resources, the operation definition may specify how references may be resolved between parameters. If a reference cannot be resolved between the parameters, the application should fall back to it's general resource resolution methods.; (xsd)resource:Resource>?
	[]<  A named part of a multi-part parameter. Only one level of nested parameters is allowed.; (xsd)part:Parameters.parameter>*

🔗  A parameter passed to or received from the operation.parameters-questionnaireresponse-extract-in.questionnaire(xsd)=
	 <#base:BackboneElement>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  The name of the parameter (reference to the operation definition). questionnaire; (xsd)name:string>
	 ( <valueAddress:Address>
		 | <valueAge:Age>
		 | <valueAnnotation:Annotation>
		 | <valueAttachment:Attachment>
		 | <valueBase64Binary:base64Binary>
		 | <valueBoolean:boolean>
		 | <valueCanonical:canonical>
		 | <valueCode:code>
		 | <valueCodeableConcept:CodeableConcept>
		 | <valueCoding:Coding>
		 | <valueContactDetail:ContactDetail>
		 | <valueContactPoint:ContactPoint>
		 | <valueContributor:Contributor>
		 | <valueCount:Count>
		 | <valueDataRequirement:DataRequirement>
		 | <valueDate:date>
		 | <valueDateTime:dateTime>
		 | <valueDecimal:decimal>
		 | <valueDistance:Distance>
		 | <valueDosage:Dosage>
		 | <valueDuration:Duration>
		 | <valueExpression:Expression>
		 | <valueHumanName:HumanName>
		 | <valueId:id>
		 | <valueIdentifier:Identifier>
		 | <valueInstant:instant>
		 | <valueInteger:integer>
		 | <valueMarkdown:markdown>
		 | <valueMeta:Meta>
		 | <valueMoney:Money>
		 | <valueOid:oid>
		 | <valueParameterDefinition:ParameterDefinition>
		 | <valuePeriod:Period>
		 | <valuePositiveInt:positiveInt>
		 | <valueQuantity:Quantity>
		 | <valueRange:Range>
		 | <valueRatio:Ratio>
		 | <valueRelatedArtifact:RelatedArtifact>
		 | <valueResource:Resource>
		 | <valueSampledData:SampledData>
		 | <valueSignature:Signature>
		 | <valueString:string>
		 | <valueTime:time>
		 | <valueTiming:Timing>
		 | <valueTriggerDefinition:TriggerDefinition>
		 | <valueUnsignedInt:unsignedInt>
		 | <valueUri:uri>
		 | <valueUrl:url>
		 | <valueUsageContext:UsageContext>
		 | <valueUuid:uuid>){0,0}
	 <  If the parameter is a whole resource. When resolving references in resources, the operation definition may specify how references may be resolved between parameters. If a reference cannot be resolved between the parameters, the application should fall back to it's general resource resolution methods.; (xsd)resource:Questionnaire>?
	 <  A named part of a multi-part parameter. Only one level of nested parameters is allowed.; (xsd)part:Parameters.parameter>{0,0}

🔗  Sets expectations for SDC-conformant systems around value set support for representing permitted question answers.sdc-codesystem(xsd)=
	 <#base:CodeSystem>
	 <  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.; (xsd)id:string>?
	 <  The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.; (xsd)meta:Meta>?
	 <  A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. 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. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.; (xsd)implicitRules:uri>?
	 <  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).; (xsd)language:code>?
	 <  A human-readable narrative that contains a summary of the resource and can 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. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied).  This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.; (xsd)text: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. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.; (xsd)contained:Resource>*
	[]<  May be used to represent additional information that is not part of the basic definition of the resource. 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 can 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.; (xsd)extension:Extension>*
	[]<  An Extension; (xsd)modifierExtension:Extension>*
	 <  An absolute URI that is used to identify this code system when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which at which an authoritative instance of this code system is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the code system is stored on different servers. This is used in [Coding](http://hl7.org/fhir/R4/datatypes.html#Coding).system. Can be a urn:uuid: or a urn:oid: but real http: addresses are preferred.  Multiple instances may share the same URL if they have a distinct version.

The determination of when to create a new version of a resource (same url, new version) vs. defining a new artifact is up to the author.  Considerations for making this decision are found in [Technical and Business Versions](http://hl7.org/fhir/R4/resource.html#versions). 

In some cases, the resource can no longer be found at the stated url, but the url itself cannot change. Implementations can use the [meta.source](http://hl7.org/fhir/R4/resource.html#meta) element to indicate where the current master source of the resource can be found.; (xsd)url:uri>?
	[]<  A formal identifier that is used to identify this code system when it is represented in other formats, or referenced in a specification, model, design or an instance. Typically, this is used for identifiers that can go in an HL7 V3 II (instance identifier) data type, and can then identify this code system outside of FHIR, where it is not possible to use the logical URI.  Note that HL7 defines at least three identifiers for many of its code systems - the FHIR canonical URL, the OID and the V2 Table 0396 mnemonic code.; (xsd)identifier:Identifier>*
	 <  The identifier that is used to identify this version of the code system when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the code system author and is not expected to be globally unique. For example, it might be a timestamp (e.g. yyyymmdd) if a managed version is not available. There is also no expectation that versions can be placed in a lexicographical sequence. This is used in [Coding](http://hl7.org/fhir/R4/datatypes.html#Coding).version. There may be different code system instances that have the same identifier but different versions.  The version can be appended to the url in a reference to allow a reference to a particular business version of the code system with the format [url]|[version].; (xsd)version:string>?
	 <  A natural language name identifying the code system. This name should be usable as an identifier for the module by machine processing applications such as code generation. The name is not expected to be globally unique. The name should be a simple alphanumeric type name to ensure that it is machine-processing friendly.; (xsd)name:string>?
	 <  A short, descriptive, user-friendly title for the code system. This name does not need to be machine-processing friendly and may contain punctuation, white-space, etc.; (xsd)title:string>?
	 <  The date (and optionally time) when the code system resource was created or revised. Allows filtering of code systems that are appropriate for use versus not.; (xsd)status:code>
	 <  A Boolean value to indicate that this code system is authored for testing purposes (or education/evaluation/marketing) and is not intended to be used for genuine usage. Allows filtering of code systems that are appropriate for use versus not.; (xsd)experimental:boolean>?
	 <  The date  (and optionally time) when the code system was published. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the code system changes. Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the code system. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource.; (xsd)date:dateTime>?
	 <  The name of the organization or individual that published the code system. Usually an organization but may be an individual. The publisher (or steward) of the code system is the organization or individual primarily responsible for the maintenance and upkeep of the code system. This is not necessarily the same individual or organization that developed and initially authored the content. The publisher is the primary point of contact for questions or issues with the code system. This item SHOULD be populated unless the information is available from context.; (xsd)publisher:string>?
	[]<  Contact details to assist a user in finding and communicating with the publisher. May be a web site, an email address, a telephone number, etc.; (xsd)contact:ContactDetail>*
	 <  A free text natural language description of the code system from a consumer's perspective. This description can be used to capture details such as why the code system was built, comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the code system as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context (e.g. the language of the code system is presumed to be the predominant language in the place the code system was created).; (xsd)description:markdown>?
	[]<  The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate code system instances. When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.; (xsd)useContext:UsageContext>*
	[]<  A legal or geographic region in which the code system is intended to be used. It may be possible for the code system to be used in jurisdictions other than those for which it was originally designed or intended.; (xsd)jurisdiction:CodeableConcept>*
	 <  Explanation of why this code system is needed and why it has been designed as it has. This element does not describe the usage of the code system. Instead, it provides traceability of ''why'' the resource is either needed or ''why'' it is defined as it is.  This may be used to point to source materials or specifications that drove the structure of this code system.; (xsd)purpose:markdown>?
	 <  A copyright statement relating to the code system and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the code system. ... Sometimes, the copyright differs between the code system and the codes that are included. The copyright statement should clearly differentiate between these when required.; (xsd)copyright:markdown>?
	 <  If code comparison is case sensitive when codes within this system are compared to each other. If this value is missing, then it is not specified whether a code system is case sensitive or not. When the rule is not known, Postel's law should be followed: produce codes with the correct case, and accept codes in any case. This element is primarily provided to support validation software.; (xsd)caseSensitive:boolean>
	 <  Canonical reference to the value set that contains the entire code system. The definition of the value set SHALL include all codes from this code system and only codes from this code system, and it SHALL be immutable.; (xsd)valueSet:canonical>?
	 <  The meaning of the hierarchy of concepts as represented in this resource. Note that other representations might have a different hierarchy or none at all, and represent the information using properties.; (xsd)hierarchyMeaning:code>?
	 <  The code system defines a compositional (post-coordination) grammar. Note that the code system resource does not define what the compositional grammar is, only whether or not there is one.; (xsd)compositional:boolean>{0,0}
	 <  This flag is used to signify that the code system does not commit to concept permanence across versions. If true, a version must be specified when referencing this code system. Best practice is that code systems do not redefine concepts, or that if concepts are redefined, a new code system definition is created. But this is not always possible, so some code systems may be defined as 'versionNeeded'.

Most code systems occasionally refine the displays defined for concepts between versions. Contexts in which the concept display values are validated may require that the version be specified for some code systems irrespective of the value of this property.; (xsd)versionNeeded:boolean>{0,0}
	 <  The extent of the content of the code system (the concepts and codes it defines) are represented in this resource instance.; (xsd)content:code>
	 <  The canonical URL of the code system that this code system supplement is adding designations and properties to. The most common use of a code system supplement is to add additional language support.; (xsd)supplements:canonical>?
	 <  The total number of concepts defined by the code system. Where the code system has a compositional grammar, the basis of this count is defined by the system steward. The count of concepts defined in this resource cannot be more than this value but may be less for several reasons - see the content element.; (xsd)count:unsignedInt>?
	[]<  A filter that can be used in a value set compose statement when selecting concepts using a filter. Note that filters defined in code systems usually require custom code on the part of any terminology engine that will make them available for use in value set filters. For this reason, they are generally only seen in high value published terminologies.; (xsd)filter:sdc-codesystem.filter>*
	[]<  A property defines an additional slot through which additional information can be provided about a concept.; (xsd)property:sdc-codesystem.property>*
	[]<  Concepts that are in the code system. The concept definitions are inherently hierarchical, but the definitions must be consulted to determine what the meanings of the hierarchical relationships are. If this is empty, it means that the code system resource does not represent the content of the code system.; (xsd)concept:sdc-codesystem.concept>*
	[]<  Indicates an extension that must be supported by the system presenting the instance for data capture or end-user consumption. If a system does not recognize the extension or cannot implement the functionality defined by the extension, it should display an error message or warning and refrain from presenting the instance to the user or using it when capturing data. This may point to extensions that control the appearance of data elements, control what value elements have, what elements are or are not available, what elements can or cannot be edited, or rules about how editing may occur. This extension does NOT apply when simply rendering a resource for publication purposes or for other purposes not intended for end-user data capture or data consumption.; (xsd)rendering-criticalExtension:sdc-rendering-criticalExtension>*

🔗  Concepts that are in the code system. The concept definitions are inherently hierarchical, but the definitions must be consulted to determine what the meanings of the hierarchical relationships are. If this is empty, it means that the code system resource does not represent the content of the code system.sdc-codesystem.concept(xsd)=
	 <#base:CodeSystem.concept>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  A code - a text symbol - that uniquely identifies the concept within the code system.; (xsd)code>
	 <  A human readable string that is the recommended default way to present this concept to a user.; (xsd)display:sdc-codesystem.concept.display>?
	 <  The formal definition of the concept. The code system resource does not make formal definitions required, because of the prevalence of legacy systems. However, they are highly recommended, as without them there is no formal meaning associated with the concept.; (xsd)definition:string>?
	[]<  Additional representations for the concept - other languages, aliases, specialized purposes, used for particular purposes, etc. Concepts have both a ```display``` and an array of ```designation```. The display is equivalent to a special designation with an implied ```designation.use``` of "primary code" and a language equal to the [Resource Language](http://hl7.org/fhir/R4/resource.html#language).; (xsd)designation:sdc-codesystem.concept.designation>*
	[]<  A property value for this concept.; (xsd)property:sdc-codesystem.concept.property>*
	[]<  Defines children of a concept to produce a hierarchy of concepts. The nature of the relationships is variable (is-a/contains/categorizes) - see hierarchyMeaning.; (xsd)concept:CodeSystem.concept>*

🔗  Additional representations for the concept - other languages, aliases, specialized purposes, used for particular purposes, etc. Concepts have both a ```display``` and an array of ```designation```. The display is equivalent to a special designation with an implied ```designation.use``` of "primary code" and a language equal to the [Resource Language](http://hl7.org/fhir/R4/resource.html#language).sdc-codesystem.concept.designation(xsd)=
	 <#base:CodeSystem.concept.designation>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  The language this designation is defined for. In the absence of a language, the resource language applies.; (xsd)language:code>?
	 <  A code that details how this designation would be used. If no use is provided, the designation can be assumed to be suitable for general display to a human user.; (xsd)use:Coding>?
	 <  The text value for this designation.; (xsd)value:sdc-codesystem.concept.designation.value>

🔗  The text value for this designation.sdc-codesystem.concept.designation.value(xsd)=
	 <#base:string>
	 <  unique id for the element within a resource (for internal references); (xsd)id:string>?
	[]<  An Extension; (xsd)extension:Extension>*
	 <  The actual value; (xsd)value:string>?
	 <  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.

For questionnaires, see additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/rendering.html#rendering-style).; (xsd)conceptDisplayLabel-renderingStyle:rendering-style>?
	 <  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. Existing [restrictions on XHTML content](http://hl7.org/fhir/R4/narrative.html#security) apply. Note that using [markdown](http://hl7.org/fhir/extensions/5.1.0StructureDefinition-rendering-markdown.html) allows for greater flexibility of display. For questionnaires, see additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/rendering.html#rendering-xhtml).; (xsd)conceptDisplayLabel-xhtml:rendering-xhtml>?

🔗  A human readable string that is the recommended default way to present this concept to a user.sdc-codesystem.concept.display(xsd)=
	 <#base:string>
	 <  unique id for the element within a resource (for internal references); (xsd)id:string>?
	[]<  An Extension; (xsd)extension:Extension>*
	 <  The actual value; (xsd)value:string>?
	 <  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.

For questionnaires, see additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/rendering.html#rendering-style).; (xsd)conceptDisplayLabel-renderingStyle:rendering-style>?
	 <  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. Existing [restrictions on XHTML content](http://hl7.org/fhir/R4/narrative.html#security) apply. Note that using [markdown](http://hl7.org/fhir/extensions/5.1.0StructureDefinition-rendering-markdown.html) allows for greater flexibility of display. For questionnaires, see additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/rendering.html#rendering-xhtml).; (xsd)conceptDisplayLabel-xhtml:rendering-xhtml>?

🔗  A property value for this concept.sdc-codesystem.concept.property(xsd)=
	 <#base:CodeSystem.concept.property>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  A code that is a reference to CodeSystem.property.code.; (xsd)code>
	 ( <valueBoolean:boolean>
		 | <valueCode:code>
		 | <valueCoding:Coding>
		 | <valueDateTime:dateTime>
		 | <valueDecimal:decimal>
		 | <valueInteger:integer>
		 | <valueString:string>)

🔗  A filter that can be used in a value set compose statement when selecting concepts using a filter. Note that filters defined in code systems usually require custom code on the part of any terminology engine that will make them available for use in value set filters. For this reason, they are generally only seen in high value published terminologies.sdc-codesystem.filter(xsd)=
	 <#base:CodeSystem.filter>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  The code that identifies this filter when it is used as a filter in [ValueSet](http://hl7.org/fhir/R4/valueset.html#).compose.include.filter.; (xsd)code>
	 <  A description of how or why the filter is used.; (xsd)description:string>?
	[]<  A list of operators that can be used with the filter.; (xsd)operator:code>+
	 <  A description of what the value for the filter should be.; (xsd)value:string>

🔗  A property defines an additional slot through which additional information can be provided about a concept.sdc-codesystem.property(xsd)=
	 <#base:CodeSystem.property>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  A code that is used to identify the property. The code is used internally (in CodeSystem.concept.property.code) and also externally, such as in property filters.; (xsd)code>
	 <  Reference to the formal meaning of the property. One possible source of meaning is the [Concept Properties](http://hl7.org/fhir/R4/codesystem-concept-properties.html) code system.; (xsd)uri>?
	 <  A description of the property- why it is defined, and how its value might be used.; (xsd)description:string>?
	 <  The type of the property value. Properties of type "code" contain a code defined by the code system (e.g. a reference to another defined concept).; (xsd)type:code>

🔗  Sets expectations for SDC-conformant systems around use of libraries.sdc-library(xsd)=
	 <#base:cqllibrary>
	 <  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.; (xsd)id:string>?
	 <  The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.; (xsd)meta:Meta>?
	 <  A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. 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. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.; (xsd)implicitRules:uri>?
	 <  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).; (xsd)language:code>?
	 <  A human-readable narrative that contains a summary of the resource and can 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. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied).  This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.; (xsd)text: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. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.; (xsd)contained:Resource>*
	[]<  May be used to represent additional information that is not part of the basic definition of the resource. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  An absolute URI that is used to identify this library when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which at which an authoritative instance of this library is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the library is stored on different servers. Can be a urn:uuid: or a urn:oid: but real http: addresses are preferred.  Multiple instances may share the same URL if they have a distinct version.

The determination of when to create a new version of a resource (same url, new version) vs. defining a new artifact is up to the author.  Considerations for making this decision are found in [Technical and Business Versions](http://hl7.org/fhir/resource.html#versions). 

In some cases, the resource can no longer be found at the stated url, but the url itself cannot change. Implementations can use the [meta.source](http://hl7.org/fhir/resource.html#meta) element to indicate where the current master source of the resource can be found.; (xsd)url:uri>?
	[]<  A formal identifier that is used to identify this library when it is represented in other formats, or referenced in a specification, model, design or an instance. e.g. CMS or NQF identifiers for a measure artifact. Note that at least one identifier is required for non-experimental active artifacts. Typically, this is used for identifiers that can go in an HL7 V3 II (instance identifier) data type, and can then identify this library outside of FHIR, where it is not possible to use the logical URI.; (xsd)identifier:Identifier>*
	 <  The identifier that is used to identify this version of the library when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the library author and is not expected to be globally unique. For example, it might be a timestamp (e.g. yyyymmdd) if a managed version is not available. There is also no expectation that versions can be placed in a lexicographical sequence. To provide a version consistent with the Decision Support Service specification, use the format Major.Minor.Revision (e.g. 1.0.0). For more information on versioning knowledge assets, refer to the Decision Support Service specification. Note that a version is required for non-experimental active artifacts. There may be different library instances that have the same identifier but different versions.  The version can be appended to the url in a reference to allow a reference to a particular business version of the library with the format [url]|[version].; (xsd)version:string>?
	 <  A natural language name identifying the library. This name should be usable as an identifier for the module by machine processing applications such as code generation. The name is not expected to be globally unique. The name should be a simple alphanumeric type name to ensure that it is machine-processing friendly.; (xsd)name:string>?
	 <  A short, descriptive, user-friendly title for the library. This name does not need to be machine-processing friendly and may contain punctuation, white-space, etc.; (xsd)title:string>?
	 <  An explanatory or alternate title for the library giving additional information about its content.; (xsd)subtitle:string>?
	 <  The status of this library. Enables tracking the life-cycle of the content. Allows filtering of libraries that are appropriate for use vs. not.; (xsd)status:code>
	 <  A Boolean value to indicate that this library is authored for testing purposes (or education/evaluation/marketing) and is not intended to be used for genuine usage. Allows filtering of librarys that are appropriate for use versus not.; (xsd)experimental:boolean>?
	 <  Identifies the type of library such as a Logic Library, Model Definition, Asset Collection, or Module Definition. http://terminology.hl7.org/CodeSystem/library-type, logic-library, Logic Library; (xsd)type:CodeableConcept>
	 <  A code or group definition that describes the intended subject of the contents of the library.; (xsd)subject:( <CodeableConcept>
		 | <Group>)>?
	 <  The date  (and optionally time) when the library was published. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the library changes. Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the library. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource.; (xsd)date:dateTime>?
	 <  The name of the organization or individual that published the library. Usually an organization but may be an individual. The publisher (or steward) of the library is the organization or individual primarily responsible for the maintenance and upkeep of the library. This is not necessarily the same individual or organization that developed and initially authored the content. The publisher is the primary point of contact for questions or issues with the library. This item SHOULD be populated unless the information is available from context.; (xsd)publisher:string>?
	[]<  Contact details to assist a user in finding and communicating with the publisher. May be a web site, an email address, a telephone number, etc.; (xsd)contact:ContactDetail>*
	 <  A free text natural language description of the library from a consumer's perspective. This description can be used to capture details such as why the library was built, comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the library as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context (e.g. the language of the library is presumed to be the predominant language in the place the library was created).; (xsd)description:markdown>?
	[]<  The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate library instances. When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.; (xsd)useContext:UsageContext>*
	[]<  A legal or geographic region in which the library is intended to be used. It may be possible for the library to be used in jurisdictions other than those for which it was originally designed or intended.; (xsd)jurisdiction:CodeableConcept>*
	 <  Explanation of why this library is needed and why it has been designed as it has. This element does not describe the usage of the library. Instead, it provides traceability of ''why'' the resource is either needed or ''why'' it is defined as it is.  This may be used to point to source materials or specifications that drove the structure of this library.; (xsd)purpose:markdown>?
	 <  A detailed description of how the library is used from a clinical perspective.; (xsd)usage:string>?
	 <  A copyright statement relating to the library and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the library.; (xsd)copyright:markdown>?
	 <  The date on which the resource content was approved by the publisher. Approval happens once when the content is officially approved for usage. The 'date' element may be more recent than the approval date because of minor changes or editorial corrections.; (xsd)approvalDate:date>?
	 <  The date on which the resource content was last reviewed. Review happens periodically after approval but does not change the original approval date. If specified, this date follows the original approval date.; (xsd)lastReviewDate:date>?
	 <  The period during which the library content was or is planned to be in active use. The effective period for a library  determines when the content is applicable for usage and is independent of publication and review dates. For example, a measure intended to be used for the year 2016 might be published in 2015.; (xsd)effectivePeriod:Period>?
	[]<  Descriptive topics related to the content of the library. Topics provide a high-level categorization of the library that can be useful for filtering and searching.; (xsd)topic:CodeableConcept>*
	[]<  An individiual or organization primarily involved in the creation and maintenance of the content.; (xsd)author:ContactDetail>*
	[]<  An individual or organization primarily responsible for internal coherence of the content.; (xsd)editor:ContactDetail>*
	[]<  An individual or organization primarily responsible for review of some aspect of the content.; (xsd)reviewer:ContactDetail>*
	[]<  An individual or organization responsible for officially endorsing the content for use in some setting.; (xsd)endorser:ContactDetail>*
	[]<  Related artifacts such as additional documentation, justification, or bibliographic references. Each related artifact is either an attachment, or a reference to another resource, but not both.; (xsd)relatedArtifact:sdc-library.relatedArtifact>*
	[]<  The parameter element defines parameters used by the library.; (xsd)parameter:ParameterDefinition>*
	[]<  Describes a set of data that must be provided in order to be able to successfully perform the computations defined by the library.; (xsd)dataRequirement:DataRequirement>*
	[]<  The content of the library as an Attachment. The content may be a reference to a url, or may be directly embedded as a base-64 string. Either way, the contentType of the attachment determines how to interpret the content.; (xsd)content:Attachment>*
	 <  The CQL content represented as base-64 encoded data.; (xsd)cqlContent:sdc-library.cqlContent>?
	 <  The FHIRPath content represented as base-64 encoded data.; (xsd)fhirpathContent:sdc-library.fhirpathContent>?
	 <  The query content represented as base-64 encoded data.; (xsd)queryContent:sdc-library.queryContent>?

🔗  The CQL content represented as base-64 encoded data.sdc-library.cqlContent(xsd)=
	 <#base:Attachment>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	 <  Identifies the type of the data in the attachment and allows a method to be chosen to interpret or render the data. Includes mime type parameters such as charset where appropriate.; (xsd)contentType:code>
	 <  The human language of the content. The value can be any valid value according to BCP 47.; (xsd)language:code>?
	 <  The actual data of the attachment - a sequence of bytes, base64 encoded. The base64-encoded data SHALL be expressed in the same character set as the base resource XML or JSON.; (xsd)data:base64Binary>
	 <  A location where the data can be accessed. If both data and url are provided, the url SHALL point to the same content as the data contains. Urls may be relative references or may reference transient locations such as a wrapping envelope using cid: though this has ramifications for using signatures. Relative URLs are interpreted relative to the service url, like a resource reference, rather than relative to the resource itself. If a URL is provided, it SHALL resolve to actual data.; (xsd)url>?
	 <  The number of bytes of data that make up this attachment (before base64 encoding, if that is done). The number of bytes is redundant if the data is provided as a base64binary, but is useful if the data is provided as a url reference.; (xsd)size:unsignedInt>?
	 <  The calculated hash of the data using SHA-1. Represented using base64. The hash is calculated on the data prior to base64 encoding, if the data is based64 encoded. The hash is not intended to support digital signatures. Where protection against malicious threats a digital signature should be considered, see [Provenance.signature](http://hl7.org/fhir/R4/provenance-definitions.html#Provenance.signature) for mechanism to protect a resource with a digital signature.; (xsd)hash:base64Binary>?
	 <  A label or set of text to display in place of the data.; (xsd)title:string>?
	 <  The date that the attachment was first created.; (xsd)creation:dateTime>?

🔗  The FHIRPath content represented as base-64 encoded data.sdc-library.fhirpathContent(xsd)=
	 <#base:Attachment>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	 <  Identifies the type of the data in the attachment and allows a method to be chosen to interpret or render the data. Includes mime type parameters such as charset where appropriate.; (xsd)contentType:code>
	 <  The human language of the content. The value can be any valid value according to BCP 47.; (xsd)language:code>?
	 <  The actual data of the attachment - a sequence of bytes, base64 encoded. The base64-encoded data SHALL be expressed in the same character set as the base resource XML or JSON.; (xsd)data:base64Binary>
	 <  A location where the data can be accessed. If both data and url are provided, the url SHALL point to the same content as the data contains. Urls may be relative references or may reference transient locations such as a wrapping envelope using cid: though this has ramifications for using signatures. Relative URLs are interpreted relative to the service url, like a resource reference, rather than relative to the resource itself. If a URL is provided, it SHALL resolve to actual data.; (xsd)url>?
	 <  The number of bytes of data that make up this attachment (before base64 encoding, if that is done). The number of bytes is redundant if the data is provided as a base64binary, but is useful if the data is provided as a url reference.; (xsd)size:unsignedInt>?
	 <  The calculated hash of the data using SHA-1. Represented using base64. The hash is calculated on the data prior to base64 encoding, if the data is based64 encoded. The hash is not intended to support digital signatures. Where protection against malicious threats a digital signature should be considered, see [Provenance.signature](http://hl7.org/fhir/R4/provenance-definitions.html#Provenance.signature) for mechanism to protect a resource with a digital signature.; (xsd)hash:base64Binary>?
	 <  A label or set of text to display in place of the data.; (xsd)title:string>?
	 <  The date that the attachment was first created.; (xsd)creation:dateTime>?

🔗  The query content represented as base-64 encoded data.sdc-library.queryContent(xsd)=
	 <#base:Attachment>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	 <  Identifies the type of the data in the attachment and allows a method to be chosen to interpret or render the data. Includes mime type parameters such as charset where appropriate.; (xsd)contentType:code>
	 <  The human language of the content. The value can be any valid value according to BCP 47.; (xsd)language:code>?
	 <  The actual data of the attachment - a sequence of bytes, base64 encoded. The base64-encoded data SHALL be expressed in the same character set as the base resource XML or JSON.; (xsd)data:base64Binary>
	 <  A location where the data can be accessed. If both data and url are provided, the url SHALL point to the same content as the data contains. Urls may be relative references or may reference transient locations such as a wrapping envelope using cid: though this has ramifications for using signatures. Relative URLs are interpreted relative to the service url, like a resource reference, rather than relative to the resource itself. If a URL is provided, it SHALL resolve to actual data.; (xsd)url>?
	 <  The number of bytes of data that make up this attachment (before base64 encoding, if that is done). The number of bytes is redundant if the data is provided as a base64binary, but is useful if the data is provided as a url reference.; (xsd)size:unsignedInt>?
	 <  The calculated hash of the data using SHA-1. Represented using base64. The hash is calculated on the data prior to base64 encoding, if the data is based64 encoded. The hash is not intended to support digital signatures. Where protection against malicious threats a digital signature should be considered, see [Provenance.signature](http://hl7.org/fhir/R4/provenance-definitions.html#Provenance.signature) for mechanism to protect a resource with a digital signature.; (xsd)hash:base64Binary>?
	 <  A label or set of text to display in place of the data.; (xsd)title:string>?
	 <  The date that the attachment was first created.; (xsd)creation:dateTime>?

🔗  Related artifacts such as additional documentation, justification, or bibliographic references. Each related artifact is either an attachment, or a reference to another resource, but not both.sdc-library.relatedArtifact(xsd)=
	 <#base:RelatedArtifact>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	 <  The type of relationship to the related artifact.; (xsd)type:code>
	 <  A short label that can be used to reference the citation from elsewhere in the containing artifact, such as a footnote index.; (xsd)label:string>?
	 <  A brief description of the document or knowledge resource being referenced, suitable for display to a consumer.; (xsd)display:string>
	 <  A bibliographic citation for the related artifact. This text SHOULD be formatted according to an accepted citation format. Additional structured information about citations should be captured as extensions.; (xsd)citation:markdown>?
	 <  A url for the artifact that can be followed to access the actual content. If a document or resource element is present, this element SHALL NOT be provided (use the url or reference in the Attachment or resource reference).; (xsd)url>
	 <  The document being referenced, represented as an attachment. This is exclusive with the resource element.; (xsd)document:Attachment>?
	 <  The related resource, such as a library, value set, profile, or other knowledge resource. If the type is predecessor, this is a reference to the succeeding knowledge resource. If the type is successor, this is a reference to the prior knowledge resource.; (xsd)resource:canonical>?

🔗  A structured set of questions intended to guide the collection of answers from end-users. Questionnaires provide detailed control over order, presentation, phraseology and grouping to allow coherent, consistent data collection.sdc-questionnaire(xsd)=
	 <#base:sdc-questionnairecommon>
	 <  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.; (xsd)id:string>?
	 <  The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.; (xsd)meta:Meta>?
	 <  A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. 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. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.; (xsd)implicitRules:uri>?
	 <  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).; (xsd)language:code>?
	 <  A human-readable narrative that contains a summary of the resource and can 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. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied).  This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.; (xsd)text: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. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.; (xsd)contained:Resource>*
	[]<  An Extension; (xsd)extension:Extension>*
	[]<  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 and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  An absolute URI that is used to identify this questionnaire when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which at which an authoritative instance of this questionnaire is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the questionnaire is stored on different servers. The name of the referenced questionnaire can be conveyed using the http://hl7.org/fhir/StructureDefinition/display extension.; (xsd)url:uri>
	[]<  A formal identifier that is used to identify this questionnaire when it is represented in other formats, or referenced in a specification, model, design or an instance. Typically, this is used for identifiers that can go in an HL7 V3 II (instance identifier) data type, and can then identify this questionnaire outside of FHIR, where it is not possible to use the logical URI.; (xsd)identifier:Identifier>*
	 <  The identifier that is used to identify this version of the questionnaire when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the questionnaire author and is not expected to be globally unique. For example, it might be a timestamp (e.g. yyyymmdd) if a managed version is not available. There is also no expectation that versions can be placed in a lexicographical sequence. There may be different questionnaire instances that have the same identifier but different versions.  The version can be appended to the url in a reference to allow a reference to a particular business version of the questionnaire with the format [url]|[version].; (xsd)version:string>?
	 <  A natural language name identifying the questionnaire. This name should be usable as an identifier for the module by machine processing applications such as code generation. The name is not expected to be globally unique. The name should be a simple alphanumeric type name to ensure that it is machine-processing friendly.; (xsd)name:string>?
	 <  A short, descriptive, user-friendly title for the questionnaire. This name does not need to be machine-processing friendly and may contain punctuation, white-space, etc.; (xsd)title:string>?
	[]<  The URL of a Questionnaire that this Questionnaire is based on.; (xsd)derivedFrom:canonical>*
	 <  The status of this questionnaire. Enables tracking the life-cycle of the content. Allows filtering of questionnaires that are appropriate for use versus not.; (xsd)status:code>
	 <  A Boolean value to indicate that this questionnaire is authored for testing purposes (or education/evaluation/marketing) and is not intended to be used for genuine usage. Allows filtering of questionnaires that are appropriate for use versus not.; (xsd)experimental:boolean>?
	[]<  The types of subjects that can be the subject of responses created for the questionnaire. If none are specified, then the subject is unlimited.; (xsd)subjectType:code>*
	 <  The date  (and optionally time) when the questionnaire was published. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the questionnaire changes. Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the questionnaire. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource.; (xsd)date:dateTime>?
	 <  The name of the organization or individual that published the questionnaire. Usually an organization but may be an individual. The publisher (or steward) of the questionnaire is the organization or individual primarily responsible for the maintenance and upkeep of the questionnaire. This is not necessarily the same individual or organization that developed and initially authored the content. The publisher is the primary point of contact for questions or issues with the questionnaire. This item SHOULD be populated unless the information is available from context.; (xsd)publisher:string>?
	[]<  Contact details to assist a user in finding and communicating with the publisher. May be a web site, an email address, a telephone number, etc.; (xsd)contact:ContactDetail>*
	 <  A free text natural language description of the questionnaire from a consumer's perspective. This description can be used to capture details such as why the questionnaire was built, comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the questionnaire as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context (e.g. the language of the questionnaire is presumed to be the predominant language in the place the questionnaire was created).; (xsd)description:markdown>?
	[]<  The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate questionnaire instances. When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.; (xsd)useContext:UsageContext>*
	[]<  A legal or geographic region in which the questionnaire is intended to be used. It may be possible for the questionnaire to be used in jurisdictions other than those for which it was originally designed or intended.; (xsd)jurisdiction:CodeableConcept>*
	 <  Explanation of why this questionnaire is needed and why it has been designed as it has. This element does not describe the usage of the questionnaire. Instead, it provides traceability of ''why'' the resource is either needed or ''why'' it is defined as it is.  This may be used to point to source materials or specifications that drove the structure of this questionnaire.; (xsd)purpose:markdown>?
	 <  A copyright statement relating to the questionnaire and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the questionnaire.; (xsd)copyright:markdown>?
	 <  The date on which the resource content was approved by the publisher. Approval happens once when the content is officially approved for usage. The 'date' element may be more recent than the approval date because of minor changes or editorial corrections.; (xsd)approvalDate:date>?
	 <  The date on which the resource content was last reviewed. Review happens periodically after approval but does not change the original approval date. If specified, this date follows the original approval date.; (xsd)lastReviewDate:date>?
	 <  The period during which the questionnaire content was or is planned to be in active use. The effective period for a questionnaire  determines when the content is applicable for usage and is independent of publication and review dates. For example, a measure intended to be used for the year 2016 might be published in 2015.; (xsd)effectivePeriod:Period>?
	[]<  An identifier for this question or group of questions in a particular terminology such as LOINC.; (xsd)code:Coding>*
	[]<  A particular question, question grouping or display text that is part of the questionnaire. The content of the questionnaire is constructed from an ordered, hierarchical collection of items.; (xsd)item:sdc-questionnaire.item>*
	 <  Optional Extension Element - found in all resources.; (xsd)versionAlgorithm:Extension>?
	 <  Optional Extension Element - found in all resources.; (xsd)copyrightLabel:Extension>?
	 <  Information captured by the author/maintainer of the questionnaire for development purposes, not intended to be seen by users. Allows capture of todos, rationale for design decisions, etc.  It can also be used to capture comments about the completion of the form in general. Allows commentary to be captured during the process of answering a questionnaire (if not already supported by the form design) as well as after the form is completed. Comments are not part of the "data" of the form. If a form prompts for a comment, this should be captured in an answer, not in this element. Formal assessments of the QuestionnaireResponse would use [[[Observation]]].; (xsd)designNote>?
	[]<  Indicates the types of resources that can record answers to a Questionnaire. Open Issue: Should this extension be moved to core?; (xsd)performerType:sdc-questionnaire-performerType>*
	 <  If present, indicates that this questionnaire has expectations with respect to assembly.  Specifically, indicates whether this form requires assembly (i.e. it can't be used directly without invoking the [$assemble](OperationDefinition-Questionnaire-assemble.html) operation operation on it) and/or whether it is intended for use only as a 'child' in an assembly process.  The assembly processs might mean filling in item metadata based on information looked up from item.definitions and/or retrieving sub-questionnaires pointed to by [sub-questionnaire](StructureDefinition-sdc-questionnaire-subQuestionnaire.html) extensions. SDC-conformant Questionnaires **SHALL** declare this extension if they require an assembly process prior to use.  If not declared, then the Questionnaire is not necessarily safe for use as a child form and does not require assembly prior to use.; (xsd)assemble-expectation:sdc-questionnaire-assemble-expectation>?

🔗  A particular question, question grouping or display text that is part of the questionnaire. The content of the questionnaire is constructed from an ordered, hierarchical collection of items.sdc-questionnaire.item(xsd)=
	 <#base:Questionnaire.item>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  An Extension; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  An identifier that is unique within the Questionnaire allowing linkage to the equivalent item in a QuestionnaireResponse resource. This ''can'' be a meaningful identifier (e.g. a LOINC code) but is not intended to have any meaning.  GUIDs or sequential numbers are appropriate here.; (xsd)linkId:string>
	 <  This element is a URI that refers to an [ElementDefinition](http://hl7.org/fhir/R4/elementdefinition.html) that provides information about this item, including information that might otherwise be included in the instance of the Questionnaire resource. A detailed description of the construction of the URI is shown in Comments, below. If this element is present then the following element values MAY be derived from the Element Definition if the corresponding elements of this Questionnaire resource instance have no value:

* code (ElementDefinition.code) 
* type (ElementDefinition.type) 
* required (ElementDefinition.min) 
* repeats (ElementDefinition.max) 
* maxLength (ElementDefinition.maxLength) 
* answerValueSet (ElementDefinition.binding)
* options (ElementDefinition.binding). The uri refers to an ElementDefinition in a [StructureDefinition](http://hl7.org/fhir/R4/structuredefinition.html#) and always starts with the [canonical URL](http://hl7.org/fhir/R4/references.html#canonical) for the target resource. When referring to a StructureDefinition, a fragment identifier is used to specify the element definition by its id [Element.id](http://hl7.org/fhir/R4/element-definitions.html#Element.id). E.g. http://hl7.org/fhir/StructureDefinition/Observation#Observation.value[x]. In the absence of a fragment identifier, the first/root element definition in the target is the matching element definition.; (xsd)definition:uri>?
	[]<  A terminology code that corresponds to this group or question (e.g. a code from LOINC, which defines many questions and answers). The value may come from the ElementDefinition referred to by .definition.; (xsd)code:Coding>*
	 <  A short label for a particular group, question or set of display text within the questionnaire used for reference by the individual completing 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.  Typically, these won't be used for "display" items, though such use is not prohibited.  Systems SHOULD NOT generate their own prefixes if prefixes are defined for any items within a Questionnaire.; (xsd)prefix:string>?
	 <  The name of a section, the text of a question or text content for a display item. When using this element to represent the name of a section, use group type item and also make sure to limit the text element to a short string suitable for display as a section heading.  Group item instructions should be included as a display type item within the group.
This is optional only to support form assembly situations where the text may be generated from another source.  In an assembled Questionnaire, it should always be present.; (xsd)text:string>?
	 <  The type of questionnaire item this is - whether text for display, a grouping of other items or a particular type of data to be captured (string, integer, coded choice, etc.). Time is handled using "string".  File is handled using Attachment.  (Content can be sent as a contained binary).; (xsd)type:code>
	[]<  A constraint indicating that this item should only be enabled (displayed/allow answers to be captured) when the specified condition is true. If multiple repetitions of this extension are present, the item should be enabled when the condition for *any* of the repetitions is true.  I.e. treat "enableWhen"s as being joined by an "or" clause.  This element is a modifier because if enableWhen is present for an item, "required" is ignored unless one of the enableWhen conditions is met. When an item is disabled, all of its descendants are disabled, regardless of what their own enableWhen logic might evaluate to.; (xsd)enableWhen:sdc-questionnaire.item.enableWhen>*
	 <  Controls how multiple enableWhen values are interpreted -  whether all or any must be true. This element must be specified if more than one enableWhen value is provided.; (xsd)enableBehavior:code>?
	 <  An indication, if true, that the item must be present in a "completed" QuestionnaireResponse.  If false, the item may be skipped when answering the questionnaire. Questionnaire.item.required only has meaning for elements that are conditionally enabled with enableWhen if the condition evaluates to true.  If an item that contains other items is marked as required, that does not automatically make the contained elements required (though required groups must contain at least one child element). The value may come from the ElementDefinition referred to by .definition.; (xsd)required:boolean>?
	 <  An indication, if true, that a QuestionnaireResponse for this item may include multiple answers associated with a single instance of this item (for question-type items) or multiple repetitions of the item (for group-type items) If a question is marked as repeats=true, then multiple answers can be provided for the question in the corresponding QuestionnaireResponse.  When rendering the questionnaire, it is up to the rendering software whether to render the question text for each answer repetition (i.e. "repeat the question") or to simply allow entry/selection of multiple answers for the question (repeat the answers).  Which is most appropriate visually may depend on the type of answer as well as whether there are nested items.

The resulting QuestionnaireResponse will be populated the same way regardless of rendering - one 'question' item with multiple answer values.

 The value may come from the ElementDefinition referred to by .definition.; (xsd)repeats:boolean>?
	 <  An indication, when true, that the value cannot be changed by a human respondent 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.; (xsd)readOnly:boolean>?
	 <  The maximum number of characters that are permitted in the answer to be considered a "valid" QuestionnaireResponse. For base64binary, reflects the number of characters representing the encoded data, not the number of bytes of the binary data. The value may come from the ElementDefinition referred to by .definition.; (xsd)maxLength:integer>?
	 <  A reference to a value set containing a list of codes representing permitted answers for a "choice" or "open-choice" question. LOINC defines many useful value sets for questionnaire responses. See [LOINC Answer Lists](http://hl7.org/fhir/R4/loinc.html#alist). The value may come from the ElementDefinition referred to by .definition.; (xsd)answerValueSet:canonical>?
	[]<  One of the permitted answers for a "choice" or "open-choice" question. This element can be used when the value set machinery of answerValueSet is deemed too cumbersome or when there's a need to capture possible answers that are not codes.; (xsd)answerOption:sdc-questionnaire.item.answerOption>*
	[]<  One or more values that should be pre-populated in the answer when initially rendering the questionnaire for user input. The user is allowed to change the value and override the default (unless marked as read-only). If the user doesn't change the value, then this initial value will be persisted when the QuestionnaireResponse is initially created.  Note that initial values can influence results.  The data type of initial[x] must agree with the item.type, and only repeating items can have more then one initial value.; (xsd)initial:sdc-questionnaire.item.initial>*
	[]<  Text, questions and other groups to be nested beneath a question or group. There is no specified limit to the depth of nesting.  However, Questionnaire authors are encouraged to consider the impact on the user and user interface of overly deep nesting.; (xsd)item:Questionnaire.item>*
	 <  If true, indicates that the extended item should not be displayed to the user. If an item is hidden, all descendant items are hidden as well.  See additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/rendering.html#hidden).; (xsd)hidden:questionnaire-hidden>?
	 <  Optional Extension Element - found in all resources.; (xsd)answerConstraint:Extension>?
	 <  Information captured by the author/maintainer of the questionnaire for development purposes, not intended to be seen by users. Allows capture of todos, rationale for design decisions, etc.  It can also be used to capture comments about specific groups or questions within it. Allows commentary to be captured during the process of answering a questionnaire (if not already supported by the form design) as well as after the form is completed. Comments are not part of the "data" of the form. If a form prompts for a comment, this should be captured in an answer, not in this element. Formal assessments of the QuestionnaireResponse would use [[[Observation]]].; (xsd)designNote>?
	 <  This extension is used when defining high-level questionnaires that will then be used as a basis for 'derived' Questionnaires that are further refined for use in specific organizations or contexts.  If the extension is present and set to 'true', it means that this item should be considered to be 'optional' from an adaptation perspective and that the question can be removed (i.e. not displayed) in derived questionnaires without impacting the validity of the instrument.  Alternatively, the element can be marked as 'hidden' and 'readOnly' and have a value or descendant item values declared using initialValue or initialExpression.  If the element with 'optionalDisplay=true' is marked as 'required=true', then this second approach is the only means to exclude the element from display. 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.; (xsd)itemOptionalDisplay:sdc-questionnaire-optionalDisplay>?

🔗  One of the permitted answers for a "choice" or "open-choice" question. This element can be used when the value set machinery of answerValueSet is deemed too cumbersome or when there's a need to capture possible answers that are not codes.sdc-questionnaire.item.answerOption(xsd)=
	 <#base:Questionnaire.item.answerOption>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 ( <valueCoding:Coding>
		 | <valueDate:date>
		 | <valueInteger:integer>
		 | <valueResource:Resource>
		 | <valueString:string>
		 | <valueTime:time>)
	 <  Indicates whether the answer value is selected when the list of possible answers is initially shown. Use this instead of initial[v] if answerValueSet is present.; (xsd)initialSelected:boolean>?

🔗  A constraint indicating that this item should only be enabled (displayed/allow answers to be captured) when the specified condition is true. If multiple repetitions of this extension are present, the item should be enabled when the condition for *any* of the repetitions is true.  I.e. treat "enableWhen"s as being joined by an "or" clause.  This element is a modifier because if enableWhen is present for an item, "required" is ignored unless one of the enableWhen conditions is met. When an item is disabled, all of its descendants are disabled, regardless of what their own enableWhen logic might evaluate to.sdc-questionnaire.item.enableWhen(xsd)=
	 <#base:Questionnaire.item.enableWhen>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  The linkId for the question whose answer (or lack of answer) governs whether this item is enabled. If multiple question occurrences are present for the same question (same linkId), then this refers to the nearest question occurrence reachable by tracing first the "ancestor" axis and then the "preceding" axis and then the "following" axis.; (xsd)question:string>
	 <  Specifies the criteria by which the question is enabled.; (xsd)operator:code>
	 <  A value that the referenced question is tested using the specified operator in order for the item to be enabled.; (xsd)answer:( <boolean>
		 | <Coding>
		 | <date>
		 | <dateTime>
		 | <decimal>
		 | <integer>
		 | <Quantity>
		 | <Resource>
		 | <string>
		 | <time>)>

🔗  One or more values that should be pre-populated in the answer when initially rendering the questionnaire for user input. The user is allowed to change the value and override the default (unless marked as read-only). If the user doesn't change the value, then this initial value will be persisted when the QuestionnaireResponse is initially created.  Note that initial values can influence results.  The data type of initial[x] must agree with the item.type, and only repeating items can have more then one initial value.sdc-questionnaire.item.initial(xsd)=
	 <#base:Questionnaire.item.initial>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 ( <valueAttachment:Attachment>
		 | <valueBoolean:boolean>
		 | <valueCoding:Coding>
		 | <valueDate:date>
		 | <valueDateTime:dateTime>
		 | <valueDecimal:decimal>
		 | <valueInteger:integer>
		 | <valueQuantity:Quantity>
		 | <valueResource:Resource>
		 | <valueString:string>
		 | <valueTime:time>
		 | <valueUri:uri>)

🔗  Defines the metadata that should be present when embedding a adaptive Questionnaire as part of a QuestionnaireResponse.sdc-questionnaire-adapt(xsd)=
	 <#base:sdc-questionnairecommon>
	 <  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.; (xsd)id:string>?
	 <  The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.; (xsd)meta:Meta>?
	 <  A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. 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. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.; (xsd)implicitRules:uri>?
	 <  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).; (xsd)language:code>?
	 <  A human-readable narrative that contains a summary of the resource and can 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. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied).  This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.; (xsd)text: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. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.; (xsd)contained:Resource>*
	[]<  An Extension This extension isn't essential because the fact the Questionnaire is adaptive can be inferred from the style, however it may still be useful to assert explicitly, and perhaps to know what servers are useable if amending the form is necessary; (xsd)extension:Extension>*
	[]<  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 and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  An absolute URI that is used to identify this questionnaire when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which at which an authoritative instance of this questionnaire is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the questionnaire is stored on different servers. The name of the referenced questionnaire can be conveyed using the http://hl7.org/fhir/StructureDefinition/display extension.; (xsd)url:uri>{0,0}
	[]<  A formal identifier that is used to identify this questionnaire when it is represented in other formats, or referenced in a specification, model, design or an instance. Typically, this is used for identifiers that can go in an HL7 V3 II (instance identifier) data type, and can then identify this questionnaire outside of FHIR, where it is not possible to use the logical URI.; (xsd)identifier:Identifier>*
	 <  The identifier that is used to identify this version of the questionnaire when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the questionnaire author and is not expected to be globally unique. For example, it might be a timestamp (e.g. yyyymmdd) if a managed version is not available. There is also no expectation that versions can be placed in a lexicographical sequence. There may be different questionnaire instances that have the same identifier but different versions.  The version can be appended to the url in a reference to allow a reference to a particular business version of the questionnaire with the format [url]|[version].; (xsd)version:string>{0,0}
	 <  A natural language name identifying the questionnaire. This name should be usable as an identifier for the module by machine processing applications such as code generation. The name is not expected to be globally unique. The name should be a simple alphanumeric type name to ensure that it is machine-processing friendly.; (xsd)name:string>?
	 <  A short, descriptive, user-friendly title for the questionnaire. This name does not need to be machine-processing friendly and may contain punctuation, white-space, etc.; (xsd)title:string>?
	 <  The URL of a Questionnaire that this Questionnaire is based on. For this profile, there must be exactly one Questionnaire which is the base Questionnaire the 'adaptive' QuestionnaireResponse completion was executed against.; (xsd)derivedFrom:canonical>
	 <  The status of this questionnaire. Enables tracking the life-cycle of the content. Allows filtering of questionnaires that are appropriate for use versus not.; (xsd)status:code>
	 <  A Boolean value to indicate that this questionnaire is authored for testing purposes (or education/evaluation/marketing) and is not intended to be used for genuine usage. Allows filtering of questionnaires that are appropriate for use versus not.; (xsd)experimental:boolean>?
	[]<  The types of subjects that can be the subject of responses created for the questionnaire. If none are specified, then the subject is unlimited.; (xsd)subjectType:code>*
	 <  The date  (and optionally time) when the questionnaire was published. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the questionnaire changes. Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the questionnaire. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource.; (xsd)date:dateTime>?
	 <  The name of the organization or individual that published the questionnaire. Usually an organization but may be an individual. The publisher (or steward) of the questionnaire is the organization or individual primarily responsible for the maintenance and upkeep of the questionnaire. This is not necessarily the same individual or organization that developed and initially authored the content. The publisher is the primary point of contact for questions or issues with the questionnaire. This item SHOULD be populated unless the information is available from context.; (xsd)publisher:string>?
	[]<  Contact details to assist a user in finding and communicating with the publisher. May be a web site, an email address, a telephone number, etc.; (xsd)contact:ContactDetail>*
	 <  A free text natural language description of the questionnaire from a consumer's perspective. This description can be used to capture details such as why the questionnaire was built, comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the questionnaire as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context (e.g. the language of the questionnaire is presumed to be the predominant language in the place the questionnaire was created).; (xsd)description:markdown>?
	[]<  The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate questionnaire instances. When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.; (xsd)useContext:UsageContext>*
	[]<  A legal or geographic region in which the questionnaire is intended to be used. It may be possible for the questionnaire to be used in jurisdictions other than those for which it was originally designed or intended.; (xsd)jurisdiction:CodeableConcept>*
	 <  Explanation of why this questionnaire is needed and why it has been designed as it has. This element does not describe the usage of the questionnaire. Instead, it provides traceability of ''why'' the resource is either needed or ''why'' it is defined as it is.  This may be used to point to source materials or specifications that drove the structure of this questionnaire.; (xsd)purpose:markdown>?
	 <  A copyright statement relating to the questionnaire and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the questionnaire.; (xsd)copyright:markdown>?
	 <  The date on which the resource content was approved by the publisher. Approval happens once when the content is officially approved for usage. The 'date' element may be more recent than the approval date because of minor changes or editorial corrections.; (xsd)approvalDate:date>?
	 <  The date on which the resource content was last reviewed. Review happens periodically after approval but does not change the original approval date. If specified, this date follows the original approval date.; (xsd)lastReviewDate:date>?
	 <  The period during which the questionnaire content was or is planned to be in active use. The effective period for a questionnaire  determines when the content is applicable for usage and is independent of publication and review dates. For example, a measure intended to be used for the year 2016 might be published in 2015.; (xsd)effectivePeriod:Period>?
	[]<  An identifier for this question or group of questions in a particular terminology such as LOINC.; (xsd)code:Coding>*
	[]<  A particular question, question grouping or display text that is part of the questionnaire. The content of the questionnaire is constructed from an ordered, hierarchical collection of items.; (xsd)item:sdc-questionnaire-adapt.item>*
	 <  Optional Extension Element - found in all resources.; (xsd)versionAlgorithm:Extension>?
	 <  Optional Extension Element - found in all resources.; (xsd)copyrightLabel:Extension>?
	[]<  Marks a questionnaire as being adaptive.  Value can either be a boolean (if true, indicates adaptive) or a URL for the base URL of a server that can perform the nextQuestion operation for this particular questionnaire. There can only be one in a questionnaire if the value used is boolean.; (xsd)questionnaireAdaptive:sdc-questionnaire-questionnaireAdaptive>*

🔗  A particular question, question grouping or display text that is part of the questionnaire. The content of the questionnaire is constructed from an ordered, hierarchical collection of items.sdc-questionnaire-adapt.item(xsd)=
	 <#base:Questionnaire.item>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  An Extension; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  An identifier that is unique within the Questionnaire allowing linkage to the equivalent item in a QuestionnaireResponse resource. This ''can'' be a meaningful identifier (e.g. a LOINC code) but is not intended to have any meaning.  GUIDs or sequential numbers are appropriate here.; (xsd)linkId:string>
	 <  This element is a URI that refers to an [ElementDefinition](http://hl7.org/fhir/R4/elementdefinition.html) that provides information about this item, including information that might otherwise be included in the instance of the Questionnaire resource. A detailed description of the construction of the URI is shown in Comments, below. If this element is present then the following element values MAY be derived from the Element Definition if the corresponding elements of this Questionnaire resource instance have no value:

* code (ElementDefinition.code) 
* type (ElementDefinition.type) 
* required (ElementDefinition.min) 
* repeats (ElementDefinition.max) 
* maxLength (ElementDefinition.maxLength) 
* answerValueSet (ElementDefinition.binding)
* options (ElementDefinition.binding). The uri refers to an ElementDefinition in a [StructureDefinition](http://hl7.org/fhir/R4/structuredefinition.html#) and always starts with the [canonical URL](http://hl7.org/fhir/R4/references.html#canonical) for the target resource. When referring to a StructureDefinition, a fragment identifier is used to specify the element definition by its id [Element.id](http://hl7.org/fhir/R4/element-definitions.html#Element.id). E.g. http://hl7.org/fhir/StructureDefinition/Observation#Observation.value[x]. In the absence of a fragment identifier, the first/root element definition in the target is the matching element definition.; (xsd)definition:uri>?
	[]<  A terminology code that corresponds to this group or question (e.g. a code from LOINC, which defines many questions and answers). The value may come from the ElementDefinition referred to by .definition.; (xsd)code:Coding>*
	 <  A short label for a particular group, question or set of display text within the questionnaire used for reference by the individual completing 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.  Typically, these won't be used for "display" items, though such use is not prohibited.  Systems SHOULD NOT generate their own prefixes if prefixes are defined for any items within a Questionnaire.; (xsd)prefix:string>?
	 <  The name of a section, the text of a question or text content for a display item. When using this element to represent the name of a section, use group type item and also make sure to limit the text element to a short string suitable for display as a section heading.  Group item instructions should be included as a display type item within the group.; (xsd)text:string>
	 <  The type of questionnaire item this is - whether text for display, a grouping of other items or a particular type of data to be captured (string, integer, coded choice, etc.). Time is handled using "string".  File is handled using Attachment.  (Content can be sent as a contained binary).; (xsd)type:code>
	[]<  A constraint indicating that this item should only be enabled (displayed/allow answers to be captured) when the specified condition is true. If multiple repetitions of this extension are present, the item should be enabled when the condition for *any* of the repetitions is true.  I.e. treat "enableWhen"s as being joined by an "or" clause.  This element is a modifier because if enableWhen is present for an item, "required" is ignored unless one of the enableWhen conditions is met. When an item is disabled, all of its descendants are disabled, regardless of what their own enableWhen logic might evaluate to.; (xsd)enableWhen:sdc-questionnaire-adapt.item.enableWhen>*
	 <  Controls how multiple enableWhen values are interpreted -  whether all or any must be true. This element must be specified if more than one enableWhen value is provided.; (xsd)enableBehavior:code>?
	 <  An indication, if true, that the item must be present in a "completed" QuestionnaireResponse.  If false, the item may be skipped when answering the questionnaire. Questionnaire.item.required only has meaning for elements that are conditionally enabled with enableWhen if the condition evaluates to true.  If an item that contains other items is marked as required, that does not automatically make the contained elements required (though required groups must contain at least one child element). The value may come from the ElementDefinition referred to by .definition.; (xsd)required:boolean>?
	 <  An indication, if true, that a QuestionnaireResponse for this item may include multiple answers associated with a single instance of this item (for question-type items) or multiple repetitions of the item (for group-type items) If a question is marked as repeats=true, then multiple answers can be provided for the question in the corresponding QuestionnaireResponse.  When rendering the questionnaire, it is up to the rendering software whether to render the question text for each answer repetition (i.e. "repeat the question") or to simply allow entry/selection of multiple answers for the question (repeat the answers).  Which is most appropriate visually may depend on the type of answer as well as whether there are nested items.

The resulting QuestionnaireResponse will be populated the same way regardless of rendering - one 'question' item with multiple answer values.

 The value may come from the ElementDefinition referred to by .definition.; (xsd)repeats:boolean>?
	 <  An indication, when true, that the value cannot be changed by a human respondent 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.; (xsd)readOnly:boolean>?
	 <  The maximum number of characters that are permitted in the answer to be considered a "valid" QuestionnaireResponse. For base64binary, reflects the number of characters representing the encoded data, not the number of bytes of the binary data. The value may come from the ElementDefinition referred to by .definition.; (xsd)maxLength:integer>?
	 <  A reference to a value set containing a list of codes representing permitted answers for a "choice" or "open-choice" question. LOINC defines many useful value sets for questionnaire responses. See [LOINC Answer Lists](http://hl7.org/fhir/R4/loinc.html#alist). The value may come from the ElementDefinition referred to by .definition.; (xsd)answerValueSet:canonical>?
	[]<  One of the permitted answers for a "choice" or "open-choice" question. This element can be used when the value set machinery of answerValueSet is deemed too cumbersome or when there's a need to capture possible answers that are not codes.; (xsd)answerOption:sdc-questionnaire-adapt.item.answerOption>*
	[]<  One or more values that should be pre-populated in the answer when initially rendering the questionnaire for user input. The user is allowed to change the value and override the default (unless marked as read-only). If the user doesn't change the value, then this initial value will be persisted when the QuestionnaireResponse is initially created.  Note that initial values can influence results.  The data type of initial[x] must agree with the item.type, and only repeating items can have more then one initial value.; (xsd)initial:sdc-questionnaire-adapt.item.initial>*
	[]<  Text, questions and other groups to be nested beneath a question or group. There is no specified limit to the depth of nesting.  However, Questionnaire authors are encouraged to consider the impact on the user and user interface of overly deep nesting.; (xsd)item:Questionnaire.item>*
	 <  If true, indicates that the extended item should not be displayed to the user. If an item is hidden, all descendant items are hidden as well.  See additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/rendering.html#hidden).; (xsd)hidden:questionnaire-hidden>?
	 <  Optional Extension Element - found in all resources.; (xsd)answerConstraint:Extension>?

🔗  One of the permitted answers for a "choice" or "open-choice" question. This element can be used when the value set machinery of answerValueSet is deemed too cumbersome or when there's a need to capture possible answers that are not codes.sdc-questionnaire-adapt.item.answerOption(xsd)=
	 <#base:Questionnaire.item.answerOption>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 ( <valueCoding:Coding>
		 | <valueDate:date>
		 | <valueInteger:integer>
		 | <valueResource:Resource>
		 | <valueString:string>
		 | <valueTime:time>)
	 <  Indicates whether the answer value is selected when the list of possible answers is initially shown. Use this instead of initial[v] if answerValueSet is present.; (xsd)initialSelected:boolean>?

🔗  A constraint indicating that this item should only be enabled (displayed/allow answers to be captured) when the specified condition is true. If multiple repetitions of this extension are present, the item should be enabled when the condition for *any* of the repetitions is true.  I.e. treat "enableWhen"s as being joined by an "or" clause.  This element is a modifier because if enableWhen is present for an item, "required" is ignored unless one of the enableWhen conditions is met. When an item is disabled, all of its descendants are disabled, regardless of what their own enableWhen logic might evaluate to.sdc-questionnaire-adapt.item.enableWhen(xsd)=
	 <#base:Questionnaire.item.enableWhen>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  The linkId for the question whose answer (or lack of answer) governs whether this item is enabled. If multiple question occurrences are present for the same question (same linkId), then this refers to the nearest question occurrence reachable by tracing first the "ancestor" axis and then the "preceding" axis and then the "following" axis.; (xsd)question:string>
	 <  Specifies the criteria by which the question is enabled.; (xsd)operator:code>
	 <  A value that the referenced question is tested using the specified operator in order for the item to be enabled.; (xsd)answer:( <boolean>
		 | <Coding>
		 | <date>
		 | <dateTime>
		 | <decimal>
		 | <integer>
		 | <Quantity>
		 | <Resource>
		 | <string>
		 | <time>)>

🔗  One or more values that should be pre-populated in the answer when initially rendering the questionnaire for user input. The user is allowed to change the value and override the default (unless marked as read-only). If the user doesn't change the value, then this initial value will be persisted when the QuestionnaireResponse is initially created.  Note that initial values can influence results.  The data type of initial[x] must agree with the item.type, and only repeating items can have more then one initial value.sdc-questionnaire-adapt.item.initial(xsd)=
	 <#base:Questionnaire.item.initial>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 ( <valueAttachment:Attachment>
		 | <valueBoolean:boolean>
		 | <valueCoding:Coding>
		 | <valueDate:date>
		 | <valueDateTime:dateTime>
		 | <valueDecimal:decimal>
		 | <valueInteger:integer>
		 | <valueQuantity:Quantity>
		 | <valueResource:Resource>
		 | <valueString:string>
		 | <valueTime:time>
		 | <valueUri:uri>)

🔗  Describes the elements that should be exposed in a response to a search for adaptive questionnaires.sdc-questionnaire-adapt-srch(xsd)=
	 <#base:sdc-questionnaire-search>
	 <  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.; (xsd)id:string>?
	 <  The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.; (xsd)meta:Meta>?
	 <  A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. 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. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.; (xsd)implicitRules:uri>?
	 <  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).; (xsd)language:code>?
	 <  A human-readable narrative that contains a summary of the resource and can 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. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied).  This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.; (xsd)text: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. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.; (xsd)contained:Resource>*
	[]<  An Extension; (xsd)extension:Extension>+
	[]<  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 and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  An absolute URI that is used to identify this questionnaire when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which at which an authoritative instance of this questionnaire is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the questionnaire is stored on different servers. The name of the referenced questionnaire can be conveyed using the http://hl7.org/fhir/StructureDefinition/display extension.; (xsd)url:uri>?
	[]<  A formal identifier that is used to identify this questionnaire when it is represented in other formats, or referenced in a specification, model, design or an instance. Typically, this is used for identifiers that can go in an HL7 V3 II (instance identifier) data type, and can then identify this questionnaire outside of FHIR, where it is not possible to use the logical URI.; (xsd)identifier:Identifier>*
	 <  The identifier that is used to identify this version of the questionnaire when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the questionnaire author and is not expected to be globally unique. For example, it might be a timestamp (e.g. yyyymmdd) if a managed version is not available. There is also no expectation that versions can be placed in a lexicographical sequence. There may be different questionnaire instances that have the same identifier but different versions.  The version can be appended to the url in a reference to allow a reference to a particular business version of the questionnaire with the format [url]|[version].; (xsd)version:string>?
	 <  A natural language name identifying the questionnaire. This name should be usable as an identifier for the module by machine processing applications such as code generation. The name is not expected to be globally unique. The name should be a simple alphanumeric type name to ensure that it is machine-processing friendly.; (xsd)name:string>?
	 <  A short, descriptive, user-friendly title for the questionnaire. This name does not need to be machine-processing friendly and may contain punctuation, white-space, etc.; (xsd)title:string>
	[]<  The URL of a Questionnaire that this Questionnaire is based on.; (xsd)derivedFrom:canonical>*
	 <  The status of this questionnaire. Enables tracking the life-cycle of the content. Allows filtering of questionnaires that are appropriate for use versus not.; (xsd)status:code>
	 <  A Boolean value to indicate that this questionnaire is authored for testing purposes (or education/evaluation/marketing) and is not intended to be used for genuine usage. Allows filtering of questionnaires that are appropriate for use versus not.; (xsd)experimental:boolean>?
	[]<  The types of subjects that can be the subject of responses created for the questionnaire. If none are specified, then the subject is unlimited.; (xsd)subjectType:code>*
	 <  Identifies when this version of the form was created.  Changes whenever the form is updated. Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the questionnaire. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource.; (xsd)date:dateTime>
	 <  The name of the organization or individual that published the questionnaire. Usually an organization but may be an individual. The publisher (or steward) of the questionnaire is the organization or individual primarily responsible for the maintenance and upkeep of the questionnaire. This is not necessarily the same individual or organization that developed and initially authored the content. The publisher is the primary point of contact for questions or issues with the questionnaire. This item SHOULD be populated unless the information is available from context.; (xsd)publisher:string>?
	[]<  Contact details to assist a user in finding and communicating with the publisher. May be a web site, an email address, a telephone number, etc.; (xsd)contact:ContactDetail>*
	 <  A free text natural language description of the questionnaire from a consumer's perspective. This description can be used to capture details such as why the questionnaire was built, comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the questionnaire as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context (e.g. the language of the questionnaire is presumed to be the predominant language in the place the questionnaire was created).; (xsd)description:markdown>?
	[]<  Specifies clinical/business/etc. metadata that can be used to retrieve, index and/or categorize an artifact. This metadata can either be specific to the applicable population (e.g., age category, DRG) or the specific context of care (e.g., venue, care setting, provider of care). When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.; (xsd)useContext:sdc-usagecontext>*
	 <  A legal or geographic region in which the questionnaire is intended to be used. Relevant for systems that support forms from multiple countries/provinces/states.; (xsd)jurisdiction:CodeableConcept>?
	 <  Explanation of why this questionnaire is needed and why it has been designed as it has. This element does not describe the usage of the questionnaire. Instead, it provides traceability of ''why'' the resource is either needed or ''why'' it is defined as it is.  This may be used to point to source materials or specifications that drove the structure of this questionnaire.; (xsd)purpose:markdown>?
	 <  A copyright statement relating to the questionnaire and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the questionnaire.; (xsd)copyright:markdown>?
	 <  The date on which the resource content was approved by the publisher. Approval happens once when the content is officially approved for usage. Relevant for systems that have strict curation requirements that govern when a form/instrument is permitted for use.; (xsd)approvalDate:date>?
	 <  The date on which the resource content was last reviewed. Review happens periodically after approval but does not change the original approval date. Relevant for systems that have strict curation requirements that govern when a form/instrument is permitted for use.; (xsd)lastReviewDate:date>?
	 <  The period during which the questionnaire content was or is planned to be in active use. Relevant for systems that have strict curation requirements that govern when a form/instrument is permitted for use.; (xsd)effectivePeriod:Period>?
	 <  An identifier for this question or group of questions in a particular terminology such as LOINC.; (xsd)code:Coding>?
	 <  A particular question, question grouping or display text that is part of the questionnaire. The content of the questionnaire is constructed from an ordered, hierarchical collection of items.; (xsd)item:sdc-questionnaire-adapt-srch.item>{0,0}
	 <  Optional Extension Element - found in all resources.; (xsd)versionAlgorithm:Extension>?
	 <  Optional Extension Element - found in all resources.; (xsd)copyrightLabel:Extension>?
	[]<  This extension will appear on the root of an assembled Questionnaire and identifies the subQuestionnaires (including version) that were used as part of the assembly process.; (xsd)assembledFrom:sdc-questionnaire-assembledFrom>*
	[]<  Marks a questionnaire as being adaptive.  Value can either be a boolean (if true, indicates adaptive) or a URL for the base URL of a server that can perform the nextQuestion operation for this particular questionnaire. There can only be one in a questionnaire if the value used is boolean.; (xsd)questionnaireAdaptive:sdc-questionnaire-questionnaireAdaptive>+
	[]<  The base URL for the server to which questionnaire response associated with this questionnaire should be submitted. If multiple repetitions are present, the completed form should be sent to all listed endpoints. 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.

Endpoints may have expectations around authorization, etc.  Some of this may be learned by consulting the CapabilityStatement associated with the endpoint.; (xsd)submissionEndpoint:sdc-questionnaire-endpoint>*

🔗  A particular question, question grouping or display text that is part of the questionnaire. The content of the questionnaire is constructed from an ordered, hierarchical collection of items.sdc-questionnaire-adapt-srch.item(xsd)=
	 <#base:Questionnaire.item>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  An Extension; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  An identifier that is unique within the Questionnaire allowing linkage to the equivalent item in a QuestionnaireResponse resource. This ''can'' be a meaningful identifier (e.g. a LOINC code) but is not intended to have any meaning.  GUIDs or sequential numbers are appropriate here.; (xsd)linkId:string>
	 <  This element is a URI that refers to an [ElementDefinition](http://hl7.org/fhir/R4/elementdefinition.html) that provides information about this item, including information that might otherwise be included in the instance of the Questionnaire resource. A detailed description of the construction of the URI is shown in Comments, below. If this element is present then the following element values MAY be derived from the Element Definition if the corresponding elements of this Questionnaire resource instance have no value:

* code (ElementDefinition.code) 
* type (ElementDefinition.type) 
* required (ElementDefinition.min) 
* repeats (ElementDefinition.max) 
* maxLength (ElementDefinition.maxLength) 
* answerValueSet (ElementDefinition.binding)
* options (ElementDefinition.binding). Systems that support searching by the 'definition' parameter SHALL support returning item.definition.; (xsd)definition:uri>?
	[]<  A terminology code that corresponds to this group or question (e.g. a code from LOINC, which defines many questions and answers). Systems that support searching by the 'code' parameter SHALL support returning item.code.; (xsd)code:Coding>*
	 <  A short label for a particular group, question or set of display text within the questionnaire used for reference by the individual completing 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.  Typically, these won't be used for "display" items, though such use is not prohibited.  Systems SHOULD NOT generate their own prefixes if prefixes are defined for any items within a Questionnaire.; (xsd)prefix:string>?
	 <  The name of a section, the text of a question or text content for a display item. When using this element to represent the name of a section, use group type item and also make sure to limit the text element to a short string suitable for display as a section heading.  Group item instructions should be included as a display type item within the group.; (xsd)text:string>?
	 <  The type of questionnaire item this is - whether text for display, a grouping of other items or a particular type of data to be captured (string, integer, coded choice, etc.). Time is handled using "string".  File is handled using Attachment.  (Content can be sent as a contained binary).; (xsd)type:code>
	[]<  A constraint indicating that this item should only be enabled (displayed/allow answers to be captured) when the specified condition is true. If multiple repetitions of this extension are present, the item should be enabled when the condition for *any* of the repetitions is true.  I.e. treat "enableWhen"s as being joined by an "or" clause.  This element is a modifier because if enableWhen is present for an item, "required" is ignored unless one of the enableWhen conditions is met. When an item is disabled, all of its descendants are disabled, regardless of what their own enableWhen logic might evaluate to.; (xsd)enableWhen:sdc-questionnaire-adapt-srch.item.enableWhen>*
	 <  Controls how multiple enableWhen values are interpreted -  whether all or any must be true. This element must be specified if more than one enableWhen value is provided.; (xsd)enableBehavior:code>?
	 <  An indication, if true, that the item must be present in a "completed" QuestionnaireResponse.  If false, the item may be skipped when answering the questionnaire. Questionnaire.item.required only has meaning for elements that are conditionally enabled with enableWhen if the condition evaluates to true.  If an item that contains other items is marked as required, that does not automatically make the contained elements required (though required groups must contain at least one child element). The value may come from the ElementDefinition referred to by .definition.; (xsd)required:boolean>?
	 <  An indication, if true, that a QuestionnaireResponse for this item may include multiple answers associated with a single instance of this item (for question-type items) or multiple repetitions of the item (for group-type items) If a question is marked as repeats=true, then multiple answers can be provided for the question in the corresponding QuestionnaireResponse.  When rendering the questionnaire, it is up to the rendering software whether to render the question text for each answer repetition (i.e. "repeat the question") or to simply allow entry/selection of multiple answers for the question (repeat the answers).  Which is most appropriate visually may depend on the type of answer as well as whether there are nested items.

The resulting QuestionnaireResponse will be populated the same way regardless of rendering - one 'question' item with multiple answer values.

 The value may come from the ElementDefinition referred to by .definition.; (xsd)repeats:boolean>?
	 <  An indication, when true, that the value cannot be changed by a human respondent 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.; (xsd)readOnly:boolean>?
	 <  The maximum number of characters that are permitted in the answer to be considered a "valid" QuestionnaireResponse. For base64binary, reflects the number of characters representing the encoded data, not the number of bytes of the binary data. The value may come from the ElementDefinition referred to by .definition.; (xsd)maxLength:integer>?
	 <  A reference to a value set containing a list of codes representing permitted answers for a "choice" or "open-choice" question. LOINC defines many useful value sets for questionnaire responses. See [LOINC Answer Lists](http://hl7.org/fhir/R4/loinc.html#alist). The value may come from the ElementDefinition referred to by .definition.; (xsd)answerValueSet:canonical>?
	[]<  One of the permitted answers for a "choice" or "open-choice" question. This element can be used when the value set machinery of answerValueSet is deemed too cumbersome or when there's a need to capture possible answers that are not codes.; (xsd)answerOption:sdc-questionnaire-adapt-srch.item.answerOption>*
	[]<  One or more values that should be pre-populated in the answer when initially rendering the questionnaire for user input. The user is allowed to change the value and override the default (unless marked as read-only). If the user doesn't change the value, then this initial value will be persisted when the QuestionnaireResponse is initially created.  Note that initial values can influence results.  The data type of initial[x] must agree with the item.type, and only repeating items can have more then one initial value.; (xsd)initial:sdc-questionnaire-adapt-srch.item.initial>*
	[]<  Text, questions and other groups to be nested beneath a question or group. There is no specified limit to the depth of nesting.  However, Questionnaire authors are encouraged to consider the impact on the user and user interface of overly deep nesting.; (xsd)item:Questionnaire.item>*
	 <  If true, indicates that the extended item should not be displayed to the user. If an item is hidden, all descendant items are hidden as well.  See additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/rendering.html#hidden).; (xsd)hidden:questionnaire-hidden>?
	 <  Optional Extension Element - found in all resources.; (xsd)answerConstraint:Extension>?

🔗  One of the permitted answers for a "choice" or "open-choice" question. This element can be used when the value set machinery of answerValueSet is deemed too cumbersome or when there's a need to capture possible answers that are not codes.sdc-questionnaire-adapt-srch.item.answerOption(xsd)=
	 <#base:Questionnaire.item.answerOption>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 ( <valueCoding:Coding>
		 | <valueDate:date>
		 | <valueInteger:integer>
		 | <valueResource:Resource>
		 | <valueString:string>
		 | <valueTime:time>)
	 <  Indicates whether the answer value is selected when the list of possible answers is initially shown. Use this instead of initial[v] if answerValueSet is present.; (xsd)initialSelected:boolean>?

🔗  A constraint indicating that this item should only be enabled (displayed/allow answers to be captured) when the specified condition is true. If multiple repetitions of this extension are present, the item should be enabled when the condition for *any* of the repetitions is true.  I.e. treat "enableWhen"s as being joined by an "or" clause.  This element is a modifier because if enableWhen is present for an item, "required" is ignored unless one of the enableWhen conditions is met. When an item is disabled, all of its descendants are disabled, regardless of what their own enableWhen logic might evaluate to.sdc-questionnaire-adapt-srch.item.enableWhen(xsd)=
	 <#base:Questionnaire.item.enableWhen>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  The linkId for the question whose answer (or lack of answer) governs whether this item is enabled. If multiple question occurrences are present for the same question (same linkId), then this refers to the nearest question occurrence reachable by tracing first the "ancestor" axis and then the "preceding" axis and then the "following" axis.; (xsd)question:string>
	 <  Specifies the criteria by which the question is enabled.; (xsd)operator:code>
	 <  A value that the referenced question is tested using the specified operator in order for the item to be enabled.; (xsd)answer:( <boolean>
		 | <Coding>
		 | <date>
		 | <dateTime>
		 | <decimal>
		 | <integer>
		 | <Quantity>
		 | <Resource>
		 | <string>
		 | <time>)>

🔗  One or more values that should be pre-populated in the answer when initially rendering the questionnaire for user input. The user is allowed to change the value and override the default (unless marked as read-only). If the user doesn't change the value, then this initial value will be persisted when the QuestionnaireResponse is initially created.  Note that initial values can influence results.  The data type of initial[x] must agree with the item.type, and only repeating items can have more then one initial value.sdc-questionnaire-adapt-srch.item.initial(xsd)=
	 <#base:Questionnaire.item.initial>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 ( <valueAttachment:Attachment>
		 | <valueBoolean:boolean>
		 | <valueCoding:Coding>
		 | <valueDate:date>
		 | <valueDateTime:dateTime>
		 | <valueDecimal:decimal>
		 | <valueInteger:integer>
		 | <valueQuantity:Quantity>
		 | <valueResource:Resource>
		 | <valueString:string>
		 | <valueTime:time>
		 | <valueUri:uri>)

🔗  An expression (FHIRPath, CQL or FHIR Query) that resolves to a list of permitted answers for the question item or that establishes context for a group item.  The user may select from among the list to choose answers for the question. This is only permitted when the containing item does NOT have any answerOption or answerValueSet elements. The results of the expression must correspond to the item type of the question the element appears on or must correspond to a resource, backbone element or complex data type for a group item.  Resources are considered a match for the Reference item type.  Quantity can be a match for decimal and integer items so long as a questionnaire-unit extension is present.  If the result of an expression returns a code or codes, it **SHALL** return the results as Coding, not code or CodeableConcept.sdc-questionnaire-answerExpression(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	 <  An Extension; (xsd)extension:Extension>{0,0}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaire-answerExpression; (xsd)url:string>
	 <  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)value:Expression>?

🔗  A complex expression that provides a list of the allowed options that should be enabled or disabled based on the evaluation of a provided expression.  It allows toggling of allowed answers based on context, including the answers provided to other expressions. For example, this allows a list of conditions to be modified based on the gender of the patientsdc-questionnaire-answerOptionsToggleExpression(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  An Extension; (xsd)extension:Extension>{2,2147483647}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaire-answerOptionsToggleExpression; (xsd)url:string>
	 ( <valueAddress:Address>
		 | <valueAge:Age>
		 | <valueAnnotation:Annotation>
		 | <valueAttachment:Attachment>
		 | <valueBase64Binary:base64Binary>
		 | <valueBoolean:boolean>
		 | <valueCanonical:canonical>
		 | <valueCode:code>
		 | <valueCodeableConcept:CodeableConcept>
		 | <valueCoding:Coding>
		 | <valueContactDetail:ContactDetail>
		 | <valueContactPoint:ContactPoint>
		 | <valueContributor:Contributor>
		 | <valueCount:Count>
		 | <valueDataRequirement:DataRequirement>
		 | <valueDate:date>
		 | <valueDateTime:dateTime>
		 | <valueDecimal:decimal>
		 | <valueDistance:Distance>
		 | <valueDosage:Dosage>
		 | <valueDuration:Duration>
		 | <valueExpression:Expression>
		 | <valueHumanName:HumanName>
		 | <valueId:id>
		 | <valueIdentifier:Identifier>
		 | <valueInstant:instant>
		 | <valueInteger:integer>
		 | <valueMarkdown:markdown>
		 | <valueMeta:Meta>
		 | <valueMoney:Money>
		 | <valueOid:oid>
		 | <valueParameterDefinition:ParameterDefinition>
		 | <valuePeriod:Period>
		 | <valuePositiveInt:positiveInt>
		 | <valueQuantity:Quantity>
		 | <valueRange:Range>
		 | <valueRatio:Ratio>
		 | <valueRelatedArtifact:RelatedArtifact>
		 | <valueResource:Resource>
		 | <valueSampledData:SampledData>
		 | <valueSignature:Signature>
		 | <valueString:string>
		 | <valueTime:time>
		 | <valueTiming:Timing>
		 | <valueTriggerDefinition:TriggerDefinition>
		 | <valueUnsignedInt:unsignedInt>
		 | <valueUri:uri>
		 | <valueUrl:url>
		 | <valueUsageContext:UsageContext>
		 | <valueUuid:uuid>){0,0}
	[]<  Each repetition is an option to toggle based on the expression; (xsd)option:sdc-questionnaire-answerOptionsToggleExpression.option>+
	 <  If this expression evaluate's to 'true', then the specified options should be enabled, otherwise they should be disabled.; (xsd)expression:sdc-questionnaire-answerOptionsToggleExpression.expression>

🔗  If this expression evaluate's to 'true', then the specified options should be enabled, otherwise they should be disabled.sdc-questionnaire-answerOptionsToggleExpression.expression(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	 <  An Extension; (xsd)extension:Extension>{0,0}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. expression; (xsd)url:string>
	 <  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)value:Expression>

🔗  Each repetition is an option to toggle based on the expressionsdc-questionnaire-answerOptionsToggleExpression.option(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	 <  An Extension; (xsd)extension:Extension>{0,0}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. option; (xsd)url:string>
	 ( <valueAddress:Address>
		 | <valueAge:Age>
		 | <valueAnnotation:Annotation>
		 | <valueAttachment:Attachment>
		 | <valueBase64Binary:base64Binary>
		 | <valueBoolean:boolean>
		 | <valueCanonical:canonical>
		 | <valueCode:code>
		 | <valueCodeableConcept:CodeableConcept>
		 | <valueCoding:Coding>
		 | <valueContactDetail:ContactDetail>
		 | <valueContactPoint:ContactPoint>
		 | <valueContributor:Contributor>
		 | <valueCount:Count>
		 | <valueDataRequirement:DataRequirement>
		 | <valueDate:date>
		 | <valueDateTime:dateTime>
		 | <valueDecimal:decimal>
		 | <valueDistance:Distance>
		 | <valueDosage:Dosage>
		 | <valueDuration:Duration>
		 | <valueExpression:Expression>
		 | <valueHumanName:HumanName>
		 | <valueId:id>
		 | <valueIdentifier:Identifier>
		 | <valueInstant:instant>
		 | <valueInteger:integer>
		 | <valueMarkdown:markdown>
		 | <valueMeta:Meta>
		 | <valueMoney:Money>
		 | <valueOid:oid>
		 | <valueParameterDefinition:ParameterDefinition>
		 | <valuePeriod:Period>
		 | <valuePositiveInt:positiveInt>
		 | <valueQuantity:Quantity>
		 | <valueRange:Range>
		 | <valueRatio:Ratio>
		 | <valueRelatedArtifact:RelatedArtifact>
		 | <valueResource:Resource>
		 | <valueSampledData:SampledData>
		 | <valueSignature:Signature>
		 | <valueString:string>
		 | <valueTime:time>
		 | <valueTiming:Timing>
		 | <valueTriggerDefinition:TriggerDefinition>
		 | <valueUnsignedInt:unsignedInt>
		 | <valueUri:uri>
		 | <valueUrl:url>
		 | <valueUsageContext:UsageContext>
		 | <valueUuid:uuid>)

🔗  This extension, used on a subQuestionnaire, indicates a FHIRPath variable that must be present in context when the subQuestionnaire is referenced.sdc-questionnaire-assembleContext(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	 <  An Extension; (xsd)extension:Extension>{0,0}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaire-assembleContext; (xsd)url:string>
	 <  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)value:string>?

🔗  This extension will appear on the root of an assembled Questionnaire and identifies the subQuestionnaires (including version) that were used as part of the assembly process.sdc-questionnaire-assembledFrom(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	 <  An Extension; (xsd)extension:Extension>{0,0}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaire-assembledFrom; (xsd)url:string>
	 <  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)value:canonical>?

🔗  If present, indicates that this questionnaire has expectations with respect to assembly.  Specifically, indicates whether this form requires assembly (i.e. it can't be used directly without invoking the [$assemble](OperationDefinition-Questionnaire-assemble.html) operation operation on it) and/or whether it is intended for use only as a 'child' in an assembly process.  The assembly processs might mean filling in item metadata based on information looked up from item.definitions and/or retrieving sub-questionnaires pointed to by [sub-questionnaire](StructureDefinition-sdc-questionnaire-subQuestionnaire.html) extensions. SDC-conformant Questionnaires **SHALL** declare this extension if they require an assembly process prior to use.  If not declared, then the Questionnaire is not necessarily safe for use as a child form and does not require assembly prior to use.sdc-questionnaire-assemble-expectation(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	 <  An Extension; (xsd)extension:Extension>{0,0}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaire-assemble-expectation; (xsd)url:string>
	 <  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)value:code>?

🔗  Defines additional capabilities for controlling data entry and calculating values within the questionnaire.sdc-questionnaire-behave(xsd)=
	 <#base:sdc-questionnairecommon>
	 <  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.; (xsd)id:string>?
	 <  The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.; (xsd)meta:Meta>?
	 <  A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. 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. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.; (xsd)implicitRules:uri>?
	 <  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).; (xsd)language:code>?
	 <  A human-readable narrative that contains a summary of the resource and can 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. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied).  This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.; (xsd)text: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. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.; (xsd)contained:Resource>*
	[]<  An Extension; (xsd)extension:Extension>*
	[]<  An Extension; (xsd)modifierExtension:Extension>*
	 <  An absolute URI that is used to identify this questionnaire when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which at which an authoritative instance of this questionnaire is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the questionnaire is stored on different servers. The name of the referenced questionnaire can be conveyed using the http://hl7.org/fhir/StructureDefinition/display extension.; (xsd)url:uri>?
	[]<  A formal identifier that is used to identify this questionnaire when it is represented in other formats, or referenced in a specification, model, design or an instance. Typically, this is used for identifiers that can go in an HL7 V3 II (instance identifier) data type, and can then identify this questionnaire outside of FHIR, where it is not possible to use the logical URI.; (xsd)identifier:Identifier>*
	 <  The identifier that is used to identify this version of the questionnaire when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the questionnaire author and is not expected to be globally unique. For example, it might be a timestamp (e.g. yyyymmdd) if a managed version is not available. There is also no expectation that versions can be placed in a lexicographical sequence. There may be different questionnaire instances that have the same identifier but different versions.  The version can be appended to the url in a reference to allow a reference to a particular business version of the questionnaire with the format [url]|[version].; (xsd)version:string>?
	 <  A natural language name identifying the questionnaire. This name should be usable as an identifier for the module by machine processing applications such as code generation. The name is not expected to be globally unique. The name should be a simple alphanumeric type name to ensure that it is machine-processing friendly.; (xsd)name:string>?
	 <  A short, descriptive, user-friendly title for the questionnaire. This name does not need to be machine-processing friendly and may contain punctuation, white-space, etc.; (xsd)title:string>?
	[]<  The URL of a Questionnaire that this Questionnaire is based on.; (xsd)derivedFrom:canonical>*
	 <  The status of this questionnaire. Enables tracking the life-cycle of the content. Allows filtering of questionnaires that are appropriate for use versus not.; (xsd)status:code>
	 <  A Boolean value to indicate that this questionnaire is authored for testing purposes (or education/evaluation/marketing) and is not intended to be used for genuine usage. Allows filtering of questionnaires that are appropriate for use versus not.; (xsd)experimental:boolean>?
	[]<  The types of subjects that can be the subject of responses created for the questionnaire. If none are specified, then the subject is unlimited.; (xsd)subjectType:code>*
	 <  The date  (and optionally time) when the questionnaire was published. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the questionnaire changes. Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the questionnaire. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource.; (xsd)date:dateTime>?
	 <  The name of the organization or individual that published the questionnaire. Usually an organization but may be an individual. The publisher (or steward) of the questionnaire is the organization or individual primarily responsible for the maintenance and upkeep of the questionnaire. This is not necessarily the same individual or organization that developed and initially authored the content. The publisher is the primary point of contact for questions or issues with the questionnaire. This item SHOULD be populated unless the information is available from context.; (xsd)publisher:string>?
	[]<  Contact details to assist a user in finding and communicating with the publisher. May be a web site, an email address, a telephone number, etc.; (xsd)contact:ContactDetail>*
	 <  A free text natural language description of the questionnaire from a consumer's perspective. This description can be used to capture details such as why the questionnaire was built, comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the questionnaire as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context (e.g. the language of the questionnaire is presumed to be the predominant language in the place the questionnaire was created).; (xsd)description:markdown>?
	[]<  The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate questionnaire instances. When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.; (xsd)useContext:UsageContext>*
	[]<  A legal or geographic region in which the questionnaire is intended to be used. It may be possible for the questionnaire to be used in jurisdictions other than those for which it was originally designed or intended.; (xsd)jurisdiction:CodeableConcept>*
	 <  Explanation of why this questionnaire is needed and why it has been designed as it has. This element does not describe the usage of the questionnaire. Instead, it provides traceability of ''why'' the resource is either needed or ''why'' it is defined as it is.  This may be used to point to source materials or specifications that drove the structure of this questionnaire.; (xsd)purpose:markdown>?
	 <  A copyright statement relating to the questionnaire and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the questionnaire.; (xsd)copyright:markdown>?
	 <  The date on which the resource content was approved by the publisher. Approval happens once when the content is officially approved for usage. The 'date' element may be more recent than the approval date because of minor changes or editorial corrections.; (xsd)approvalDate:date>?
	 <  The date on which the resource content was last reviewed. Review happens periodically after approval but does not change the original approval date. If specified, this date follows the original approval date.; (xsd)lastReviewDate:date>?
	 <  The period during which the questionnaire content was or is planned to be in active use. The effective period for a questionnaire  determines when the content is applicable for usage and is independent of publication and review dates. For example, a measure intended to be used for the year 2016 might be published in 2015.; (xsd)effectivePeriod:Period>?
	[]<  An identifier for this question or group of questions in a particular terminology such as LOINC.; (xsd)code:Coding>*
	[]<  A particular question, question grouping or display text that is part of the questionnaire. The content of the questionnaire is constructed from an ordered, hierarchical collection of items.; (xsd)item:sdc-questionnaire-behave.item>*
	 <  Optional Extension Element - found in all resources.; (xsd)versionAlgorithm:Extension>?
	 <  Optional Extension Element - found in all resources.; (xsd)copyrightLabel:Extension>?
	[]<  Indicates how questions within the questionnaire should be presented to the end-user.  Specifically, differentiates whether the questions should be displayed one-at-a-time with no ability to adjust prior entries; one-at-a-time or continuously expanding where all questions up to the current question can be looked at and edited, or random, where all questions can be seen and the questions can be filled out in any order desired. The prior-edit functionality can be accomplished by adding questions to the screen as each subsequent question is answered (resulting in all questions being displayed in a single screen) or with a view that shows only one question at a time but allows backward navigation to view and/or edit prior answers.; (xsd)entryMode:sdc-questionnaire-entryMode>*
	[]<  The base URL for the server to which questionnaire response associated with this questionnaire should be submitted. If multiple repetitions are present, the completed form should be sent to all listed endpoints. 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.

Endpoints may have expectations around authorization, etc.  Some of this may be learned by consulting the CapabilityStatement associated with the endpoint.; (xsd)submissionEndpoint:sdc-questionnaire-endpoint>*
	[]<  Indicates that a signature (of the specified type) is needed when completing the QuestionnaireResponse. If this appears at the Questionnaire level, then the signature will be gathered for the entire form when it is marked complete.  If it appears on a particular item, then it will be gathered on that question or group when it is filled in.  (E.g. seeking the user's initials beside certain questions.)

The signature can be captured using the http://hl7.org/fhir/StructureDefinition/questionnaireresponse-signature extension.  See additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/behavior.html#signatureRequired).; (xsd)signatureRequired:questionnaire-signatureRequired>*
	[]<  Specifies a constraint that is enforced on instantiated (or target) resources. This extension can be applied to definitional resources (such as ActivityDefinition or Measure) and indicates that the constraint should be enforced on resources that are instantiated from the definition. Can be used on any definitional artifact to define a constraint that is enforced in the context of an instantiated resource. The constraint expression will have access to `%target` and `%definition` variables, where target is the instantiated resource, and definition is the definition used to instantiate.; (xsd)constraint:Extension>*
	[]<  A reference to a library containing cql used in this Questionnaire. For questionnaires, see additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/behavior.html#cqf-library).; (xsd)library:cqf-library>*
	[]<  Resources that provide context for form processing logic (pre-population, flow-control, drop-down selection, etc.) when creating/displaying/editing a QuestionnaireResponse. 3 of these launch contexts are aligned with the existing SMART on FHIR "launch" contexts.; (xsd)launchContext:sdc-questionnaire-launchContext>*
	[]<  Variable specifying a logic to generate a variable for use in subsequent logic.  The name of the variable will be added to FHIRPath's context when processing descendants of the element that contains this extension as well as extensions within the same element. Ordering of variable extension declarations is significant as variables declared in one repetition of this extension might be used in subsequent extension repetitions

For questionnaires, see additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/behavior.html#variable).; (xsd)variable>*
	[]<  Indicates an extension that must be supported by the system presenting the instance for data capture or end-user consumption. If a system does not recognize the extension or cannot implement the functionality defined by the extension, it should display an error message or warning and refrain from presenting the instance to the user or using it when capturing data. This may point to extensions that control the appearance of data elements, control what value elements have, what elements are or are not available, what elements can or cannot be edited, or rules about how editing may occur. This extension does NOT apply when simply rendering a resource for publication purposes or for other purposes not intended for end-user data capture or data consumption.; (xsd)rendering-criticalExtension:sdc-rendering-criticalExtension>*

🔗  A particular question, question grouping or display text that is part of the questionnaire. The content of the questionnaire is constructed from an ordered, hierarchical collection of items.sdc-questionnaire-behave.item(xsd)=
	 <#base:Questionnaire.item>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  An Extension; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  An identifier that is unique within the Questionnaire allowing linkage to the equivalent item in a QuestionnaireResponse resource. This ''can'' be a meaningful identifier (e.g. a LOINC code) but is not intended to have any meaning.  GUIDs or sequential numbers are appropriate here.; (xsd)linkId:string>
	 <  This element is a URI that refers to an [ElementDefinition](http://hl7.org/fhir/R4/elementdefinition.html) that provides information about this item, including information that might otherwise be included in the instance of the Questionnaire resource. A detailed description of the construction of the URI is shown in Comments, below. If this element is present then the following element values MAY be derived from the Element Definition if the corresponding elements of this Questionnaire resource instance have no value:

* code (ElementDefinition.code) 
* type (ElementDefinition.type) 
* required (ElementDefinition.min) 
* repeats (ElementDefinition.max) 
* maxLength (ElementDefinition.maxLength) 
* answerValueSet (ElementDefinition.binding)
* options (ElementDefinition.binding). The uri refers to an ElementDefinition in a [StructureDefinition](http://hl7.org/fhir/R4/structuredefinition.html#) and always starts with the [canonical URL](http://hl7.org/fhir/R4/references.html#canonical) for the target resource. When referring to a StructureDefinition, a fragment identifier is used to specify the element definition by its id [Element.id](http://hl7.org/fhir/R4/element-definitions.html#Element.id). E.g. http://hl7.org/fhir/StructureDefinition/Observation#Observation.value[x]. In the absence of a fragment identifier, the first/root element definition in the target is the matching element definition.; (xsd)definition:uri>?
	[]<  A terminology code that corresponds to this group or question (e.g. a code from LOINC, which defines many questions and answers). The value may come from the ElementDefinition referred to by .definition.; (xsd)code:Coding>*
	 <  A short label for a particular group, question or set of display text within the questionnaire used for reference by the individual completing 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.  Typically, these won't be used for "display" items, though such use is not prohibited.  Systems SHOULD NOT generate their own prefixes if prefixes are defined for any items within a Questionnaire.; (xsd)prefix:string>?
	 <  The name of a section, the text of a question or text content for a display item. When using this element to represent the name of a section, use group type item and also make sure to limit the text element to a short string suitable for display as a section heading.  Group item instructions should be included as a display type item within the group.; (xsd)text:string>?
	 <  The type of questionnaire item this is - whether text for display, a grouping of other items or a particular type of data to be captured (string, integer, coded choice, etc.). Time is handled using "string".  File is handled using Attachment.  (Content can be sent as a contained binary).; (xsd)type:code>
	[]<  A constraint indicating that this item should only be enabled (displayed/allow answers to be captured) when the specified condition is true. If multiple repetitions of this extension are present, the item should be enabled when the condition for *any* of the repetitions is true.  I.e. treat "enableWhen"s as being joined by an "or" clause.  This element is a modifier because if enableWhen is present for an item, "required" is ignored unless one of the enableWhen conditions is met. When an item is disabled, all of its descendants are disabled, regardless of what their own enableWhen logic might evaluate to.; (xsd)enableWhen:sdc-questionnaire-behave.item.enableWhen>*
	 <  Controls how multiple enableWhen values are interpreted -  whether all or any must be true. This element must be specified if more than one enableWhen value is provided.; (xsd)enableBehavior:code>?
	 <  An indication, if true, that the item must be present in a "completed" QuestionnaireResponse.  If false, the item may be skipped when answering the questionnaire. Questionnaire.item.required only has meaning for elements that are conditionally enabled with enableWhen if the condition evaluates to true.  If an item that contains other items is marked as required, that does not automatically make the contained elements required (though required groups must contain at least one child element). The value may come from the ElementDefinition referred to by .definition.; (xsd)required:sdc-questionnaire-behave.item.required>?
	 <  An indication, if true, that a QuestionnaireResponse for this item may include multiple answers associated with a single instance of this item (for question-type items) or multiple repetitions of the item (for group-type items) If a question is marked as repeats=true, then multiple answers can be provided for the question in the corresponding QuestionnaireResponse.  When rendering the questionnaire, it is up to the rendering software whether to render the question text for each answer repetition (i.e. "repeat the question") or to simply allow entry/selection of multiple answers for the question (repeat the answers).  Which is most appropriate visually may depend on the type of answer as well as whether there are nested items.

The resulting QuestionnaireResponse will be populated the same way regardless of rendering - one 'question' item with multiple answer values.

 The value may come from the ElementDefinition referred to by .definition.; (xsd)repeats:sdc-questionnaire-behave.item.repeats>?
	 <  An indication, when true, that the value cannot be changed by a human respondent 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.; (xsd)readOnly:sdc-questionnaire-behave.item.readOnly>?
	 <  The maximum number of characters that are permitted in the answer to be considered a "valid" QuestionnaireResponse. For base64binary, reflects the number of characters representing the encoded data, not the number of bytes of the binary data. The value may come from the ElementDefinition referred to by .definition.; (xsd)maxLength:integer>?
	 <  A reference to a value set containing a list of codes representing permitted answers for a "choice" or "open-choice" question. LOINC defines many useful value sets for questionnaire responses. See [LOINC Answer Lists](http://hl7.org/fhir/R4/loinc.html#alist). The value may come from the ElementDefinition referred to by .definition.; (xsd)answerValueSet:canonical>?
	[]<  One of the permitted answers for a "choice" or "open-choice" question. This element can be used when the value set machinery of answerValueSet is deemed too cumbersome or when there's a need to capture possible answers that are not codes.; (xsd)answerOption:sdc-questionnaire-behave.item.answerOption>*
	[]<  One or more values that should be pre-populated in the answer when initially rendering the questionnaire for user input. The user is allowed to change the value and override the default (unless marked as read-only). If the user doesn't change the value, then this initial value will be persisted when the QuestionnaireResponse is initially created.  Note that initial values can influence results.  The data type of initial[x] must agree with the item.type, and only repeating items can have more then one initial value.; (xsd)initial:sdc-questionnaire-behave.item.initial>*
	[]<  Text, questions and other groups to be nested beneath a question or group. There is no specified limit to the depth of nesting.  However, Questionnaire authors are encouraged to consider the impact on the user and user interface of overly deep nesting.; (xsd)item:Questionnaire.item>*
	 <  If true, indicates that the extended item should not be displayed to the user. If an item is hidden, all descendant items are hidden as well.  See additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/rendering.html#hidden).; (xsd)hidden:questionnaire-hidden>?
	 <  Optional Extension Element - found in all resources.; (xsd)answerConstraint:Extension>?
	 <  Optional Extension Element - found in all resources.; (xsd)disabledDisplay:Extension>?
	 <  An expression (FHIRPath, CQL or FHIR Query) that resolves to a list of permitted answers for the question item or that establishes context for a group item.  The user may select from among the list to choose answers for the question. This is only permitted when the containing item does NOT have any answerOption or answerValueSet elements. The results of the expression must correspond to the item type of the question the element appears on or must correspond to a resource, backbone element or complex data type for a group item.  Resources are considered a match for the Reference item type.  Quantity can be a match for decimal and integer items so long as a questionnaire-unit extension is present.  If the result of an expression returns a code or codes, it **SHALL** return the results as Coding, not code or CodeableConcept.; (xsd)answerExpression:sdc-questionnaire-answerExpression>?
	 <  Identifies that the specified element should only appear in certain "modes" of operation. See additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/behavior.html#usageMode).; (xsd)usageMode:questionnaire-usageMode>?
	[]<  Indicates that a signature (of the specified type) is needed when completing the QuestionnaireResponse. If this appears at the Questionnaire level, then the signature will be gathered for the entire form when it is marked complete.  If it appears on a particular item, then it will be gathered on that question or group when it is filled in.  (E.g. seeking the user's initials beside certain questions.)

The signature can be captured using the http://hl7.org/fhir/StructureDefinition/questionnaireresponse-signature extension.  See additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/behavior.html#signatureRequired).; (xsd)itemSignatureRequired:questionnaire-signatureRequired>*
	 <  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.  See additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/behavior.html#minOccurs).; (xsd)itemMinOccurs:questionnaire-minOccurs>?
	 <  The maximum number of times the group must appear, or the maximum 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.  See additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/behavior.html#maxOccurs).; (xsd)itemMaxOccurs:questionnaire-maxOccurs>?
	 <  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.  For questionnaires, see additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/behavior.html#minLength).; (xsd)minLength>?
	 <  A regular expression that defines the syntax for the data element to be considered valid.; (xsd)regex>?
	 <  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.  For questionnaires, see additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/behavior.html#minValue).; (xsd)minValue>?
	 <  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.  For questionnaires, see additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/behavior.html#maxValue).; (xsd)maxValue>?
	 <  The inclusive lower bound on the range of allowed values for a 'quantity' type question.  Open Issue: Revisit whether this should be folded into the regular minValue extension once there are better capabilities around defining conformance expectations regarding extensions. This  must only be used if the set of permitted units is constrained to UCUM codes and the minimum  checks will be performed by converting the answer.valueQuantity to the same units as the minQuantity unit prior to comparison.; (xsd)minQuantity:sdc-questionnaire-minQuantity>?
	 <  The inclusive upper bound on the range of allowed values for  a 'quantity' type question.  Open Issue: Revisit whether this should be folded into the regular maxValue extension once there are better capabilities around defining conformance expectations regarding extensions. This  must only be used if the set of permitted units is constrained to UCUM codes and the maximum checks will be performed by converting the answer.valueQuantity to the same units as the maxQuantity unit prior to comparison.; (xsd)maxQuantity:sdc-questionnaire-maxQuantity>?
	 <  Identifies the maximum number of decimal places that may be specified for the data element. For questionnaires, see additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/behavior.html#maxDecimalPlaces).; (xsd)maxDecimalPlaces>?
	[]<  Identifies the kind(s) of attachment allowed to be sent for an element. This extension only has meaning if the element has a type of Attachment.  For questionnaires, see additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/behavior.html#mimeType).; (xsd)mimeType>*
	 <  For attachment answers, indicates the maximum size in bytes an attachment can be. This extension only has meaning if the element has a type of Attachment.  For questionnaires, see additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/behavior.html#maxSize).; (xsd)maxSize>?
	[]<  A complex expression that provides a list of the allowed options that should be enabled or disabled based on the evaluation of a provided expression.  It allows toggling of allowed answers based on context, including the answers provided to other expressions. For example, this allows a list of conditions to be modified based on the gender of the patient; (xsd)answerOptionsToggleExpression:sdc-questionnaire-answerOptionsToggleExpression>*
	[]<  A unit that the user may choose when providing a quantity value. Provide either unitOption(s) or unitValueSet.  If either of the extensions are present, the units for a Quantity element are constrained to only the units listed by the extensions - i.e. it is treated as a "required", not an "extensible" binding.  In the absence of either, any unit is valid.  See additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/behavior.html#unitOption).  If this extension present and an answer is provided for the question item in the QuestionnaireResponse, then the valueQuantity **SHALL** have a Quantity.code and Quantity.system that match the Coding.code and system of one of the allowed values if the Coding has a code and/or system.  If the Coding only has a display, then the Quantity.unit must match.  (Note that Coding with only a display is strongly discouraged.)  If there is a match on code and system, but no match on display/unit, systems MAY raise a warning.  However, because of translation and bandwidth considerations, some systems **MAY** opt to drop the unit or express it in an alternate language.; (xsd)unitOption:questionnaire-unitOption>*
	 <  A set of units that the user may choose when providing a quantity value. Provide either unitOption(s) or unitValueSet.  If either of the extensions are present, the units for a Quantity element are constrained to only the units listed by the extensions - i.e. it is treated as a "required", not an "extensible" binding.  In the absence of either, any unit is valid.  See additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/behavior#unitValusSet).  If this extension present and an answer is provided for the question item in the QuestionnaireResponse, then the valueQuantity **SHALL** have a Quantity.code and Quantity.system that match the Coding.code and system of one of the allowed values if the Coding has a code and/or system.  If the Coding only has a display, then the Quantity.unit must match.  (Note that Coding with only a display is strongly discouraged.)  If there is a match on code and system, but no match on display/unit, systems MAY raise a warning.  However, because of translation and bandwidth considerations, some systems **MAY** opt to drop the unit or express it in an alternate language.  Validation of the Quantity unit **MAY** be performed by using the $validateCode operation, populating the elements passed into the operation from the Quantity.code, system and unit elements.; (xsd)unitValueSet:questionnaire-unitValueSet>?
	 <  Indicates whether the list of supported units (conveyed in other extensions) are the exhaustive list from which the user must choose or whether they're able to select alternate codes or specify a string.; (xsd)unitOpen:sdc-questionnaire-unitOpen>?
	 <  If the questionnaire-unit-open extension indicates that additional units other than the set of options provided for the question are allowed, this indicates the code system those units are expected to be drawn from.  This extension SHOULD be present on any question where questionare-unit-open allows additional coded values.; (xsd)unitSupplementalSystem:sdc-questionnaire-unitSupplementalSystem>?
	[]<  Where the type for a question is "Reference", indicates a type of resource that is permitted. This extension only has meaning if the question.type = Reference.  If no allowedResource extensions are present, the presumption is that any type of resource is permitted.  If multiple are present, then any of the specified types are permitted.  See additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/behavior.html#referenceResource).; (xsd)allowedResource:questionnaire-referenceResource>*
	[]<  Where the type for a question is "Reference", indicates a profile that the resource instances pointed to in answers to this question must be valid against. If multiple profiles are present, then the resource must be valid against at least one of them.  See additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/behavior.html#referenceProfile).; (xsd)allowedProfile:questionnaire-referenceProfile>*
	 <  A FHIRPath or CQL expression, or FHIR Query that resolves to a list of candidate answers for the question item or that establishes context for a group item.  The user may select from among the candidates to choose answers for the question. The results of the expression must correspond to the item type of the question the element appears on or must correspond to a resource, backbone element or complex data type for a group item.  Resources are considered a match for the Reference item type.  Quantity can be a match for decimal and integer items so long as a questionnaire-unit extension is present.  If the expression returns coded data, it **SHALL* return the information as either code or Coding, not CodeableConcept.  If the expression returns elements of type 'code', when the user selects one or more candidates, the code will be matched against the allowed Codings (from answerValueSet, answerOptions, or answerExpresssion).  In this case, it is an error if there is more than one Coding with the same code.; (xsd)candidateExpression:sdc-questionnaire-candidateExpression>?
	 <  For items of type reference, the reference can be populated either by picking an existing entity or by creating a new one.  In the latter case, this Questionnaire allows specifying the Questionnaire to use in creating the target instance.  Typically this will result in a QuestionnaireResponse that can be [extracted](extraction.html) to produce the desired resource.  However, if the target resource for the reference is a QuestionnaireResponse, then the QuestionnaireResponse resulting from the Questionnaire can be referenced directly.; (xsd)lookupQuestionnaire:sdc-questionnaire-lookupQuestionnaire>?
	[]<  Specifies a constraint that is enforced on instantiated (or target) resources. This extension can be applied to definitional resources (such as ActivityDefinition or Measure) and indicates that the constraint should be enforced on resources that are instantiated from the definition. Can be used on any definitional artifact to define a constraint that is enforced in the context of an instantiated resource. The constraint expression will have access to `%target` and `%definition` variables, where target is the instantiated resource, and definition is the definition used to instantiate.; (xsd)itemConstraint:Extension>*
	 <  Initial value for a question answer as determined by an evaluated expression. Initial value is only calculated at the time the QuestionnaireResponse is first generated.  If the expression returns coded data, it **SHALL* return the information as either code or Coding, not CodeableConcept.  If the expression returns elements of type 'code', when the user selects one or more candidates, the code will be matched against the allowed Codings (from answerValueSet, answerOptions, or answerExpression).  In this case, it is an error if there is more than one Coding with the same code.; (xsd)initialExpression:sdc-questionnaire-initialExpression>?
	 <  Calculated value for a question answer as determined by an evaluated expression. Calculated value is updated  as other answers in the QuestionnaireResponse are filled in.; (xsd)calculatedExpression:sdc-questionnaire-calculatedExpression>?
	 <  An expression that returns a boolean value for whether to enable the item. This is only permitted when the containing item does NOT have any enableWhen elements.

If the expression involves comparisons between elements that have different precisions but are otherwise equal, FHIRPath will resolve the expression to an empty set, which will in turn evaluate to false (meaning the item won't be enabled).  If this is not the desired behavior, the author should add a `.allTrue()` to the end of the expression, which will result in an indeterminate outcome because of precision differences being handled as 'true' and the item being enabled.  Questionnaires SHOULD be designed to take into account challenges around varying precision to minimize non-deterministic situations by setting constraints around expected precision, etc.

If the expression evaluates to something other than a boolean true or false, the Form Filler SHOULD still display the form, and if it does so, SHOULD treat the element as 'enabled' and display a warning to the user that the questionnaire logic was faulty and it's possible that the item shouldn't be enabled.; (xsd)enableWhenExpression:sdc-questionnaire-enableWhenExpression>?
	 <  For string or text items, indicates the 'keyboard type' that should be used by the user interface to guide entry. The assertion applies on a per item basis and is not inherited.  If the item is 'text', only 'chat' should be declared if this extension is present.; (xsd)keyboardType:sdc-questionnaire-keyboard>?

🔗  One of the permitted answers for a "choice" or "open-choice" question. This element can be used when the value set machinery of answerValueSet is deemed too cumbersome or when there's a need to capture possible answers that are not codes.sdc-questionnaire-behave.item.answerOption(xsd)=
	 <#base:Questionnaire.item.answerOption>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  An Extension; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 ( <valueCoding:Coding>
		 | <valueDate:date>
		 | <valueInteger:integer>
		 | <valueResource:Resource>
		 | <valueString:string>
		 | <valueTime:time>)
	 <  Indicates whether the answer value is selected when the list of possible answers is initially shown. Use this instead of initial[v] if answerValueSet is present.; (xsd)initialSelected:boolean>?
	 <  If true, indicates that if this answerOption is selected, no other possible answers may be selected, even if the item is a repeating question. See additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/behavior.html#optionExclusive).; (xsd)optionExclusive:questionnaire-optionExclusive>?
	 <  A numeric value that allows the comparison (less than, greater than) or other numerical manipulation of a concept (e.g. Adding up components of a score). Scores are usually a whole number, but occasionally decimals are encountered in scores. In the CodeSystem and ValueSet resources, the item weight is represented using the [itemWeight property](http://hl7.org/fhir/R4/codesystem-concept-properties.html#concept-properties-itemWeight) NOTE: questionnaire.item.answerOption can have a type of Coding, potentially allowing two different scopes for this extension.  In the case where answerOption is available, the weight SHALL be declared on the answerOption rather than on the answerOption.valueCoding.; (xsd)itemWeight:Extension>?

🔗  A reference to a value set containing a list of codes representing permitted answers for a "choice" or "open-choice" question. LOINC defines many useful value sets for questionnaire responses. See [LOINC Answer Lists](http://hl7.org/fhir/R4/loinc.html#alist). The value may come from the ElementDefinition referred to by .definition.sdc-questionnaire-behave.item.answerValueSet(xsd)=
	 <#base:canonical>
	 <  unique id for the element within a resource (for internal references); (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the resource. 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 can 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.; (xsd)extension:Extension>*
	 <  Primitive value for canonical; (xsd)value:( <http://hl7.org/fhirpath/System.String:string>
		 | <sdc-questionnaire-behave.item.answerValueSet.value>)>?

🔗  Primitive value for canonicalsdc-questionnaire-behave.item.answerValueSet.value(xsd)=
	 <  unique id for the element within a resource (for internal references); (xsd)id:string>?
	[]<  An Extension; (xsd)extension:Extension>*
	 <  The actual value; (xsd)value:string>?
	 <  An expression that, when evaluated, provides the value for the element on which it appears. For questionnaires, see additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/behavior.html#cqf-expression).; (xsd)answerValueSetExpression:cqf-expression>?

🔗  A constraint indicating that this item should only be enabled (displayed/allow answers to be captured) when the specified condition is true. If multiple repetitions of this extension are present, the item should be enabled when the condition for *any* of the repetitions is true.  I.e. treat "enableWhen"s as being joined by an "or" clause.  This element is a modifier because if enableWhen is present for an item, "required" is ignored unless one of the enableWhen conditions is met. When an item is disabled, all of its descendants are disabled, regardless of what their own enableWhen logic might evaluate to.sdc-questionnaire-behave.item.enableWhen(xsd)=
	 <#base:Questionnaire.item.enableWhen>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  The linkId for the question whose answer (or lack of answer) governs whether this item is enabled. If multiple question occurrences are present for the same question (same linkId), then this refers to the nearest question occurrence reachable by tracing first the "ancestor" axis and then the "preceding" axis and then the "following" axis.; (xsd)question:string>
	 <  Specifies the criteria by which the question is enabled.; (xsd)operator:code>
	 <  A value that the referenced question is tested using the specified operator in order for the item to be enabled.; (xsd)answer:( <boolean>
		 | <Coding>
		 | <date>
		 | <dateTime>
		 | <decimal>
		 | <integer>
		 | <Quantity>
		 | <Resource>
		 | <string>
		 | <time>)>

🔗  One or more values that should be pre-populated in the answer when initially rendering the questionnaire for user input. The user is allowed to change the value and override the default (unless marked as read-only). If the user doesn't change the value, then this initial value will be persisted when the QuestionnaireResponse is initially created.  Note that initial values can influence results.  The data type of initial[x] must agree with the item.type, and only repeating items can have more then one initial value.sdc-questionnaire-behave.item.initial(xsd)=
	 <#base:Questionnaire.item.initial>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 ( <valueAttachment:Attachment>
		 | <valueBoolean:boolean>
		 | <valueCoding:Coding>
		 | <valueDate:date>
		 | <valueDateTime:dateTime>
		 | <valueDecimal:decimal>
		 | <valueInteger:integer>
		 | <valueQuantity:Quantity>
		 | <valueResource:Resource>
		 | <valueString:string>
		 | <valueTime:time>
		 | <valueUri:uri>)

🔗  The maximum number of times the group must appear, or the maximum 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.  See additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/behavior.html#maxOccurs).sdc-questionnaire-behave.item.itemMaxOccurs(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	 <  An Extension; (xsd)extension:Extension>{0,0}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. http://hl7.org/fhir/StructureDefinition/questionnaire-maxOccurs; (xsd)url:string>
	 <  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R5/extensibility.html) for a list).; (xsd)value:sdc-questionnaire-behave.item.itemMaxOccurs.value[x]>

🔗  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R5/extensibility.html) for a list).sdc-questionnaire-behave.item.itemMaxOccurs.value[x](xsd)=
	 <#base:integer>
	 <  unique id for the element within a resource (for internal references); (xsd)id:string>?
	[]<  An Extension; (xsd)extension:Extension>*
	 <  The actual value; (xsd)value:integer>?
	 <  An expression that, when evaluated, provides the value for the element on which it appears. For questionnaires, see additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/behavior.html#cqf-expression).; (xsd)itemMaxOccursExpression:cqf-expression>?

🔗  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.  See additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/behavior.html#minOccurs).sdc-questionnaire-behave.item.itemMinOccurs(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	 <  An Extension; (xsd)extension:Extension>{0,0}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. http://hl7.org/fhir/StructureDefinition/questionnaire-minOccurs; (xsd)url:string>
	 <  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R5/extensibility.html) for a list).; (xsd)value:sdc-questionnaire-behave.item.itemMinOccurs.value[x]>

🔗  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R5/extensibility.html) for a list).sdc-questionnaire-behave.item.itemMinOccurs.value[x](xsd)=
	 <#base:integer>
	 <  unique id for the element within a resource (for internal references); (xsd)id:string>?
	[]<  An Extension; (xsd)extension:Extension>*
	 <  The actual value; (xsd)value:integer>?
	 <  An expression that, when evaluated, provides the value for the element on which it appears. For questionnaires, see additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/behavior.html#cqf-expression).; (xsd)itemMinOccursExpression:cqf-expression>?

🔗  The inclusive upper bound on the range of allowed values for  a 'quantity' type question.  Open Issue: Revisit whether this should be folded into the regular maxValue extension once there are better capabilities around defining conformance expectations regarding extensions. This  must only be used if the set of permitted units is constrained to UCUM codes and the maximum checks will be performed by converting the answer.valueQuantity to the same units as the maxQuantity unit prior to comparison.sdc-questionnaire-behave.item.maxQuantity(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	 <  An Extension; (xsd)extension:Extension>{0,0}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaire-maxQuantity; (xsd)url:string>
	 <  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)value:sdc-questionnaire-behave.item.maxQuantity.value[x]>?

🔗  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).sdc-questionnaire-behave.item.maxQuantity.value[x](xsd)=
	 <#base:Quantity>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	 <  The value of the measured amount. The value includes an implicit precision in the presentation of the value. The implicit precision in the value should always be honored. Monetary values have their own rules for handling precision (refer to standard accounting text books).; (xsd)value:decimal>?
	 <  How the value should be understood and represented - whether the actual value is greater or less than the stated value due to measurement issues; e.g. if the comparator is "<" , then the real value is < stated value.; (xsd)comparator:code>?
	 <  A human-readable form of the unit.; (xsd)unit:string>?
	 <  The identification of the system that provides the coded form of the unit.; (xsd)system:uri>?
	 <  A computer processable form of the unit in some unit representation system. The preferred system is UCUM, but SNOMED CT can also be used (for customary units) or ISO 4217 for currency.  The context of use may additionally require a code from a particular system.; (xsd)code>?
	 <  An expression that determines a calculated value. The expression may be simply the name of a expression in a referenced library, or it may be a complete inline expression. For questionnaires, see additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/behavior.html#cqf-calculatedValue).; (xsd)maxQuantityCalculated:cqf-calculatedValue>?

🔗  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.  For questionnaires, see additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/behavior.html#maxValue).sdc-questionnaire-behave.item.maxValue(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	 <  An Extension; (xsd)extension:Extension>{0,0}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. http://hl7.org/fhir/StructureDefinition/maxValue; (xsd)url:string>
	 <  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R5/extensibility.html) for a list).; (xsd)value:sdc-questionnaire-behave.item.maxValue.value[x]>

🔗  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R5/extensibility.html) for a list).sdc-questionnaire-behave.item.maxValue.value[x](xsd)=
	 <#base:Quantity>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	 <  An expression that determines a calculated value. The expression may be simply the name of a expression in a referenced library, or it may be a complete inline expression. For questionnaires, see additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/behavior.html#cqf-calculatedValue).; (xsd)maxValueCalculated:cqf-calculatedValue>?

🔗  The inclusive lower bound on the range of allowed values for a 'quantity' type question.  Open Issue: Revisit whether this should be folded into the regular minValue extension once there are better capabilities around defining conformance expectations regarding extensions. This  must only be used if the set of permitted units is constrained to UCUM codes and the minimum  checks will be performed by converting the answer.valueQuantity to the same units as the minQuantity unit prior to comparison.sdc-questionnaire-behave.item.minQuantity(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	 <  An Extension; (xsd)extension:Extension>{0,0}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaire-minQuantity; (xsd)url:string>
	 <  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)value:sdc-questionnaire-behave.item.minQuantity.value[x]>?

🔗  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).sdc-questionnaire-behave.item.minQuantity.value[x](xsd)=
	 <#base:Quantity>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	 <  The value of the measured amount. The value includes an implicit precision in the presentation of the value. The implicit precision in the value should always be honored. Monetary values have their own rules for handling precision (refer to standard accounting text books).; (xsd)value:decimal>?
	 <  How the value should be understood and represented - whether the actual value is greater or less than the stated value due to measurement issues; e.g. if the comparator is "<" , then the real value is < stated value.; (xsd)comparator:code>?
	 <  A human-readable form of the unit.; (xsd)unit:string>?
	 <  The identification of the system that provides the coded form of the unit.; (xsd)system:uri>?
	 <  A computer processable form of the unit in some unit representation system. The preferred system is UCUM, but SNOMED CT can also be used (for customary units) or ISO 4217 for currency.  The context of use may additionally require a code from a particular system.; (xsd)code>?
	 <  An expression that determines a calculated value. The expression may be simply the name of a expression in a referenced library, or it may be a complete inline expression. For questionnaires, see additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/behavior.html#cqf-calculatedValue).; (xsd)minQuantityCalculated:cqf-calculatedValue>?

🔗  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.  For questionnaires, see additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/behavior.html#minValue).sdc-questionnaire-behave.item.minValue(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	 <  An Extension; (xsd)extension:Extension>{0,0}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. http://hl7.org/fhir/StructureDefinition/minValue; (xsd)url:string>
	 <  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R5/extensibility.html) for a list).; (xsd)value:sdc-questionnaire-behave.item.minValue.value[x]>

🔗  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R5/extensibility.html) for a list).sdc-questionnaire-behave.item.minValue.value[x](xsd)=
	 <#base:Quantity>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	 <  An expression that determines a calculated value. The expression may be simply the name of a expression in a referenced library, or it may be a complete inline expression. For questionnaires, see additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/behavior.html#cqf-calculatedValue).; (xsd)minValueCalculated:cqf-calculatedValue>?

🔗  An indication, when true, that the value cannot be changed by a human respondent 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.sdc-questionnaire-behave.item.readOnly(xsd)=
	 <#base:boolean>
	 <  unique id for the element within a resource (for internal references); (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the resource. 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 can 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.; (xsd)extension:Extension>*
	 <  The actual value; (xsd)value:( <http://hl7.org/fhirpath/System.Boolean:boolean>
		 | <sdc-questionnaire-behave.item.readOnly.value>)>?

🔗  The actual valuesdc-questionnaire-behave.item.readOnly.value(xsd)=
	 <  unique id for the element within a resource (for internal references); (xsd)id:string>?
	[]<  An Extension; (xsd)extension:Extension>*
	 <  The actual value; (xsd)value:boolean>?
	 <  An expression that, when evaluated, provides the value for the element on which it appears. For questionnaires, see additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/behavior.html#cqf-expression).; (xsd)readOnlyExpression:cqf-expression>?

🔗  An indication, if true, that a QuestionnaireResponse for this item may include multiple answers associated with a single instance of this item (for question-type items) or multiple repetitions of the item (for group-type items) If a question is marked as repeats=true, then multiple answers can be provided for the question in the corresponding QuestionnaireResponse.  When rendering the questionnaire, it is up to the rendering software whether to render the question text for each answer repetition (i.e. "repeat the question") or to simply allow entry/selection of multiple answers for the question (repeat the answers).  Which is most appropriate visually may depend on the type of answer as well as whether there are nested items.

The resulting QuestionnaireResponse will be populated the same way regardless of rendering - one 'question' item with multiple answer values.

 The value may come from the ElementDefinition referred to by .definition.sdc-questionnaire-behave.item.repeats(xsd)=
	 <#base:boolean>
	 <  unique id for the element within a resource (for internal references); (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the resource. 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 can 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.; (xsd)extension:Extension>*
	 <  The actual value; (xsd)value:( <http://hl7.org/fhirpath/System.Boolean:boolean>
		 | <sdc-questionnaire-behave.item.repeats.value>)>?

🔗  The actual valuesdc-questionnaire-behave.item.repeats.value(xsd)=
	 <  unique id for the element within a resource (for internal references); (xsd)id:string>?
	[]<  An Extension; (xsd)extension:Extension>*
	 <  The actual value; (xsd)value:boolean>?
	 <  An expression that, when evaluated, provides the value for the element on which it appears. For questionnaires, see additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/behavior.html#cqf-expression).; (xsd)repeatsExpression:cqf-expression>?

🔗  An indication, if true, that the item must be present in a "completed" QuestionnaireResponse.  If false, the item may be skipped when answering the questionnaire. Questionnaire.item.required only has meaning for elements that are conditionally enabled with enableWhen if the condition evaluates to true.  If an item that contains other items is marked as required, that does not automatically make the contained elements required (though required groups must contain at least one child element). The value may come from the ElementDefinition referred to by .definition.sdc-questionnaire-behave.item.required(xsd)=
	 <#base:boolean>
	 <  unique id for the element within a resource (for internal references); (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the resource. 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 can 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.; (xsd)extension:Extension>*
	 <  The actual value; (xsd)value:( <http://hl7.org/fhirpath/System.Boolean:boolean>
		 | <sdc-questionnaire-behave.item.required.value>)>?

🔗  The actual valuesdc-questionnaire-behave.item.required.value(xsd)=
	 <  unique id for the element within a resource (for internal references); (xsd)id:string>?
	[]<  An Extension; (xsd)extension:Extension>*
	 <  The actual value; (xsd)value:boolean>?
	 <  An expression that, when evaluated, provides the value for the element on which it appears. For questionnaires, see additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/behavior.html#cqf-expression).; (xsd)requiredExpression:cqf-expression>?

🔗  Calculated value for a question answer as determined by an evaluated expression. Calculated value is updated  as other answers in the QuestionnaireResponse are filled in.sdc-questionnaire-calculatedExpression(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	 <  An Extension; (xsd)extension:Extension>{0,0}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaire-calculatedExpression; (xsd)url:string>
	 <  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)value:Expression>

🔗  A FHIRPath or CQL expression, or FHIR Query that resolves to a list of candidate answers for the question item or that establishes context for a group item.  The user may select from among the candidates to choose answers for the question. The results of the expression must correspond to the item type of the question the element appears on or must correspond to a resource, backbone element or complex data type for a group item.  Resources are considered a match for the Reference item type.  Quantity can be a match for decimal and integer items so long as a questionnaire-unit extension is present.  If the expression returns coded data, it **SHALL* return the information as either code or Coding, not CodeableConcept.  If the expression returns elements of type 'code', when the user selects one or more candidates, the code will be matched against the allowed Codings (from answerValueSet, answerOptions, or answerExpresssion).  In this case, it is an error if there is more than one Coding with the same code.sdc-questionnaire-candidateExpression(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	 <  An Extension; (xsd)extension:Extension>{0,0}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaire-candidateExpression; (xsd)url:string>
	 <  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)value:Expression>?

🔗  Indicates whether the child items of a group or question item is displayed in collapsible form.sdc-questionnaire-collapsible(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	 <  An Extension; (xsd)extension:Extension>{0,0}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaire-collapsible; (xsd)url:string>
	 <  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)value:code>?

🔗  For questions with a set of options, indicates the number of columns across which those choices should be organized. E.g., 2 columns, 5 columns, etc. Systems will split the options to maintain balance across the columns. Whether the choices are listed horizontally first or vertically first depends on the choice-orientation extension. Default is vertically first. Note that the number of columns is a recommendation and may not be achievable in all display form factors.sdc-questionnaire-columnCount(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	 <  An Extension; (xsd)extension:Extension>{0,0}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaire-columnCount; (xsd)url:string>
	 <  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)value:positiveInt>?

🔗  A structured set of questions intended to guide the collection of answers from end-users. Questionnaires provide detailed control over order, presentation, phraseology and grouping to allow coherent, consistent data collection.sdc-questionnairecommon(xsd)=
	 <#base:Questionnaire>
	 <  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.; (xsd)id:string>?
	 <  The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.; (xsd)meta:Meta>?
	 <  A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. 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. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.; (xsd)implicitRules:uri>?
	 <  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).; (xsd)language:code>?
	 <  A human-readable narrative that contains a summary of the resource and can 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. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied).  This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.; (xsd)text: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. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.; (xsd)contained:Resource>*
	[]<  An Extension; (xsd)extension:Extension>*
	[]<  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 and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  An absolute URI that is used to identify this questionnaire when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which at which an authoritative instance of this questionnaire is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the questionnaire is stored on different servers. The name of the referenced questionnaire can be conveyed using the http://hl7.org/fhir/StructureDefinition/display extension.; (xsd)url:uri>?
	[]<  A formal identifier that is used to identify this questionnaire when it is represented in other formats, or referenced in a specification, model, design or an instance. Typically, this is used for identifiers that can go in an HL7 V3 II (instance identifier) data type, and can then identify this questionnaire outside of FHIR, where it is not possible to use the logical URI.; (xsd)identifier:Identifier>*
	 <  The identifier that is used to identify this version of the questionnaire when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the questionnaire author and is not expected to be globally unique. For example, it might be a timestamp (e.g. yyyymmdd) if a managed version is not available. There is also no expectation that versions can be placed in a lexicographical sequence. There may be different questionnaire instances that have the same identifier but different versions.  The version can be appended to the url in a reference to allow a reference to a particular business version of the questionnaire with the format [url]|[version].; (xsd)version:string>?
	 <  A natural language name identifying the questionnaire. This name should be usable as an identifier for the module by machine processing applications such as code generation. The name is not expected to be globally unique. The name should be a simple alphanumeric type name to ensure that it is machine-processing friendly.; (xsd)name:string>?
	 <  A short, descriptive, user-friendly title for the questionnaire. This name does not need to be machine-processing friendly and may contain punctuation, white-space, etc.; (xsd)title:string>?
	[]<  The URL of a Questionnaire that this Questionnaire is based on.; (xsd)derivedFrom:canonical>*
	 <  The status of this questionnaire. Enables tracking the life-cycle of the content. Allows filtering of questionnaires that are appropriate for use versus not.; (xsd)status:code>
	 <  A Boolean value to indicate that this questionnaire is authored for testing purposes (or education/evaluation/marketing) and is not intended to be used for genuine usage. Allows filtering of questionnaires that are appropriate for use versus not.; (xsd)experimental:boolean>?
	[]<  The types of subjects that can be the subject of responses created for the questionnaire. If none are specified, then the subject is unlimited.; (xsd)subjectType:code>*
	 <  The date  (and optionally time) when the questionnaire was published. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the questionnaire changes. Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the questionnaire. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource.; (xsd)date:dateTime>?
	 <  The name of the organization or individual that published the questionnaire. Usually an organization but may be an individual. The publisher (or steward) of the questionnaire is the organization or individual primarily responsible for the maintenance and upkeep of the questionnaire. This is not necessarily the same individual or organization that developed and initially authored the content. The publisher is the primary point of contact for questions or issues with the questionnaire. This item SHOULD be populated unless the information is available from context.; (xsd)publisher:string>?
	[]<  Contact details to assist a user in finding and communicating with the publisher. May be a web site, an email address, a telephone number, etc.; (xsd)contact:ContactDetail>*
	 <  A free text natural language description of the questionnaire from a consumer's perspective. This description can be used to capture details such as why the questionnaire was built, comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the questionnaire as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context (e.g. the language of the questionnaire is presumed to be the predominant language in the place the questionnaire was created).; (xsd)description:markdown>?
	[]<  The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate questionnaire instances. When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.; (xsd)useContext:UsageContext>*
	[]<  A legal or geographic region in which the questionnaire is intended to be used. It may be possible for the questionnaire to be used in jurisdictions other than those for which it was originally designed or intended.; (xsd)jurisdiction:CodeableConcept>*
	 <  Explanation of why this questionnaire is needed and why it has been designed as it has. This element does not describe the usage of the questionnaire. Instead, it provides traceability of ''why'' the resource is either needed or ''why'' it is defined as it is.  This may be used to point to source materials or specifications that drove the structure of this questionnaire.; (xsd)purpose:markdown>?
	 <  A copyright statement relating to the questionnaire and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the questionnaire.; (xsd)copyright:markdown>?
	 <  The date on which the resource content was approved by the publisher. Approval happens once when the content is officially approved for usage. The 'date' element may be more recent than the approval date because of minor changes or editorial corrections.; (xsd)approvalDate:date>?
	 <  The date on which the resource content was last reviewed. Review happens periodically after approval but does not change the original approval date. If specified, this date follows the original approval date.; (xsd)lastReviewDate:date>?
	 <  The period during which the questionnaire content was or is planned to be in active use. The effective period for a questionnaire  determines when the content is applicable for usage and is independent of publication and review dates. For example, a measure intended to be used for the year 2016 might be published in 2015.; (xsd)effectivePeriod:Period>?
	[]<  An identifier for this question or group of questions in a particular terminology such as LOINC.; (xsd)code:Coding>*
	[]<  A particular question, question grouping or display text that is part of the questionnaire. The content of the questionnaire is constructed from an ordered, hierarchical collection of items.; (xsd)item:sdc-questionnairecommon.item>*
	 <  Optional Extension Element - found in all resources.; (xsd)versionAlgorithm:Extension>?
	 <  Optional Extension Element - found in all resources.; (xsd)copyrightLabel:Extension>?

🔗  A particular question, question grouping or display text that is part of the questionnaire. The content of the questionnaire is constructed from an ordered, hierarchical collection of items.sdc-questionnairecommon.item(xsd)=
	 <#base:Questionnaire.item>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  An Extension; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  An identifier that is unique within the Questionnaire allowing linkage to the equivalent item in a QuestionnaireResponse resource. This ''can'' be a meaningful identifier (e.g. a LOINC code) but is not intended to have any meaning.  GUIDs or sequential numbers are appropriate here.; (xsd)linkId:string>
	 <  This element is a URI that refers to an [ElementDefinition](http://hl7.org/fhir/R4/elementdefinition.html) that provides information about this item, including information that might otherwise be included in the instance of the Questionnaire resource. A detailed description of the construction of the URI is shown in Comments, below. If this element is present then the following element values MAY be derived from the Element Definition if the corresponding elements of this Questionnaire resource instance have no value:

* code (ElementDefinition.code) 
* type (ElementDefinition.type) 
* required (ElementDefinition.min) 
* repeats (ElementDefinition.max) 
* maxLength (ElementDefinition.maxLength) 
* answerValueSet (ElementDefinition.binding)
* options (ElementDefinition.binding). The uri refers to an ElementDefinition in a [StructureDefinition](http://hl7.org/fhir/R4/structuredefinition.html#) and always starts with the [canonical URL](http://hl7.org/fhir/R4/references.html#canonical) for the target resource. When referring to a StructureDefinition, a fragment identifier is used to specify the element definition by its id [Element.id](http://hl7.org/fhir/R4/element-definitions.html#Element.id). E.g. http://hl7.org/fhir/StructureDefinition/Observation#Observation.value[x]. In the absence of a fragment identifier, the first/root element definition in the target is the matching element definition.; (xsd)definition:uri>?
	[]<  A terminology code that corresponds to this group or question (e.g. a code from LOINC, which defines many questions and answers). The value may come from the ElementDefinition referred to by .definition.; (xsd)code:Coding>*
	 <  A short label for a particular group, question or set of display text within the questionnaire used for reference by the individual completing 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.  Typically, these won't be used for "display" items, though such use is not prohibited.  Systems SHOULD NOT generate their own prefixes if prefixes are defined for any items within a Questionnaire.; (xsd)prefix:string>?
	 <  The name of a section, the text of a question or text content for a display item. When using this element to represent the name of a section, use group type item and also make sure to limit the text element to a short string suitable for display as a section heading.  Group item instructions should be included as a display type item within the group.; (xsd)text:string>?
	 <  The type of questionnaire item this is - whether text for display, a grouping of other items or a particular type of data to be captured (string, integer, coded choice, etc.). Time is handled using "string".  File is handled using Attachment.  (Content can be sent as a contained binary).; (xsd)type:code>
	[]<  A constraint indicating that this item should only be enabled (displayed/allow answers to be captured) when the specified condition is true. If multiple repetitions of this extension are present, the item should be enabled when the condition for *any* of the repetitions is true.  I.e. treat "enableWhen"s as being joined by an "or" clause.  This element is a modifier because if enableWhen is present for an item, "required" is ignored unless one of the enableWhen conditions is met. When an item is disabled, all of its descendants are disabled, regardless of what their own enableWhen logic might evaluate to.; (xsd)enableWhen:sdc-questionnairecommon.item.enableWhen>*
	 <  Controls how multiple enableWhen values are interpreted -  whether all or any must be true. This element must be specified if more than one enableWhen value is provided.; (xsd)enableBehavior:code>?
	 <  An indication, if true, that the item must be present in a "completed" QuestionnaireResponse.  If false, the item may be skipped when answering the questionnaire. Questionnaire.item.required only has meaning for elements that are conditionally enabled with enableWhen if the condition evaluates to true.  If an item that contains other items is marked as required, that does not automatically make the contained elements required (though required groups must contain at least one child element). The value may come from the ElementDefinition referred to by .definition.; (xsd)required:boolean>?
	 <  An indication, if true, that a QuestionnaireResponse for this item may include multiple answers associated with a single instance of this item (for question-type items) or multiple repetitions of the item (for group-type items) If a question is marked as repeats=true, then multiple answers can be provided for the question in the corresponding QuestionnaireResponse.  When rendering the questionnaire, it is up to the rendering software whether to render the question text for each answer repetition (i.e. "repeat the question") or to simply allow entry/selection of multiple answers for the question (repeat the answers).  Which is most appropriate visually may depend on the type of answer as well as whether there are nested items.

The resulting QuestionnaireResponse will be populated the same way regardless of rendering - one 'question' item with multiple answer values.

 The value may come from the ElementDefinition referred to by .definition.; (xsd)repeats:boolean>?
	 <  An indication, when true, that the value cannot be changed by a human respondent 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.; (xsd)readOnly:boolean>?
	 <  The maximum number of characters that are permitted in the answer to be considered a "valid" QuestionnaireResponse. For base64binary, reflects the number of characters representing the encoded data, not the number of bytes of the binary data. The value may come from the ElementDefinition referred to by .definition.; (xsd)maxLength:integer>?
	 <  A reference to a value set containing a list of codes representing permitted answers for a "choice" or "open-choice" question. LOINC defines many useful value sets for questionnaire responses. See [LOINC Answer Lists](http://hl7.org/fhir/R4/loinc.html#alist). The value may come from the ElementDefinition referred to by .definition.; (xsd)answerValueSet:canonical>?
	[]<  One of the permitted answers for a "choice" or "open-choice" question. This element can be used when the value set machinery of answerValueSet is deemed too cumbersome or when there's a need to capture possible answers that are not codes.; (xsd)answerOption:sdc-questionnairecommon.item.answerOption>*
	[]<  One or more values that should be pre-populated in the answer when initially rendering the questionnaire for user input. The user is allowed to change the value and override the default (unless marked as read-only). If the user doesn't change the value, then this initial value will be persisted when the QuestionnaireResponse is initially created.  Note that initial values can influence results.  The data type of initial[x] must agree with the item.type, and only repeating items can have more then one initial value.; (xsd)initial:sdc-questionnairecommon.item.initial>*
	[]<  Text, questions and other groups to be nested beneath a question or group. There is no specified limit to the depth of nesting.  However, Questionnaire authors are encouraged to consider the impact on the user and user interface of overly deep nesting.; (xsd)item:Questionnaire.item>*
	 <  If true, indicates that the extended item should not be displayed to the user. If an item is hidden, all descendant items are hidden as well.  See additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/rendering.html#hidden).; (xsd)hidden:questionnaire-hidden>?
	 <  Optional Extension Element - found in all resources.; (xsd)answerConstraint:Extension>?

🔗  One of the permitted answers for a "choice" or "open-choice" question. This element can be used when the value set machinery of answerValueSet is deemed too cumbersome or when there's a need to capture possible answers that are not codes.sdc-questionnairecommon.item.answerOption(xsd)=
	 <#base:Questionnaire.item.answerOption>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 ( <valueCoding:Coding>
		 | <valueDate:date>
		 | <valueInteger:integer>
		 | <valueResource:Resource>
		 | <valueString:string>
		 | <valueTime:time>)
	 <  Indicates whether the answer value is selected when the list of possible answers is initially shown. Use this instead of initial[v] if answerValueSet is present.; (xsd)initialSelected:boolean>?

🔗  A constraint indicating that this item should only be enabled (displayed/allow answers to be captured) when the specified condition is true. If multiple repetitions of this extension are present, the item should be enabled when the condition for *any* of the repetitions is true.  I.e. treat "enableWhen"s as being joined by an "or" clause.  This element is a modifier because if enableWhen is present for an item, "required" is ignored unless one of the enableWhen conditions is met. When an item is disabled, all of its descendants are disabled, regardless of what their own enableWhen logic might evaluate to.sdc-questionnairecommon.item.enableWhen(xsd)=
	 <#base:Questionnaire.item.enableWhen>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  The linkId for the question whose answer (or lack of answer) governs whether this item is enabled. If multiple question occurrences are present for the same question (same linkId), then this refers to the nearest question occurrence reachable by tracing first the "ancestor" axis and then the "preceding" axis and then the "following" axis.; (xsd)question:string>
	 <  Specifies the criteria by which the question is enabled.; (xsd)operator:code>
	 <  A value that the referenced question is tested using the specified operator in order for the item to be enabled.; (xsd)answer:( <boolean>
		 | <Coding>
		 | <date>
		 | <dateTime>
		 | <decimal>
		 | <integer>
		 | <Quantity>
		 | <Resource>
		 | <string>
		 | <time>)>

🔗  One or more values that should be pre-populated in the answer when initially rendering the questionnaire for user input. The user is allowed to change the value and override the default (unless marked as read-only). If the user doesn't change the value, then this initial value will be persisted when the QuestionnaireResponse is initially created.  Note that initial values can influence results.  The data type of initial[x] must agree with the item.type, and only repeating items can have more then one initial value.sdc-questionnairecommon.item.initial(xsd)=
	 <#base:Questionnaire.item.initial>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 ( <valueAttachment:Attachment>
		 | <valueBoolean:boolean>
		 | <valueCoding:Coding>
		 | <valueDate:date>
		 | <valueDateTime:dateTime>
		 | <valueDecimal:decimal>
		 | <valueInteger:integer>
		 | <valueQuantity:Quantity>
		 | <valueResource:Resource>
		 | <valueString:string>
		 | <valueTime:time>
		 | <valueUri:uri>)

🔗  A FHIR Query that resolves to one or more resources that can be displayed to the user to help provide context for answering a question. For example, if the question is "Has the patient discussed this issue on any visits in the past year?", the contextExpression might return the set of patient's encounters for the prior 12 month period to help jog the practitioner's memory.sdc-questionnaire-contextExpression(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  An Extension; (xsd)extension:Extension>{2,2147483647}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaire-contextExpression; (xsd)url:string>
	 ( <valueAddress:Address>
		 | <valueAge:Age>
		 | <valueAnnotation:Annotation>
		 | <valueAttachment:Attachment>
		 | <valueBase64Binary:base64Binary>
		 | <valueBoolean:boolean>
		 | <valueCanonical:canonical>
		 | <valueCode:code>
		 | <valueCodeableConcept:CodeableConcept>
		 | <valueCoding:Coding>
		 | <valueContactDetail:ContactDetail>
		 | <valueContactPoint:ContactPoint>
		 | <valueContributor:Contributor>
		 | <valueCount:Count>
		 | <valueDataRequirement:DataRequirement>
		 | <valueDate:date>
		 | <valueDateTime:dateTime>
		 | <valueDecimal:decimal>
		 | <valueDistance:Distance>
		 | <valueDosage:Dosage>
		 | <valueDuration:Duration>
		 | <valueExpression:Expression>
		 | <valueHumanName:HumanName>
		 | <valueId:id>
		 | <valueIdentifier:Identifier>
		 | <valueInstant:instant>
		 | <valueInteger:integer>
		 | <valueMarkdown:markdown>
		 | <valueMeta:Meta>
		 | <valueMoney:Money>
		 | <valueOid:oid>
		 | <valueParameterDefinition:ParameterDefinition>
		 | <valuePeriod:Period>
		 | <valuePositiveInt:positiveInt>
		 | <valueQuantity:Quantity>
		 | <valueRange:Range>
		 | <valueRatio:Ratio>
		 | <valueRelatedArtifact:RelatedArtifact>
		 | <valueResource:Resource>
		 | <valueSampledData:SampledData>
		 | <valueSignature:Signature>
		 | <valueString:string>
		 | <valueTime:time>
		 | <valueTiming:Timing>
		 | <valueTriggerDefinition:TriggerDefinition>
		 | <valueUnsignedInt:unsignedInt>
		 | <valueUri:uri>
		 | <valueUrl:url>
		 | <valueUsageContext:UsageContext>
		 | <valueUuid:uuid>){0,0}
	 <  The text to display in the form filler user interface that explains what the returned context information means; (xsd)label:sdc-questionnaire-contextExpression.label>
	 <  The computable rules that identify the contextual information to display to the user; (xsd)expression:sdc-questionnaire-contextExpression.expression>

🔗  The computable rules that identify the contextual information to display to the usersdc-questionnaire-contextExpression.expression(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	 <  An Extension; (xsd)extension:Extension>{0,0}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. expression; (xsd)url:string>
	 <  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)value:Expression>

🔗  The text to display in the form filler user interface that explains what the returned context information meanssdc-questionnaire-contextExpression.label(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	 <  An Extension; (xsd)extension:Extension>{0,0}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. label; (xsd)url:string>
	 <  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)value:string>

🔗  Specifies the resource type/profile for the definition based extraction of a resource and optionally the `fullUrl` and other `Bundle.entry.request` properties as needed.sdc-questionnaire-definitionExtract(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  An Extension; (xsd)extension:Extension>+
	 <  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 SHALL be a URI for the Structure Definition defining the extension. http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaire-definitionExtract; (xsd)url:string>
	 ( <valueAddress:Address>
		 | <valueAge:Age>
		 | <valueAnnotation:Annotation>
		 | <valueAttachment:Attachment>
		 | <valueBase64Binary:base64Binary>
		 | <valueBoolean:boolean>
		 | <valueCanonical:canonical>
		 | <valueCode:code>
		 | <valueCodeableConcept:CodeableConcept>
		 | <valueCoding:Coding>
		 | <valueContactDetail:ContactDetail>
		 | <valueContactPoint:ContactPoint>
		 | <valueContributor:Contributor>
		 | <valueCount:Count>
		 | <valueDataRequirement:DataRequirement>
		 | <valueDate:date>
		 | <valueDateTime:dateTime>
		 | <valueDecimal:decimal>
		 | <valueDistance:Distance>
		 | <valueDosage:Dosage>
		 | <valueDuration:Duration>
		 | <valueExpression:Expression>
		 | <valueHumanName:HumanName>
		 | <valueId:id>
		 | <valueIdentifier:Identifier>
		 | <valueInstant:instant>
		 | <valueInteger:integer>
		 | <valueMarkdown:markdown>
		 | <valueMeta:Meta>
		 | <valueMoney:Money>
		 | <valueOid:oid>
		 | <valueParameterDefinition:ParameterDefinition>
		 | <valuePeriod:Period>
		 | <valuePositiveInt:positiveInt>
		 | <valueQuantity:Quantity>
		 | <valueRange:Range>
		 | <valueRatio:Ratio>
		 | <valueRelatedArtifact:RelatedArtifact>
		 | <valueResource:Resource>
		 | <valueSampledData:SampledData>
		 | <valueSignature:Signature>
		 | <valueString:string>
		 | <valueTime:time>
		 | <valueTiming:Timing>
		 | <valueTriggerDefinition:TriggerDefinition>
		 | <valueUnsignedInt:unsignedInt>
		 | <valueUri:uri>
		 | <valueUrl:url>
		 | <valueUsageContext:UsageContext>
		 | <valueUuid:uuid>){0,0}
	 <  The resource type/profile canonical Url defining the resource type to be extracted. The canonical URL for a base resource can be used if a specific profile is not required, e.g. `http://hl7.org/fhir/StructureDefinition/Patient`.

  The value used here will be the prefix value (before the #) in any child items `definition` value.

  Where a specific profile is used (not the base resource), then this canonical value will be set in the created resource's `meta.profile` collection.; (xsd)definition:sdc-questionnaire-definitionExtract.definition>
	 <  A fhirpath expression to evaluate to extract the value into the fullUrl property. If no value is evaluated, then the element is not extracted.; (xsd)fullUrl:sdc-questionnaire-definitionExtract.fullUrl>?
	 <  A fhirpath expression to evaluate to extract the value into the ifNoneMatch property. If no value is evaluated, then the element is not extracted.; (xsd)ifNoneMatch:sdc-questionnaire-definitionExtract.ifNoneMatch>?
	 <  A fhirpath expression to evaluate to extract the value into the ifModifiedSince property. If no value is evaluated, then the element is not extracted.; (xsd)ifModifiedSince:sdc-questionnaire-definitionExtract.ifModifiedSince>?
	 <  A fhirpath expression to evaluate to extract the value into the ifMatch property. If no value is evaluated, then the element is not extracted.; (xsd)ifMatch:sdc-questionnaire-definitionExtract.ifMatch>?
	 <  A fhirpath expression to evaluate to extract the value into the ifNoneExist property. If no value is evaluated, then the element is not extracted.; (xsd)ifNoneExist:sdc-questionnaire-definitionExtract.ifNoneExist>?

🔗  The resource type/profile canonical Url defining the resource type to be extracted. The canonical URL for a base resource can be used if a specific profile is not required, e.g. `http://hl7.org/fhir/StructureDefinition/Patient`.

  The value used here will be the prefix value (before the #) in any child items `definition` value.

  Where a specific profile is used (not the base resource), then this canonical value will be set in the created resource's `meta.profile` collection.sdc-questionnaire-definitionExtract.definition(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	 <  An Extension; (xsd)extension:Extension>{0,0}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. definition; (xsd)url:string>
	 <  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)value:canonical>

🔗  A fhirpath expression to evaluate to extract the value into the fullUrl property. If no value is evaluated, then the element is not extracted.sdc-questionnaire-definitionExtract.fullUrl(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	 <  An Extension; (xsd)extension:Extension>{0,0}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. fullUrl; (xsd)url:string>
	 <  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)value:string>

🔗  A fhirpath expression to evaluate to extract the value into the ifMatch property. If no value is evaluated, then the element is not extracted.sdc-questionnaire-definitionExtract.ifMatch(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	 <  An Extension; (xsd)extension:Extension>{0,0}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. ifMatch; (xsd)url:string>
	 <  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)value:string>

🔗  A fhirpath expression to evaluate to extract the value into the ifModifiedSince property. If no value is evaluated, then the element is not extracted.sdc-questionnaire-definitionExtract.ifModifiedSince(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	 <  An Extension; (xsd)extension:Extension>{0,0}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. ifModifiedSince; (xsd)url:string>
	 <  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)value:string>

🔗  A fhirpath expression to evaluate to extract the value into the ifNoneExist property. If no value is evaluated, then the element is not extracted.sdc-questionnaire-definitionExtract.ifNoneExist(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	 <  An Extension; (xsd)extension:Extension>{0,0}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. ifNoneExist; (xsd)url:string>
	 <  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)value:string>

🔗  A fhirpath expression to evaluate to extract the value into the ifNoneMatch property. If no value is evaluated, then the element is not extracted.sdc-questionnaire-definitionExtract.ifNoneMatch(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	 <  An Extension; (xsd)extension:Extension>{0,0}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. ifNoneMatch; (xsd)url:string>
	 <  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)value:string>

🔗  Provide either a fixed value, or an expression to evaluate, to be used as the value for the extracted resource's property based on the `definition` value.sdc-questionnaire-definitionExtractValue(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  An Extension; (xsd)extension:Extension>+
	 <  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 SHALL be a URI for the Structure Definition defining the extension. http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaire-definitionExtractValue; (xsd)url:string>
	 ( <valueAddress:Address>
		 | <valueAge:Age>
		 | <valueAnnotation:Annotation>
		 | <valueAttachment:Attachment>
		 | <valueBase64Binary:base64Binary>
		 | <valueBoolean:boolean>
		 | <valueCanonical:canonical>
		 | <valueCode:code>
		 | <valueCodeableConcept:CodeableConcept>
		 | <valueCoding:Coding>
		 | <valueContactDetail:ContactDetail>
		 | <valueContactPoint:ContactPoint>
		 | <valueContributor:Contributor>
		 | <valueCount:Count>
		 | <valueDataRequirement:DataRequirement>
		 | <valueDate:date>
		 | <valueDateTime:dateTime>
		 | <valueDecimal:decimal>
		 | <valueDistance:Distance>
		 | <valueDosage:Dosage>
		 | <valueDuration:Duration>
		 | <valueExpression:Expression>
		 | <valueHumanName:HumanName>
		 | <valueId:id>
		 | <valueIdentifier:Identifier>
		 | <valueInstant:instant>
		 | <valueInteger:integer>
		 | <valueMarkdown:markdown>
		 | <valueMeta:Meta>
		 | <valueMoney:Money>
		 | <valueOid:oid>
		 | <valueParameterDefinition:ParameterDefinition>
		 | <valuePeriod:Period>
		 | <valuePositiveInt:positiveInt>
		 | <valueQuantity:Quantity>
		 | <valueRange:Range>
		 | <valueRatio:Ratio>
		 | <valueRelatedArtifact:RelatedArtifact>
		 | <valueResource:Resource>
		 | <valueSampledData:SampledData>
		 | <valueSignature:Signature>
		 | <valueString:string>
		 | <valueTime:time>
		 | <valueTiming:Timing>
		 | <valueTriggerDefinition:TriggerDefinition>
		 | <valueUnsignedInt:unsignedInt>
		 | <valueUri:uri>
		 | <valueUrl:url>
		 | <valueUsageContext:UsageContext>
		 | <valueUuid:uuid>){0,0}
	 <  This is the profile canonical Url, followed by `#` and the element id, that the value should be extracted into.; (xsd)definition:sdc-questionnaire-definitionExtractValue.definition>
	 <  An expression to evaluate to extract the value into the specified element definition. If no value is evaluated, then the element is not extracted.; (xsd)expression:sdc-questionnaire-definitionExtractValue.expression>?
	 <  A fixed value to extract into the specified element definition.; (xsd)fixed-value:sdc-questionnaire-definitionExtractValue.fixed-value>?

🔗  This is the profile canonical Url, followed by `#` and the element id, that the value should be extracted into.sdc-questionnaire-definitionExtractValue.definition(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	 <  An Extension; (xsd)extension:Extension>{0,0}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. definition; (xsd)url:string>
	 <  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)value:uri>

🔗  An expression to evaluate to extract the value into the specified element definition. If no value is evaluated, then the element is not extracted.sdc-questionnaire-definitionExtractValue.expression(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	 <  An Extension; (xsd)extension:Extension>{0,0}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. expression; (xsd)url:string>
	 <  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)value:Expression>

🔗  A fixed value to extract into the specified element definition.sdc-questionnaire-definitionExtractValue.fixed-value(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	 <  An Extension; (xsd)extension:Extension>{0,0}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. fixed-value; (xsd)url:string>
	 ( <valueAddress:Address>
		 | <valueAge:Age>
		 | <valueAnnotation:Annotation>
		 | <valueAttachment:Attachment>
		 | <valueBase64Binary:base64Binary>
		 | <valueBoolean:boolean>
		 | <valueCanonical:canonical>
		 | <valueCode:code>
		 | <valueCodeableConcept:CodeableConcept>
		 | <valueCoding:Coding>
		 | <valueContactDetail:ContactDetail>
		 | <valueContactPoint:ContactPoint>
		 | <valueContributor:Contributor>
		 | <valueCount:Count>
		 | <valueDataRequirement:DataRequirement>
		 | <valueDate:date>
		 | <valueDateTime:dateTime>
		 | <valueDecimal:decimal>
		 | <valueDistance:Distance>
		 | <valueDosage:Dosage>
		 | <valueDuration:Duration>
		 | <valueExpression:Expression>
		 | <valueHumanName:HumanName>
		 | <valueId:id>
		 | <valueIdentifier:Identifier>
		 | <valueInstant:instant>
		 | <valueInteger:integer>
		 | <valueMarkdown:markdown>
		 | <valueMeta:Meta>
		 | <valueMoney:Money>
		 | <valueOid:oid>
		 | <valueParameterDefinition:ParameterDefinition>
		 | <valuePeriod:Period>
		 | <valuePositiveInt:positiveInt>
		 | <valueQuantity:Quantity>
		 | <valueRange:Range>
		 | <valueRatio:Ratio>
		 | <valueRelatedArtifact:RelatedArtifact>
		 | <valueResource:Resource>
		 | <valueSampledData:SampledData>
		 | <valueSignature:Signature>
		 | <valueString:string>
		 | <valueTime:time>
		 | <valueTiming:Timing>
		 | <valueTriggerDefinition:TriggerDefinition>
		 | <valueUnsignedInt:unsignedInt>
		 | <valueUri:uri>
		 | <valueUrl:url>
		 | <valueUsageContext:UsageContext>
		 | <valueUuid:uuid>)

🔗  An expression that returns a boolean value for whether to enable the item. This is only permitted when the containing item does NOT have any enableWhen elements.

If the expression involves comparisons between elements that have different precisions but are otherwise equal, FHIRPath will resolve the expression to an empty set, which will in turn evaluate to false (meaning the item won't be enabled).  If this is not the desired behavior, the author should add a `.allTrue()` to the end of the expression, which will result in an indeterminate outcome because of precision differences being handled as 'true' and the item being enabled.  Questionnaires SHOULD be designed to take into account challenges around varying precision to minimize non-deterministic situations by setting constraints around expected precision, etc.

If the expression evaluates to something other than a boolean true or false, the Form Filler SHOULD still display the form, and if it does so, SHOULD treat the element as 'enabled' and display a warning to the user that the questionnaire logic was faulty and it's possible that the item shouldn't be enabled.sdc-questionnaire-enableWhenExpression(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	 <  An Extension; (xsd)extension:Extension>{0,0}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaire-enableWhenExpression; (xsd)url:string>
	 <  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)value:Expression>?

🔗  The base URL for the server to which questionnaire response associated with this questionnaire should be submitted. If multiple repetitions are present, the completed form should be sent to all listed endpoints. 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.

Endpoints may have expectations around authorization, etc.  Some of this may be learned by consulting the CapabilityStatement associated with the endpoint.sdc-questionnaire-endpoint(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	 <  An Extension; (xsd)extension:Extension>{0,0}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaire-endpoint; (xsd)url:string>
	 <  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)value:uri>?

🔗  Indicates how questions within the questionnaire should be presented to the end-user.  Specifically, differentiates whether the questions should be displayed one-at-a-time with no ability to adjust prior entries; one-at-a-time or continuously expanding where all questions up to the current question can be looked at and edited, or random, where all questions can be seen and the questions can be filled out in any order desired. The prior-edit functionality can be accomplished by adding questions to the screen as each subsequent question is answered (resulting in all questions being displayed in a single screen) or with a view that shows only one question at a time but allows backward navigation to view and/or edit prior answers.sdc-questionnaire-entryMode(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	 <  An Extension; (xsd)extension:Extension>{0,0}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaire-entryMode; (xsd)url:string>
	 <  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)value:code>?

🔗  Allocate a new uuid in a named variable for use in extraction. This is usually used to set the `fullUrl` for a resource in the output extraction bundle, and then referenced in other resources in that bundle (via fhirpath expressions). The format of the uuid will be `urn:uuid:(uuid)`. e.g. urn:uuid:6f6177d2-13ee-4d27-b0e8-3eaf663dd031sdc-questionnaire-extractAllocateId(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	 <  An Extension; (xsd)extension:Extension>{0,0}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaire-extractAllocateId; (xsd)url:string>
	 <  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)value:string>

🔗  Defines elements that allow conversion of a QuestionnaireResponse to a FHIR resource or Bundle of FHIR resources using the Definition-based extraction mechanism.sdc-questionnaire-extr-defn(xsd)=
	 <#base:sdc-questionnairecommon>
	 <  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.; (xsd)id:string>?
	 <  The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.; (xsd)meta:Meta>?
	 <  A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. 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. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.; (xsd)implicitRules:uri>?
	 <  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).; (xsd)language:code>?
	 <  A human-readable narrative that contains a summary of the resource and can 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. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied).  This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.; (xsd)text: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. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.; (xsd)contained:Resource>*
	[]<  An Extension; (xsd)extension:Extension>*
	[]<  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 and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  An absolute URI that is used to identify this questionnaire when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which at which an authoritative instance of this questionnaire is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the questionnaire is stored on different servers. The name of the referenced questionnaire can be conveyed using the http://hl7.org/fhir/StructureDefinition/display extension.; (xsd)url:uri>?
	[]<  A formal identifier that is used to identify this questionnaire when it is represented in other formats, or referenced in a specification, model, design or an instance. Typically, this is used for identifiers that can go in an HL7 V3 II (instance identifier) data type, and can then identify this questionnaire outside of FHIR, where it is not possible to use the logical URI.; (xsd)identifier:Identifier>*
	 <  The identifier that is used to identify this version of the questionnaire when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the questionnaire author and is not expected to be globally unique. For example, it might be a timestamp (e.g. yyyymmdd) if a managed version is not available. There is also no expectation that versions can be placed in a lexicographical sequence. There may be different questionnaire instances that have the same identifier but different versions.  The version can be appended to the url in a reference to allow a reference to a particular business version of the questionnaire with the format [url]|[version].; (xsd)version:string>?
	 <  A natural language name identifying the questionnaire. This name should be usable as an identifier for the module by machine processing applications such as code generation. The name is not expected to be globally unique. The name should be a simple alphanumeric type name to ensure that it is machine-processing friendly.; (xsd)name:string>?
	 <  A short, descriptive, user-friendly title for the questionnaire. This name does not need to be machine-processing friendly and may contain punctuation, white-space, etc.; (xsd)title:string>?
	[]<  The URL of a Questionnaire that this Questionnaire is based on.; (xsd)derivedFrom:canonical>*
	 <  The status of this questionnaire. Enables tracking the life-cycle of the content. Allows filtering of questionnaires that are appropriate for use versus not.; (xsd)status:code>
	 <  A Boolean value to indicate that this questionnaire is authored for testing purposes (or education/evaluation/marketing) and is not intended to be used for genuine usage. Allows filtering of questionnaires that are appropriate for use versus not.; (xsd)experimental:boolean>?
	[]<  The types of subjects that can be the subject of responses created for the questionnaire. If none are specified, then the subject is unlimited.; (xsd)subjectType:code>*
	 <  The date  (and optionally time) when the questionnaire was published. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the questionnaire changes. Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the questionnaire. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource.; (xsd)date:dateTime>?
	 <  The name of the organization or individual that published the questionnaire. Usually an organization but may be an individual. The publisher (or steward) of the questionnaire is the organization or individual primarily responsible for the maintenance and upkeep of the questionnaire. This is not necessarily the same individual or organization that developed and initially authored the content. The publisher is the primary point of contact for questions or issues with the questionnaire. This item SHOULD be populated unless the information is available from context.; (xsd)publisher:string>?
	[]<  Contact details to assist a user in finding and communicating with the publisher. May be a web site, an email address, a telephone number, etc.; (xsd)contact:ContactDetail>*
	 <  A free text natural language description of the questionnaire from a consumer's perspective. This description can be used to capture details such as why the questionnaire was built, comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the questionnaire as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context (e.g. the language of the questionnaire is presumed to be the predominant language in the place the questionnaire was created).; (xsd)description:markdown>?
	[]<  The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate questionnaire instances. When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.; (xsd)useContext:UsageContext>*
	[]<  A legal or geographic region in which the questionnaire is intended to be used. It may be possible for the questionnaire to be used in jurisdictions other than those for which it was originally designed or intended.; (xsd)jurisdiction:CodeableConcept>*
	 <  Explanation of why this questionnaire is needed and why it has been designed as it has. This element does not describe the usage of the questionnaire. Instead, it provides traceability of ''why'' the resource is either needed or ''why'' it is defined as it is.  This may be used to point to source materials or specifications that drove the structure of this questionnaire.; (xsd)purpose:markdown>?
	 <  A copyright statement relating to the questionnaire and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the questionnaire.; (xsd)copyright:markdown>?
	 <  The date on which the resource content was approved by the publisher. Approval happens once when the content is officially approved for usage. The 'date' element may be more recent than the approval date because of minor changes or editorial corrections.; (xsd)approvalDate:date>?
	 <  The date on which the resource content was last reviewed. Review happens periodically after approval but does not change the original approval date. If specified, this date follows the original approval date.; (xsd)lastReviewDate:date>?
	 <  The period during which the questionnaire content was or is planned to be in active use. The effective period for a questionnaire  determines when the content is applicable for usage and is independent of publication and review dates. For example, a measure intended to be used for the year 2016 might be published in 2015.; (xsd)effectivePeriod:Period>?
	[]<  An identifier for this question or group of questions in a particular terminology such as LOINC.; (xsd)code:Coding>*
	[]<  A particular question, question grouping or display text that is part of the questionnaire. The content of the questionnaire is constructed from an ordered, hierarchical collection of items.; (xsd)item:sdc-questionnaire-extr-defn.item>*
	 <  Optional Extension Element - found in all resources.; (xsd)versionAlgorithm:Extension>?
	 <  Optional Extension Element - found in all resources.; (xsd)copyrightLabel:Extension>?
	 <  Specifies the resource type/profile for the definition based extraction of a resource and optionally the `fullUrl` and other `Bundle.entry.request` properties as needed.; (xsd)definitionExtract:sdc-questionnaire-definitionExtract>?
	[]<  Provide either a fixed value, or an expression to evaluate, to be used as the value for the extracted resource's property based on the `definition` value.; (xsd)definitionExtractValue:sdc-questionnaire-definitionExtractValue>*
	[]<  Allocate a new uuid in a named variable for use in extraction. This is usually used to set the `fullUrl` for a resource in the output extraction bundle, and then referenced in other resources in that bundle (via fhirpath expressions). The format of the uuid will be `urn:uuid:(uuid)`. e.g. urn:uuid:6f6177d2-13ee-4d27-b0e8-3eaf663dd031; (xsd)extractAllocateId:sdc-questionnaire-extractAllocateId>*
	[]<  A reference to a library containing cql used in this Questionnaire. For questionnaires, see additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/behavior.html#cqf-library).; (xsd)library:cqf-library>*

🔗  A particular question, question grouping or display text that is part of the questionnaire. The content of the questionnaire is constructed from an ordered, hierarchical collection of items.sdc-questionnaire-extr-defn.item(xsd)=
	 <#base:Questionnaire.item>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  An Extension; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  An identifier that is unique within the Questionnaire allowing linkage to the equivalent item in a QuestionnaireResponse resource. This ''can'' be a meaningful identifier (e.g. a LOINC code) but is not intended to have any meaning.  GUIDs or sequential numbers are appropriate here.; (xsd)linkId:string>
	 <  This element is a URI that refers to an [ElementDefinition](http://hl7.org/fhir/R4/elementdefinition.html) that provides information about this item, including information that might otherwise be included in the instance of the Questionnaire resource. A detailed description of the construction of the URI is shown in Comments, below. If this element is present then the following element values MAY be derived from the Element Definition if the corresponding elements of this Questionnaire resource instance have no value:

* code (ElementDefinition.code) 
* type (ElementDefinition.type) 
* required (ElementDefinition.min) 
* repeats (ElementDefinition.max) 
* maxLength (ElementDefinition.maxLength) 
* answerValueSet (ElementDefinition.binding)
* options (ElementDefinition.binding). The uri refers to an ElementDefinition in a [StructureDefinition](http://hl7.org/fhir/R4/structuredefinition.html#) and always starts with the [canonical URL](http://hl7.org/fhir/R4/references.html#canonical) for the target resource. When referring to a StructureDefinition, a fragment identifier is used to specify the element definition by its id [Element.id](http://hl7.org/fhir/R4/element-definitions.html#Element.id). E.g. http://hl7.org/fhir/StructureDefinition/Observation#Observation.value[x]. In the absence of a fragment identifier, the first/root element definition in the target is the matching element definition.; (xsd)definition:uri>?
	[]<  A terminology code that corresponds to this group or question (e.g. a code from LOINC, which defines many questions and answers). The value may come from the ElementDefinition referred to by .definition.; (xsd)code:Coding>*
	 <  A short label for a particular group, question or set of display text within the questionnaire used for reference by the individual completing 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.  Typically, these won't be used for "display" items, though such use is not prohibited.  Systems SHOULD NOT generate their own prefixes if prefixes are defined for any items within a Questionnaire.; (xsd)prefix:string>?
	 <  The name of a section, the text of a question or text content for a display item. When using this element to represent the name of a section, use group type item and also make sure to limit the text element to a short string suitable for display as a section heading.  Group item instructions should be included as a display type item within the group.; (xsd)text:string>?
	 <  The type of questionnaire item this is - whether text for display, a grouping of other items or a particular type of data to be captured (string, integer, coded choice, etc.). Time is handled using "string".  File is handled using Attachment.  (Content can be sent as a contained binary).; (xsd)type:code>
	[]<  A constraint indicating that this item should only be enabled (displayed/allow answers to be captured) when the specified condition is true. If multiple repetitions of this extension are present, the item should be enabled when the condition for *any* of the repetitions is true.  I.e. treat "enableWhen"s as being joined by an "or" clause.  This element is a modifier because if enableWhen is present for an item, "required" is ignored unless one of the enableWhen conditions is met. When an item is disabled, all of its descendants are disabled, regardless of what their own enableWhen logic might evaluate to.; (xsd)enableWhen:sdc-questionnaire-extr-defn.item.enableWhen>*
	 <  Controls how multiple enableWhen values are interpreted -  whether all or any must be true. This element must be specified if more than one enableWhen value is provided.; (xsd)enableBehavior:code>?
	 <  An indication, if true, that the item must be present in a "completed" QuestionnaireResponse.  If false, the item may be skipped when answering the questionnaire. Questionnaire.item.required only has meaning for elements that are conditionally enabled with enableWhen if the condition evaluates to true.  If an item that contains other items is marked as required, that does not automatically make the contained elements required (though required groups must contain at least one child element). The value may come from the ElementDefinition referred to by .definition.; (xsd)required:boolean>?
	 <  An indication, if true, that a QuestionnaireResponse for this item may include multiple answers associated with a single instance of this item (for question-type items) or multiple repetitions of the item (for group-type items) If a question is marked as repeats=true, then multiple answers can be provided for the question in the corresponding QuestionnaireResponse.  When rendering the questionnaire, it is up to the rendering software whether to render the question text for each answer repetition (i.e. "repeat the question") or to simply allow entry/selection of multiple answers for the question (repeat the answers).  Which is most appropriate visually may depend on the type of answer as well as whether there are nested items.

The resulting QuestionnaireResponse will be populated the same way regardless of rendering - one 'question' item with multiple answer values.

 The value may come from the ElementDefinition referred to by .definition.; (xsd)repeats:boolean>?
	 <  An indication, when true, that the value cannot be changed by a human respondent 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.; (xsd)readOnly:boolean>?
	 <  The maximum number of characters that are permitted in the answer to be considered a "valid" QuestionnaireResponse. For base64binary, reflects the number of characters representing the encoded data, not the number of bytes of the binary data. The value may come from the ElementDefinition referred to by .definition.; (xsd)maxLength:integer>?
	 <  A reference to a value set containing a list of codes representing permitted answers for a "choice" or "open-choice" question. LOINC defines many useful value sets for questionnaire responses. See [LOINC Answer Lists](http://hl7.org/fhir/R4/loinc.html#alist). The value may come from the ElementDefinition referred to by .definition.; (xsd)answerValueSet:canonical>?
	[]<  One of the permitted answers for a "choice" or "open-choice" question. This element can be used when the value set machinery of answerValueSet is deemed too cumbersome or when there's a need to capture possible answers that are not codes.; (xsd)answerOption:sdc-questionnaire-extr-defn.item.answerOption>*
	[]<  One or more values that should be pre-populated in the answer when initially rendering the questionnaire for user input. The user is allowed to change the value and override the default (unless marked as read-only). If the user doesn't change the value, then this initial value will be persisted when the QuestionnaireResponse is initially created.  Note that initial values can influence results.  The data type of initial[x] must agree with the item.type, and only repeating items can have more then one initial value.; (xsd)initial:sdc-questionnaire-extr-defn.item.initial>*
	[]<  Text, questions and other groups to be nested beneath a question or group. There is no specified limit to the depth of nesting.  However, Questionnaire authors are encouraged to consider the impact on the user and user interface of overly deep nesting.; (xsd)item:Questionnaire.item>*
	 <  If true, indicates that the extended item should not be displayed to the user. If an item is hidden, all descendant items are hidden as well.  See additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/rendering.html#hidden).; (xsd)hidden:questionnaire-hidden>?
	 <  Optional Extension Element - found in all resources.; (xsd)answerConstraint:Extension>?
	[]<  Specifies the resource type/profile for the definition based extraction of a resource and optionally the `fullUrl` and other `Bundle.entry.request` properties as needed.; (xsd)definitionExtract:sdc-questionnaire-definitionExtract>*
	[]<  Provide either a fixed value, or an expression to evaluate, to be used as the value for the extracted resource's property based on the `definition` value.; (xsd)definitionExtractValue:sdc-questionnaire-definitionExtractValue>*
	[]<  Allocate a new uuid in a named variable for use in extraction. This is usually used to set the `fullUrl` for a resource in the output extraction bundle, and then referenced in other resources in that bundle (via fhirpath expressions). The format of the uuid will be `urn:uuid:(uuid)`. e.g. urn:uuid:6f6177d2-13ee-4d27-b0e8-3eaf663dd031; (xsd)extractAllocateId:sdc-questionnaire-extractAllocateId>*
	 <  Provides a computable unit of measure associated with numeric questions to support subsequent computation on responses. This is for use on items of type integer and decimal, and it's purpose is to support converting the integer or decimal answer into a Quantity when extracting the data into a resource. The human-readable unit is conveyed as a display element.  This element is for computation purposes.; (xsd)unit:questionnaire-unit>?

🔗  One of the permitted answers for a "choice" or "open-choice" question. This element can be used when the value set machinery of answerValueSet is deemed too cumbersome or when there's a need to capture possible answers that are not codes.sdc-questionnaire-extr-defn.item.answerOption(xsd)=
	 <#base:Questionnaire.item.answerOption>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 ( <valueCoding:Coding>
		 | <valueDate:date>
		 | <valueInteger:integer>
		 | <valueResource:Resource>
		 | <valueString:string>
		 | <valueTime:time>)
	 <  Indicates whether the answer value is selected when the list of possible answers is initially shown. Use this instead of initial[v] if answerValueSet is present.; (xsd)initialSelected:boolean>?

🔗  A constraint indicating that this item should only be enabled (displayed/allow answers to be captured) when the specified condition is true. If multiple repetitions of this extension are present, the item should be enabled when the condition for *any* of the repetitions is true.  I.e. treat "enableWhen"s as being joined by an "or" clause.  This element is a modifier because if enableWhen is present for an item, "required" is ignored unless one of the enableWhen conditions is met. When an item is disabled, all of its descendants are disabled, regardless of what their own enableWhen logic might evaluate to.sdc-questionnaire-extr-defn.item.enableWhen(xsd)=
	 <#base:Questionnaire.item.enableWhen>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  The linkId for the question whose answer (or lack of answer) governs whether this item is enabled. If multiple question occurrences are present for the same question (same linkId), then this refers to the nearest question occurrence reachable by tracing first the "ancestor" axis and then the "preceding" axis and then the "following" axis.; (xsd)question:string>
	 <  Specifies the criteria by which the question is enabled.; (xsd)operator:code>
	 <  A value that the referenced question is tested using the specified operator in order for the item to be enabled.; (xsd)answer:( <boolean>
		 | <Coding>
		 | <date>
		 | <dateTime>
		 | <decimal>
		 | <integer>
		 | <Quantity>
		 | <Resource>
		 | <string>
		 | <time>)>

🔗  One or more values that should be pre-populated in the answer when initially rendering the questionnaire for user input. The user is allowed to change the value and override the default (unless marked as read-only). If the user doesn't change the value, then this initial value will be persisted when the QuestionnaireResponse is initially created.  Note that initial values can influence results.  The data type of initial[x] must agree with the item.type, and only repeating items can have more then one initial value.sdc-questionnaire-extr-defn.item.initial(xsd)=
	 <#base:Questionnaire.item.initial>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 ( <valueAttachment:Attachment>
		 | <valueBoolean:boolean>
		 | <valueCoding:Coding>
		 | <valueDate:date>
		 | <valueDateTime:dateTime>
		 | <valueDecimal:decimal>
		 | <valueInteger:integer>
		 | <valueQuantity:Quantity>
		 | <valueResource:Resource>
		 | <valueString:string>
		 | <valueTime:time>
		 | <valueUri:uri>)

🔗  Defines elements that allow conversion of a QuestionnaireResponse to an Observation resource or Bundle of Observation resources using the Observation-based extraction mechanism.sdc-questionnaire-extr-obsn(xsd)=
	 <#base:sdc-questionnairecommon>
	 <  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.; (xsd)id:string>?
	 <  The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.; (xsd)meta:Meta>?
	 <  A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. 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. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.; (xsd)implicitRules:uri>?
	 <  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).; (xsd)language:code>?
	 <  A human-readable narrative that contains a summary of the resource and can 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. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied).  This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.; (xsd)text: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. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.; (xsd)contained:Resource>*
	[]<  An Extension; (xsd)extension:Extension>*
	[]<  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 and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  An absolute URI that is used to identify this questionnaire when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which at which an authoritative instance of this questionnaire is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the questionnaire is stored on different servers. The name of the referenced questionnaire can be conveyed using the http://hl7.org/fhir/StructureDefinition/display extension.; (xsd)url:uri>?
	[]<  A formal identifier that is used to identify this questionnaire when it is represented in other formats, or referenced in a specification, model, design or an instance. Typically, this is used for identifiers that can go in an HL7 V3 II (instance identifier) data type, and can then identify this questionnaire outside of FHIR, where it is not possible to use the logical URI.; (xsd)identifier:Identifier>*
	 <  The identifier that is used to identify this version of the questionnaire when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the questionnaire author and is not expected to be globally unique. For example, it might be a timestamp (e.g. yyyymmdd) if a managed version is not available. There is also no expectation that versions can be placed in a lexicographical sequence. There may be different questionnaire instances that have the same identifier but different versions.  The version can be appended to the url in a reference to allow a reference to a particular business version of the questionnaire with the format [url]|[version].; (xsd)version:string>?
	 <  A natural language name identifying the questionnaire. This name should be usable as an identifier for the module by machine processing applications such as code generation. The name is not expected to be globally unique. The name should be a simple alphanumeric type name to ensure that it is machine-processing friendly.; (xsd)name:string>?
	 <  A short, descriptive, user-friendly title for the questionnaire. This name does not need to be machine-processing friendly and may contain punctuation, white-space, etc.; (xsd)title:string>?
	[]<  The URL of a Questionnaire that this Questionnaire is based on.; (xsd)derivedFrom:canonical>*
	 <  The status of this questionnaire. Enables tracking the life-cycle of the content. Allows filtering of questionnaires that are appropriate for use versus not.; (xsd)status:code>
	 <  A Boolean value to indicate that this questionnaire is authored for testing purposes (or education/evaluation/marketing) and is not intended to be used for genuine usage. Allows filtering of questionnaires that are appropriate for use versus not.; (xsd)experimental:boolean>?
	[]<  The types of subjects that can be the subject of responses created for the questionnaire. If none are specified, then the subject is unlimited.; (xsd)subjectType:code>*
	 <  The date  (and optionally time) when the questionnaire was published. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the questionnaire changes. Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the questionnaire. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource.; (xsd)date:dateTime>?
	 <  The name of the organization or individual that published the questionnaire. Usually an organization but may be an individual. The publisher (or steward) of the questionnaire is the organization or individual primarily responsible for the maintenance and upkeep of the questionnaire. This is not necessarily the same individual or organization that developed and initially authored the content. The publisher is the primary point of contact for questions or issues with the questionnaire. This item SHOULD be populated unless the information is available from context.; (xsd)publisher:string>?
	[]<  Contact details to assist a user in finding and communicating with the publisher. May be a web site, an email address, a telephone number, etc.; (xsd)contact:ContactDetail>*
	 <  A free text natural language description of the questionnaire from a consumer's perspective. This description can be used to capture details such as why the questionnaire was built, comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the questionnaire as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context (e.g. the language of the questionnaire is presumed to be the predominant language in the place the questionnaire was created).; (xsd)description:markdown>?
	[]<  The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate questionnaire instances. When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.; (xsd)useContext:UsageContext>*
	[]<  A legal or geographic region in which the questionnaire is intended to be used. It may be possible for the questionnaire to be used in jurisdictions other than those for which it was originally designed or intended.; (xsd)jurisdiction:CodeableConcept>*
	 <  Explanation of why this questionnaire is needed and why it has been designed as it has. This element does not describe the usage of the questionnaire. Instead, it provides traceability of ''why'' the resource is either needed or ''why'' it is defined as it is.  This may be used to point to source materials or specifications that drove the structure of this questionnaire.; (xsd)purpose:markdown>?
	 <  A copyright statement relating to the questionnaire and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the questionnaire.; (xsd)copyright:markdown>?
	 <  The date on which the resource content was approved by the publisher. Approval happens once when the content is officially approved for usage. The 'date' element may be more recent than the approval date because of minor changes or editorial corrections.; (xsd)approvalDate:date>?
	 <  The date on which the resource content was last reviewed. Review happens periodically after approval but does not change the original approval date. If specified, this date follows the original approval date.; (xsd)lastReviewDate:date>?
	 <  The period during which the questionnaire content was or is planned to be in active use. The effective period for a questionnaire  determines when the content is applicable for usage and is independent of publication and review dates. For example, a measure intended to be used for the year 2016 might be published in 2015.; (xsd)effectivePeriod:Period>?
	[]<  An identifier for this question or group of questions in a particular terminology such as LOINC.; (xsd)code:Coding>*
	[]<  A particular question, question grouping or display text that is part of the questionnaire. The content of the questionnaire is constructed from an ordered, hierarchical collection of items.; (xsd)item:sdc-questionnaire-extr-obsn.item>*
	 <  Optional Extension Element - found in all resources.; (xsd)versionAlgorithm:Extension>?
	 <  Optional Extension Element - found in all resources.; (xsd)copyrightLabel:Extension>?
	 <  Indicates how the observation-based extraction approach should be applied to an item or all items in a questionnaire. When set to `true`, the item is extracted as an independent Observation with no relationship to a parent Observation (If true, indicates that the observation-based approach should be used to extract either the particular item (if extension is defined on an individual question or group based on the code present) or all items in the questionnaire (if defined at the questionnaire root and if they have a code present)). When set to a `code` value (e.g., `member` or `component`), the extracted Observation is related to a parent Observation according to the specified relationship. Mixing `boolean` and `code` values within the same item is invalid and will result in an error. This extension canot be specified on "display" items.; (xsd)observationExtract:sdc-questionnaire-observationExtract>?

🔗  A particular question, question grouping or display text that is part of the questionnaire. The content of the questionnaire is constructed from an ordered, hierarchical collection of items.sdc-questionnaire-extr-obsn.item(xsd)=
	 <#base:Questionnaire.item>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  An Extension; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  An identifier that is unique within the Questionnaire allowing linkage to the equivalent item in a QuestionnaireResponse resource. This ''can'' be a meaningful identifier (e.g. a LOINC code) but is not intended to have any meaning.  GUIDs or sequential numbers are appropriate here.; (xsd)linkId:string>
	 <  This element is a URI that refers to an [ElementDefinition](http://hl7.org/fhir/R4/elementdefinition.html) that provides information about this item, including information that might otherwise be included in the instance of the Questionnaire resource. A detailed description of the construction of the URI is shown in Comments, below. If this element is present then the following element values MAY be derived from the Element Definition if the corresponding elements of this Questionnaire resource instance have no value:

* code (ElementDefinition.code) 
* type (ElementDefinition.type) 
* required (ElementDefinition.min) 
* repeats (ElementDefinition.max) 
* maxLength (ElementDefinition.maxLength) 
* answerValueSet (ElementDefinition.binding)
* options (ElementDefinition.binding). The uri refers to an ElementDefinition in a [StructureDefinition](http://hl7.org/fhir/R4/structuredefinition.html#) and always starts with the [canonical URL](http://hl7.org/fhir/R4/references.html#canonical) for the target resource. When referring to a StructureDefinition, a fragment identifier is used to specify the element definition by its id [Element.id](http://hl7.org/fhir/R4/element-definitions.html#Element.id). E.g. http://hl7.org/fhir/StructureDefinition/Observation#Observation.value[x]. In the absence of a fragment identifier, the first/root element definition in the target is the matching element definition.; (xsd)definition:uri>?
	[]<  A terminology code that corresponds to this group or question (e.g. a code from LOINC, which defines many questions and answers). The value may come from the ElementDefinition referred to by .definition.; (xsd)code:sdc-questionnaire-extr-obsn.item.code>*
	 <  A short label for a particular group, question or set of display text within the questionnaire used for reference by the individual completing 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.  Typically, these won't be used for "display" items, though such use is not prohibited.  Systems SHOULD NOT generate their own prefixes if prefixes are defined for any items within a Questionnaire.; (xsd)prefix:string>?
	 <  The name of a section, the text of a question or text content for a display item. When using this element to represent the name of a section, use group type item and also make sure to limit the text element to a short string suitable for display as a section heading.  Group item instructions should be included as a display type item within the group.; (xsd)text:string>?
	 <  The type of questionnaire item this is - whether text for display, a grouping of other items or a particular type of data to be captured (string, integer, coded choice, etc.). Time is handled using "string".  File is handled using Attachment.  (Content can be sent as a contained binary).; (xsd)type:code>
	[]<  A constraint indicating that this item should only be enabled (displayed/allow answers to be captured) when the specified condition is true. If multiple repetitions of this extension are present, the item should be enabled when the condition for *any* of the repetitions is true.  I.e. treat "enableWhen"s as being joined by an "or" clause.  This element is a modifier because if enableWhen is present for an item, "required" is ignored unless one of the enableWhen conditions is met. When an item is disabled, all of its descendants are disabled, regardless of what their own enableWhen logic might evaluate to.; (xsd)enableWhen:sdc-questionnaire-extr-obsn.item.enableWhen>*
	 <  Controls how multiple enableWhen values are interpreted -  whether all or any must be true. This element must be specified if more than one enableWhen value is provided.; (xsd)enableBehavior:code>?
	 <  An indication, if true, that the item must be present in a "completed" QuestionnaireResponse.  If false, the item may be skipped when answering the questionnaire. Questionnaire.item.required only has meaning for elements that are conditionally enabled with enableWhen if the condition evaluates to true.  If an item that contains other items is marked as required, that does not automatically make the contained elements required (though required groups must contain at least one child element). The value may come from the ElementDefinition referred to by .definition.; (xsd)required:boolean>?
	 <  An indication, if true, that a QuestionnaireResponse for this item may include multiple answers associated with a single instance of this item (for question-type items) or multiple repetitions of the item (for group-type items) If a question is marked as repeats=true, then multiple answers can be provided for the question in the corresponding QuestionnaireResponse.  When rendering the questionnaire, it is up to the rendering software whether to render the question text for each answer repetition (i.e. "repeat the question") or to simply allow entry/selection of multiple answers for the question (repeat the answers).  Which is most appropriate visually may depend on the type of answer as well as whether there are nested items.

The resulting QuestionnaireResponse will be populated the same way regardless of rendering - one 'question' item with multiple answer values.

 The value may come from the ElementDefinition referred to by .definition.; (xsd)repeats:boolean>?
	 <  An indication, when true, that the value cannot be changed by a human respondent 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.; (xsd)readOnly:boolean>?
	 <  The maximum number of characters that are permitted in the answer to be considered a "valid" QuestionnaireResponse. For base64binary, reflects the number of characters representing the encoded data, not the number of bytes of the binary data. The value may come from the ElementDefinition referred to by .definition.; (xsd)maxLength:integer>?
	 <  A reference to a value set containing a list of codes representing permitted answers for a "choice" or "open-choice" question. LOINC defines many useful value sets for questionnaire responses. See [LOINC Answer Lists](http://hl7.org/fhir/R4/loinc.html#alist). The value may come from the ElementDefinition referred to by .definition.; (xsd)answerValueSet:canonical>?
	[]<  One of the permitted answers for a "choice" or "open-choice" question. This element can be used when the value set machinery of answerValueSet is deemed too cumbersome or when there's a need to capture possible answers that are not codes.; (xsd)answerOption:sdc-questionnaire-extr-obsn.item.answerOption>*
	[]<  One or more values that should be pre-populated in the answer when initially rendering the questionnaire for user input. The user is allowed to change the value and override the default (unless marked as read-only). If the user doesn't change the value, then this initial value will be persisted when the QuestionnaireResponse is initially created.  Note that initial values can influence results.  The data type of initial[x] must agree with the item.type, and only repeating items can have more then one initial value.; (xsd)initial:sdc-questionnaire-extr-obsn.item.initial>*
	[]<  Text, questions and other groups to be nested beneath a question or group. There is no specified limit to the depth of nesting.  However, Questionnaire authors are encouraged to consider the impact on the user and user interface of overly deep nesting.; (xsd)item:Questionnaire.item>*
	 <  If true, indicates that the extended item should not be displayed to the user. If an item is hidden, all descendant items are hidden as well.  See additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/rendering.html#hidden).; (xsd)hidden:questionnaire-hidden>?
	 <  Optional Extension Element - found in all resources.; (xsd)answerConstraint:Extension>?
	 <  Provides a computable unit of measure associated with numeric questions to support subsequent computation on responses. This is for use on items of type integer and decimal, and it's purpose is to support converting the integer or decimal answer into a Quantity when extracting the data into a resource. The human-readable unit is conveyed as a display element.  This element is for computation purposes.; (xsd)unit:questionnaire-unit>?
	 <  Indicates how the observation-based extraction approach should be applied to an item or all items in a questionnaire. When set to `true`, the item is extracted as an independent Observation with no relationship to a parent Observation (If true, indicates that the observation-based approach should be used to extract either the particular item (if extension is defined on an individual question or group based on the code present) or all items in the questionnaire (if defined at the questionnaire root and if they have a code present)). When set to a `code` value (e.g., `member` or `component`), the extracted Observation is related to a parent Observation according to the specified relationship. Mixing `boolean` and `code` values within the same item is invalid and will result in an error. This extension canot be specified on "display" items.; (xsd)observationExtract:sdc-questionnaire-observationExtract>?
	[]<  Indicates the Observation.category value(s) that should appear on extracted Observations for the entire Questionnaire or for the current item and descendant items.  If this extension appears at multiple levels in the Questionnaire, those defined on lower-level items override those declared on higher-level items. This extension canot be specified on "display" items.; (xsd)observationExtractCategory:sdc-questionnaire-observation-extract-category>*
	 <  If present and true, indicates that the item establishes a different subject for the group in a response. The item type must be "reference" and there can only be one item with this extension in each group.; (xsd)isSubject:sdc-questionnaire-isSubject>?

🔗  One of the permitted answers for a "choice" or "open-choice" question. This element can be used when the value set machinery of answerValueSet is deemed too cumbersome or when there's a need to capture possible answers that are not codes.sdc-questionnaire-extr-obsn.item.answerOption(xsd)=
	 <#base:Questionnaire.item.answerOption>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 ( <valueCoding:Coding>
		 | <valueDate:date>
		 | <valueInteger:integer>
		 | <valueResource:Resource>
		 | <valueString:string>
		 | <valueTime:time>)
	 <  Indicates whether the answer value is selected when the list of possible answers is initially shown. Use this instead of initial[v] if answerValueSet is present.; (xsd)initialSelected:boolean>?

🔗  A terminology code that corresponds to this group or question (e.g. a code from LOINC, which defines many questions and answers). The value may come from the ElementDefinition referred to by .definition.sdc-questionnaire-extr-obsn.item.code(xsd)=
	 <#base:Coding>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	 <  The identification of the code system that defines the meaning of the symbol in the code. The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...).  OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously.; (xsd)system:uri>?
	 <  The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.; (xsd)version:string>?
	 <  A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).; (xsd)code>?
	 <  A representation of the meaning of the code in the system, following the rules of the system.; (xsd)display:string>?
	 <  Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.; (xsd)userSelected:boolean>?
	 <  Indicates how the observation-based extraction approach should be applied to an item or all items in a questionnaire. When set to `true`, the item is extracted as an independent Observation with no relationship to a parent Observation (If true, indicates that the observation-based approach should be used to extract either the particular item (if extension is defined on an individual question or group based on the code present) or all items in the questionnaire (if defined at the questionnaire root and if they have a code present)). When set to a `code` value (e.g., `member` or `component`), the extracted Observation is related to a parent Observation according to the specified relationship. Mixing `boolean` and `code` values within the same item is invalid and will result in an error. This extension canot be specified on "display" items.; (xsd)observationExtract:sdc-questionnaire-observationExtract>?

🔗  A constraint indicating that this item should only be enabled (displayed/allow answers to be captured) when the specified condition is true. If multiple repetitions of this extension are present, the item should be enabled when the condition for *any* of the repetitions is true.  I.e. treat "enableWhen"s as being joined by an "or" clause.  This element is a modifier because if enableWhen is present for an item, "required" is ignored unless one of the enableWhen conditions is met. When an item is disabled, all of its descendants are disabled, regardless of what their own enableWhen logic might evaluate to.sdc-questionnaire-extr-obsn.item.enableWhen(xsd)=
	 <#base:Questionnaire.item.enableWhen>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  The linkId for the question whose answer (or lack of answer) governs whether this item is enabled. If multiple question occurrences are present for the same question (same linkId), then this refers to the nearest question occurrence reachable by tracing first the "ancestor" axis and then the "preceding" axis and then the "following" axis.; (xsd)question:string>
	 <  Specifies the criteria by which the question is enabled.; (xsd)operator:code>
	 <  A value that the referenced question is tested using the specified operator in order for the item to be enabled.; (xsd)answer:( <boolean>
		 | <Coding>
		 | <date>
		 | <dateTime>
		 | <decimal>
		 | <integer>
		 | <Quantity>
		 | <Resource>
		 | <string>
		 | <time>)>

🔗  One or more values that should be pre-populated in the answer when initially rendering the questionnaire for user input. The user is allowed to change the value and override the default (unless marked as read-only). If the user doesn't change the value, then this initial value will be persisted when the QuestionnaireResponse is initially created.  Note that initial values can influence results.  The data type of initial[x] must agree with the item.type, and only repeating items can have more then one initial value.sdc-questionnaire-extr-obsn.item.initial(xsd)=
	 <#base:Questionnaire.item.initial>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 ( <valueAttachment:Attachment>
		 | <valueBoolean:boolean>
		 | <valueCoding:Coding>
		 | <valueDate:date>
		 | <valueDateTime:dateTime>
		 | <valueDecimal:decimal>
		 | <valueInteger:integer>
		 | <valueQuantity:Quantity>
		 | <valueResource:Resource>
		 | <valueString:string>
		 | <valueTime:time>
		 | <valueUri:uri>)

🔗  Defines elements that allow conversion of a QuestionnaireResponse to a FHIR resource or Bundle of FHIR resources using the StructureMap-based extraction mechanism.sdc-questionnaire-extr-smap(xsd)=
	 <#base:sdc-questionnairecommon>
	 <  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.; (xsd)id:string>?
	 <  The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.; (xsd)meta:Meta>?
	 <  A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. 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. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.; (xsd)implicitRules:uri>?
	 <  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).; (xsd)language:code>?
	 <  A human-readable narrative that contains a summary of the resource and can 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. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied).  This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.; (xsd)text: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. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.; (xsd)contained:Resource>*
	[]<  An Extension; (xsd)extension:Extension>*
	[]<  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 and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  An absolute URI that is used to identify this questionnaire when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which at which an authoritative instance of this questionnaire is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the questionnaire is stored on different servers. The name of the referenced questionnaire can be conveyed using the http://hl7.org/fhir/StructureDefinition/display extension.; (xsd)url:uri>?
	[]<  A formal identifier that is used to identify this questionnaire when it is represented in other formats, or referenced in a specification, model, design or an instance. Typically, this is used for identifiers that can go in an HL7 V3 II (instance identifier) data type, and can then identify this questionnaire outside of FHIR, where it is not possible to use the logical URI.; (xsd)identifier:Identifier>*
	 <  The identifier that is used to identify this version of the questionnaire when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the questionnaire author and is not expected to be globally unique. For example, it might be a timestamp (e.g. yyyymmdd) if a managed version is not available. There is also no expectation that versions can be placed in a lexicographical sequence. There may be different questionnaire instances that have the same identifier but different versions.  The version can be appended to the url in a reference to allow a reference to a particular business version of the questionnaire with the format [url]|[version].; (xsd)version:string>?
	 <  A natural language name identifying the questionnaire. This name should be usable as an identifier for the module by machine processing applications such as code generation. The name is not expected to be globally unique. The name should be a simple alphanumeric type name to ensure that it is machine-processing friendly.; (xsd)name:string>?
	 <  A short, descriptive, user-friendly title for the questionnaire. This name does not need to be machine-processing friendly and may contain punctuation, white-space, etc.; (xsd)title:string>?
	[]<  The URL of a Questionnaire that this Questionnaire is based on.; (xsd)derivedFrom:canonical>*
	 <  The status of this questionnaire. Enables tracking the life-cycle of the content. Allows filtering of questionnaires that are appropriate for use versus not.; (xsd)status:code>
	 <  A Boolean value to indicate that this questionnaire is authored for testing purposes (or education/evaluation/marketing) and is not intended to be used for genuine usage. Allows filtering of questionnaires that are appropriate for use versus not.; (xsd)experimental:boolean>?
	[]<  The types of subjects that can be the subject of responses created for the questionnaire. If none are specified, then the subject is unlimited.; (xsd)subjectType:code>*
	 <  The date  (and optionally time) when the questionnaire was published. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the questionnaire changes. Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the questionnaire. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource.; (xsd)date:dateTime>?
	 <  The name of the organization or individual that published the questionnaire. Usually an organization but may be an individual. The publisher (or steward) of the questionnaire is the organization or individual primarily responsible for the maintenance and upkeep of the questionnaire. This is not necessarily the same individual or organization that developed and initially authored the content. The publisher is the primary point of contact for questions or issues with the questionnaire. This item SHOULD be populated unless the information is available from context.; (xsd)publisher:string>?
	[]<  Contact details to assist a user in finding and communicating with the publisher. May be a web site, an email address, a telephone number, etc.; (xsd)contact:ContactDetail>*
	 <  A free text natural language description of the questionnaire from a consumer's perspective. This description can be used to capture details such as why the questionnaire was built, comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the questionnaire as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context (e.g. the language of the questionnaire is presumed to be the predominant language in the place the questionnaire was created).; (xsd)description:markdown>?
	[]<  The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate questionnaire instances. When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.; (xsd)useContext:UsageContext>*
	[]<  A legal or geographic region in which the questionnaire is intended to be used. It may be possible for the questionnaire to be used in jurisdictions other than those for which it was originally designed or intended.; (xsd)jurisdiction:CodeableConcept>*
	 <  Explanation of why this questionnaire is needed and why it has been designed as it has. This element does not describe the usage of the questionnaire. Instead, it provides traceability of ''why'' the resource is either needed or ''why'' it is defined as it is.  This may be used to point to source materials or specifications that drove the structure of this questionnaire.; (xsd)purpose:markdown>?
	 <  A copyright statement relating to the questionnaire and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the questionnaire.; (xsd)copyright:markdown>?
	 <  The date on which the resource content was approved by the publisher. Approval happens once when the content is officially approved for usage. The 'date' element may be more recent than the approval date because of minor changes or editorial corrections.; (xsd)approvalDate:date>?
	 <  The date on which the resource content was last reviewed. Review happens periodically after approval but does not change the original approval date. If specified, this date follows the original approval date.; (xsd)lastReviewDate:date>?
	 <  The period during which the questionnaire content was or is planned to be in active use. The effective period for a questionnaire  determines when the content is applicable for usage and is independent of publication and review dates. For example, a measure intended to be used for the year 2016 might be published in 2015.; (xsd)effectivePeriod:Period>?
	[]<  An identifier for this question or group of questions in a particular terminology such as LOINC.; (xsd)code:Coding>*
	[]<  A particular question, question grouping or display text that is part of the questionnaire. The content of the questionnaire is constructed from an ordered, hierarchical collection of items.; (xsd)item:sdc-questionnaire-extr-smap.item>*
	 <  Optional Extension Element - found in all resources.; (xsd)versionAlgorithm:Extension>?
	 <  Optional Extension Element - found in all resources.; (xsd)copyrightLabel:Extension>?
	[]<  StructureMaps that have QuestionnaireResponses of this Questionnaire as 'source'- i.e. that can be used to create other artifacts from QuestionnaireResponses that are valid against this Questionnaire.; (xsd)targetStructureMap:sdc-questionnaire-targetStructureMap>*

🔗  A particular question, question grouping or display text that is part of the questionnaire. The content of the questionnaire is constructed from an ordered, hierarchical collection of items.sdc-questionnaire-extr-smap.item(xsd)=
	 <#base:Questionnaire.item>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  An Extension; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  An identifier that is unique within the Questionnaire allowing linkage to the equivalent item in a QuestionnaireResponse resource. This ''can'' be a meaningful identifier (e.g. a LOINC code) but is not intended to have any meaning.  GUIDs or sequential numbers are appropriate here.; (xsd)linkId:string>
	 <  This element is a URI that refers to an [ElementDefinition](http://hl7.org/fhir/R4/elementdefinition.html) that provides information about this item, including information that might otherwise be included in the instance of the Questionnaire resource. A detailed description of the construction of the URI is shown in Comments, below. If this element is present then the following element values MAY be derived from the Element Definition if the corresponding elements of this Questionnaire resource instance have no value:

* code (ElementDefinition.code) 
* type (ElementDefinition.type) 
* required (ElementDefinition.min) 
* repeats (ElementDefinition.max) 
* maxLength (ElementDefinition.maxLength) 
* answerValueSet (ElementDefinition.binding)
* options (ElementDefinition.binding). The uri refers to an ElementDefinition in a [StructureDefinition](http://hl7.org/fhir/R4/structuredefinition.html#) and always starts with the [canonical URL](http://hl7.org/fhir/R4/references.html#canonical) for the target resource. When referring to a StructureDefinition, a fragment identifier is used to specify the element definition by its id [Element.id](http://hl7.org/fhir/R4/element-definitions.html#Element.id). E.g. http://hl7.org/fhir/StructureDefinition/Observation#Observation.value[x]. In the absence of a fragment identifier, the first/root element definition in the target is the matching element definition.; (xsd)definition:uri>?
	[]<  A terminology code that corresponds to this group or question (e.g. a code from LOINC, which defines many questions and answers). The value may come from the ElementDefinition referred to by .definition.; (xsd)code:Coding>*
	 <  A short label for a particular group, question or set of display text within the questionnaire used for reference by the individual completing 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.  Typically, these won't be used for "display" items, though such use is not prohibited.  Systems SHOULD NOT generate their own prefixes if prefixes are defined for any items within a Questionnaire.; (xsd)prefix:string>?
	 <  The name of a section, the text of a question or text content for a display item. When using this element to represent the name of a section, use group type item and also make sure to limit the text element to a short string suitable for display as a section heading.  Group item instructions should be included as a display type item within the group.; (xsd)text:string>?
	 <  The type of questionnaire item this is - whether text for display, a grouping of other items or a particular type of data to be captured (string, integer, coded choice, etc.). Time is handled using "string".  File is handled using Attachment.  (Content can be sent as a contained binary).; (xsd)type:code>
	[]<  A constraint indicating that this item should only be enabled (displayed/allow answers to be captured) when the specified condition is true. If multiple repetitions of this extension are present, the item should be enabled when the condition for *any* of the repetitions is true.  I.e. treat "enableWhen"s as being joined by an "or" clause.  This element is a modifier because if enableWhen is present for an item, "required" is ignored unless one of the enableWhen conditions is met. When an item is disabled, all of its descendants are disabled, regardless of what their own enableWhen logic might evaluate to.; (xsd)enableWhen:sdc-questionnaire-extr-smap.item.enableWhen>*
	 <  Controls how multiple enableWhen values are interpreted -  whether all or any must be true. This element must be specified if more than one enableWhen value is provided.; (xsd)enableBehavior:code>?
	 <  An indication, if true, that the item must be present in a "completed" QuestionnaireResponse.  If false, the item may be skipped when answering the questionnaire. Questionnaire.item.required only has meaning for elements that are conditionally enabled with enableWhen if the condition evaluates to true.  If an item that contains other items is marked as required, that does not automatically make the contained elements required (though required groups must contain at least one child element). The value may come from the ElementDefinition referred to by .definition.; (xsd)required:boolean>?
	 <  An indication, if true, that a QuestionnaireResponse for this item may include multiple answers associated with a single instance of this item (for question-type items) or multiple repetitions of the item (for group-type items) If a question is marked as repeats=true, then multiple answers can be provided for the question in the corresponding QuestionnaireResponse.  When rendering the questionnaire, it is up to the rendering software whether to render the question text for each answer repetition (i.e. "repeat the question") or to simply allow entry/selection of multiple answers for the question (repeat the answers).  Which is most appropriate visually may depend on the type of answer as well as whether there are nested items.

The resulting QuestionnaireResponse will be populated the same way regardless of rendering - one 'question' item with multiple answer values.

 The value may come from the ElementDefinition referred to by .definition.; (xsd)repeats:boolean>?
	 <  An indication, when true, that the value cannot be changed by a human respondent 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.; (xsd)readOnly:boolean>?
	 <  The maximum number of characters that are permitted in the answer to be considered a "valid" QuestionnaireResponse. For base64binary, reflects the number of characters representing the encoded data, not the number of bytes of the binary data. The value may come from the ElementDefinition referred to by .definition.; (xsd)maxLength:integer>?
	 <  A reference to a value set containing a list of codes representing permitted answers for a "choice" or "open-choice" question. LOINC defines many useful value sets for questionnaire responses. See [LOINC Answer Lists](http://hl7.org/fhir/R4/loinc.html#alist). The value may come from the ElementDefinition referred to by .definition.; (xsd)answerValueSet:canonical>?
	[]<  One of the permitted answers for a "choice" or "open-choice" question. This element can be used when the value set machinery of answerValueSet is deemed too cumbersome or when there's a need to capture possible answers that are not codes.; (xsd)answerOption:sdc-questionnaire-extr-smap.item.answerOption>*
	[]<  One or more values that should be pre-populated in the answer when initially rendering the questionnaire for user input. The user is allowed to change the value and override the default (unless marked as read-only). If the user doesn't change the value, then this initial value will be persisted when the QuestionnaireResponse is initially created.  Note that initial values can influence results.  The data type of initial[x] must agree with the item.type, and only repeating items can have more then one initial value.; (xsd)initial:sdc-questionnaire-extr-smap.item.initial>*
	[]<  Text, questions and other groups to be nested beneath a question or group. There is no specified limit to the depth of nesting.  However, Questionnaire authors are encouraged to consider the impact on the user and user interface of overly deep nesting.; (xsd)item:Questionnaire.item>*
	 <  If true, indicates that the extended item should not be displayed to the user. If an item is hidden, all descendant items are hidden as well.  See additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/rendering.html#hidden).; (xsd)hidden:questionnaire-hidden>?
	 <  Optional Extension Element - found in all resources.; (xsd)answerConstraint:Extension>?
	 <  Provides a computable unit of measure associated with numeric questions to support subsequent computation on responses. This is for use on items of type integer and decimal, and it's purpose is to support converting the integer or decimal answer into a Quantity when extracting the data into a resource. The human-readable unit is conveyed as a display element.  This element is for computation purposes.; (xsd)unit:questionnaire-unit>?
	 <  If true, indicates that the extended item should not be displayed to the user. If an item is hidden, all descendant items are hidden as well.  See additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/rendering.html#hidden).; (xsd)itemHidden:questionnaire-hidden>?

🔗  One of the permitted answers for a "choice" or "open-choice" question. This element can be used when the value set machinery of answerValueSet is deemed too cumbersome or when there's a need to capture possible answers that are not codes.sdc-questionnaire-extr-smap.item.answerOption(xsd)=
	 <#base:Questionnaire.item.answerOption>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 ( <valueCoding:Coding>
		 | <valueDate:date>
		 | <valueInteger:integer>
		 | <valueResource:Resource>
		 | <valueString:string>
		 | <valueTime:time>)
	 <  Indicates whether the answer value is selected when the list of possible answers is initially shown. Use this instead of initial[v] if answerValueSet is present.; (xsd)initialSelected:boolean>?

🔗  A constraint indicating that this item should only be enabled (displayed/allow answers to be captured) when the specified condition is true. If multiple repetitions of this extension are present, the item should be enabled when the condition for *any* of the repetitions is true.  I.e. treat "enableWhen"s as being joined by an "or" clause.  This element is a modifier because if enableWhen is present for an item, "required" is ignored unless one of the enableWhen conditions is met. When an item is disabled, all of its descendants are disabled, regardless of what their own enableWhen logic might evaluate to.sdc-questionnaire-extr-smap.item.enableWhen(xsd)=
	 <#base:Questionnaire.item.enableWhen>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  The linkId for the question whose answer (or lack of answer) governs whether this item is enabled. If multiple question occurrences are present for the same question (same linkId), then this refers to the nearest question occurrence reachable by tracing first the "ancestor" axis and then the "preceding" axis and then the "following" axis.; (xsd)question:string>
	 <  Specifies the criteria by which the question is enabled.; (xsd)operator:code>
	 <  A value that the referenced question is tested using the specified operator in order for the item to be enabled.; (xsd)answer:( <boolean>
		 | <Coding>
		 | <date>
		 | <dateTime>
		 | <decimal>
		 | <integer>
		 | <Quantity>
		 | <Resource>
		 | <string>
		 | <time>)>

🔗  One or more values that should be pre-populated in the answer when initially rendering the questionnaire for user input. The user is allowed to change the value and override the default (unless marked as read-only). If the user doesn't change the value, then this initial value will be persisted when the QuestionnaireResponse is initially created.  Note that initial values can influence results.  The data type of initial[x] must agree with the item.type, and only repeating items can have more then one initial value.sdc-questionnaire-extr-smap.item.initial(xsd)=
	 <#base:Questionnaire.item.initial>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 ( <valueAttachment:Attachment>
		 | <valueBoolean:boolean>
		 | <valueCoding:Coding>
		 | <valueDate:date>
		 | <valueDateTime:dateTime>
		 | <valueDecimal:decimal>
		 | <valueInteger:integer>
		 | <valueQuantity:Quantity>
		 | <valueResource:Resource>
		 | <valueString:string>
		 | <valueTime:time>
		 | <valueUri:uri>)

🔗  Defines elements that allow conversion of a QuestionnaireResponse to a FHIR resource or Bundle of FHIR resources using the Template-based extraction mechanism.sdc-questionnaire-extr-template(xsd)=
	 <#base:sdc-questionnairecommon>
	 <  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.; (xsd)id:string>?
	 <  The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.; (xsd)meta:Meta>?
	 <  A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. 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. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.; (xsd)implicitRules:uri>?
	 <  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).; (xsd)language:code>?
	 <  A human-readable narrative that contains a summary of the resource and can 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. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied).  This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.; (xsd)text: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. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.; (xsd)contained:Resource>+
	[]<  An Extension; (xsd)extension:Extension>*
	[]<  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 and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  An absolute URI that is used to identify this questionnaire when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which at which an authoritative instance of this questionnaire is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the questionnaire is stored on different servers. The name of the referenced questionnaire can be conveyed using the http://hl7.org/fhir/StructureDefinition/display extension.; (xsd)url:uri>?
	[]<  A formal identifier that is used to identify this questionnaire when it is represented in other formats, or referenced in a specification, model, design or an instance. Typically, this is used for identifiers that can go in an HL7 V3 II (instance identifier) data type, and can then identify this questionnaire outside of FHIR, where it is not possible to use the logical URI.; (xsd)identifier:Identifier>*
	 <  The identifier that is used to identify this version of the questionnaire when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the questionnaire author and is not expected to be globally unique. For example, it might be a timestamp (e.g. yyyymmdd) if a managed version is not available. There is also no expectation that versions can be placed in a lexicographical sequence. There may be different questionnaire instances that have the same identifier but different versions.  The version can be appended to the url in a reference to allow a reference to a particular business version of the questionnaire with the format [url]|[version].; (xsd)version:string>?
	 <  A natural language name identifying the questionnaire. This name should be usable as an identifier for the module by machine processing applications such as code generation. The name is not expected to be globally unique. The name should be a simple alphanumeric type name to ensure that it is machine-processing friendly.; (xsd)name:string>?
	 <  A short, descriptive, user-friendly title for the questionnaire. This name does not need to be machine-processing friendly and may contain punctuation, white-space, etc.; (xsd)title:string>?
	[]<  The URL of a Questionnaire that this Questionnaire is based on.; (xsd)derivedFrom:canonical>*
	 <  The status of this questionnaire. Enables tracking the life-cycle of the content. Allows filtering of questionnaires that are appropriate for use versus not.; (xsd)status:code>
	 <  A Boolean value to indicate that this questionnaire is authored for testing purposes (or education/evaluation/marketing) and is not intended to be used for genuine usage. Allows filtering of questionnaires that are appropriate for use versus not.; (xsd)experimental:boolean>?
	[]<  The types of subjects that can be the subject of responses created for the questionnaire. If none are specified, then the subject is unlimited.; (xsd)subjectType:code>*
	 <  The date  (and optionally time) when the questionnaire was published. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the questionnaire changes. Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the questionnaire. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource.; (xsd)date:dateTime>?
	 <  The name of the organization or individual that published the questionnaire. Usually an organization but may be an individual. The publisher (or steward) of the questionnaire is the organization or individual primarily responsible for the maintenance and upkeep of the questionnaire. This is not necessarily the same individual or organization that developed and initially authored the content. The publisher is the primary point of contact for questions or issues with the questionnaire. This item SHOULD be populated unless the information is available from context.; (xsd)publisher:string>?
	[]<  Contact details to assist a user in finding and communicating with the publisher. May be a web site, an email address, a telephone number, etc.; (xsd)contact:ContactDetail>*
	 <  A free text natural language description of the questionnaire from a consumer's perspective. This description can be used to capture details such as why the questionnaire was built, comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the questionnaire as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context (e.g. the language of the questionnaire is presumed to be the predominant language in the place the questionnaire was created).; (xsd)description:markdown>?
	[]<  The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate questionnaire instances. When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.; (xsd)useContext:UsageContext>*
	[]<  A legal or geographic region in which the questionnaire is intended to be used. It may be possible for the questionnaire to be used in jurisdictions other than those for which it was originally designed or intended.; (xsd)jurisdiction:CodeableConcept>*
	 <  Explanation of why this questionnaire is needed and why it has been designed as it has. This element does not describe the usage of the questionnaire. Instead, it provides traceability of ''why'' the resource is either needed or ''why'' it is defined as it is.  This may be used to point to source materials or specifications that drove the structure of this questionnaire.; (xsd)purpose:markdown>?
	 <  A copyright statement relating to the questionnaire and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the questionnaire.; (xsd)copyright:markdown>?
	 <  The date on which the resource content was approved by the publisher. Approval happens once when the content is officially approved for usage. The 'date' element may be more recent than the approval date because of minor changes or editorial corrections.; (xsd)approvalDate:date>?
	 <  The date on which the resource content was last reviewed. Review happens periodically after approval but does not change the original approval date. If specified, this date follows the original approval date.; (xsd)lastReviewDate:date>?
	 <  The period during which the questionnaire content was or is planned to be in active use. The effective period for a questionnaire  determines when the content is applicable for usage and is independent of publication and review dates. For example, a measure intended to be used for the year 2016 might be published in 2015.; (xsd)effectivePeriod:Period>?
	[]<  An identifier for this question or group of questions in a particular terminology such as LOINC.; (xsd)code:Coding>*
	[]<  A particular question, question grouping or display text that is part of the questionnaire. The content of the questionnaire is constructed from an ordered, hierarchical collection of items.; (xsd)item:sdc-questionnaire-extr-template.item>*
	 <  Optional Extension Element - found in all resources.; (xsd)versionAlgorithm:Extension>?
	 <  Optional Extension Element - found in all resources.; (xsd)copyrightLabel:Extension>?
	[]<  Specifies a reference to a contained resource template (or set of resources for a repeating item) to be extracted from this item once the QuestionnaireResponse is complete.; (xsd)templateExtract:sdc-questionnaire-templateExtract>*
	[]<  Specifies a reference to a contained resource template to be extracted from this item once the QuestionnaireResponse is complete.; (xsd)templateExtractBundle:sdc-questionnaire-templateExtractBundle>*
	[]<  If value is of type 'string', then it is to be evaluated as a fhirpath expression. If a value of type 'Expression' is provided, only fhirpath expressions are supported, and the language MAY be omitted.; (xsd)extractContext:sdc-questionnaire-templateExtractContext>*
	[]<  Allocate a new uuid in a named variable for use in extraction. This is usually used to set the `fullUrl` for a resource in the output extraction bundle, and then referenced in other resources in that bundle (via fhirpath expressions). The format of the uuid will be `urn:uuid:(uuid)`. e.g. urn:uuid:6f6177d2-13ee-4d27-b0e8-3eaf663dd031; (xsd)extractAllocateId:sdc-questionnaire-extractAllocateId>*

🔗  A particular question, question grouping or display text that is part of the questionnaire. The content of the questionnaire is constructed from an ordered, hierarchical collection of items.sdc-questionnaire-extr-template.item(xsd)=
	 <#base:Questionnaire.item>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  An Extension; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  An identifier that is unique within the Questionnaire allowing linkage to the equivalent item in a QuestionnaireResponse resource. This ''can'' be a meaningful identifier (e.g. a LOINC code) but is not intended to have any meaning.  GUIDs or sequential numbers are appropriate here.; (xsd)linkId:string>
	 <  This element is a URI that refers to an [ElementDefinition](http://hl7.org/fhir/R4/elementdefinition.html) that provides information about this item, including information that might otherwise be included in the instance of the Questionnaire resource. A detailed description of the construction of the URI is shown in Comments, below. If this element is present then the following element values MAY be derived from the Element Definition if the corresponding elements of this Questionnaire resource instance have no value:

* code (ElementDefinition.code) 
* type (ElementDefinition.type) 
* required (ElementDefinition.min) 
* repeats (ElementDefinition.max) 
* maxLength (ElementDefinition.maxLength) 
* answerValueSet (ElementDefinition.binding)
* options (ElementDefinition.binding). The uri refers to an ElementDefinition in a [StructureDefinition](http://hl7.org/fhir/R4/structuredefinition.html#) and always starts with the [canonical URL](http://hl7.org/fhir/R4/references.html#canonical) for the target resource. When referring to a StructureDefinition, a fragment identifier is used to specify the element definition by its id [Element.id](http://hl7.org/fhir/R4/element-definitions.html#Element.id). E.g. http://hl7.org/fhir/StructureDefinition/Observation#Observation.value[x]. In the absence of a fragment identifier, the first/root element definition in the target is the matching element definition.; (xsd)definition:uri>?
	[]<  A terminology code that corresponds to this group or question (e.g. a code from LOINC, which defines many questions and answers). The value may come from the ElementDefinition referred to by .definition.; (xsd)code:Coding>*
	 <  A short label for a particular group, question or set of display text within the questionnaire used for reference by the individual completing 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.  Typically, these won't be used for "display" items, though such use is not prohibited.  Systems SHOULD NOT generate their own prefixes if prefixes are defined for any items within a Questionnaire.; (xsd)prefix:string>?
	 <  The name of a section, the text of a question or text content for a display item. When using this element to represent the name of a section, use group type item and also make sure to limit the text element to a short string suitable for display as a section heading.  Group item instructions should be included as a display type item within the group.; (xsd)text:string>?
	 <  The type of questionnaire item this is - whether text for display, a grouping of other items or a particular type of data to be captured (string, integer, coded choice, etc.). Time is handled using "string".  File is handled using Attachment.  (Content can be sent as a contained binary).; (xsd)type:code>
	[]<  A constraint indicating that this item should only be enabled (displayed/allow answers to be captured) when the specified condition is true. If multiple repetitions of this extension are present, the item should be enabled when the condition for *any* of the repetitions is true.  I.e. treat "enableWhen"s as being joined by an "or" clause.  This element is a modifier because if enableWhen is present for an item, "required" is ignored unless one of the enableWhen conditions is met. When an item is disabled, all of its descendants are disabled, regardless of what their own enableWhen logic might evaluate to.; (xsd)enableWhen:sdc-questionnaire-extr-template.item.enableWhen>*
	 <  Controls how multiple enableWhen values are interpreted -  whether all or any must be true. This element must be specified if more than one enableWhen value is provided.; (xsd)enableBehavior:code>?
	 <  An indication, if true, that the item must be present in a "completed" QuestionnaireResponse.  If false, the item may be skipped when answering the questionnaire. Questionnaire.item.required only has meaning for elements that are conditionally enabled with enableWhen if the condition evaluates to true.  If an item that contains other items is marked as required, that does not automatically make the contained elements required (though required groups must contain at least one child element). The value may come from the ElementDefinition referred to by .definition.; (xsd)required:boolean>?
	 <  An indication, if true, that a QuestionnaireResponse for this item may include multiple answers associated with a single instance of this item (for question-type items) or multiple repetitions of the item (for group-type items) If a question is marked as repeats=true, then multiple answers can be provided for the question in the corresponding QuestionnaireResponse.  When rendering the questionnaire, it is up to the rendering software whether to render the question text for each answer repetition (i.e. "repeat the question") or to simply allow entry/selection of multiple answers for the question (repeat the answers).  Which is most appropriate visually may depend on the type of answer as well as whether there are nested items.

The resulting QuestionnaireResponse will be populated the same way regardless of rendering - one 'question' item with multiple answer values.

 The value may come from the ElementDefinition referred to by .definition.; (xsd)repeats:boolean>?
	 <  An indication, when true, that the value cannot be changed by a human respondent 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.; (xsd)readOnly:boolean>?
	 <  The maximum number of characters that are permitted in the answer to be considered a "valid" QuestionnaireResponse. For base64binary, reflects the number of characters representing the encoded data, not the number of bytes of the binary data. The value may come from the ElementDefinition referred to by .definition.; (xsd)maxLength:integer>?
	 <  A reference to a value set containing a list of codes representing permitted answers for a "choice" or "open-choice" question. LOINC defines many useful value sets for questionnaire responses. See [LOINC Answer Lists](http://hl7.org/fhir/R4/loinc.html#alist). The value may come from the ElementDefinition referred to by .definition.; (xsd)answerValueSet:canonical>?
	[]<  One of the permitted answers for a "choice" or "open-choice" question. This element can be used when the value set machinery of answerValueSet is deemed too cumbersome or when there's a need to capture possible answers that are not codes.; (xsd)answerOption:sdc-questionnaire-extr-template.item.answerOption>*
	[]<  One or more values that should be pre-populated in the answer when initially rendering the questionnaire for user input. The user is allowed to change the value and override the default (unless marked as read-only). If the user doesn't change the value, then this initial value will be persisted when the QuestionnaireResponse is initially created.  Note that initial values can influence results.  The data type of initial[x] must agree with the item.type, and only repeating items can have more then one initial value.; (xsd)initial:sdc-questionnaire-extr-template.item.initial>*
	[]<  Text, questions and other groups to be nested beneath a question or group. There is no specified limit to the depth of nesting.  However, Questionnaire authors are encouraged to consider the impact on the user and user interface of overly deep nesting.; (xsd)item:Questionnaire.item>*
	 <  If true, indicates that the extended item should not be displayed to the user. If an item is hidden, all descendant items are hidden as well.  See additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/rendering.html#hidden).; (xsd)hidden:questionnaire-hidden>?
	 <  Optional Extension Element - found in all resources.; (xsd)answerConstraint:Extension>?
	[]<  Specifies a reference to a contained resource template (or set of resources for a repeating item) to be extracted from this item once the QuestionnaireResponse is complete.; (xsd)templateExtract:sdc-questionnaire-templateExtract>*
	[]<  If value is of type 'string', then it is to be evaluated as a fhirpath expression. If a value of type 'Expression' is provided, only fhirpath expressions are supported, and the language MAY be omitted.; (xsd)extractContext:sdc-questionnaire-templateExtractContext>*
	[]<  Allocate a new uuid in a named variable for use in extraction. This is usually used to set the `fullUrl` for a resource in the output extraction bundle, and then referenced in other resources in that bundle (via fhirpath expressions). The format of the uuid will be `urn:uuid:(uuid)`. e.g. urn:uuid:6f6177d2-13ee-4d27-b0e8-3eaf663dd031; (xsd)extractAllocateId:sdc-questionnaire-extractAllocateId>*

🔗  One of the permitted answers for a "choice" or "open-choice" question. This element can be used when the value set machinery of answerValueSet is deemed too cumbersome or when there's a need to capture possible answers that are not codes.sdc-questionnaire-extr-template.item.answerOption(xsd)=
	 <#base:Questionnaire.item.answerOption>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 ( <valueCoding:Coding>
		 | <valueDate:date>
		 | <valueInteger:integer>
		 | <valueResource:Resource>
		 | <valueString:string>
		 | <valueTime:time>)
	 <  Indicates whether the answer value is selected when the list of possible answers is initially shown. Use this instead of initial[v] if answerValueSet is present.; (xsd)initialSelected:boolean>?

🔗  A constraint indicating that this item should only be enabled (displayed/allow answers to be captured) when the specified condition is true. If multiple repetitions of this extension are present, the item should be enabled when the condition for *any* of the repetitions is true.  I.e. treat "enableWhen"s as being joined by an "or" clause.  This element is a modifier because if enableWhen is present for an item, "required" is ignored unless one of the enableWhen conditions is met. When an item is disabled, all of its descendants are disabled, regardless of what their own enableWhen logic might evaluate to.sdc-questionnaire-extr-template.item.enableWhen(xsd)=
	 <#base:Questionnaire.item.enableWhen>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  The linkId for the question whose answer (or lack of answer) governs whether this item is enabled. If multiple question occurrences are present for the same question (same linkId), then this refers to the nearest question occurrence reachable by tracing first the "ancestor" axis and then the "preceding" axis and then the "following" axis.; (xsd)question:string>
	 <  Specifies the criteria by which the question is enabled.; (xsd)operator:code>
	 <  A value that the referenced question is tested using the specified operator in order for the item to be enabled.; (xsd)answer:( <boolean>
		 | <Coding>
		 | <date>
		 | <dateTime>
		 | <decimal>
		 | <integer>
		 | <Quantity>
		 | <Resource>
		 | <string>
		 | <time>)>

🔗  One or more values that should be pre-populated in the answer when initially rendering the questionnaire for user input. The user is allowed to change the value and override the default (unless marked as read-only). If the user doesn't change the value, then this initial value will be persisted when the QuestionnaireResponse is initially created.  Note that initial values can influence results.  The data type of initial[x] must agree with the item.type, and only repeating items can have more then one initial value.sdc-questionnaire-extr-template.item.initial(xsd)=
	 <#base:Questionnaire.item.initial>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 ( <valueAttachment:Attachment>
		 | <valueBoolean:boolean>
		 | <valueCoding:Coding>
		 | <valueDate:date>
		 | <valueDateTime:dateTime>
		 | <valueDecimal:decimal>
		 | <valueInteger:integer>
		 | <valueQuantity:Quantity>
		 | <valueResource:Resource>
		 | <valueString:string>
		 | <valueTime:time>
		 | <valueUri:uri>)

🔗  Provides guidelines for rendering multi-column choices.  I.e. when displaying a list of codes (for `choice` or `open-choice` items) or a list of resources (for `reference` items), this extension allows the drop-down to have multiple columns.  For codes, the author can pick additional code system properties to display - such as alternate display names strength or form for drug codes, etc.  For references, the author can choose particular columns from the resource (e.g. first name, last name, specialty, address). Each repetition represents a column to display.sdc-questionnaire-choiceColumn(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  An Extension; (xsd)extension:Extension>+
	 <  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 SHALL be a URI for the Structure Definition defining the extension. http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaire-choiceColumn; (xsd)url:string>
	 ( <valueAddress:Address>
		 | <valueAge:Age>
		 | <valueAnnotation:Annotation>
		 | <valueAttachment:Attachment>
		 | <valueBase64Binary:base64Binary>
		 | <valueBoolean:boolean>
		 | <valueCanonical:canonical>
		 | <valueCode:code>
		 | <valueCodeableConcept:CodeableConcept>
		 | <valueCoding:Coding>
		 | <valueContactDetail:ContactDetail>
		 | <valueContactPoint:ContactPoint>
		 | <valueContributor:Contributor>
		 | <valueCount:Count>
		 | <valueDataRequirement:DataRequirement>
		 | <valueDate:date>
		 | <valueDateTime:dateTime>
		 | <valueDecimal:decimal>
		 | <valueDistance:Distance>
		 | <valueDosage:Dosage>
		 | <valueDuration:Duration>
		 | <valueExpression:Expression>
		 | <valueHumanName:HumanName>
		 | <valueId:id>
		 | <valueIdentifier:Identifier>
		 | <valueInstant:instant>
		 | <valueInteger:integer>
		 | <valueMarkdown:markdown>
		 | <valueMeta:Meta>
		 | <valueMoney:Money>
		 | <valueOid:oid>
		 | <valueParameterDefinition:ParameterDefinition>
		 | <valuePeriod:Period>
		 | <valuePositiveInt:positiveInt>
		 | <valueQuantity:Quantity>
		 | <valueRange:Range>
		 | <valueRatio:Ratio>
		 | <valueRelatedArtifact:RelatedArtifact>
		 | <valueResource:Resource>
		 | <valueSampledData:SampledData>
		 | <valueSignature:Signature>
		 | <valueString:string>
		 | <valueTime:time>
		 | <valueTiming:Timing>
		 | <valueTriggerDefinition:TriggerDefinition>
		 | <valueUnsignedInt:unsignedInt>
		 | <valueUri:uri>
		 | <valueUrl:url>
		 | <valueUsageContext:UsageContext>
		 | <valueUuid:uuid>){0,0}
	 <  The element to display within the column (see notes). When the question has a type of choice or open-choice, the path will be interpreted as the 'code' of a property for the code that is available from the answerValueSet.  For code systems that have alternate designations, the path can also indicate the language or designation use, provided that the code system only has one designation for each language or use within the code system.  A path of 'display' will refer to the default displayname for the code as specified in CodeSystem.concept.display.

When the question has a type of reference, the path will be interpreted as a FHIRPath evaluated against the candidate resources.; (xsd)path:sdc-questionnaire-choiceColumn.path>
	 <  The label to appear at the top of the column.; (xsd)label:sdc-questionnaire-choiceColumn.label>?
	 <  The size to allocate for the column within the table showing the choices. code missing = pixels; code = % = percentage.; (xsd)width:sdc-questionnaire-choiceColumn.width>?
	 <  If true, indicates that this column should be used as (or as part of) the display value for the coding or reference once selected.  I.e. Coding.display or Reference.display as stored in the QuestionnaireResponse and displayed to the user as the selected answer. For codes, only one column can be picked and it must be a column that corresponds to a legal display name for the code from the value set.  For references, multiple columns can be picked.  If more than one column is chosen, the Reference.display will contain concatenate the column values in the order defined separating them with a single space.; (xsd)forDisplay:sdc-questionnaire-choiceColumn.forDisplay>?

🔗  If true, indicates that this column should be used as (or as part of) the display value for the coding or reference once selected.  I.e. Coding.display or Reference.display as stored in the QuestionnaireResponse and displayed to the user as the selected answer. For codes, only one column can be picked and it must be a column that corresponds to a legal display name for the code from the value set.  For references, multiple columns can be picked.  If more than one column is chosen, the Reference.display will contain concatenate the column values in the order defined separating them with a single space.sdc-questionnaire-choiceColumn.forDisplay(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	 <  An Extension; (xsd)extension:Extension>{0,0}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. forDisplay; (xsd)url:string>
	 <  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)value:boolean>?

🔗  The label to appear at the top of the column.sdc-questionnaire-choiceColumn.label(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	 <  An Extension; (xsd)extension:Extension>{0,0}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. label; (xsd)url:string>
	 <  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)value:string>?

🔗  The element to display within the column (see notes). When the question has a type of choice or open-choice, the path will be interpreted as the 'code' of a property for the code that is available from the answerValueSet.  For code systems that have alternate designations, the path can also indicate the language or designation use, provided that the code system only has one designation for each language or use within the code system.  A path of 'display' will refer to the default displayname for the code as specified in CodeSystem.concept.display.

When the question has a type of reference, the path will be interpreted as a FHIRPath evaluated against the candidate resources.sdc-questionnaire-choiceColumn.path(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	 <  An Extension; (xsd)extension:Extension>{0,0}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. path; (xsd)url:string>
	 <  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)value:string>?

🔗  The size to allocate for the column within the table showing the choices. code missing = pixels; code = % = percentage.sdc-questionnaire-choiceColumn.width(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	 <  An Extension; (xsd)extension:Extension>{0,0}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. width; (xsd)url:string>
	 <  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)value:Quantity>?

🔗  Initial value for a question answer as determined by an evaluated expression. Initial value is only calculated at the time the QuestionnaireResponse is first generated.  If the expression returns coded data, it **SHALL* return the information as either code or Coding, not CodeableConcept.  If the expression returns elements of type 'code', when the user selects one or more candidates, the code will be matched against the allowed Codings (from answerValueSet, answerOptions, or answerExpression).  In this case, it is an error if there is more than one Coding with the same code.sdc-questionnaire-initialExpression(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	 <  An Extension; (xsd)extension:Extension>{0,0}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaire-initialExpression; (xsd)url:string>
	 <  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)value:Expression>?

🔗  If present and true, indicates that the item establishes a different subject for the group in a response. The item type must be "reference" and there can only be one item with this extension in each group.sdc-questionnaire-isSubject(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	 <  An Extension; (xsd)extension:Extension>{0,0}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaire-isSubject; (xsd)url:string>
	 <  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)value:boolean>?

🔗  Media to render/make available as an accompaniment to a specific answer optionsdc-questionnaire-itemAnswerMedia(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	 <  An Extension; (xsd)extension:Extension>{0,0}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaire-itemAnswerMedia; (xsd)url:string>
	 <  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)value:Attachment>?

🔗  Specifies a query or other expression that identifies the resource (or set of resources for a repeating item)  to be extracted from this item once the QuestionnaireResponse is complete.sdc-questionnaire-itemExtractionContext(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	 <  An Extension; (xsd)extension:Extension>{0,0}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaire-itemExtractionContext; (xsd)url:string>
	 ( <valueCode:code>
		 | <valueExpression:Expression>)?

🔗  Media to render/make available as an accompaniment to the question being askedsdc-questionnaire-itemMedia(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	 <  An Extension; (xsd)extension:Extension>{0,0}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaire-itemMedia; (xsd)url:string>
	 <  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)value:Attachment>?

🔗  Specifies a query or other expression that identifies the resource (or set of resources for a repeating item) that should be used to support the population of this Questionnaire or Questionnaire.item on initial population.  When populating the questionnaire, it will set the specified variable name to that resource repetition for use in processing items within the group.sdc-questionnaire-itemPopulationContext(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	 <  An Extension; (xsd)extension:Extension>{0,0}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaire-itemPopulationContext; (xsd)url:string>
	 <  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)value:Expression>?

🔗  For string or text items, indicates the 'keyboard type' that should be used by the user interface to guide entry. The assertion applies on a per item basis and is not inherited.  If the item is 'text', only 'chat' should be declared if this extension is present.sdc-questionnaire-keyboard(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	 <  An Extension; (xsd)extension:Extension>{0,0}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaire-keyboard; (xsd)url:string>
	 <  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)value:Coding>?

🔗  Resources that provide context for form processing logic (pre-population, flow-control, drop-down selection, etc.) when creating/displaying/editing a QuestionnaireResponse. 3 of these launch contexts are aligned with the existing SMART on FHIR "launch" contexts.sdc-questionnaire-launchContext(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  An Extension; (xsd)extension:Extension>{2,2147483647}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaire-launchContext; (xsd)url:string>
	 ( <valueAddress:Address>
		 | <valueAge:Age>
		 | <valueAnnotation:Annotation>
		 | <valueAttachment:Attachment>
		 | <valueBase64Binary:base64Binary>
		 | <valueBoolean:boolean>
		 | <valueCanonical:canonical>
		 | <valueCode:code>
		 | <valueCodeableConcept:CodeableConcept>
		 | <valueCoding:Coding>
		 | <valueContactDetail:ContactDetail>
		 | <valueContactPoint:ContactPoint>
		 | <valueContributor:Contributor>
		 | <valueCount:Count>
		 | <valueDataRequirement:DataRequirement>
		 | <valueDate:date>
		 | <valueDateTime:dateTime>
		 | <valueDecimal:decimal>
		 | <valueDistance:Distance>
		 | <valueDosage:Dosage>
		 | <valueDuration:Duration>
		 | <valueExpression:Expression>
		 | <valueHumanName:HumanName>
		 | <valueId:id>
		 | <valueIdentifier:Identifier>
		 | <valueInstant:instant>
		 | <valueInteger:integer>
		 | <valueMarkdown:markdown>
		 | <valueMeta:Meta>
		 | <valueMoney:Money>
		 | <valueOid:oid>
		 | <valueParameterDefinition:ParameterDefinition>
		 | <valuePeriod:Period>
		 | <valuePositiveInt:positiveInt>
		 | <valueQuantity:Quantity>
		 | <valueRange:Range>
		 | <valueRatio:Ratio>
		 | <valueRelatedArtifact:RelatedArtifact>
		 | <valueResource:Resource>
		 | <valueSampledData:SampledData>
		 | <valueSignature:Signature>
		 | <valueString:string>
		 | <valueTime:time>
		 | <valueTiming:Timing>
		 | <valueTriggerDefinition:TriggerDefinition>
		 | <valueUnsignedInt:unsignedInt>
		 | <valueUri:uri>
		 | <valueUrl:url>
		 | <valueUsageContext:UsageContext>
		 | <valueUuid:uuid>){0,0}
	 <  The variable name the passed resource will be referenced by within the Questionnaire logic.; (xsd)name:sdc-questionnaire-launchContext.name>
	[]<  The kind of resource to be provided.; (xsd)type:sdc-questionnaire-launchContext.type>+
	 <  Guidance on the resource to be provided and what impact providing it will have on questionnaire behavior.; (xsd)description:sdc-questionnaire-launchContext.description>?
	 <  Indicates whether multiple resources are permitted for this context element.; (xsd)multiplesAllowed:sdc-questionnaire-launchContext.multiplesAllowed>?

🔗  Guidance on the resource to be provided and what impact providing it will have on questionnaire behavior.sdc-questionnaire-launchContext.description(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	 <  An Extension; (xsd)extension:Extension>{0,0}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. description; (xsd)url:string>
	 <  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)value:string>

🔗  Indicates whether multiple resources are permitted for this context element.sdc-questionnaire-launchContext.multiplesAllowed(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	 <  An Extension; (xsd)extension:Extension>{0,0}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. multiplesAllowed; (xsd)url:string>
	 <  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)value:boolean>?

🔗  The variable name the passed resource will be referenced by within the Questionnaire logic.sdc-questionnaire-launchContext.name(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	 <  An Extension; (xsd)extension:Extension>{0,0}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. name; (xsd)url:string>
	 <  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)value:Coding>

🔗  The kind of resource to be provided.sdc-questionnaire-launchContext.type(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	 <  An Extension; (xsd)extension:Extension>{0,0}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. type; (xsd)url:string>
	 <  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)value:code>

🔗  For items of type reference, the reference can be populated either by picking an existing entity or by creating a new one.  In the latter case, this Questionnaire allows specifying the Questionnaire to use in creating the target instance.  Typically this will result in a QuestionnaireResponse that can be [extracted](extraction.html) to produce the desired resource.  However, if the target resource for the reference is a QuestionnaireResponse, then the QuestionnaireResponse resulting from the Questionnaire can be referenced directly.sdc-questionnaire-lookupQuestionnaire(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	 <  An Extension; (xsd)extension:Extension>{0,0}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaire-lookupQuestionnaire; (xsd)url:string>
	 <  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)value:canonical>?

🔗  The inclusive upper bound on the range of allowed values for  a 'quantity' type question.  Open Issue: Revisit whether this should be folded into the regular maxValue extension once there are better capabilities around defining conformance expectations regarding extensions. This  must only be used if the set of permitted units is constrained to UCUM codes and the maximum checks will be performed by converting the answer.valueQuantity to the same units as the maxQuantity unit prior to comparison.sdc-questionnaire-maxQuantity(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	 <  An Extension; (xsd)extension:Extension>{0,0}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaire-maxQuantity; (xsd)url:string>
	 <  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)value:Quantity>?

🔗  The inclusive lower bound on the range of allowed values for a 'quantity' type question.  Open Issue: Revisit whether this should be folded into the regular minValue extension once there are better capabilities around defining conformance expectations regarding extensions. This  must only be used if the set of permitted units is constrained to UCUM codes and the minimum  checks will be performed by converting the answer.valueQuantity to the same units as the minQuantity unit prior to comparison.sdc-questionnaire-minQuantity(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	 <  An Extension; (xsd)extension:Extension>{0,0}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaire-minQuantity; (xsd)url:string>
	 <  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)value:Quantity>?

🔗  Indicates expectations for questionnaires that draw their item content (not just codes) from other resourcessdc-questionnaire-modular(xsd)=
	 <#base:sdc-questionnaire>
	 <  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.; (xsd)id:string>?
	 <  The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.; (xsd)meta:Meta>?
	 <  A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. 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. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.; (xsd)implicitRules:uri>?
	 <  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).; (xsd)language:code>?
	 <  A human-readable narrative that contains a summary of the resource and can 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. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied).  This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.; (xsd)text: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. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.; (xsd)contained:Resource>*
	[]<  An Extension; (xsd)extension:Extension>+
	[]<  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 and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  An absolute URI that is used to identify this questionnaire when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which at which an authoritative instance of this questionnaire is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the questionnaire is stored on different servers. The name of the referenced questionnaire can be conveyed using the http://hl7.org/fhir/StructureDefinition/display extension.; (xsd)url:uri>
	[]<  A formal identifier that is used to identify this questionnaire when it is represented in other formats, or referenced in a specification, model, design or an instance. Typically, this is used for identifiers that can go in an HL7 V3 II (instance identifier) data type, and can then identify this questionnaire outside of FHIR, where it is not possible to use the logical URI.; (xsd)identifier:Identifier>*
	 <  The identifier that is used to identify this version of the questionnaire when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the questionnaire author and is not expected to be globally unique. For example, it might be a timestamp (e.g. yyyymmdd) if a managed version is not available. There is also no expectation that versions can be placed in a lexicographical sequence. There may be different questionnaire instances that have the same identifier but different versions.  The version can be appended to the url in a reference to allow a reference to a particular business version of the questionnaire with the format [url]|[version].; (xsd)version:string>?
	 <  A natural language name identifying the questionnaire. This name should be usable as an identifier for the module by machine processing applications such as code generation. The name is not expected to be globally unique. The name should be a simple alphanumeric type name to ensure that it is machine-processing friendly.; (xsd)name:string>?
	 <  A short, descriptive, user-friendly title for the questionnaire. This name does not need to be machine-processing friendly and may contain punctuation, white-space, etc.; (xsd)title:string>?
	[]<  The URL of a Questionnaire that this Questionnaire is based on.; (xsd)derivedFrom:canonical>*
	 <  The status of this questionnaire. Enables tracking the life-cycle of the content. Allows filtering of questionnaires that are appropriate for use versus not.; (xsd)status:code>
	 <  A Boolean value to indicate that this questionnaire is authored for testing purposes (or education/evaluation/marketing) and is not intended to be used for genuine usage. Allows filtering of questionnaires that are appropriate for use versus not.; (xsd)experimental:boolean>?
	[]<  The types of subjects that can be the subject of responses created for the questionnaire. If none are specified, then the subject is unlimited.; (xsd)subjectType:code>*
	 <  The date  (and optionally time) when the questionnaire was published. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the questionnaire changes. Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the questionnaire. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource.; (xsd)date:dateTime>?
	 <  The name of the organization or individual that published the questionnaire. Usually an organization but may be an individual. The publisher (or steward) of the questionnaire is the organization or individual primarily responsible for the maintenance and upkeep of the questionnaire. This is not necessarily the same individual or organization that developed and initially authored the content. The publisher is the primary point of contact for questions or issues with the questionnaire. This item SHOULD be populated unless the information is available from context.; (xsd)publisher:string>?
	[]<  Contact details to assist a user in finding and communicating with the publisher. May be a web site, an email address, a telephone number, etc.; (xsd)contact:ContactDetail>*
	 <  A free text natural language description of the questionnaire from a consumer's perspective. This description can be used to capture details such as why the questionnaire was built, comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the questionnaire as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context (e.g. the language of the questionnaire is presumed to be the predominant language in the place the questionnaire was created).; (xsd)description:markdown>?
	[]<  The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate questionnaire instances. When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.; (xsd)useContext:UsageContext>*
	[]<  A legal or geographic region in which the questionnaire is intended to be used. It may be possible for the questionnaire to be used in jurisdictions other than those for which it was originally designed or intended.; (xsd)jurisdiction:CodeableConcept>*
	 <  Explanation of why this questionnaire is needed and why it has been designed as it has. This element does not describe the usage of the questionnaire. Instead, it provides traceability of ''why'' the resource is either needed or ''why'' it is defined as it is.  This may be used to point to source materials or specifications that drove the structure of this questionnaire.; (xsd)purpose:markdown>?
	 <  A copyright statement relating to the questionnaire and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the questionnaire.; (xsd)copyright:markdown>?
	 <  The date on which the resource content was approved by the publisher. Approval happens once when the content is officially approved for usage. The 'date' element may be more recent than the approval date because of minor changes or editorial corrections.; (xsd)approvalDate:date>?
	 <  The date on which the resource content was last reviewed. Review happens periodically after approval but does not change the original approval date. If specified, this date follows the original approval date.; (xsd)lastReviewDate:date>?
	 <  The period during which the questionnaire content was or is planned to be in active use. The effective period for a questionnaire  determines when the content is applicable for usage and is independent of publication and review dates. For example, a measure intended to be used for the year 2016 might be published in 2015.; (xsd)effectivePeriod:Period>?
	[]<  An identifier for this question or group of questions in a particular terminology such as LOINC.; (xsd)code:Coding>*
	[]<  A particular question, question grouping or display text that is part of the questionnaire. The content of the questionnaire is constructed from an ordered, hierarchical collection of items.; (xsd)item:sdc-questionnaire-modular.item>*
	 <  Optional Extension Element - found in all resources.; (xsd)versionAlgorithm:Extension>?
	 <  Optional Extension Element - found in all resources.; (xsd)copyrightLabel:Extension>?
	 <  Information captured by the author/maintainer of the questionnaire for development purposes, not intended to be seen by users. Allows capture of todos, rationale for design decisions, etc.  It can also be used to capture comments about the completion of the form in general. Allows commentary to be captured during the process of answering a questionnaire (if not already supported by the form design) as well as after the form is completed. Comments are not part of the "data" of the form. If a form prompts for a comment, this should be captured in an answer, not in this element. Formal assessments of the QuestionnaireResponse would use [[[Observation]]].; (xsd)designNote>?
	[]<  Indicates the types of resources that can record answers to a Questionnaire. Open Issue: Should this extension be moved to core?; (xsd)performerType:sdc-questionnaire-performerType>*
	 <  If present, indicates that this questionnaire has expectations with respect to assembly.  Specifically, indicates whether this form requires assembly (i.e. it can't be used directly without invoking the [$assemble](OperationDefinition-Questionnaire-assemble.html) operation operation on it) and/or whether it is intended for use only as a 'child' in an assembly process.  The assembly processs might mean filling in item metadata based on information looked up from item.definitions and/or retrieving sub-questionnaires pointed to by [sub-questionnaire](StructureDefinition-sdc-questionnaire-subQuestionnaire.html) extensions. SDC-conformant Questionnaires **SHALL** declare this extension if they require an assembly process prior to use.  If not declared, then the Questionnaire is not necessarily safe for use as a child form and does not require assembly prior to use.; (xsd)assemble-expectation:sdc-questionnaire-assemble-expectation>
	[]<  This extension, used on a subQuestionnaire, indicates a FHIRPath variable that must be present in context when the subQuestionnaire is referenced.; (xsd)assembleContext:sdc-questionnaire-assembleContext>*

🔗  A particular question, question grouping or display text that is part of the questionnaire. The content of the questionnaire is constructed from an ordered, hierarchical collection of items.sdc-questionnaire-modular.item(xsd)=
	 <#base:Questionnaire.item>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  An Extension; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  An identifier that is unique within the Questionnaire allowing linkage to the equivalent item in a QuestionnaireResponse resource. This ''can'' be a meaningful identifier (e.g. a LOINC code) but is not intended to have any meaning.  GUIDs or sequential numbers are appropriate here.; (xsd)linkId:string>
	 <  This element is a URI that refers to an [ElementDefinition](http://hl7.org/fhir/R4/elementdefinition.html) that provides information about this item, including information that might otherwise be included in the instance of the Questionnaire resource. A detailed description of the construction of the URI is shown in Comments, below. If this element is present then the following element values MAY be derived from the Element Definition if the corresponding elements of this Questionnaire resource instance have no value:

* code (ElementDefinition.code) 
* type (ElementDefinition.type) 
* required (ElementDefinition.min) 
* repeats (ElementDefinition.max) 
* maxLength (ElementDefinition.maxLength) 
* answerValueSet (ElementDefinition.binding)
* options (ElementDefinition.binding). The uri refers to an ElementDefinition in a [StructureDefinition](http://hl7.org/fhir/R4/structuredefinition.html#) and always starts with the [canonical URL](http://hl7.org/fhir/R4/references.html#canonical) for the target resource. When referring to a StructureDefinition, a fragment identifier is used to specify the element definition by its id [Element.id](http://hl7.org/fhir/R4/element-definitions.html#Element.id). E.g. http://hl7.org/fhir/StructureDefinition/Observation#Observation.value[x]. In the absence of a fragment identifier, the first/root element definition in the target is the matching element definition.; (xsd)definition:uri>?
	[]<  A terminology code that corresponds to this group or question (e.g. a code from LOINC, which defines many questions and answers). The value may come from the ElementDefinition referred to by .definition.; (xsd)code:Coding>*
	 <  A short label for a particular group, question or set of display text within the questionnaire used for reference by the individual completing 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.  Typically, these won't be used for "display" items, though such use is not prohibited.  Systems SHOULD NOT generate their own prefixes if prefixes are defined for any items within a Questionnaire.; (xsd)prefix:string>?
	 <  The name of a section, the text of a question or text content for a display item. When using this element to represent the name of a section, use group type item and also make sure to limit the text element to a short string suitable for display as a section heading.  Group item instructions should be included as a display type item within the group.
This is optional only to support form assembly situations where the text may be generated from another source.  In an assembled Questionnaire, it should always be present.; (xsd)text:string>?
	 <  The type of questionnaire item this is - whether text for display, a grouping of other items or a particular type of data to be captured (string, integer, coded choice, etc.). Time is handled using "string".  File is handled using Attachment.  (Content can be sent as a contained binary).; (xsd)type:code>
	[]<  A constraint indicating that this item should only be enabled (displayed/allow answers to be captured) when the specified condition is true. If multiple repetitions of this extension are present, the item should be enabled when the condition for *any* of the repetitions is true.  I.e. treat "enableWhen"s as being joined by an "or" clause.  This element is a modifier because if enableWhen is present for an item, "required" is ignored unless one of the enableWhen conditions is met. When an item is disabled, all of its descendants are disabled, regardless of what their own enableWhen logic might evaluate to.; (xsd)enableWhen:sdc-questionnaire-modular.item.enableWhen>*
	 <  Controls how multiple enableWhen values are interpreted -  whether all or any must be true. This element must be specified if more than one enableWhen value is provided.; (xsd)enableBehavior:code>?
	 <  An indication, if true, that the item must be present in a "completed" QuestionnaireResponse.  If false, the item may be skipped when answering the questionnaire. Questionnaire.item.required only has meaning for elements that are conditionally enabled with enableWhen if the condition evaluates to true.  If an item that contains other items is marked as required, that does not automatically make the contained elements required (though required groups must contain at least one child element). The value may come from the ElementDefinition referred to by .definition.; (xsd)required:boolean>?
	 <  An indication, if true, that a QuestionnaireResponse for this item may include multiple answers associated with a single instance of this item (for question-type items) or multiple repetitions of the item (for group-type items) If a question is marked as repeats=true, then multiple answers can be provided for the question in the corresponding QuestionnaireResponse.  When rendering the questionnaire, it is up to the rendering software whether to render the question text for each answer repetition (i.e. "repeat the question") or to simply allow entry/selection of multiple answers for the question (repeat the answers).  Which is most appropriate visually may depend on the type of answer as well as whether there are nested items.

The resulting QuestionnaireResponse will be populated the same way regardless of rendering - one 'question' item with multiple answer values.

 The value may come from the ElementDefinition referred to by .definition.; (xsd)repeats:boolean>?
	 <  An indication, when true, that the value cannot be changed by a human respondent 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.; (xsd)readOnly:boolean>?
	 <  The maximum number of characters that are permitted in the answer to be considered a "valid" QuestionnaireResponse. For base64binary, reflects the number of characters representing the encoded data, not the number of bytes of the binary data. The value may come from the ElementDefinition referred to by .definition.; (xsd)maxLength:integer>?
	 <  A reference to a value set containing a list of codes representing permitted answers for a "choice" or "open-choice" question. LOINC defines many useful value sets for questionnaire responses. See [LOINC Answer Lists](http://hl7.org/fhir/R4/loinc.html#alist). The value may come from the ElementDefinition referred to by .definition.; (xsd)answerValueSet:canonical>?
	[]<  One of the permitted answers for a "choice" or "open-choice" question. This element can be used when the value set machinery of answerValueSet is deemed too cumbersome or when there's a need to capture possible answers that are not codes.; (xsd)answerOption:sdc-questionnaire-modular.item.answerOption>*
	[]<  One or more values that should be pre-populated in the answer when initially rendering the questionnaire for user input. The user is allowed to change the value and override the default (unless marked as read-only). If the user doesn't change the value, then this initial value will be persisted when the QuestionnaireResponse is initially created.  Note that initial values can influence results.  The data type of initial[x] must agree with the item.type, and only repeating items can have more then one initial value.; (xsd)initial:sdc-questionnaire-modular.item.initial>*
	[]<  Text, questions and other groups to be nested beneath a question or group. There is no specified limit to the depth of nesting.  However, Questionnaire authors are encouraged to consider the impact on the user and user interface of overly deep nesting.; (xsd)item:Questionnaire.item>*
	 <  If true, indicates that the extended item should not be displayed to the user. If an item is hidden, all descendant items are hidden as well.  See additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/rendering.html#hidden).; (xsd)hidden:questionnaire-hidden>?
	 <  Optional Extension Element - found in all resources.; (xsd)answerConstraint:Extension>?
	 <  Information captured by the author/maintainer of the questionnaire for development purposes, not intended to be seen by users. Allows capture of todos, rationale for design decisions, etc.  It can also be used to capture comments about specific groups or questions within it. Allows commentary to be captured during the process of answering a questionnaire (if not already supported by the form design) as well as after the form is completed. Comments are not part of the "data" of the form. If a form prompts for a comment, this should be captured in an answer, not in this element. Formal assessments of the QuestionnaireResponse would use [[[Observation]]].; (xsd)designNote>?
	 <  This extension is used when defining high-level questionnaires that will then be used as a basis for 'derived' Questionnaires that are further refined for use in specific organizations or contexts.  If the extension is present and set to 'true', it means that this item should be considered to be 'optional' from an adaptation perspective and that the question can be removed (i.e. not displayed) in derived questionnaires without impacting the validity of the instrument.  Alternatively, the element can be marked as 'hidden' and 'readOnly' and have a value or descendant item values declared using initialValue or initialExpression.  If the element with 'optionalDisplay=true' is marked as 'required=true', then this second approach is the only means to exclude the element from display. 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.; (xsd)itemOptionalDisplay:sdc-questionnaire-optionalDisplay>?
	[]<  Indicates that the display item on which this extension appears should be replaced with the referenced Questionnaire; (xsd)subQuestionnaire:sdc-questionnaire-subQuestionnaire>*

🔗  One of the permitted answers for a "choice" or "open-choice" question. This element can be used when the value set machinery of answerValueSet is deemed too cumbersome or when there's a need to capture possible answers that are not codes.sdc-questionnaire-modular.item.answerOption(xsd)=
	 <#base:Questionnaire.item.answerOption>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 ( <valueCoding:Coding>
		 | <valueDate:date>
		 | <valueInteger:integer>
		 | <valueResource:Resource>
		 | <valueString:string>
		 | <valueTime:time>)
	 <  Indicates whether the answer value is selected when the list of possible answers is initially shown. Use this instead of initial[v] if answerValueSet is present.; (xsd)initialSelected:boolean>?

🔗  A constraint indicating that this item should only be enabled (displayed/allow answers to be captured) when the specified condition is true. If multiple repetitions of this extension are present, the item should be enabled when the condition for *any* of the repetitions is true.  I.e. treat "enableWhen"s as being joined by an "or" clause.  This element is a modifier because if enableWhen is present for an item, "required" is ignored unless one of the enableWhen conditions is met. When an item is disabled, all of its descendants are disabled, regardless of what their own enableWhen logic might evaluate to.sdc-questionnaire-modular.item.enableWhen(xsd)=
	 <#base:Questionnaire.item.enableWhen>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  The linkId for the question whose answer (or lack of answer) governs whether this item is enabled. If multiple question occurrences are present for the same question (same linkId), then this refers to the nearest question occurrence reachable by tracing first the "ancestor" axis and then the "preceding" axis and then the "following" axis.; (xsd)question:string>
	 <  Specifies the criteria by which the question is enabled.; (xsd)operator:code>
	 <  A value that the referenced question is tested using the specified operator in order for the item to be enabled.; (xsd)answer:( <boolean>
		 | <Coding>
		 | <date>
		 | <dateTime>
		 | <decimal>
		 | <integer>
		 | <Quantity>
		 | <Resource>
		 | <string>
		 | <time>)>

🔗  One or more values that should be pre-populated in the answer when initially rendering the questionnaire for user input. The user is allowed to change the value and override the default (unless marked as read-only). If the user doesn't change the value, then this initial value will be persisted when the QuestionnaireResponse is initially created.  Note that initial values can influence results.  The data type of initial[x] must agree with the item.type, and only repeating items can have more then one initial value.sdc-questionnaire-modular.item.initial(xsd)=
	 <#base:Questionnaire.item.initial>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 ( <valueAttachment:Attachment>
		 | <valueBoolean:boolean>
		 | <valueCoding:Coding>
		 | <valueDate:date>
		 | <valueDateTime:dateTime>
		 | <valueDecimal:decimal>
		 | <valueInteger:integer>
		 | <valueQuantity:Quantity>
		 | <valueResource:Resource>
		 | <valueString:string>
		 | <valueTime:time>
		 | <valueUri:uri>)

🔗  Indicates how the observation-based extraction approach should be applied to an item or all items in a questionnaire. When set to `true`, the item is extracted as an independent Observation with no relationship to a parent Observation (If true, indicates that the observation-based approach should be used to extract either the particular item (if extension is defined on an individual question or group based on the code present) or all items in the questionnaire (if defined at the questionnaire root and if they have a code present)). When set to a `code` value (e.g., `member` or `component`), the extracted Observation is related to a parent Observation according to the specified relationship. Mixing `boolean` and `code` values within the same item is invalid and will result in an error. This extension canot be specified on "display" items.sdc-questionnaire-observationExtract(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	 <  An Extension; (xsd)extension:Extension>{0,0}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaire-observationExtract; (xsd)url:string>
	 ( <valueBoolean:boolean>
		 | <valueCode:code>)?

🔗  Indicates the Observation.category value(s) that should appear on extracted Observations for the entire Questionnaire or for the current item and descendant items.  If this extension appears at multiple levels in the Questionnaire, those defined on lower-level items override those declared on higher-level items. This extension canot be specified on "display" items.sdc-questionnaire-observation-extract-category(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	 <  An Extension; (xsd)extension:Extension>{0,0}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaire-observation-extract-category; (xsd)url:string>
	 <  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)value:CodeableConcept>?

🔗  Indicates the time-period (from 'now') to search for observations that match the Questionnaire.item.code and Questionnaire.subject when pre-populating the QuestionnaireResponse. If multiple Observations are found, the most recent is used.sdc-questionnaire-observationLinkPeriod(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	 <  An Extension; (xsd)extension:Extension>{0,0}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaire-observationLinkPeriod; (xsd)url:string>
	 <  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)value:Duration>?

🔗  The label text to display beside free-text and/or unrestricted type values for an 'open' choice element.  E.g. 'Other, please specify', or 'Additional condition', or 'More reason(s)', etc.sdc-questionnaire-openLabel(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	 <  An Extension; (xsd)extension:Extension>{0,0}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaire-openLabel; (xsd)url:string>
	 <  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)value:string>?

🔗  This extension is used when defining high-level questionnaires that will then be used as a basis for 'derived' Questionnaires that are further refined for use in specific organizations or contexts.  If the extension is present and set to 'true', it means that this item should be considered to be 'optional' from an adaptation perspective and that the question can be removed (i.e. not displayed) in derived questionnaires without impacting the validity of the instrument.  Alternatively, the element can be marked as 'hidden' and 'readOnly' and have a value or descendant item values declared using initialValue or initialExpression.  If the element with 'optionalDisplay=true' is marked as 'required=true', then this second approach is the only means to exclude the element from display. 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.sdc-questionnaire-optionalDisplay(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	 <  An Extension; (xsd)extension:Extension>{0,0}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaire-optionalDisplay; (xsd)url:string>
	 <  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)value:boolean>?

🔗  Indicates the types of resources that can record answers to a Questionnaire. Open Issue: Should this extension be moved to core?sdc-questionnaire-performerType(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	 <  An Extension; (xsd)extension:Extension>{0,0}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaire-performerType; (xsd)url:string>
	 <  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)value:code>?

🔗  Defines elements that support auto-population and pre-population of questionnaires using the Expression-based population mechanism.sdc-questionnaire-pop-exp(xsd)=
	 <#base:sdc-questionnairecommon>
	 <  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.; (xsd)id:string>?
	 <  The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.; (xsd)meta:Meta>?
	 <  A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. 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. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.; (xsd)implicitRules:uri>?
	 <  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).; (xsd)language:code>?
	 <  A human-readable narrative that contains a summary of the resource and can 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. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied).  This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.; (xsd)text: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. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.; (xsd)contained:Resource>*
	[]<  An Extension; (xsd)extension:Extension>*
	[]<  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 and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  An absolute URI that is used to identify this questionnaire when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which at which an authoritative instance of this questionnaire is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the questionnaire is stored on different servers. The name of the referenced questionnaire can be conveyed using the http://hl7.org/fhir/StructureDefinition/display extension.; (xsd)url:uri>?
	[]<  A formal identifier that is used to identify this questionnaire when it is represented in other formats, or referenced in a specification, model, design or an instance. Typically, this is used for identifiers that can go in an HL7 V3 II (instance identifier) data type, and can then identify this questionnaire outside of FHIR, where it is not possible to use the logical URI.; (xsd)identifier:Identifier>*
	 <  The identifier that is used to identify this version of the questionnaire when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the questionnaire author and is not expected to be globally unique. For example, it might be a timestamp (e.g. yyyymmdd) if a managed version is not available. There is also no expectation that versions can be placed in a lexicographical sequence. There may be different questionnaire instances that have the same identifier but different versions.  The version can be appended to the url in a reference to allow a reference to a particular business version of the questionnaire with the format [url]|[version].; (xsd)version:string>?
	 <  A natural language name identifying the questionnaire. This name should be usable as an identifier for the module by machine processing applications such as code generation. The name is not expected to be globally unique. The name should be a simple alphanumeric type name to ensure that it is machine-processing friendly.; (xsd)name:string>?
	 <  A short, descriptive, user-friendly title for the questionnaire. This name does not need to be machine-processing friendly and may contain punctuation, white-space, etc.; (xsd)title:string>?
	[]<  The URL of a Questionnaire that this Questionnaire is based on.; (xsd)derivedFrom:canonical>*
	 <  The status of this questionnaire. Enables tracking the life-cycle of the content. Allows filtering of questionnaires that are appropriate for use versus not.; (xsd)status:code>
	 <  A Boolean value to indicate that this questionnaire is authored for testing purposes (or education/evaluation/marketing) and is not intended to be used for genuine usage. Allows filtering of questionnaires that are appropriate for use versus not.; (xsd)experimental:boolean>?
	[]<  The types of subjects that can be the subject of responses created for the questionnaire. If none are specified, then the subject is unlimited.; (xsd)subjectType:code>*
	 <  The date  (and optionally time) when the questionnaire was published. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the questionnaire changes. Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the questionnaire. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource.; (xsd)date:dateTime>?
	 <  The name of the organization or individual that published the questionnaire. Usually an organization but may be an individual. The publisher (or steward) of the questionnaire is the organization or individual primarily responsible for the maintenance and upkeep of the questionnaire. This is not necessarily the same individual or organization that developed and initially authored the content. The publisher is the primary point of contact for questions or issues with the questionnaire. This item SHOULD be populated unless the information is available from context.; (xsd)publisher:string>?
	[]<  Contact details to assist a user in finding and communicating with the publisher. May be a web site, an email address, a telephone number, etc.; (xsd)contact:ContactDetail>*
	 <  A free text natural language description of the questionnaire from a consumer's perspective. This description can be used to capture details such as why the questionnaire was built, comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the questionnaire as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context (e.g. the language of the questionnaire is presumed to be the predominant language in the place the questionnaire was created).; (xsd)description:markdown>?
	[]<  The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate questionnaire instances. When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.; (xsd)useContext:UsageContext>*
	[]<  A legal or geographic region in which the questionnaire is intended to be used. It may be possible for the questionnaire to be used in jurisdictions other than those for which it was originally designed or intended.; (xsd)jurisdiction:CodeableConcept>*
	 <  Explanation of why this questionnaire is needed and why it has been designed as it has. This element does not describe the usage of the questionnaire. Instead, it provides traceability of ''why'' the resource is either needed or ''why'' it is defined as it is.  This may be used to point to source materials or specifications that drove the structure of this questionnaire.; (xsd)purpose:markdown>?
	 <  A copyright statement relating to the questionnaire and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the questionnaire.; (xsd)copyright:markdown>?
	 <  The date on which the resource content was approved by the publisher. Approval happens once when the content is officially approved for usage. The 'date' element may be more recent than the approval date because of minor changes or editorial corrections.; (xsd)approvalDate:date>?
	 <  The date on which the resource content was last reviewed. Review happens periodically after approval but does not change the original approval date. If specified, this date follows the original approval date.; (xsd)lastReviewDate:date>?
	 <  The period during which the questionnaire content was or is planned to be in active use. The effective period for a questionnaire  determines when the content is applicable for usage and is independent of publication and review dates. For example, a measure intended to be used for the year 2016 might be published in 2015.; (xsd)effectivePeriod:Period>?
	[]<  An identifier for this question or group of questions in a particular terminology such as LOINC.; (xsd)code:Coding>*
	[]<  A particular question, question grouping or display text that is part of the questionnaire. The content of the questionnaire is constructed from an ordered, hierarchical collection of items.; (xsd)item:sdc-questionnaire-pop-exp.item>*
	 <  Optional Extension Element - found in all resources.; (xsd)versionAlgorithm:Extension>?
	 <  Optional Extension Element - found in all resources.; (xsd)copyrightLabel:Extension>?
	[]<  A reference to a library containing cql used in this Questionnaire. For questionnaires, see additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/behavior.html#cqf-library).; (xsd)library:cqf-library>*
	[]<  Resources that provide context for form processing logic (pre-population, flow-control, drop-down selection, etc.) when creating/displaying/editing a QuestionnaireResponse. 3 of these launch contexts are aligned with the existing SMART on FHIR "launch" contexts.; (xsd)launchContext:sdc-questionnaire-launchContext>*
	 <  Specifies a query or other expression that identifies the resource (or set of resources for a repeating item) that should be used to support the population of this Questionnaire or Questionnaire.item on initial population.  When populating the questionnaire, it will set the specified variable name to that resource repetition for use in processing items within the group.; (xsd)itemPopulationContext:sdc-questionnaire-itemPopulationContext>?
	[]<  Variable specifying a logic to generate a variable for use in subsequent logic.  The name of the variable will be added to FHIRPath's context when processing descendants of the element that contains this extension as well as extensions within the same element. Ordering of variable extension declarations is significant as variables declared in one repetition of this extension might be used in subsequent extension repetitions

For questionnaires, see additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/behavior.html#variable).; (xsd)variable>*

🔗  A particular question, question grouping or display text that is part of the questionnaire. The content of the questionnaire is constructed from an ordered, hierarchical collection of items.sdc-questionnaire-pop-exp.item(xsd)=
	 <#base:Questionnaire.item>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  An Extension; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  An identifier that is unique within the Questionnaire allowing linkage to the equivalent item in a QuestionnaireResponse resource. This ''can'' be a meaningful identifier (e.g. a LOINC code) but is not intended to have any meaning.  GUIDs or sequential numbers are appropriate here.; (xsd)linkId:string>
	 <  This element is a URI that refers to an [ElementDefinition](http://hl7.org/fhir/R4/elementdefinition.html) that provides information about this item, including information that might otherwise be included in the instance of the Questionnaire resource. A detailed description of the construction of the URI is shown in Comments, below. If this element is present then the following element values MAY be derived from the Element Definition if the corresponding elements of this Questionnaire resource instance have no value:

* code (ElementDefinition.code) 
* type (ElementDefinition.type) 
* required (ElementDefinition.min) 
* repeats (ElementDefinition.max) 
* maxLength (ElementDefinition.maxLength) 
* answerValueSet (ElementDefinition.binding)
* options (ElementDefinition.binding). The uri refers to an ElementDefinition in a [StructureDefinition](http://hl7.org/fhir/R4/structuredefinition.html#) and always starts with the [canonical URL](http://hl7.org/fhir/R4/references.html#canonical) for the target resource. When referring to a StructureDefinition, a fragment identifier is used to specify the element definition by its id [Element.id](http://hl7.org/fhir/R4/element-definitions.html#Element.id). E.g. http://hl7.org/fhir/StructureDefinition/Observation#Observation.value[x]. In the absence of a fragment identifier, the first/root element definition in the target is the matching element definition.; (xsd)definition:uri>?
	[]<  A terminology code that corresponds to this group or question (e.g. a code from LOINC, which defines many questions and answers). The value may come from the ElementDefinition referred to by .definition.; (xsd)code:Coding>*
	 <  A short label for a particular group, question or set of display text within the questionnaire used for reference by the individual completing 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.  Typically, these won't be used for "display" items, though such use is not prohibited.  Systems SHOULD NOT generate their own prefixes if prefixes are defined for any items within a Questionnaire.; (xsd)prefix:string>?
	 <  The name of a section, the text of a question or text content for a display item. When using this element to represent the name of a section, use group type item and also make sure to limit the text element to a short string suitable for display as a section heading.  Group item instructions should be included as a display type item within the group.; (xsd)text:string>?
	 <  The type of questionnaire item this is - whether text for display, a grouping of other items or a particular type of data to be captured (string, integer, coded choice, etc.). Time is handled using "string".  File is handled using Attachment.  (Content can be sent as a contained binary).; (xsd)type:code>
	[]<  A constraint indicating that this item should only be enabled (displayed/allow answers to be captured) when the specified condition is true. If multiple repetitions of this extension are present, the item should be enabled when the condition for *any* of the repetitions is true.  I.e. treat "enableWhen"s as being joined by an "or" clause.  This element is a modifier because if enableWhen is present for an item, "required" is ignored unless one of the enableWhen conditions is met. When an item is disabled, all of its descendants are disabled, regardless of what their own enableWhen logic might evaluate to.; (xsd)enableWhen:sdc-questionnaire-pop-exp.item.enableWhen>*
	 <  Controls how multiple enableWhen values are interpreted -  whether all or any must be true. This element must be specified if more than one enableWhen value is provided.; (xsd)enableBehavior:code>?
	 <  An indication, if true, that the item must be present in a "completed" QuestionnaireResponse.  If false, the item may be skipped when answering the questionnaire. Questionnaire.item.required only has meaning for elements that are conditionally enabled with enableWhen if the condition evaluates to true.  If an item that contains other items is marked as required, that does not automatically make the contained elements required (though required groups must contain at least one child element). The value may come from the ElementDefinition referred to by .definition.; (xsd)required:boolean>?
	 <  An indication, if true, that a QuestionnaireResponse for this item may include multiple answers associated with a single instance of this item (for question-type items) or multiple repetitions of the item (for group-type items) If a question is marked as repeats=true, then multiple answers can be provided for the question in the corresponding QuestionnaireResponse.  When rendering the questionnaire, it is up to the rendering software whether to render the question text for each answer repetition (i.e. "repeat the question") or to simply allow entry/selection of multiple answers for the question (repeat the answers).  Which is most appropriate visually may depend on the type of answer as well as whether there are nested items.

The resulting QuestionnaireResponse will be populated the same way regardless of rendering - one 'question' item with multiple answer values.

 The value may come from the ElementDefinition referred to by .definition.; (xsd)repeats:boolean>?
	 <  An indication, when true, that the value cannot be changed by a human respondent 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.; (xsd)readOnly:boolean>?
	 <  The maximum number of characters that are permitted in the answer to be considered a "valid" QuestionnaireResponse. For base64binary, reflects the number of characters representing the encoded data, not the number of bytes of the binary data. The value may come from the ElementDefinition referred to by .definition.; (xsd)maxLength:integer>?
	 <  A reference to a value set containing a list of codes representing permitted answers for a "choice" or "open-choice" question. LOINC defines many useful value sets for questionnaire responses. See [LOINC Answer Lists](http://hl7.org/fhir/R4/loinc.html#alist). The value may come from the ElementDefinition referred to by .definition.; (xsd)answerValueSet:canonical>?
	[]<  One of the permitted answers for a "choice" or "open-choice" question. This element can be used when the value set machinery of answerValueSet is deemed too cumbersome or when there's a need to capture possible answers that are not codes.; (xsd)answerOption:sdc-questionnaire-pop-exp.item.answerOption>*
	[]<  One or more values that should be pre-populated in the answer when initially rendering the questionnaire for user input. The user is allowed to change the value and override the default (unless marked as read-only). If the user doesn't change the value, then this initial value will be persisted when the QuestionnaireResponse is initially created.  Note that initial values can influence results.  The data type of initial[x] must agree with the item.type, and only repeating items can have more then one initial value.; (xsd)initial:sdc-questionnaire-pop-exp.item.initial>*
	[]<  Text, questions and other groups to be nested beneath a question or group. There is no specified limit to the depth of nesting.  However, Questionnaire authors are encouraged to consider the impact on the user and user interface of overly deep nesting.; (xsd)item:Questionnaire.item>*
	 <  If true, indicates that the extended item should not be displayed to the user. If an item is hidden, all descendant items are hidden as well.  See additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/rendering.html#hidden).; (xsd)hidden:questionnaire-hidden>?
	 <  Optional Extension Element - found in all resources.; (xsd)answerConstraint:Extension>?
	 <  Provides a computable unit of measure associated with numeric questions to support subsequent computation on responses. This is for use on items of type integer and decimal, and it's purpose is to support converting the integer or decimal answer into a Quantity when extracting the data into a resource. The human-readable unit is conveyed as a display element.  This element is for computation purposes.; (xsd)unit:questionnaire-unit>?
	 <  Specifies a query or other expression that identifies the resource (or set of resources for a repeating item) that should be used to support the population of this Questionnaire or Questionnaire.item on initial population.  When populating the questionnaire, it will set the specified variable name to that resource repetition for use in processing items within the group.; (xsd)itemPopulationContext:sdc-questionnaire-itemPopulationContext>?
	[]<  Variable specifying a logic to generate a variable for use in subsequent logic.  The name of the variable will be added to FHIRPath's context when processing descendants of the element that contains this extension as well as extensions within the same element. Ordering of variable extension declarations is significant as variables declared in one repetition of this extension might be used in subsequent extension repetitions

For questionnaires, see additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/behavior.html#variable).; (xsd)itemVariable:variable>*
	 <  Initial value for a question answer as determined by an evaluated expression. Initial value is only calculated at the time the QuestionnaireResponse is first generated.  If the expression returns coded data, it **SHALL* return the information as either code or Coding, not CodeableConcept.  If the expression returns elements of type 'code', when the user selects one or more candidates, the code will be matched against the allowed Codings (from answerValueSet, answerOptions, or answerExpression).  In this case, it is an error if there is more than one Coding with the same code.; (xsd)initialExpression:sdc-questionnaire-initialExpression>?
	 <  A FHIRPath or CQL expression, or FHIR Query that resolves to a list of candidate answers for the question item or that establishes context for a group item.  The user may select from among the candidates to choose answers for the question. The results of the expression must correspond to the item type of the question the element appears on or must correspond to a resource, backbone element or complex data type for a group item.  Resources are considered a match for the Reference item type.  Quantity can be a match for decimal and integer items so long as a questionnaire-unit extension is present.  If the expression returns coded data, it **SHALL* return the information as either code or Coding, not CodeableConcept.  If the expression returns elements of type 'code', when the user selects one or more candidates, the code will be matched against the allowed Codings (from answerValueSet, answerOptions, or answerExpresssion).  In this case, it is an error if there is more than one Coding with the same code.; (xsd)candidateExpression:sdc-questionnaire-candidateExpression>?
	[]<  A FHIR Query that resolves to one or more resources that can be displayed to the user to help provide context for answering a question. For example, if the question is "Has the patient discussed this issue on any visits in the past year?", the contextExpression might return the set of patient's encounters for the prior 12 month period to help jog the practitioner's memory.; (xsd)contextExpression:sdc-questionnaire-contextExpression>*
	 <  If true, indicates that the extended item should not be displayed to the user. If an item is hidden, all descendant items are hidden as well.  See additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/rendering.html#hidden).; (xsd)itemHidden:questionnaire-hidden>?
	[]<  Provides guidelines for rendering multi-column choices.  I.e. when displaying a list of codes (for `choice` or `open-choice` items) or a list of resources (for `reference` items), this extension allows the drop-down to have multiple columns.  For codes, the author can pick additional code system properties to display - such as alternate display names strength or form for drug codes, etc.  For references, the author can choose particular columns from the resource (e.g. first name, last name, specialty, address). Each repetition represents a column to display.; (xsd)choiceColumn:sdc-questionnaire-choiceColumn>*
	 <  If present and true, indicates that the item establishes a different subject for the group in a response. The item type must be "reference" and there can only be one item with this extension in each group.; (xsd)isSubject:sdc-questionnaire-isSubject>?

🔗  One of the permitted answers for a "choice" or "open-choice" question. This element can be used when the value set machinery of answerValueSet is deemed too cumbersome or when there's a need to capture possible answers that are not codes.sdc-questionnaire-pop-exp.item.answerOption(xsd)=
	 <#base:Questionnaire.item.answerOption>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 ( <valueCoding:Coding>
		 | <valueDate:date>
		 | <valueInteger:integer>
		 | <valueResource:Resource>
		 | <valueString:string>
		 | <valueTime:time>)
	 <  Indicates whether the answer value is selected when the list of possible answers is initially shown. Use this instead of initial[v] if answerValueSet is present.; (xsd)initialSelected:boolean>?

🔗  A constraint indicating that this item should only be enabled (displayed/allow answers to be captured) when the specified condition is true. If multiple repetitions of this extension are present, the item should be enabled when the condition for *any* of the repetitions is true.  I.e. treat "enableWhen"s as being joined by an "or" clause.  This element is a modifier because if enableWhen is present for an item, "required" is ignored unless one of the enableWhen conditions is met. When an item is disabled, all of its descendants are disabled, regardless of what their own enableWhen logic might evaluate to.sdc-questionnaire-pop-exp.item.enableWhen(xsd)=
	 <#base:Questionnaire.item.enableWhen>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  The linkId for the question whose answer (or lack of answer) governs whether this item is enabled. If multiple question occurrences are present for the same question (same linkId), then this refers to the nearest question occurrence reachable by tracing first the "ancestor" axis and then the "preceding" axis and then the "following" axis.; (xsd)question:string>
	 <  Specifies the criteria by which the question is enabled.; (xsd)operator:code>
	 <  A value that the referenced question is tested using the specified operator in order for the item to be enabled.; (xsd)answer:( <boolean>
		 | <Coding>
		 | <date>
		 | <dateTime>
		 | <decimal>
		 | <integer>
		 | <Quantity>
		 | <Resource>
		 | <string>
		 | <time>)>

🔗  One or more values that should be pre-populated in the answer when initially rendering the questionnaire for user input. The user is allowed to change the value and override the default (unless marked as read-only). If the user doesn't change the value, then this initial value will be persisted when the QuestionnaireResponse is initially created.  Note that initial values can influence results.  The data type of initial[x] must agree with the item.type, and only repeating items can have more then one initial value.sdc-questionnaire-pop-exp.item.initial(xsd)=
	 <#base:Questionnaire.item.initial>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 ( <valueAttachment:Attachment>
		 | <valueBoolean:boolean>
		 | <valueCoding:Coding>
		 | <valueDate:date>
		 | <valueDateTime:dateTime>
		 | <valueDecimal:decimal>
		 | <valueInteger:integer>
		 | <valueQuantity:Quantity>
		 | <valueResource:Resource>
		 | <valueString:string>
		 | <valueTime:time>
		 | <valueUri:uri>)

🔗  Defines elements that support auto-population and pre-population of questionnaires using the Observation-based population mechanism.sdc-questionnaire-pop-obsn(xsd)=
	 <#base:sdc-questionnairecommon>
	 <  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.; (xsd)id:string>?
	 <  The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.; (xsd)meta:Meta>?
	 <  A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. 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. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.; (xsd)implicitRules:uri>?
	 <  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).; (xsd)language:code>?
	 <  A human-readable narrative that contains a summary of the resource and can 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. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied).  This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.; (xsd)text: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. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.; (xsd)contained:Resource>*
	[]<  An Extension; (xsd)extension:Extension>*
	[]<  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 and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  An absolute URI that is used to identify this questionnaire when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which at which an authoritative instance of this questionnaire is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the questionnaire is stored on different servers. The name of the referenced questionnaire can be conveyed using the http://hl7.org/fhir/StructureDefinition/display extension.; (xsd)url:uri>?
	[]<  A formal identifier that is used to identify this questionnaire when it is represented in other formats, or referenced in a specification, model, design or an instance. Typically, this is used for identifiers that can go in an HL7 V3 II (instance identifier) data type, and can then identify this questionnaire outside of FHIR, where it is not possible to use the logical URI.; (xsd)identifier:Identifier>*
	 <  The identifier that is used to identify this version of the questionnaire when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the questionnaire author and is not expected to be globally unique. For example, it might be a timestamp (e.g. yyyymmdd) if a managed version is not available. There is also no expectation that versions can be placed in a lexicographical sequence. There may be different questionnaire instances that have the same identifier but different versions.  The version can be appended to the url in a reference to allow a reference to a particular business version of the questionnaire with the format [url]|[version].; (xsd)version:string>?
	 <  A natural language name identifying the questionnaire. This name should be usable as an identifier for the module by machine processing applications such as code generation. The name is not expected to be globally unique. The name should be a simple alphanumeric type name to ensure that it is machine-processing friendly.; (xsd)name:string>?
	 <  A short, descriptive, user-friendly title for the questionnaire. This name does not need to be machine-processing friendly and may contain punctuation, white-space, etc.; (xsd)title:string>?
	[]<  The URL of a Questionnaire that this Questionnaire is based on.; (xsd)derivedFrom:canonical>*
	 <  The status of this questionnaire. Enables tracking the life-cycle of the content. Allows filtering of questionnaires that are appropriate for use versus not.; (xsd)status:code>
	 <  A Boolean value to indicate that this questionnaire is authored for testing purposes (or education/evaluation/marketing) and is not intended to be used for genuine usage. Allows filtering of questionnaires that are appropriate for use versus not.; (xsd)experimental:boolean>?
	[]<  The types of subjects that can be the subject of responses created for the questionnaire. If none are specified, then the subject is unlimited.; (xsd)subjectType:code>*
	 <  The date  (and optionally time) when the questionnaire was published. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the questionnaire changes. Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the questionnaire. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource.; (xsd)date:dateTime>?
	 <  The name of the organization or individual that published the questionnaire. Usually an organization but may be an individual. The publisher (or steward) of the questionnaire is the organization or individual primarily responsible for the maintenance and upkeep of the questionnaire. This is not necessarily the same individual or organization that developed and initially authored the content. The publisher is the primary point of contact for questions or issues with the questionnaire. This item SHOULD be populated unless the information is available from context.; (xsd)publisher:string>?
	[]<  Contact details to assist a user in finding and communicating with the publisher. May be a web site, an email address, a telephone number, etc.; (xsd)contact:ContactDetail>*
	 <  A free text natural language description of the questionnaire from a consumer's perspective. This description can be used to capture details such as why the questionnaire was built, comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the questionnaire as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context (e.g. the language of the questionnaire is presumed to be the predominant language in the place the questionnaire was created).; (xsd)description:markdown>?
	[]<  The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate questionnaire instances. When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.; (xsd)useContext:UsageContext>*
	[]<  A legal or geographic region in which the questionnaire is intended to be used. It may be possible for the questionnaire to be used in jurisdictions other than those for which it was originally designed or intended.; (xsd)jurisdiction:CodeableConcept>*
	 <  Explanation of why this questionnaire is needed and why it has been designed as it has. This element does not describe the usage of the questionnaire. Instead, it provides traceability of ''why'' the resource is either needed or ''why'' it is defined as it is.  This may be used to point to source materials or specifications that drove the structure of this questionnaire.; (xsd)purpose:markdown>?
	 <  A copyright statement relating to the questionnaire and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the questionnaire.; (xsd)copyright:markdown>?
	 <  The date on which the resource content was approved by the publisher. Approval happens once when the content is officially approved for usage. The 'date' element may be more recent than the approval date because of minor changes or editorial corrections.; (xsd)approvalDate:date>?
	 <  The date on which the resource content was last reviewed. Review happens periodically after approval but does not change the original approval date. If specified, this date follows the original approval date.; (xsd)lastReviewDate:date>?
	 <  The period during which the questionnaire content was or is planned to be in active use. The effective period for a questionnaire  determines when the content is applicable for usage and is independent of publication and review dates. For example, a measure intended to be used for the year 2016 might be published in 2015.; (xsd)effectivePeriod:Period>?
	[]<  An identifier for this question or group of questions in a particular terminology such as LOINC.; (xsd)code:Coding>*
	[]<  A particular question, question grouping or display text that is part of the questionnaire. The content of the questionnaire is constructed from an ordered, hierarchical collection of items.; (xsd)item:sdc-questionnaire-pop-obsn.item>*
	 <  Optional Extension Element - found in all resources.; (xsd)versionAlgorithm:Extension>?
	 <  Optional Extension Element - found in all resources.; (xsd)copyrightLabel:Extension>?
	 <  Indicates the time-period (from 'now') to search for observations that match the Questionnaire.item.code and Questionnaire.subject when pre-populating the QuestionnaireResponse. If multiple Observations are found, the most recent is used.; (xsd)observationLinkPeriod:sdc-questionnaire-observationLinkPeriod>?

🔗  A particular question, question grouping or display text that is part of the questionnaire. The content of the questionnaire is constructed from an ordered, hierarchical collection of items.sdc-questionnaire-pop-obsn.item(xsd)=
	 <#base:Questionnaire.item>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  An Extension; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  An identifier that is unique within the Questionnaire allowing linkage to the equivalent item in a QuestionnaireResponse resource. This ''can'' be a meaningful identifier (e.g. a LOINC code) but is not intended to have any meaning.  GUIDs or sequential numbers are appropriate here.; (xsd)linkId:string>
	 <  This element is a URI that refers to an [ElementDefinition](http://hl7.org/fhir/R4/elementdefinition.html) that provides information about this item, including information that might otherwise be included in the instance of the Questionnaire resource. A detailed description of the construction of the URI is shown in Comments, below. If this element is present then the following element values MAY be derived from the Element Definition if the corresponding elements of this Questionnaire resource instance have no value:

* code (ElementDefinition.code) 
* type (ElementDefinition.type) 
* required (ElementDefinition.min) 
* repeats (ElementDefinition.max) 
* maxLength (ElementDefinition.maxLength) 
* answerValueSet (ElementDefinition.binding)
* options (ElementDefinition.binding). The uri refers to an ElementDefinition in a [StructureDefinition](http://hl7.org/fhir/R4/structuredefinition.html#) and always starts with the [canonical URL](http://hl7.org/fhir/R4/references.html#canonical) for the target resource. When referring to a StructureDefinition, a fragment identifier is used to specify the element definition by its id [Element.id](http://hl7.org/fhir/R4/element-definitions.html#Element.id). E.g. http://hl7.org/fhir/StructureDefinition/Observation#Observation.value[x]. In the absence of a fragment identifier, the first/root element definition in the target is the matching element definition.; (xsd)definition:uri>?
	[]<  A terminology code that corresponds to this group or question (e.g. a code from LOINC, which defines many questions and answers). The value may come from the ElementDefinition referred to by .definition.; (xsd)code:Coding>*
	 <  A short label for a particular group, question or set of display text within the questionnaire used for reference by the individual completing 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.  Typically, these won't be used for "display" items, though such use is not prohibited.  Systems SHOULD NOT generate their own prefixes if prefixes are defined for any items within a Questionnaire.; (xsd)prefix:string>?
	 <  The name of a section, the text of a question or text content for a display item. When using this element to represent the name of a section, use group type item and also make sure to limit the text element to a short string suitable for display as a section heading.  Group item instructions should be included as a display type item within the group.; (xsd)text:string>?
	 <  The type of questionnaire item this is - whether text for display, a grouping of other items or a particular type of data to be captured (string, integer, coded choice, etc.). Time is handled using "string".  File is handled using Attachment.  (Content can be sent as a contained binary).; (xsd)type:code>
	[]<  A constraint indicating that this item should only be enabled (displayed/allow answers to be captured) when the specified condition is true. If multiple repetitions of this extension are present, the item should be enabled when the condition for *any* of the repetitions is true.  I.e. treat "enableWhen"s as being joined by an "or" clause.  This element is a modifier because if enableWhen is present for an item, "required" is ignored unless one of the enableWhen conditions is met. When an item is disabled, all of its descendants are disabled, regardless of what their own enableWhen logic might evaluate to.; (xsd)enableWhen:sdc-questionnaire-pop-obsn.item.enableWhen>*
	 <  Controls how multiple enableWhen values are interpreted -  whether all or any must be true. This element must be specified if more than one enableWhen value is provided.; (xsd)enableBehavior:code>?
	 <  An indication, if true, that the item must be present in a "completed" QuestionnaireResponse.  If false, the item may be skipped when answering the questionnaire. Questionnaire.item.required only has meaning for elements that are conditionally enabled with enableWhen if the condition evaluates to true.  If an item that contains other items is marked as required, that does not automatically make the contained elements required (though required groups must contain at least one child element). The value may come from the ElementDefinition referred to by .definition.; (xsd)required:boolean>?
	 <  An indication, if true, that a QuestionnaireResponse for this item may include multiple answers associated with a single instance of this item (for question-type items) or multiple repetitions of the item (for group-type items) If a question is marked as repeats=true, then multiple answers can be provided for the question in the corresponding QuestionnaireResponse.  When rendering the questionnaire, it is up to the rendering software whether to render the question text for each answer repetition (i.e. "repeat the question") or to simply allow entry/selection of multiple answers for the question (repeat the answers).  Which is most appropriate visually may depend on the type of answer as well as whether there are nested items.

The resulting QuestionnaireResponse will be populated the same way regardless of rendering - one 'question' item with multiple answer values.

 The value may come from the ElementDefinition referred to by .definition.; (xsd)repeats:boolean>?
	 <  An indication, when true, that the value cannot be changed by a human respondent 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.; (xsd)readOnly:boolean>?
	 <  The maximum number of characters that are permitted in the answer to be considered a "valid" QuestionnaireResponse. For base64binary, reflects the number of characters representing the encoded data, not the number of bytes of the binary data. The value may come from the ElementDefinition referred to by .definition.; (xsd)maxLength:integer>?
	 <  A reference to a value set containing a list of codes representing permitted answers for a "choice" or "open-choice" question. LOINC defines many useful value sets for questionnaire responses. See [LOINC Answer Lists](http://hl7.org/fhir/R4/loinc.html#alist). The value may come from the ElementDefinition referred to by .definition.; (xsd)answerValueSet:canonical>?
	[]<  One of the permitted answers for a "choice" or "open-choice" question. This element can be used when the value set machinery of answerValueSet is deemed too cumbersome or when there's a need to capture possible answers that are not codes.; (xsd)answerOption:sdc-questionnaire-pop-obsn.item.answerOption>*
	[]<  One or more values that should be pre-populated in the answer when initially rendering the questionnaire for user input. The user is allowed to change the value and override the default (unless marked as read-only). If the user doesn't change the value, then this initial value will be persisted when the QuestionnaireResponse is initially created.  Note that initial values can influence results.  The data type of initial[x] must agree with the item.type, and only repeating items can have more then one initial value.; (xsd)initial:sdc-questionnaire-pop-obsn.item.initial>*
	[]<  Text, questions and other groups to be nested beneath a question or group. There is no specified limit to the depth of nesting.  However, Questionnaire authors are encouraged to consider the impact on the user and user interface of overly deep nesting.; (xsd)item:Questionnaire.item>*
	 <  If true, indicates that the extended item should not be displayed to the user. If an item is hidden, all descendant items are hidden as well.  See additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/rendering.html#hidden).; (xsd)hidden:questionnaire-hidden>?
	 <  Optional Extension Element - found in all resources.; (xsd)answerConstraint:Extension>?
	 <  Indicates the time-period (from 'now') to search for observations that match the Questionnaire.item.code and Questionnaire.subject when pre-populating the QuestionnaireResponse. If multiple Observations are found, the most recent is used.; (xsd)observationLinkPeriod:sdc-questionnaire-observationLinkPeriod>?
	 <  Provides a computable unit of measure associated with numeric questions to support subsequent computation on responses. This is for use on items of type integer and decimal, and it's purpose is to support converting the integer or decimal answer into a Quantity when extracting the data into a resource. The human-readable unit is conveyed as a display element.  This element is for computation purposes.; (xsd)unit:questionnaire-unit>?
	 <  If present and true, indicates that the item establishes a different subject for the group in a response. The item type must be "reference" and there can only be one item with this extension in each group.; (xsd)isSubject:sdc-questionnaire-isSubject>?

🔗  One of the permitted answers for a "choice" or "open-choice" question. This element can be used when the value set machinery of answerValueSet is deemed too cumbersome or when there's a need to capture possible answers that are not codes.sdc-questionnaire-pop-obsn.item.answerOption(xsd)=
	 <#base:Questionnaire.item.answerOption>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 ( <valueCoding:Coding>
		 | <valueDate:date>
		 | <valueInteger:integer>
		 | <valueResource:Resource>
		 | <valueString:string>
		 | <valueTime:time>)
	 <  Indicates whether the answer value is selected when the list of possible answers is initially shown. Use this instead of initial[v] if answerValueSet is present.; (xsd)initialSelected:boolean>?

🔗  A constraint indicating that this item should only be enabled (displayed/allow answers to be captured) when the specified condition is true. If multiple repetitions of this extension are present, the item should be enabled when the condition for *any* of the repetitions is true.  I.e. treat "enableWhen"s as being joined by an "or" clause.  This element is a modifier because if enableWhen is present for an item, "required" is ignored unless one of the enableWhen conditions is met. When an item is disabled, all of its descendants are disabled, regardless of what their own enableWhen logic might evaluate to.sdc-questionnaire-pop-obsn.item.enableWhen(xsd)=
	 <#base:Questionnaire.item.enableWhen>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  The linkId for the question whose answer (or lack of answer) governs whether this item is enabled. If multiple question occurrences are present for the same question (same linkId), then this refers to the nearest question occurrence reachable by tracing first the "ancestor" axis and then the "preceding" axis and then the "following" axis.; (xsd)question:string>
	 <  Specifies the criteria by which the question is enabled.; (xsd)operator:code>
	 <  A value that the referenced question is tested using the specified operator in order for the item to be enabled.; (xsd)answer:( <boolean>
		 | <Coding>
		 | <date>
		 | <dateTime>
		 | <decimal>
		 | <integer>
		 | <Quantity>
		 | <Resource>
		 | <string>
		 | <time>)>

🔗  One or more values that should be pre-populated in the answer when initially rendering the questionnaire for user input. The user is allowed to change the value and override the default (unless marked as read-only). If the user doesn't change the value, then this initial value will be persisted when the QuestionnaireResponse is initially created.  Note that initial values can influence results.  The data type of initial[x] must agree with the item.type, and only repeating items can have more then one initial value.sdc-questionnaire-pop-obsn.item.initial(xsd)=
	 <#base:Questionnaire.item.initial>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 ( <valueAttachment:Attachment>
		 | <valueBoolean:boolean>
		 | <valueCoding:Coding>
		 | <valueDate:date>
		 | <valueDateTime:dateTime>
		 | <valueDecimal:decimal>
		 | <valueInteger:integer>
		 | <valueQuantity:Quantity>
		 | <valueResource:Resource>
		 | <valueString:string>
		 | <valueTime:time>
		 | <valueUri:uri>)

🔗  Defines elements that support auto-population and pre-population of questionnaires  using the StructureMap-based population mechanism.sdc-questionnaire-pop-smap(xsd)=
	 <#base:sdc-questionnairecommon>
	 <  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.; (xsd)id:string>?
	 <  The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.; (xsd)meta:Meta>?
	 <  A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. 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. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.; (xsd)implicitRules:uri>?
	 <  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).; (xsd)language:code>?
	 <  A human-readable narrative that contains a summary of the resource and can 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. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied).  This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.; (xsd)text: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. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.; (xsd)contained:Resource>*
	[]<  An Extension; (xsd)extension:Extension>*
	[]<  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 and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  An absolute URI that is used to identify this questionnaire when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which at which an authoritative instance of this questionnaire is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the questionnaire is stored on different servers. The name of the referenced questionnaire can be conveyed using the http://hl7.org/fhir/StructureDefinition/display extension.; (xsd)url:uri>?
	[]<  A formal identifier that is used to identify this questionnaire when it is represented in other formats, or referenced in a specification, model, design or an instance. Typically, this is used for identifiers that can go in an HL7 V3 II (instance identifier) data type, and can then identify this questionnaire outside of FHIR, where it is not possible to use the logical URI.; (xsd)identifier:Identifier>*
	 <  The identifier that is used to identify this version of the questionnaire when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the questionnaire author and is not expected to be globally unique. For example, it might be a timestamp (e.g. yyyymmdd) if a managed version is not available. There is also no expectation that versions can be placed in a lexicographical sequence. There may be different questionnaire instances that have the same identifier but different versions.  The version can be appended to the url in a reference to allow a reference to a particular business version of the questionnaire with the format [url]|[version].; (xsd)version:string>?
	 <  A natural language name identifying the questionnaire. This name should be usable as an identifier for the module by machine processing applications such as code generation. The name is not expected to be globally unique. The name should be a simple alphanumeric type name to ensure that it is machine-processing friendly.; (xsd)name:string>?
	 <  A short, descriptive, user-friendly title for the questionnaire. This name does not need to be machine-processing friendly and may contain punctuation, white-space, etc.; (xsd)title:string>?
	[]<  The URL of a Questionnaire that this Questionnaire is based on.; (xsd)derivedFrom:canonical>*
	 <  The status of this questionnaire. Enables tracking the life-cycle of the content. Allows filtering of questionnaires that are appropriate for use versus not.; (xsd)status:code>
	 <  A Boolean value to indicate that this questionnaire is authored for testing purposes (or education/evaluation/marketing) and is not intended to be used for genuine usage. Allows filtering of questionnaires that are appropriate for use versus not.; (xsd)experimental:boolean>?
	[]<  The types of subjects that can be the subject of responses created for the questionnaire. If none are specified, then the subject is unlimited.; (xsd)subjectType:code>*
	 <  The date  (and optionally time) when the questionnaire was published. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the questionnaire changes. Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the questionnaire. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource.; (xsd)date:dateTime>?
	 <  The name of the organization or individual that published the questionnaire. Usually an organization but may be an individual. The publisher (or steward) of the questionnaire is the organization or individual primarily responsible for the maintenance and upkeep of the questionnaire. This is not necessarily the same individual or organization that developed and initially authored the content. The publisher is the primary point of contact for questions or issues with the questionnaire. This item SHOULD be populated unless the information is available from context.; (xsd)publisher:string>?
	[]<  Contact details to assist a user in finding and communicating with the publisher. May be a web site, an email address, a telephone number, etc.; (xsd)contact:ContactDetail>*
	 <  A free text natural language description of the questionnaire from a consumer's perspective. This description can be used to capture details such as why the questionnaire was built, comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the questionnaire as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context (e.g. the language of the questionnaire is presumed to be the predominant language in the place the questionnaire was created).; (xsd)description:markdown>?
	[]<  The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate questionnaire instances. When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.; (xsd)useContext:UsageContext>*
	[]<  A legal or geographic region in which the questionnaire is intended to be used. It may be possible for the questionnaire to be used in jurisdictions other than those for which it was originally designed or intended.; (xsd)jurisdiction:CodeableConcept>*
	 <  Explanation of why this questionnaire is needed and why it has been designed as it has. This element does not describe the usage of the questionnaire. Instead, it provides traceability of ''why'' the resource is either needed or ''why'' it is defined as it is.  This may be used to point to source materials or specifications that drove the structure of this questionnaire.; (xsd)purpose:markdown>?
	 <  A copyright statement relating to the questionnaire and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the questionnaire.; (xsd)copyright:markdown>?
	 <  The date on which the resource content was approved by the publisher. Approval happens once when the content is officially approved for usage. The 'date' element may be more recent than the approval date because of minor changes or editorial corrections.; (xsd)approvalDate:date>?
	 <  The date on which the resource content was last reviewed. Review happens periodically after approval but does not change the original approval date. If specified, this date follows the original approval date.; (xsd)lastReviewDate:date>?
	 <  The period during which the questionnaire content was or is planned to be in active use. The effective period for a questionnaire  determines when the content is applicable for usage and is independent of publication and review dates. For example, a measure intended to be used for the year 2016 might be published in 2015.; (xsd)effectivePeriod:Period>?
	[]<  An identifier for this question or group of questions in a particular terminology such as LOINC.; (xsd)code:Coding>*
	[]<  A particular question, question grouping or display text that is part of the questionnaire. The content of the questionnaire is constructed from an ordered, hierarchical collection of items.; (xsd)item:sdc-questionnaire-pop-smap.item>*
	 <  Optional Extension Element - found in all resources.; (xsd)versionAlgorithm:Extension>?
	 <  Optional Extension Element - found in all resources.; (xsd)copyrightLabel:Extension>?
	[]<  Resources that provide context for form processing logic (pre-population, flow-control, drop-down selection, etc.) when creating/displaying/editing a QuestionnaireResponse. 3 of these launch contexts are aligned with the existing SMART on FHIR "launch" contexts.; (xsd)launchContext:sdc-questionnaire-launchContext>*
	 <  A Batch Bundle containing a set of queries that should be executed to provide source data for a StructureMap to create a populated QuestionnaireResponse.; (xsd)sourceQueries:sdc-questionnaire-sourceQueries>?
	[]<  StructureMaps that have this QuestionnaireResponses for this Questionnaire as 'target' - i.e. that can be used to create QuestionnaireResponses that are valid against this Questionnaire.; (xsd)sourceStructureMap:sdc-questionnaire-sourceStructureMap>*

🔗  A particular question, question grouping or display text that is part of the questionnaire. The content of the questionnaire is constructed from an ordered, hierarchical collection of items.sdc-questionnaire-pop-smap.item(xsd)=
	 <#base:Questionnaire.item>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  An Extension; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  An identifier that is unique within the Questionnaire allowing linkage to the equivalent item in a QuestionnaireResponse resource. This ''can'' be a meaningful identifier (e.g. a LOINC code) but is not intended to have any meaning.  GUIDs or sequential numbers are appropriate here.; (xsd)linkId:string>
	 <  This element is a URI that refers to an [ElementDefinition](http://hl7.org/fhir/R4/elementdefinition.html) that provides information about this item, including information that might otherwise be included in the instance of the Questionnaire resource. A detailed description of the construction of the URI is shown in Comments, below. If this element is present then the following element values MAY be derived from the Element Definition if the corresponding elements of this Questionnaire resource instance have no value:

* code (ElementDefinition.code) 
* type (ElementDefinition.type) 
* required (ElementDefinition.min) 
* repeats (ElementDefinition.max) 
* maxLength (ElementDefinition.maxLength) 
* answerValueSet (ElementDefinition.binding)
* options (ElementDefinition.binding). The uri refers to an ElementDefinition in a [StructureDefinition](http://hl7.org/fhir/R4/structuredefinition.html#) and always starts with the [canonical URL](http://hl7.org/fhir/R4/references.html#canonical) for the target resource. When referring to a StructureDefinition, a fragment identifier is used to specify the element definition by its id [Element.id](http://hl7.org/fhir/R4/element-definitions.html#Element.id). E.g. http://hl7.org/fhir/StructureDefinition/Observation#Observation.value[x]. In the absence of a fragment identifier, the first/root element definition in the target is the matching element definition.; (xsd)definition:uri>?
	[]<  A terminology code that corresponds to this group or question (e.g. a code from LOINC, which defines many questions and answers). The value may come from the ElementDefinition referred to by .definition.; (xsd)code:Coding>*
	 <  A short label for a particular group, question or set of display text within the questionnaire used for reference by the individual completing 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.  Typically, these won't be used for "display" items, though such use is not prohibited.  Systems SHOULD NOT generate their own prefixes if prefixes are defined for any items within a Questionnaire.; (xsd)prefix:string>?
	 <  The name of a section, the text of a question or text content for a display item. When using this element to represent the name of a section, use group type item and also make sure to limit the text element to a short string suitable for display as a section heading.  Group item instructions should be included as a display type item within the group.; (xsd)text:string>?
	 <  The type of questionnaire item this is - whether text for display, a grouping of other items or a particular type of data to be captured (string, integer, coded choice, etc.). Time is handled using "string".  File is handled using Attachment.  (Content can be sent as a contained binary).; (xsd)type:code>
	[]<  A constraint indicating that this item should only be enabled (displayed/allow answers to be captured) when the specified condition is true. If multiple repetitions of this extension are present, the item should be enabled when the condition for *any* of the repetitions is true.  I.e. treat "enableWhen"s as being joined by an "or" clause.  This element is a modifier because if enableWhen is present for an item, "required" is ignored unless one of the enableWhen conditions is met. When an item is disabled, all of its descendants are disabled, regardless of what their own enableWhen logic might evaluate to.; (xsd)enableWhen:sdc-questionnaire-pop-smap.item.enableWhen>*
	 <  Controls how multiple enableWhen values are interpreted -  whether all or any must be true. This element must be specified if more than one enableWhen value is provided.; (xsd)enableBehavior:code>?
	 <  An indication, if true, that the item must be present in a "completed" QuestionnaireResponse.  If false, the item may be skipped when answering the questionnaire. Questionnaire.item.required only has meaning for elements that are conditionally enabled with enableWhen if the condition evaluates to true.  If an item that contains other items is marked as required, that does not automatically make the contained elements required (though required groups must contain at least one child element). The value may come from the ElementDefinition referred to by .definition.; (xsd)required:boolean>?
	 <  An indication, if true, that a QuestionnaireResponse for this item may include multiple answers associated with a single instance of this item (for question-type items) or multiple repetitions of the item (for group-type items) If a question is marked as repeats=true, then multiple answers can be provided for the question in the corresponding QuestionnaireResponse.  When rendering the questionnaire, it is up to the rendering software whether to render the question text for each answer repetition (i.e. "repeat the question") or to simply allow entry/selection of multiple answers for the question (repeat the answers).  Which is most appropriate visually may depend on the type of answer as well as whether there are nested items.

The resulting QuestionnaireResponse will be populated the same way regardless of rendering - one 'question' item with multiple answer values.

 The value may come from the ElementDefinition referred to by .definition.; (xsd)repeats:boolean>?
	 <  An indication, when true, that the value cannot be changed by a human respondent 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.; (xsd)readOnly:boolean>?
	 <  The maximum number of characters that are permitted in the answer to be considered a "valid" QuestionnaireResponse. For base64binary, reflects the number of characters representing the encoded data, not the number of bytes of the binary data. The value may come from the ElementDefinition referred to by .definition.; (xsd)maxLength:integer>?
	 <  A reference to a value set containing a list of codes representing permitted answers for a "choice" or "open-choice" question. LOINC defines many useful value sets for questionnaire responses. See [LOINC Answer Lists](http://hl7.org/fhir/R4/loinc.html#alist). The value may come from the ElementDefinition referred to by .definition.; (xsd)answerValueSet:canonical>?
	[]<  One of the permitted answers for a "choice" or "open-choice" question. This element can be used when the value set machinery of answerValueSet is deemed too cumbersome or when there's a need to capture possible answers that are not codes.; (xsd)answerOption:sdc-questionnaire-pop-smap.item.answerOption>*
	[]<  One or more values that should be pre-populated in the answer when initially rendering the questionnaire for user input. The user is allowed to change the value and override the default (unless marked as read-only). If the user doesn't change the value, then this initial value will be persisted when the QuestionnaireResponse is initially created.  Note that initial values can influence results.  The data type of initial[x] must agree with the item.type, and only repeating items can have more then one initial value.; (xsd)initial:sdc-questionnaire-pop-smap.item.initial>*
	[]<  Text, questions and other groups to be nested beneath a question or group. There is no specified limit to the depth of nesting.  However, Questionnaire authors are encouraged to consider the impact on the user and user interface of overly deep nesting.; (xsd)item:Questionnaire.item>*
	 <  If true, indicates that the extended item should not be displayed to the user. If an item is hidden, all descendant items are hidden as well.  See additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/rendering.html#hidden).; (xsd)hidden:questionnaire-hidden>?
	 <  Optional Extension Element - found in all resources.; (xsd)answerConstraint:Extension>?
	 <  Provides a computable unit of measure associated with numeric questions to support subsequent computation on responses. This is for use on items of type integer and decimal, and it's purpose is to support converting the integer or decimal answer into a Quantity when extracting the data into a resource. The human-readable unit is conveyed as a display element.  This element is for computation purposes.; (xsd)unit:questionnaire-unit>?
	 <  If true, indicates that the extended item should not be displayed to the user. If an item is hidden, all descendant items are hidden as well.  See additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/rendering.html#hidden).; (xsd)itemHidden:questionnaire-hidden>?
	 <  If present and true, indicates that the item establishes a different subject for the group in a response. The item type must be "reference" and there can only be one item with this extension in each group.; (xsd)isSubject:sdc-questionnaire-isSubject>?

🔗  One of the permitted answers for a "choice" or "open-choice" question. This element can be used when the value set machinery of answerValueSet is deemed too cumbersome or when there's a need to capture possible answers that are not codes.sdc-questionnaire-pop-smap.item.answerOption(xsd)=
	 <#base:Questionnaire.item.answerOption>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 ( <valueCoding:Coding>
		 | <valueDate:date>
		 | <valueInteger:integer>
		 | <valueResource:Resource>
		 | <valueString:string>
		 | <valueTime:time>)
	 <  Indicates whether the answer value is selected when the list of possible answers is initially shown. Use this instead of initial[v] if answerValueSet is present.; (xsd)initialSelected:boolean>?

🔗  A constraint indicating that this item should only be enabled (displayed/allow answers to be captured) when the specified condition is true. If multiple repetitions of this extension are present, the item should be enabled when the condition for *any* of the repetitions is true.  I.e. treat "enableWhen"s as being joined by an "or" clause.  This element is a modifier because if enableWhen is present for an item, "required" is ignored unless one of the enableWhen conditions is met. When an item is disabled, all of its descendants are disabled, regardless of what their own enableWhen logic might evaluate to.sdc-questionnaire-pop-smap.item.enableWhen(xsd)=
	 <#base:Questionnaire.item.enableWhen>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  The linkId for the question whose answer (or lack of answer) governs whether this item is enabled. If multiple question occurrences are present for the same question (same linkId), then this refers to the nearest question occurrence reachable by tracing first the "ancestor" axis and then the "preceding" axis and then the "following" axis.; (xsd)question:string>
	 <  Specifies the criteria by which the question is enabled.; (xsd)operator:code>
	 <  A value that the referenced question is tested using the specified operator in order for the item to be enabled.; (xsd)answer:( <boolean>
		 | <Coding>
		 | <date>
		 | <dateTime>
		 | <decimal>
		 | <integer>
		 | <Quantity>
		 | <Resource>
		 | <string>
		 | <time>)>

🔗  One or more values that should be pre-populated in the answer when initially rendering the questionnaire for user input. The user is allowed to change the value and override the default (unless marked as read-only). If the user doesn't change the value, then this initial value will be persisted when the QuestionnaireResponse is initially created.  Note that initial values can influence results.  The data type of initial[x] must agree with the item.type, and only repeating items can have more then one initial value.sdc-questionnaire-pop-smap.item.initial(xsd)=
	 <#base:Questionnaire.item.initial>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 ( <valueAttachment:Attachment>
		 | <valueBoolean:boolean>
		 | <valueCoding:Coding>
		 | <valueDate:date>
		 | <valueDateTime:dateTime>
		 | <valueDecimal:decimal>
		 | <valueInteger:integer>
		 | <valueQuantity:Quantity>
		 | <valueResource:Resource>
		 | <valueString:string>
		 | <valueTime:time>
		 | <valueUri:uri>)

🔗  Indicates the terminology server(s) that are known to be capable of returning and potentially expanding the value set(s) associated with the whole questionnaire or a particular group or question within the questionnaire (depending on where the extension appears).  If a full URL is not provided AND the requested query is a terminology operation (e.g. $lookup or $expand) the client SHOULD execute the operation against the preferredTerminologyServer rather than the local repository. Systems SHOULD evaluate value sets using terminology servers as follows:  First, try any terminology servers declared on the item in question.  If there are more then one, try them in the order they appear.  Then try any servers that appear on ancestor items in order of closest ancestor up to any on the Questionnaire.  If there are no declared servers or none of the ones listed provide a useful response, the form filler may then try any of the typical servers it would normally use.  A 'useful response' means a response that provides a valid (though potentially empty) expansion.  Clients MAY wish to log/report errors returned by terminology servers. This includes those referenced by answerValueSet as well as the unitValueSet extension.sdc-questionnaire-preferredTerminologyServer(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	 <  An Extension; (xsd)extension:Extension>{0,0}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaire-preferredTerminologyServer; (xsd)url:string>
	 <  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)value:url>?

🔗  Marks a questionnaire as being adaptive.  Value can either be a boolean (if true, indicates adaptive) or a URL for the base URL of a server that can perform the nextQuestion operation for this particular questionnaire. There can only be one in a questionnaire if the value used is boolean.sdc-questionnaire-questionnaireAdaptive(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	 <  An Extension; (xsd)extension:Extension>{0,0}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaire-questionnaireAdaptive; (xsd)url:string>
	 ( <valueBoolean:boolean>
		 | <valueUrl:url>)?

🔗  Defines additional capabilities for controlling the rendering of the questionnaire.sdc-questionnaire-render(xsd)=
	 <#base:sdc-questionnairecommon>
	 <  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.; (xsd)id:string>?
	 <  The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.; (xsd)meta:Meta>?
	 <  A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. 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. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.; (xsd)implicitRules:uri>?
	 <  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).; (xsd)language:code>?
	 <  A human-readable narrative that contains a summary of the resource and can 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. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied).  This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.; (xsd)text: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. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.; (xsd)contained:Resource>*
	[]<  An Extension; (xsd)extension:Extension>*
	[]<  An Extension; (xsd)modifierExtension:Extension>*
	 <  An absolute URI that is used to identify this questionnaire when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which at which an authoritative instance of this questionnaire is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the questionnaire is stored on different servers. The name of the referenced questionnaire can be conveyed using the http://hl7.org/fhir/StructureDefinition/display extension.; (xsd)url:uri>?
	[]<  A formal identifier that is used to identify this questionnaire when it is represented in other formats, or referenced in a specification, model, design or an instance. Typically, this is used for identifiers that can go in an HL7 V3 II (instance identifier) data type, and can then identify this questionnaire outside of FHIR, where it is not possible to use the logical URI.; (xsd)identifier:Identifier>*
	 <  The identifier that is used to identify this version of the questionnaire when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the questionnaire author and is not expected to be globally unique. For example, it might be a timestamp (e.g. yyyymmdd) if a managed version is not available. There is also no expectation that versions can be placed in a lexicographical sequence. There may be different questionnaire instances that have the same identifier but different versions.  The version can be appended to the url in a reference to allow a reference to a particular business version of the questionnaire with the format [url]|[version].; (xsd)version:string>?
	 <  A natural language name identifying the questionnaire. This name should be usable as an identifier for the module by machine processing applications such as code generation. The name is not expected to be globally unique. The name should be a simple alphanumeric type name to ensure that it is machine-processing friendly.; (xsd)name:string>?
	 <  A short, descriptive, user-friendly title for the questionnaire. This name does not need to be machine-processing friendly and may contain punctuation, white-space, etc.; (xsd)title:sdc-questionnaire-render.title>?
	[]<  The URL of a Questionnaire that this Questionnaire is based on.; (xsd)derivedFrom:canonical>*
	 <  The status of this questionnaire. Enables tracking the life-cycle of the content. Allows filtering of questionnaires that are appropriate for use versus not.; (xsd)status:code>
	 <  A Boolean value to indicate that this questionnaire is authored for testing purposes (or education/evaluation/marketing) and is not intended to be used for genuine usage. Allows filtering of questionnaires that are appropriate for use versus not.; (xsd)experimental:boolean>?
	[]<  The types of subjects that can be the subject of responses created for the questionnaire. If none are specified, then the subject is unlimited.; (xsd)subjectType:code>*
	 <  The date  (and optionally time) when the questionnaire was published. The date must change when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the questionnaire changes. Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the questionnaire. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource.; (xsd)date:dateTime>?
	 <  The name of the organization or individual that published the questionnaire. Usually an organization but may be an individual. The publisher (or steward) of the questionnaire is the organization or individual primarily responsible for the maintenance and upkeep of the questionnaire. This is not necessarily the same individual or organization that developed and initially authored the content. The publisher is the primary point of contact for questions or issues with the questionnaire. This item SHOULD be populated unless the information is available from context.; (xsd)publisher:string>?
	[]<  Contact details to assist a user in finding and communicating with the publisher. May be a web site, an email address, a telephone number, etc.; (xsd)contact:ContactDetail>*
	 <  A free text natural language description of the questionnaire from a consumer's perspective. This description can be used to capture details such as why the questionnaire was built, comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the questionnaire as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context (e.g. the language of the questionnaire is presumed to be the predominant language in the place the questionnaire was created).; (xsd)description:markdown>?
	[]<  The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate questionnaire instances. When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.; (xsd)useContext:UsageContext>*
	[]<  A legal or geographic region in which the questionnaire is intended to be used. It may be possible for the questionnaire to be used in jurisdictions other than those for which it was originally designed or intended.; (xsd)jurisdiction:CodeableConcept>*
	 <  Explanation of why this questionnaire is needed and why it has been designed as it has. This element does not describe the usage of the questionnaire. Instead, it provides traceability of ''why'' the resource is either needed or ''why'' it is defined as it is.  This may be used to point to source materials or specifications that drove the structure of this questionnaire.; (xsd)purpose:markdown>?
	 <  A copyright statement relating to the questionnaire and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the questionnaire.; (xsd)copyright:markdown>?
	 <  The date on which the resource content was approved by the publisher. Approval happens once when the content is officially approved for usage. The 'date' element may be more recent than the approval date because of minor changes or editorial corrections.; (xsd)approvalDate:date>?
	 <  The date on which the resource content was last reviewed. Review happens periodically after approval but does not change the original approval date. If specified, this date follows the original approval date.; (xsd)lastReviewDate:date>?
	 <  The period during which the questionnaire content was or is planned to be in active use. The effective period for a questionnaire  determines when the content is applicable for usage and is independent of publication and review dates. For example, a measure intended to be used for the year 2016 might be published in 2015.; (xsd)effectivePeriod:Period>?
	[]<  An identifier for this question or group of questions in a particular terminology such as LOINC.; (xsd)code:Coding>*
	[]<  A particular question, question grouping or display text that is part of the questionnaire. The content of the questionnaire is constructed from an ordered, hierarchical collection of items.; (xsd)item:sdc-questionnaire-render.item>*
	 <  Optional Extension Element - found in all resources.; (xsd)versionAlgorithm:Extension>?
	 <  Optional Extension Element - found in all resources.; (xsd)copyrightLabel:Extension>?
	[]<  Indicates an extension that must be supported by the system presenting the instance for data capture or end-user consumption. If a system does not recognize the extension or cannot implement the functionality defined by the extension, it should display an error message or warning and refrain from presenting the instance to the user or using it when capturing data. This may point to extensions that control the appearance of data elements, control what value elements have, what elements are or are not available, what elements can or cannot be edited, or rules about how editing may occur. This extension does NOT apply when simply rendering a resource for publication purposes or for other purposes not intended for end-user data capture or data consumption.; (xsd)rendering-criticalExtension:sdc-rendering-criticalExtension>*

🔗  A particular question, question grouping or display text that is part of the questionnaire. The content of the questionnaire is constructed from an ordered, hierarchical collection of items.sdc-questionnaire-render.item(xsd)=
	 <#base:Questionnaire.item>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  An Extension; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  An identifier that is unique within the Questionnaire allowing linkage to the equivalent item in a QuestionnaireResponse resource. This ''can'' be a meaningful identifier (e.g. a LOINC code) but is not intended to have any meaning.  GUIDs or sequential numbers are appropriate here.; (xsd)linkId:string>
	 <  This element is a URI that refers to an [ElementDefinition](http://hl7.org/fhir/R4/elementdefinition.html) that provides information about this item, including information that might otherwise be included in the instance of the Questionnaire resource. A detailed description of the construction of the URI is shown in Comments, below. If this element is present then the following element values MAY be derived from the Element Definition if the corresponding elements of this Questionnaire resource instance have no value:

* code (ElementDefinition.code) 
* type (ElementDefinition.type) 
* required (ElementDefinition.min) 
* repeats (ElementDefinition.max) 
* maxLength (ElementDefinition.maxLength) 
* answerValueSet (ElementDefinition.binding)
* options (ElementDefinition.binding). The uri refers to an ElementDefinition in a [StructureDefinition](http://hl7.org/fhir/R4/structuredefinition.html#) and always starts with the [canonical URL](http://hl7.org/fhir/R4/references.html#canonical) for the target resource. When referring to a StructureDefinition, a fragment identifier is used to specify the element definition by its id [Element.id](http://hl7.org/fhir/R4/element-definitions.html#Element.id). E.g. http://hl7.org/fhir/StructureDefinition/Observation#Observation.value[x]. In the absence of a fragment identifier, the first/root element definition in the target is the matching element definition.; (xsd)definition:uri>?
	[]<  A terminology code that corresponds to this group or question (e.g. a code from LOINC, which defines many questions and answers). The value may come from the ElementDefinition referred to by .definition.; (xsd)code:Coding>*
	 <  A short label for a particular group, question or set of display text within the questionnaire used for reference by the individual completing 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.  Typically, these won't be used for "display" items, though such use is not prohibited.  Systems SHOULD NOT generate their own prefixes if prefixes are defined for any items within a Questionnaire.; (xsd)prefix:sdc-questionnaire-render.item.prefix>?
	 <  The name of a section, the text of a question or text content for a display item. When using this element to represent the name of a section, use group type item and also make sure to limit the text element to a short string suitable for display as a section heading.  Group item instructions should be included as a display type item within the group.; (xsd)text:sdc-questionnaire-render.item.text>?
	 <  The type of questionnaire item this is - whether text for display, a grouping of other items or a particular type of data to be captured (string, integer, coded choice, etc.). Time is handled using "string".  File is handled using Attachment.  (Content can be sent as a contained binary).; (xsd)type:code>
	[]<  A constraint indicating that this item should only be enabled (displayed/allow answers to be captured) when the specified condition is true. If multiple repetitions of this extension are present, the item should be enabled when the condition for *any* of the repetitions is true.  I.e. treat "enableWhen"s as being joined by an "or" clause.  This element is a modifier because if enableWhen is present for an item, "required" is ignored unless one of the enableWhen conditions is met. When an item is disabled, all of its descendants are disabled, regardless of what their own enableWhen logic might evaluate to.; (xsd)enableWhen:sdc-questionnaire-render.item.enableWhen>*
	 <  Controls how multiple enableWhen values are interpreted -  whether all or any must be true. This element must be specified if more than one enableWhen value is provided.; (xsd)enableBehavior:code>?
	 <  An indication, if true, that the item must be present in a "completed" QuestionnaireResponse.  If false, the item may be skipped when answering the questionnaire. Questionnaire.item.required only has meaning for elements that are conditionally enabled with enableWhen if the condition evaluates to true.  If an item that contains other items is marked as required, that does not automatically make the contained elements required (though required groups must contain at least one child element). The value may come from the ElementDefinition referred to by .definition.; (xsd)required:boolean>?
	 <  An indication, if true, that a QuestionnaireResponse for this item may include multiple answers associated with a single instance of this item (for question-type items) or multiple repetitions of the item (for group-type items) If a question is marked as repeats=true, then multiple answers can be provided for the question in the corresponding QuestionnaireResponse.  When rendering the questionnaire, it is up to the rendering software whether to render the question text for each answer repetition (i.e. "repeat the question") or to simply allow entry/selection of multiple answers for the question (repeat the answers).  Which is most appropriate visually may depend on the type of answer as well as whether there are nested items.

The resulting QuestionnaireResponse will be populated the same way regardless of rendering - one 'question' item with multiple answer values.

 The value may come from the ElementDefinition referred to by .definition.; (xsd)repeats:boolean>?
	 <  An indication, when true, that the value cannot be changed by a human respondent 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.; (xsd)readOnly:boolean>?
	 <  The maximum number of characters that are permitted in the answer to be considered a "valid" QuestionnaireResponse. For base64binary, reflects the number of characters representing the encoded data, not the number of bytes of the binary data. The value may come from the ElementDefinition referred to by .definition.; (xsd)maxLength:integer>?
	 <  A reference to a value set containing a list of codes representing permitted answers for a "choice" or "open-choice" question. LOINC defines many useful value sets for questionnaire responses. See [LOINC Answer Lists](http://hl7.org/fhir/R4/loinc.html#alist). The value may come from the ElementDefinition referred to by .definition.; (xsd)answerValueSet:canonical>?
	[]<  One of the permitted answers for a "choice" or "open-choice" question. This element can be used when the value set machinery of answerValueSet is deemed too cumbersome or when there's a need to capture possible answers that are not codes.; (xsd)answerOption:sdc-questionnaire-render.item.answerOption>*
	[]<  One or more values that should be pre-populated in the answer when initially rendering the questionnaire for user input. The user is allowed to change the value and override the default (unless marked as read-only). If the user doesn't change the value, then this initial value will be persisted when the QuestionnaireResponse is initially created.  Note that initial values can influence results.  The data type of initial[x] must agree with the item.type, and only repeating items can have more then one initial value.; (xsd)initial:sdc-questionnaire-render.item.initial>*
	[]<  Text, questions and other groups to be nested beneath a question or group. There is no specified limit to the depth of nesting.  However, Questionnaire authors are encouraged to consider the impact on the user and user interface of overly deep nesting.; (xsd)item:Questionnaire.item>*
	 <  If true, indicates that the extended item should not be displayed to the user. If an item is hidden, all descendant items are hidden as well.  See additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/rendering.html#hidden).; (xsd)hidden:questionnaire-hidden>?
	 <  Optional Extension Element - found in all resources.; (xsd)answerConstraint:Extension>?
	 <  Media to render/make available as an accompaniment to the question being asked; (xsd)itemMedia:sdc-questionnaire-itemMedia>?
	 <  This extension is used when defining high-level questionnaires that will then be used as a basis for 'derived' Questionnaires that are further refined for use in specific organizations or contexts.  If the extension is present and set to 'true', it means that this item should be considered to be 'optional' from an adaptation perspective and that the question can be removed (i.e. not displayed) in derived questionnaires without impacting the validity of the instrument.  Alternatively, the element can be marked as 'hidden' and 'readOnly' and have a value or descendant item values declared using initialValue or initialExpression.  If the element with 'optionalDisplay=true' is marked as 'required=true', then this second approach is the only means to exclude the element from display. 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.; (xsd)itemOptionalDisplay:sdc-questionnaire-optionalDisplay>?
	 <  The short text for the item. This element is useful for an item that require a shorter text when rendered  (e.g. when displaying the item on a mobile phone).; (xsd)itemShortText:sdc-questionnaire-shortText>?
	 <  The label text to display beside free-text and/or unrestricted type values for an 'open' choice element.  E.g. 'Other, please specify', or 'Additional condition', or 'More reason(s)', etc.; (xsd)openLabel:sdc-questionnaire-openLabel>?
	 <  The type of data entry control or structure that should be used to render the item. Different controls may be appropriate for different item types.  It is up to the system rendering a questionnaire as to what controls it will support and for which data types.  See additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/rendering.html#itemControl).; (xsd)itemControl:questionnaire-itemControl>?
	 <  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.).  See additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/rendering.html#choiceOrientation).; (xsd)choiceOrientation:questionnaire-choiceOrientation>?
	 <  Describes the intended purpose of the rendered text.  For example - instructions, guidance on access control, maintenance information, etc. See additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/rendering.html#displayCategory).; (xsd)displayCategory:questionnaire-displayCategory>?
	[]<  A URL that resolves to additional supporting information or guidance related to the question.  See additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/rendering.html#supportLink).; (xsd)supportLink:questionnaire-supportLink>*
	[]<  Provides guidelines for rendering multi-column choices.  I.e. when displaying a list of codes (for `choice` or `open-choice` items) or a list of resources (for `reference` items), this extension allows the drop-down to have multiple columns.  For codes, the author can pick additional code system properties to display - such as alternate display names strength or form for drug codes, etc.  For references, the author can choose particular columns from the resource (e.g. first name, last name, specialty, address). Each repetition represents a column to display.; (xsd)choiceColumn:sdc-questionnaire-choiceColumn>*
	 <  When used with an item control that causes the question to appear as a column in a table, indicates the width to give to the column for this question. code missing = pixels; code = % = percentage.; (xsd)width:sdc-questionnaire-width>?
	 <  For slider-based controls, indicates the step size to use when toggling the control up or down. See additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/rendering.html#sliderStepValue).; (xsd)sliderStepValue:questionnaire-sliderStepValue>?
	 <  Additional instructions for the user to guide their input (i.e. a human readable version of a regular expression like "nnn-nnn-nnn"). In most UIs this is the placeholder (or 'ghost') text placed directly inside the edit controls and that disappear when the control gets the focus. For questionnaires, see additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/rendering.html#entryFormat).; (xsd)entryFormat>?
	 <  Indicates whether the child items of a group or question item is displayed in collapsible form.; (xsd)collapsible:sdc-questionnaire-collapsible>?
	 <  For questions with a set of options, indicates the number of columns across which those choices should be organized. E.g., 2 columns, 5 columns, etc. Systems will split the options to maintain balance across the columns. Whether the choices are listed horizontally first or vertically first depends on the choice-orientation extension. Default is vertically first. Note that the number of columns is a recommendation and may not be achievable in all display form factors.; (xsd)columnCount:sdc-questionnaire-columnCount>?
	 <  For string or text items, indicates the 'keyboard type' that should be used by the user interface to guide entry. The assertion applies on a per item basis and is not inherited.  If the item is 'text', only 'chat' should be declared if this extension is present.; (xsd)keyboardType:sdc-questionnaire-keyboard>?

🔗  One of the permitted answers for a "choice" or "open-choice" question. This element can be used when the value set machinery of answerValueSet is deemed too cumbersome or when there's a need to capture possible answers that are not codes.sdc-questionnaire-render.item.answerOption(xsd)=
	 <#base:Questionnaire.item.answerOption>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  An Extension; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 ( <valueCoding:Coding>
		 | <valueDate:date>
		 | <valueInteger:integer>
		 | <valueResource:Resource>
		 | <valueString:string>
		 | <valueTime:time>)
	 <  Indicates whether the answer value is selected when the list of possible answers is initially shown. Use this instead of initial[v] if answerValueSet is present.; (xsd)initialSelected:boolean>?
	 <  Media to render/make available as an accompaniment to a specific answer option; (xsd)itemAnswerMedia:sdc-questionnaire-itemAnswerMedia>?
	 <  The label to list in front of a code when presenting a list of possible values in a questionnaire-like fashion. See additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/rendering.html#optionPrefix).; (xsd)optionPrefix:questionnaire-optionPrefix>?
	 <  A potential answer that's allowed as the answer to this question. The data type of the value must agree with the item.type.; (xsd)valueString:sdc-questionnaire-render.item.answerOption.valueString>?
	 <  A potential answer that's allowed as the answer to this question. The data type of the value must agree with the item.type.; (xsd)valueCoding:sdc-questionnaire-render.item.answerOption.valueCoding>?

🔗  A potential answer that's allowed as the answer to this question. The data type of the value must agree with the item.type.sdc-questionnaire-render.item.answerOption.valueCoding(xsd)=
	 <#base:Coding>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	 <  The identification of the code system that defines the meaning of the symbol in the code. The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...).  OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously.; (xsd)system:uri>?
	 <  The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.; (xsd)version:string>?
	 <  A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).; (xsd)code>?
	 <  A representation of the meaning of the code in the system, following the rules of the system.; (xsd)display:sdc-questionnaire-render.item.answerOption.valueCoding.display>?
	 <  Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.; (xsd)userSelected:boolean>?

🔗  A representation of the meaning of the code in the system, following the rules of the system.sdc-questionnaire-render.item.answerOption.valueCoding.display(xsd)=
	 <#base:string>
	 <  unique id for the element within a resource (for internal references); (xsd)id:string>?
	[]<  An Extension; (xsd)extension:Extension>*
	 <  The actual value; (xsd)value:string>?
	 <  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.

For questionnaires, see additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/rendering.html#rendering-style).; (xsd)optionDisplay-renderingStyle:rendering-style>?
	 <  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. Existing [restrictions on XHTML content](http://hl7.org/fhir/R4/narrative.html#security) apply. Note that using [markdown](http://hl7.org/fhir/extensions/5.1.0StructureDefinition-rendering-markdown.html) allows for greater flexibility of display. For questionnaires, see additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/rendering.html#rendering-xhtml).; (xsd)optionDisplay-xhtml:rendering-xhtml>?

🔗  A potential answer that's allowed as the answer to this question. The data type of the value must agree with the item.type.sdc-questionnaire-render.item.answerOption.valueString(xsd)=
	 <#base:string>
	 <  unique id for the element within a resource (for internal references); (xsd)id:string>?
	[]<  An Extension; (xsd)extension:Extension>*
	 <  The actual value; (xsd)value:string>?
	 <  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.

For questionnaires, see additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/rendering.html#rendering-style).; (xsd)optionString-renderingStyle:rendering-style>?
	 <  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. Existing [restrictions on XHTML content](http://hl7.org/fhir/R4/narrative.html#security) apply. Note that using [markdown](http://hl7.org/fhir/extensions/5.1.0StructureDefinition-rendering-markdown.html) allows for greater flexibility of display. For questionnaires, see additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/rendering.html#rendering-xhtml).; (xsd)optionString-xhtml:rendering-xhtml>?

🔗  A constraint indicating that this item should only be enabled (displayed/allow answers to be captured) when the specified condition is true. If multiple repetitions of this extension are present, the item should be enabled when the condition for *any* of the repetitions is true.  I.e. treat "enableWhen"s as being joined by an "or" clause.  This element is a modifier because if enableWhen is present for an item, "required" is ignored unless one of the enableWhen conditions is met. When an item is disabled, all of its descendants are disabled, regardless of what their own enableWhen logic might evaluate to.sdc-questionnaire-render.item.enableWhen(xsd)=
	 <#base:Questionnaire.item.enableWhen>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  The linkId for the question whose answer (or lack of answer) governs whether this item is enabled. If multiple question occurrences are present for the same question (same linkId), then this refers to the nearest question occurrence reachable by tracing first the "ancestor" axis and then the "preceding" axis and then the "following" axis.; (xsd)question:string>
	 <  Specifies the criteria by which the question is enabled.; (xsd)operator:code>
	 <  A value that the referenced question is tested using the specified operator in order for the item to be enabled.; (xsd)answer:( <boolean>
		 | <Coding>
		 | <date>
		 | <dateTime>
		 | <decimal>
		 | <integer>
		 | <Quantity>
		 | <Resource>
		 | <string>
		 | <time>)>

🔗  One or more values that should be pre-populated in the answer when initially rendering the questionnaire for user input. The user is allowed to change the value and override the default (unless marked as read-only). If the user doesn't change the value, then this initial value will be persisted when the QuestionnaireResponse is initially created.  Note that initial values can influence results.  The data type of initial[x] must agree with the item.type, and only repeating items can have more then one initial value.sdc-questionnaire-render.item.initial(xsd)=
	 <#base:Questionnaire.item.initial>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 ( <valueAttachment:Attachment>
		 | <valueBoolean:boolean>
		 | <valueCoding:Coding>
		 | <valueDate:date>
		 | <valueDateTime:dateTime>
		 | <valueDecimal:decimal>
		 | <valueInteger:integer>
		 | <valueQuantity:Quantity>
		 | <valueResource:Resource>
		 | <valueString:string>
		 | <valueTime:time>
		 | <valueUri:uri>)

🔗  A short label for a particular group, question or set of display text within the questionnaire used for reference by the individual completing 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.  Typically, these won't be used for "display" items, though such use is not prohibited.  Systems SHOULD NOT generate their own prefixes if prefixes are defined for any items within a Questionnaire.sdc-questionnaire-render.item.prefix(xsd)=
	 <#base:string>
	 <  unique id for the element within a resource (for internal references); (xsd)id:string>?
	[]<  An Extension; (xsd)extension:Extension>*
	 <  The actual value; (xsd)value:string>?
	 <  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.

For questionnaires, see additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/rendering.html#rendering-style).; (xsd)itemLabel-renderingStyle:rendering-style>?
	 <  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. Existing [restrictions on XHTML content](http://hl7.org/fhir/R4/narrative.html#security) apply. Note that using [markdown](http://hl7.org/fhir/extensions/5.1.0StructureDefinition-rendering-markdown.html) allows for greater flexibility of display. For questionnaires, see additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/rendering.html#rendering-xhtml).; (xsd)itemLabel-xhtml:rendering-xhtml>?

🔗  The name of a section, the text of a question or text content for a display item. When using this element to represent the name of a section, use group type item and also make sure to limit the text element to a short string suitable for display as a section heading.  Group item instructions should be included as a display type item within the group.sdc-questionnaire-render.item.text(xsd)=
	 <#base:string>
	 <  unique id for the element within a resource (for internal references); (xsd)id:string>?
	[]<  An Extension; (xsd)extension:Extension>*
	 <  The actual value; (xsd)value:string>?
	 <  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.

For questionnaires, see additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/rendering.html#rendering-style).; (xsd)groupText-renderingStyle:rendering-style>?
	 <  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. Existing [restrictions on XHTML content](http://hl7.org/fhir/R4/narrative.html#security) apply. Note that using [markdown](http://hl7.org/fhir/extensions/5.1.0StructureDefinition-rendering-markdown.html) allows for greater flexibility of display. For questionnaires, see additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/rendering.html#rendering-xhtml).; (xsd)groupText-xhtml:rendering-xhtml>?
	 <  An expression that, when evaluated, provides the value for the element on which it appears. Note: The variation cannot change the meaning of the question. The extension can be used even if text is present; and if the extension is supported, the evaluation will replace the text provided (with 'smarter' text). ; (xsd)expression:cqf-expression>?

🔗  A short, descriptive, user-friendly title for the questionnaire. This name does not need to be machine-processing friendly and may contain punctuation, white-space, etc.sdc-questionnaire-render.title(xsd)=
	 <#base:string>
	 <  unique id for the element within a resource (for internal references); (xsd)id:string>?
	[]<  An Extension; (xsd)extension:Extension>*
	 <  The actual value; (xsd)value:string>?
	 <  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.

For questionnaires, see additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/rendering.html#rendering-style).; (xsd)title-renderingStyle:rendering-style>?
	 <  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. Existing [restrictions on XHTML content](http://hl7.org/fhir/R4/narrative.html#security) apply. Note that using [markdown](http://hl7.org/fhir/extensions/5.1.0StructureDefinition-rendering-markdown.html) allows for greater flexibility of display. For questionnaires, see additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/rendering.html#rendering-xhtml).; (xsd)title-xhtml:rendering-xhtml>?

🔗  Sets expectations for supported capabilities for questionnaire responses for SDC-conformant systems. The QuestionnaireResponse contains enough information about the questions asked and their organization that it can be interpreted somewhat independently from the Questionnaire it is based on.  I.e. You don't need access to the Questionnaire in order to extract basic information from a QuestionnaireResponse.sdc-questionnaireresponse(xsd)=
	 <#base:sdc-questionnaireresponsecommon>
	 <  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.; (xsd)id:string>?
	 <  The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.; (xsd)meta:Meta>?
	 <  A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. 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. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.; (xsd)implicitRules:uri>?
	 <  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).; (xsd)language:code>?
	 <  A human-readable narrative that contains a summary of the resource and can 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. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied).  This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.; (xsd)text: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. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.; (xsd)contained:Resource>*
	[]<  An Extension; (xsd)extension:Extension>*
	[]<  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 and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  A business identifier assigned to a particular completed (or partially completed) questionnaire.; (xsd)identifier:Identifier>?
	[]<  The order, proposal or plan that is fulfilled in whole or in part by this QuestionnaireResponse.  For example, a ServiceRequest seeking an intake assessment or a decision support recommendation to assess for post-partum depression.; (xsd)basedOn:( <CarePlan>
		 | <ServiceRequest>)>*
	[]<  A procedure or observation that this questionnaire was performed as part of the execution of.  For example, the surgery a checklist was executed as part of. Composition of questionnaire responses will be handled by the parent questionnaire having answers that reference the child questionnaire.  For relationships to referrals, and other types of requests, use basedOn.; (xsd)partOf:( <Observation>
		 | <Procedure>)>*
	 <  The Questionnaire that defines and organizes the questions for which answers are being provided. For SDC, this SHALL be the version-specific URL of the form as hosted on the Form Manager.; (xsd)questionnaire:canonical>
	 <  The position of the questionnaire response within its overall lifecycle. This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid.; (xsd)status:code>
	 <  The subject of the questionnaire response.  This could be a patient, organization, practitioner, device, etc.  This is who/what the answers apply to, but is not necessarily the source of information. If the Questionnaire declared a subjectType, the resource pointed to by this element must be an instance of one of the listed types.
  If subject is omitted - because the QuestionnaireResponse is not associated with a specific subject, ensure that QuestionnaireRsponse.identifier is present or the QuestionnaireResponse is referenced somewhere (e.g. Task.output, Composition.section.entry, etc.) to allow tracking and retrieval of the QuestionnaireResponse; (xsd)subject:Resource*>?
	 <  The Encounter during which this questionnaire response was created or to which the creation of this record is tightly associated. This will typically be the encounter the event occurred within, but some activities may be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter. A questionnaire that was initiated during an encounter but not fully completed during the encounter would still generally be associated with the encounter.; (xsd)encounter:Encounter*>?
	 <  Identifies when this version of the answer set was created.  Changes whenever the answers are updated. May be different from the lastUpdateTime of the resource itself, because that reflects when the data was known to the server, not when the data was captured.

This element is optional to allow for systems that might not know the value, however it SHOULD be populated if possible.; (xsd)authored:dateTime>
	 <  Person who received the answers to the questions in the QuestionnaireResponse and recorded them in the system. Mapping a subject's answers to multiple choice options and determining what to put in the textual answer is a matter of interpretation.  Authoring by device would indicate that some portion of the questionnaire had been auto-populated.; (xsd)author:( <Device>
		 | <Organization>
		 | <Patient>
		 | <Practitioner>
		 | <PractitionerRole>
		 | <RelatedPerson>)>?
	 <  The person who answered the questions about the subject. If not specified, no inference can be made about who provided the data.; (xsd)source:( <Patient>
		 | <Practitioner>
		 | <PractitionerRole>
		 | <RelatedPerson>)>?
	[]<  A group or question item from the original questionnaire for which answers are provided. Groups cannot have answers and therefore must nest directly within item. When dealing with questions, nesting must occur within each answer because some questions may have multiple answers (and the nesting occurs for each answer).; (xsd)item:sdc-questionnaireresponse.item>*
	[]<  The action represented by this resource has been determined to satisfy the expectations established by the referenced Definition resource. If changes are made to this event record, the determination must be made whether, with the change, the action still complies with the referenced Definition.  Revisions may result in adheresTo assertions being removed, or - if the system has an algorithm for determining which targets are appropriate - being added.

Also see the [notes](workflow-extensions.html#instantiation) in the workflow extensions area for more guidance on this element.; (xsd)adheresTo:Extension>*
	 <  This resource came into being as a result of expectations set in the referenced Definition resource.  I.e. This resource represents a 'step' dictated within the protocol/order set/etc. See the [notes](workflow-extensions.html#instantiation) in the workflow extensions area for more guidance on this element.; (xsd)triggeredBy:Extension>?
	[]<  Represents a wet or electronic signature for either the form overall or for the question or item it's associated with.; (xsd)signature:questionnaireresponse-signature>*
	 <  Indicates how the individual completing the QuestionnaireResponse provided their responses.; (xsd)completionMode:questionnaireresponse-completionMode>?
	 <  Optional Extension Element - found in all resources.; (xsd)source:Extension>?

🔗  A group or question item from the original questionnaire for which answers are provided. Groups cannot have answers and therefore must nest directly within item. When dealing with questions, nesting must occur within each answer because some questions may have multiple answers (and the nesting occurs for each answer).sdc-questionnaireresponse.item(xsd)=
	 <#base:QuestionnaireResponse.item>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  An Extension; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  The item from the Questionnaire that corresponds to this item in the QuestionnaireResponse resource.; (xsd)linkId:string>
	 <  A reference to an [ElementDefinition](http://hl7.org/fhir/R4/elementdefinition.html) that provides the details for the item. The ElementDefinition must be in a [StructureDefinition](http://hl7.org/fhir/R4/structuredefinition.html#), and must have a fragment identifier that identifies the specific data element by its id (Element.id). E.g. http://hl7.org/fhir/StructureDefinition/Observation#Observation.value[x].

There is no need for this element if the item pointed to by the linkId has a definition listed.; (xsd)definition:uri>?
	 <  Text that is displayed above the contents of the group or as the text of the question being answered.; (xsd)text:string>?
	[]<  The respondent's answer(s) to the question. The value is nested because we cannot have a repeating structure that has variable type.; (xsd)answer:sdc-questionnaireresponse.item.answer>*
	[]<  Questions or sub-groups nested beneath a question or group.; (xsd)item:QuestionnaireResponse.item>*
	 <  Media to render/make available as an accompaniment to the question being asked; (xsd)itemMedia:sdc-questionnaire-itemMedia>?
	[]<  Represents a wet or electronic signature for either the form overall or for the question or item it's associated with.; (xsd)ItemSignature:questionnaireresponse-signature>*

🔗  The respondent's answer(s) to the question. The value is nested because we cannot have a repeating structure that has variable type.sdc-questionnaireresponse.item.answer(xsd)=
	 <#base:QuestionnaireResponse.item.answer>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  An Extension; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 ( <valueAttachment:Attachment>
		 | <valueBoolean:boolean>
		 | <valueCoding:Coding>
		 | <valueDate:date>
		 | <valueDateTime:dateTime>
		 | <valueDecimal:decimal>
		 | <valueInteger:integer>
		 | <valueQuantity:Quantity>
		 | <valueResource:Resource>
		 | <valueString:string>
		 | <valueTime:time>
		 | <valueUri:uri>)?
	[]<  Nested groups and/or questions found within this particular answer.; (xsd)item:QuestionnaireResponse.item>*
	 <  Media to render/make available as an accompaniment to a specific answer option; (xsd)itemAnswerMedia:sdc-questionnaire-itemAnswerMedia>?
	 <  A numeric value that allows the comparison (less than, greater than) or other numerical manipulation of a concept (e.g. Adding up components of a score). Scores are usually a whole number, but occasionally decimals are encountered in scores. In the CodeSystem and ValueSet resources, the item weight is represented using the [itemWeight property](http://hl7.org/fhir/extensions/5.1.0codesystem-concept-properties.html#concept-properties-itemWeight) Inclusion of weights in QRs can increase performance when calculating based on weights.; (xsd)itemWeight:Extension>?

🔗  Sets expectations for supported capabilities for questionnaire responses for SDC-conformant systems. The QuestionnaireResponse contains enough information about the questions asked and their organization that it can be interpreted somewhat independently from the Questionnaire it is based on.  I.e. You don't need access to the Questionnaire in order to extract basic information from a QuestionnaireResponse.sdc-questionnaireresponse-adapt(xsd)=
	 <#base:sdc-questionnaireresponsecommon>
	 <  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.; (xsd)id:string>?
	 <  The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.; (xsd)meta:Meta>?
	 <  A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. 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. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.; (xsd)implicitRules:uri>?
	 <  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).; (xsd)language:code>?
	 <  A human-readable narrative that contains a summary of the resource and can 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. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied).  This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.; (xsd)text: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. The referenced Questionnaire SHALL be sent as a contained resource.; (xsd)contained:Resource>+
	[]<  An Extension; (xsd)extension:Extension>*
	[]<  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 and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  A business identifier assigned to a particular completed (or partially completed) questionnaire.; (xsd)identifier:Identifier>?
	[]<  The order, proposal or plan that is fulfilled in whole or in part by this QuestionnaireResponse.  For example, a ServiceRequest seeking an intake assessment or a decision support recommendation to assess for post-partum depression.; (xsd)basedOn:( <CarePlan>
		 | <ServiceRequest>)>*
	[]<  A procedure or observation that this questionnaire was performed as part of the execution of.  For example, the surgery a checklist was executed as part of. Composition of questionnaire responses will be handled by the parent questionnaire having answers that reference the child questionnaire.  For relationships to referrals, and other types of requests, use basedOn.; (xsd)partOf:( <Observation>
		 | <Procedure>)>*
	 <  The Questionnaire that defines and organizes the questions for which answers are being provided. If a QuestionnaireResponse references a Questionnaire, then the QuestionnaireResponse structure must be consistent with the Questionnaire (i.e. questions must be organized into the same groups, nested questions must still be nested, etc.).; (xsd)questionnaire:canonical>
	 <  The position of the questionnaire response within its overall lifecycle. This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid.; (xsd)status:code>
	 <  The subject of the questionnaire response.  This could be a patient, organization, practitioner, device, etc.  This is who/what the answers apply to, but is not necessarily the source of information. If the Questionnaire declared a subjectType, the resource pointed to by this element must be an instance of one of the listed types.
  If subject is omitted - because the QuestionnaireResponse is not associated with a specific subject, ensure that QuestionnaireRsponse.identifier is present or the QuestionnaireResponse is referenced somewhere (e.g. Task.output, Composition.section.entry, etc.) to allow tracking and retrieval of the QuestionnaireResponse; (xsd)subject:Resource*>?
	 <  The Encounter during which this questionnaire response was created or to which the creation of this record is tightly associated. This will typically be the encounter the event occurred within, but some activities may be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter. A questionnaire that was initiated during an encounter but not fully completed during the encounter would still generally be associated with the encounter.; (xsd)encounter:Encounter*>?
	 <  Identifies when this version of the answer set was created.  Changes whenever the answers are updated. May be different from the lastUpdateTime of the resource itself, because that reflects when the data was known to the server, not when the data was captured.

This element is optional to allow for systems that might not know the value, however it SHOULD be populated if possible.; (xsd)authored:dateTime>
	 <  Person who received the answers to the questions in the QuestionnaireResponse and recorded them in the system. Mapping a subject's answers to multiple choice options and determining what to put in the textual answer is a matter of interpretation.  Authoring by device would indicate that some portion of the questionnaire had been auto-populated.; (xsd)author:( <Device>
		 | <Organization>
		 | <Patient>
		 | <Practitioner>
		 | <PractitionerRole>
		 | <RelatedPerson>)>?
	 <  The person who answered the questions about the subject. If not specified, no inference can be made about who provided the data.; (xsd)source:( <Patient>
		 | <Practitioner>
		 | <PractitionerRole>
		 | <RelatedPerson>)>?
	[]<  A group or question item from the original questionnaire for which answers are provided. Groups cannot have answers and therefore must nest directly within item. When dealing with questions, nesting must occur within each answer because some questions may have multiple answers (and the nesting occurs for each answer).; (xsd)item:sdc-questionnaireresponse-adapt.item>*
	[]<  The action represented by this resource has been determined to satisfy the expectations established by the referenced Definition resource. If changes are made to this event record, the determination must be made whether, with the change, the action still complies with the referenced Definition.  Revisions may result in adheresTo assertions being removed, or - if the system has an algorithm for determining which targets are appropriate - being added.

Also see the [notes](workflow-extensions.html#instantiation) in the workflow extensions area for more guidance on this element.; (xsd)adheresTo:Extension>*
	 <  This resource came into being as a result of expectations set in the referenced Definition resource.  I.e. This resource represents a 'step' dictated within the protocol/order set/etc. See the [notes](workflow-extensions.html#instantiation) in the workflow extensions area for more guidance on this element.; (xsd)triggeredBy:Extension>?
	[]<  Represents a wet or electronic signature for either the form overall or for the question or item it's associated with.; (xsd)signature:questionnaireresponse-signature>*
	 <  Indicates how the individual completing the QuestionnaireResponse provided their responses.; (xsd)completionMode:questionnaireresponse-completionMode>?
	 <  Optional Extension Element - found in all resources.; (xsd)source:Extension>?

🔗  A group or question item from the original questionnaire for which answers are provided. Groups cannot have answers and therefore must nest directly within item. When dealing with questions, nesting must occur within each answer because some questions may have multiple answers (and the nesting occurs for each answer).sdc-questionnaireresponse-adapt.item(xsd)=
	 <#base:QuestionnaireResponse.item>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  An Extension; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  The item from the Questionnaire that corresponds to this item in the QuestionnaireResponse resource.; (xsd)linkId:string>
	 <  A reference to an [ElementDefinition](http://hl7.org/fhir/R4/elementdefinition.html) that provides the details for the item. The ElementDefinition must be in a [StructureDefinition](http://hl7.org/fhir/R4/structuredefinition.html#), and must have a fragment identifier that identifies the specific data element by its id (Element.id). E.g. http://hl7.org/fhir/StructureDefinition/Observation#Observation.value[x].

There is no need for this element if the item pointed to by the linkId has a definition listed.; (xsd)definition:uri>?
	 <  Text that is displayed above the contents of the group or as the text of the question being answered.; (xsd)text:string>?
	[]<  The respondent's answer(s) to the question. The value is nested because we cannot have a repeating structure that has variable type.; (xsd)answer:sdc-questionnaireresponse-adapt.item.answer>*
	[]<  Questions or sub-groups nested beneath a question or group.; (xsd)item:QuestionnaireResponse.item>*
	 <  Media to render/make available as an accompaniment to the question being asked; (xsd)itemMedia:sdc-questionnaire-itemMedia>?
	[]<  Represents a wet or electronic signature for either the form overall or for the question or item it's associated with.; (xsd)ItemSignature:questionnaireresponse-signature>*

🔗  The respondent's answer(s) to the question. The value is nested because we cannot have a repeating structure that has variable type.sdc-questionnaireresponse-adapt.item.answer(xsd)=
	 <#base:QuestionnaireResponse.item.answer>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  An Extension; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 ( <valueAttachment:Attachment>
		 | <valueBoolean:boolean>
		 | <valueCoding:Coding>
		 | <valueDate:date>
		 | <valueDateTime:dateTime>
		 | <valueDecimal:decimal>
		 | <valueInteger:integer>
		 | <valueQuantity:Quantity>
		 | <valueResource:Resource>
		 | <valueString:string>
		 | <valueTime:time>
		 | <valueUri:uri>)?
	[]<  Nested groups and/or questions found within this particular answer.; (xsd)item:QuestionnaireResponse.item>*
	 <  Media to render/make available as an accompaniment to a specific answer option; (xsd)itemAnswerMedia:sdc-questionnaire-itemAnswerMedia>?
	 <  A numeric value that allows the comparison (less than, greater than) or other numerical manipulation of a concept (e.g. Adding up components of a score). Scores are usually a whole number, but occasionally decimals are encountered in scores. In the CodeSystem and ValueSet resources, the item weight is represented using the [itemWeight property](http://hl7.org/fhir/extensions/5.1.0codesystem-concept-properties.html#concept-properties-itemWeight) Inclusion of weights in QRs can increase performance when calculating based on weights.; (xsd)itemWeight:Extension>?

🔗  Sets expectations for supported capabilities for questionnaire responses for SDC-conformant systems. The QuestionnaireResponse contains enough information about the questions asked and their organization that it can be interpreted somewhat independently from the Questionnaire it is based on.  I.e. You don't need access to the Questionnaire in order to extract basic information from a QuestionnaireResponse.sdc-questionnaireresponsecommon(xsd)=
	 <#base:QuestionnaireResponse>
	 <  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.; (xsd)id:string>?
	 <  The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.; (xsd)meta:Meta>?
	 <  A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. 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. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.; (xsd)implicitRules:uri>?
	 <  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).; (xsd)language:code>?
	 <  A human-readable narrative that contains a summary of the resource and can 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. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied).  This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.; (xsd)text: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. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.; (xsd)contained:Resource>*
	[]<  An Extension; (xsd)extension:Extension>*
	[]<  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 and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  A business identifier assigned to a particular completed (or partially completed) questionnaire.; (xsd)identifier:Identifier>?
	[]<  The order, proposal or plan that is fulfilled in whole or in part by this QuestionnaireResponse.  For example, a ServiceRequest seeking an intake assessment or a decision support recommendation to assess for post-partum depression.; (xsd)basedOn:( <CarePlan>
		 | <ServiceRequest>)>*
	[]<  A procedure or observation that this questionnaire was performed as part of the execution of.  For example, the surgery a checklist was executed as part of. Composition of questionnaire responses will be handled by the parent questionnaire having answers that reference the child questionnaire.  For relationships to referrals, and other types of requests, use basedOn.; (xsd)partOf:( <Observation>
		 | <Procedure>)>*
	 <  The Questionnaire that defines and organizes the questions for which answers are being provided. If a QuestionnaireResponse references a Questionnaire, then the QuestionnaireResponse structure must be consistent with the Questionnaire (i.e. questions must be organized into the same groups, nested questions must still be nested, etc.).; (xsd)questionnaire:canonical>
	 <  The position of the questionnaire response within its overall lifecycle. This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid.; (xsd)status:code>
	 <  The subject of the questionnaire response.  This could be a patient, organization, practitioner, device, etc.  This is who/what the answers apply to, but is not necessarily the source of information. If the Questionnaire declared a subjectType, the resource pointed to by this element must be an instance of one of the listed types.
  If subject is omitted - because the QuestionnaireResponse is not associated with a specific subject, ensure that QuestionnaireRsponse.identifier is present or the QuestionnaireResponse is referenced somewhere (e.g. Task.output, Composition.section.entry, etc.) to allow tracking and retrieval of the QuestionnaireResponse; (xsd)subject:Resource*>?
	 <  The Encounter during which this questionnaire response was created or to which the creation of this record is tightly associated. This will typically be the encounter the event occurred within, but some activities may be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter. A questionnaire that was initiated during an encounter but not fully completed during the encounter would still generally be associated with the encounter.; (xsd)encounter:Encounter*>?
	 <  Identifies when this version of the answer set was created.  Changes whenever the answers are updated. May be different from the lastUpdateTime of the resource itself, because that reflects when the data was known to the server, not when the data was captured.

This element is optional to allow for systems that might not know the value, however it SHOULD be populated if possible.; (xsd)authored:dateTime>
	 <  Person who received the answers to the questions in the QuestionnaireResponse and recorded them in the system. Mapping a subject's answers to multiple choice options and determining what to put in the textual answer is a matter of interpretation.  Authoring by device would indicate that some portion of the questionnaire had been auto-populated.; (xsd)author:( <Device>
		 | <Organization>
		 | <Patient>
		 | <Practitioner>
		 | <PractitionerRole>
		 | <RelatedPerson>)>?
	 <  The person who answered the questions about the subject. If not specified, no inference can be made about who provided the data.; (xsd)source:( <Patient>
		 | <Practitioner>
		 | <PractitionerRole>
		 | <RelatedPerson>)>?
	[]<  A group or question item from the original questionnaire for which answers are provided. Groups cannot have answers and therefore must nest directly within item. When dealing with questions, nesting must occur within each answer because some questions may have multiple answers (and the nesting occurs for each answer).; (xsd)item:sdc-questionnaireresponsecommon.item>*
	[]<  The action represented by this resource has been determined to satisfy the expectations established by the referenced Definition resource. If changes are made to this event record, the determination must be made whether, with the change, the action still complies with the referenced Definition.  Revisions may result in adheresTo assertions being removed, or - if the system has an algorithm for determining which targets are appropriate - being added.

Also see the [notes](workflow-extensions.html#instantiation) in the workflow extensions area for more guidance on this element.; (xsd)adheresTo:Extension>*
	 <  This resource came into being as a result of expectations set in the referenced Definition resource.  I.e. This resource represents a 'step' dictated within the protocol/order set/etc. See the [notes](workflow-extensions.html#instantiation) in the workflow extensions area for more guidance on this element.; (xsd)triggeredBy:Extension>?
	[]<  Represents a wet or electronic signature for either the form overall or for the question or item it's associated with.; (xsd)signature:questionnaireresponse-signature>*
	 <  Indicates how the individual completing the QuestionnaireResponse provided their responses.; (xsd)completionMode:questionnaireresponse-completionMode>?
	 <  Optional Extension Element - found in all resources.; (xsd)source:Extension>?

🔗  A group or question item from the original questionnaire for which answers are provided. Groups cannot have answers and therefore must nest directly within item. When dealing with questions, nesting must occur within each answer because some questions may have multiple answers (and the nesting occurs for each answer).sdc-questionnaireresponsecommon.item(xsd)=
	 <#base:QuestionnaireResponse.item>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  An Extension; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  The item from the Questionnaire that corresponds to this item in the QuestionnaireResponse resource.; (xsd)linkId:string>
	 <  A reference to an [ElementDefinition](http://hl7.org/fhir/R4/elementdefinition.html) that provides the details for the item. The ElementDefinition must be in a [StructureDefinition](http://hl7.org/fhir/R4/structuredefinition.html#), and must have a fragment identifier that identifies the specific data element by its id (Element.id). E.g. http://hl7.org/fhir/StructureDefinition/Observation#Observation.value[x].

There is no need for this element if the item pointed to by the linkId has a definition listed.; (xsd)definition:uri>?
	 <  Text that is displayed above the contents of the group or as the text of the question being answered.; (xsd)text:string>?
	[]<  The respondent's answer(s) to the question. The value is nested because we cannot have a repeating structure that has variable type.; (xsd)answer:sdc-questionnaireresponsecommon.item.answer>*
	[]<  Questions or sub-groups nested beneath a question or group.; (xsd)item:QuestionnaireResponse.item>*
	 <  Media to render/make available as an accompaniment to the question being asked; (xsd)itemMedia:sdc-questionnaire-itemMedia>?
	[]<  Represents a wet or electronic signature for either the form overall or for the question or item it's associated with.; (xsd)ItemSignature:questionnaireresponse-signature>*

🔗  The respondent's answer(s) to the question. The value is nested because we cannot have a repeating structure that has variable type.sdc-questionnaireresponsecommon.item.answer(xsd)=
	 <#base:QuestionnaireResponse.item.answer>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  An Extension; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 ( <valueAttachment:Attachment>
		 | <valueBoolean:boolean>
		 | <valueCoding:Coding>
		 | <valueDate:date>
		 | <valueDateTime:dateTime>
		 | <valueDecimal:decimal>
		 | <valueInteger:integer>
		 | <valueQuantity:Quantity>
		 | <valueResource:Resource>
		 | <valueString:string>
		 | <valueTime:time>
		 | <valueUri:uri>)?
	[]<  Nested groups and/or questions found within this particular answer.; (xsd)item:QuestionnaireResponse.item>*
	 <  Media to render/make available as an accompaniment to a specific answer option; (xsd)itemAnswerMedia:sdc-questionnaire-itemAnswerMedia>?
	 <  A numeric value that allows the comparison (less than, greater than) or other numerical manipulation of a concept (e.g. Adding up components of a score). Scores are usually a whole number, but occasionally decimals are encountered in scores. In the CodeSystem and ValueSet resources, the item weight is represented using the [itemWeight property](http://hl7.org/fhir/extensions/5.1.0codesystem-concept-properties.html#concept-properties-itemWeight) Inclusion of weights in QRs can increase performance when calculating based on weights.; (xsd)itemWeight:Extension>?

🔗  If present and true, indicates that the item indicates a different subject for this group. The item type must be "reference" and there can only be one item with this extension in each group.sdc-questionnaireresponse-isSubject(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	 <  An Extension; (xsd)extension:Extension>{0,0}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaireresponse-isSubject; (xsd)url:string>
	 <  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)value:boolean>?

🔗  Describes the elements that should be exposed in a response to a search for questionnaires.sdc-questionnaire-search(xsd)=
	 <#base:sdc-questionnairecommon>
	 <  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.; (xsd)id:string>?
	 <  The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.; (xsd)meta:Meta>?
	 <  A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. 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. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.; (xsd)implicitRules:uri>?
	 <  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).; (xsd)language:code>?
	 <  A human-readable narrative that contains a summary of the resource and can 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. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied).  This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.; (xsd)text: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. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.; (xsd)contained:Resource>*
	[]<  An Extension; (xsd)extension:Extension>*
	[]<  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 and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  An absolute URI that is used to identify this questionnaire when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which at which an authoritative instance of this questionnaire is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the questionnaire is stored on different servers. The name of the referenced questionnaire can be conveyed using the http://hl7.org/fhir/StructureDefinition/display extension.; (xsd)url:uri>?
	[]<  A formal identifier that is used to identify this questionnaire when it is represented in other formats, or referenced in a specification, model, design or an instance. Typically, this is used for identifiers that can go in an HL7 V3 II (instance identifier) data type, and can then identify this questionnaire outside of FHIR, where it is not possible to use the logical URI.; (xsd)identifier:Identifier>*
	 <  The identifier that is used to identify this version of the questionnaire when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the questionnaire author and is not expected to be globally unique. For example, it might be a timestamp (e.g. yyyymmdd) if a managed version is not available. There is also no expectation that versions can be placed in a lexicographical sequence. There may be different questionnaire instances that have the same identifier but different versions.  The version can be appended to the url in a reference to allow a reference to a particular business version of the questionnaire with the format [url]|[version].; (xsd)version:string>?
	 <  A natural language name identifying the questionnaire. This name should be usable as an identifier for the module by machine processing applications such as code generation. The name is not expected to be globally unique. The name should be a simple alphanumeric type name to ensure that it is machine-processing friendly.; (xsd)name:string>?
	 <  A short, descriptive, user-friendly title for the questionnaire. This name does not need to be machine-processing friendly and may contain punctuation, white-space, etc.; (xsd)title:string>
	[]<  The URL of a Questionnaire that this Questionnaire is based on.; (xsd)derivedFrom:canonical>*
	 <  The status of this questionnaire. Enables tracking the life-cycle of the content. Allows filtering of questionnaires that are appropriate for use versus not.; (xsd)status:code>
	 <  A Boolean value to indicate that this questionnaire is authored for testing purposes (or education/evaluation/marketing) and is not intended to be used for genuine usage. Allows filtering of questionnaires that are appropriate for use versus not.; (xsd)experimental:boolean>?
	[]<  The types of subjects that can be the subject of responses created for the questionnaire. If none are specified, then the subject is unlimited.; (xsd)subjectType:code>*
	 <  Identifies when this version of the form was created.  Changes whenever the form is updated. Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the questionnaire. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource.; (xsd)date:dateTime>
	 <  The name of the organization or individual that published the questionnaire. Usually an organization but may be an individual. The publisher (or steward) of the questionnaire is the organization or individual primarily responsible for the maintenance and upkeep of the questionnaire. This is not necessarily the same individual or organization that developed and initially authored the content. The publisher is the primary point of contact for questions or issues with the questionnaire. This item SHOULD be populated unless the information is available from context.; (xsd)publisher:string>?
	[]<  Contact details to assist a user in finding and communicating with the publisher. May be a web site, an email address, a telephone number, etc.; (xsd)contact:ContactDetail>*
	 <  A free text natural language description of the questionnaire from a consumer's perspective. This description can be used to capture details such as why the questionnaire was built, comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the questionnaire as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context (e.g. the language of the questionnaire is presumed to be the predominant language in the place the questionnaire was created).; (xsd)description:markdown>?
	[]<  Specifies clinical/business/etc. metadata that can be used to retrieve, index and/or categorize an artifact. This metadata can either be specific to the applicable population (e.g., age category, DRG) or the specific context of care (e.g., venue, care setting, provider of care). When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.; (xsd)useContext:sdc-usagecontext>*
	 <  A legal or geographic region in which the questionnaire is intended to be used. Relevant for systems that support forms from multiple countries/provinces/states.; (xsd)jurisdiction:CodeableConcept>?
	 <  Explanation of why this questionnaire is needed and why it has been designed as it has. This element does not describe the usage of the questionnaire. Instead, it provides traceability of ''why'' the resource is either needed or ''why'' it is defined as it is.  This may be used to point to source materials or specifications that drove the structure of this questionnaire.; (xsd)purpose:markdown>?
	 <  A copyright statement relating to the questionnaire and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the questionnaire.; (xsd)copyright:markdown>?
	 <  The date on which the resource content was approved by the publisher. Approval happens once when the content is officially approved for usage. Relevant for systems that have strict curation requirements that govern when a form/instrument is permitted for use.; (xsd)approvalDate:date>?
	 <  The date on which the resource content was last reviewed. Review happens periodically after approval but does not change the original approval date. Relevant for systems that have strict curation requirements that govern when a form/instrument is permitted for use.; (xsd)lastReviewDate:date>?
	 <  The period during which the questionnaire content was or is planned to be in active use. Relevant for systems that have strict curation requirements that govern when a form/instrument is permitted for use.; (xsd)effectivePeriod:Period>?
	 <  An identifier for this question or group of questions in a particular terminology such as LOINC.; (xsd)code:Coding>?
	[]<  A particular question, question grouping or display text that is part of the questionnaire. The content of the questionnaire is constructed from an ordered, hierarchical collection of items.; (xsd)item:sdc-questionnaire-search.item>*
	 <  Optional Extension Element - found in all resources.; (xsd)versionAlgorithm:Extension>?
	 <  Optional Extension Element - found in all resources.; (xsd)copyrightLabel:Extension>?
	[]<  This extension will appear on the root of an assembled Questionnaire and identifies the subQuestionnaires (including version) that were used as part of the assembly process.; (xsd)assembledFrom:sdc-questionnaire-assembledFrom>*

🔗  A particular question, question grouping or display text that is part of the questionnaire. The content of the questionnaire is constructed from an ordered, hierarchical collection of items.sdc-questionnaire-search.item(xsd)=
	 <#base:Questionnaire.item>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  An Extension; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  An identifier that is unique within the Questionnaire allowing linkage to the equivalent item in a QuestionnaireResponse resource. This ''can'' be a meaningful identifier (e.g. a LOINC code) but is not intended to have any meaning.  GUIDs or sequential numbers are appropriate here.; (xsd)linkId:string>
	 <  This element is a URI that refers to an [ElementDefinition](http://hl7.org/fhir/R4/elementdefinition.html) that provides information about this item, including information that might otherwise be included in the instance of the Questionnaire resource. A detailed description of the construction of the URI is shown in Comments, below. If this element is present then the following element values MAY be derived from the Element Definition if the corresponding elements of this Questionnaire resource instance have no value:

* code (ElementDefinition.code) 
* type (ElementDefinition.type) 
* required (ElementDefinition.min) 
* repeats (ElementDefinition.max) 
* maxLength (ElementDefinition.maxLength) 
* answerValueSet (ElementDefinition.binding)
* options (ElementDefinition.binding). Systems that support searching by the 'definition' parameter SHALL support returning item.definition.; (xsd)definition:uri>?
	[]<  A terminology code that corresponds to this group or question (e.g. a code from LOINC, which defines many questions and answers). Systems that support searching by the 'code' parameter SHALL support returning item.code.; (xsd)code:Coding>*
	 <  A short label for a particular group, question or set of display text within the questionnaire used for reference by the individual completing 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.  Typically, these won't be used for "display" items, though such use is not prohibited.  Systems SHOULD NOT generate their own prefixes if prefixes are defined for any items within a Questionnaire.; (xsd)prefix:string>?
	 <  The name of a section, the text of a question or text content for a display item. When using this element to represent the name of a section, use group type item and also make sure to limit the text element to a short string suitable for display as a section heading.  Group item instructions should be included as a display type item within the group.; (xsd)text:string>?
	 <  The type of questionnaire item this is - whether text for display, a grouping of other items or a particular type of data to be captured (string, integer, coded choice, etc.). Time is handled using "string".  File is handled using Attachment.  (Content can be sent as a contained binary).; (xsd)type:code>
	[]<  A constraint indicating that this item should only be enabled (displayed/allow answers to be captured) when the specified condition is true. If multiple repetitions of this extension are present, the item should be enabled when the condition for *any* of the repetitions is true.  I.e. treat "enableWhen"s as being joined by an "or" clause.  This element is a modifier because if enableWhen is present for an item, "required" is ignored unless one of the enableWhen conditions is met. When an item is disabled, all of its descendants are disabled, regardless of what their own enableWhen logic might evaluate to.; (xsd)enableWhen:sdc-questionnaire-search.item.enableWhen>*
	 <  Controls how multiple enableWhen values are interpreted -  whether all or any must be true. This element must be specified if more than one enableWhen value is provided.; (xsd)enableBehavior:code>?
	 <  An indication, if true, that the item must be present in a "completed" QuestionnaireResponse.  If false, the item may be skipped when answering the questionnaire. Questionnaire.item.required only has meaning for elements that are conditionally enabled with enableWhen if the condition evaluates to true.  If an item that contains other items is marked as required, that does not automatically make the contained elements required (though required groups must contain at least one child element). The value may come from the ElementDefinition referred to by .definition.; (xsd)required:boolean>?
	 <  An indication, if true, that a QuestionnaireResponse for this item may include multiple answers associated with a single instance of this item (for question-type items) or multiple repetitions of the item (for group-type items) If a question is marked as repeats=true, then multiple answers can be provided for the question in the corresponding QuestionnaireResponse.  When rendering the questionnaire, it is up to the rendering software whether to render the question text for each answer repetition (i.e. "repeat the question") or to simply allow entry/selection of multiple answers for the question (repeat the answers).  Which is most appropriate visually may depend on the type of answer as well as whether there are nested items.

The resulting QuestionnaireResponse will be populated the same way regardless of rendering - one 'question' item with multiple answer values.

 The value may come from the ElementDefinition referred to by .definition.; (xsd)repeats:boolean>?
	 <  An indication, when true, that the value cannot be changed by a human respondent 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.; (xsd)readOnly:boolean>?
	 <  The maximum number of characters that are permitted in the answer to be considered a "valid" QuestionnaireResponse. For base64binary, reflects the number of characters representing the encoded data, not the number of bytes of the binary data. The value may come from the ElementDefinition referred to by .definition.; (xsd)maxLength:integer>?
	 <  A reference to a value set containing a list of codes representing permitted answers for a "choice" or "open-choice" question. LOINC defines many useful value sets for questionnaire responses. See [LOINC Answer Lists](http://hl7.org/fhir/R4/loinc.html#alist). The value may come from the ElementDefinition referred to by .definition.; (xsd)answerValueSet:canonical>?
	[]<  One of the permitted answers for a "choice" or "open-choice" question. This element can be used when the value set machinery of answerValueSet is deemed too cumbersome or when there's a need to capture possible answers that are not codes.; (xsd)answerOption:sdc-questionnaire-search.item.answerOption>*
	[]<  One or more values that should be pre-populated in the answer when initially rendering the questionnaire for user input. The user is allowed to change the value and override the default (unless marked as read-only). If the user doesn't change the value, then this initial value will be persisted when the QuestionnaireResponse is initially created.  Note that initial values can influence results.  The data type of initial[x] must agree with the item.type, and only repeating items can have more then one initial value.; (xsd)initial:sdc-questionnaire-search.item.initial>*
	[]<  Text, questions and other groups to be nested beneath a question or group. There is no specified limit to the depth of nesting.  However, Questionnaire authors are encouraged to consider the impact on the user and user interface of overly deep nesting.; (xsd)item:Questionnaire.item>*
	 <  If true, indicates that the extended item should not be displayed to the user. If an item is hidden, all descendant items are hidden as well.  See additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/rendering.html#hidden).; (xsd)hidden:questionnaire-hidden>?
	 <  Optional Extension Element - found in all resources.; (xsd)answerConstraint:Extension>?

🔗  One of the permitted answers for a "choice" or "open-choice" question. This element can be used when the value set machinery of answerValueSet is deemed too cumbersome or when there's a need to capture possible answers that are not codes.sdc-questionnaire-search.item.answerOption(xsd)=
	 <#base:Questionnaire.item.answerOption>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 ( <valueCoding:Coding>
		 | <valueDate:date>
		 | <valueInteger:integer>
		 | <valueResource:Resource>
		 | <valueString:string>
		 | <valueTime:time>)
	 <  Indicates whether the answer value is selected when the list of possible answers is initially shown. Use this instead of initial[v] if answerValueSet is present.; (xsd)initialSelected:boolean>?

🔗  A constraint indicating that this item should only be enabled (displayed/allow answers to be captured) when the specified condition is true. If multiple repetitions of this extension are present, the item should be enabled when the condition for *any* of the repetitions is true.  I.e. treat "enableWhen"s as being joined by an "or" clause.  This element is a modifier because if enableWhen is present for an item, "required" is ignored unless one of the enableWhen conditions is met. When an item is disabled, all of its descendants are disabled, regardless of what their own enableWhen logic might evaluate to.sdc-questionnaire-search.item.enableWhen(xsd)=
	 <#base:Questionnaire.item.enableWhen>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  The linkId for the question whose answer (or lack of answer) governs whether this item is enabled. If multiple question occurrences are present for the same question (same linkId), then this refers to the nearest question occurrence reachable by tracing first the "ancestor" axis and then the "preceding" axis and then the "following" axis.; (xsd)question:string>
	 <  Specifies the criteria by which the question is enabled.; (xsd)operator:code>
	 <  A value that the referenced question is tested using the specified operator in order for the item to be enabled.; (xsd)answer:( <boolean>
		 | <Coding>
		 | <date>
		 | <dateTime>
		 | <decimal>
		 | <integer>
		 | <Quantity>
		 | <Resource>
		 | <string>
		 | <time>)>

🔗  One or more values that should be pre-populated in the answer when initially rendering the questionnaire for user input. The user is allowed to change the value and override the default (unless marked as read-only). If the user doesn't change the value, then this initial value will be persisted when the QuestionnaireResponse is initially created.  Note that initial values can influence results.  The data type of initial[x] must agree with the item.type, and only repeating items can have more then one initial value.sdc-questionnaire-search.item.initial(xsd)=
	 <#base:Questionnaire.item.initial>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 ( <valueAttachment:Attachment>
		 | <valueBoolean:boolean>
		 | <valueCoding:Coding>
		 | <valueDate:date>
		 | <valueDateTime:dateTime>
		 | <valueDecimal:decimal>
		 | <valueInteger:integer>
		 | <valueQuantity:Quantity>
		 | <valueResource:Resource>
		 | <valueString:string>
		 | <valueTime:time>
		 | <valueUri:uri>)

🔗  The short text for the item. This element is useful for an item that require a shorter text when rendered  (e.g. when displaying the item on a mobile phone).sdc-questionnaire-shortText(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	 <  An Extension; (xsd)extension:Extension>{0,0}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaire-shortText; (xsd)url:string>
	 <  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)value:string>?

🔗  A Batch Bundle containing a set of queries that should be executed to provide source data for a StructureMap to create a populated QuestionnaireResponse.sdc-questionnaire-sourceQueries(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	 <  An Extension; (xsd)extension:Extension>{0,0}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaire-sourceQueries; (xsd)url:string>
	 <  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)value:Bundle*>?

🔗  StructureMaps that have this QuestionnaireResponses for this Questionnaire as 'target' - i.e. that can be used to create QuestionnaireResponses that are valid against this Questionnaire.sdc-questionnaire-sourceStructureMap(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	 <  An Extension; (xsd)extension:Extension>{0,0}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaire-sourceStructureMap; (xsd)url:string>
	 <  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)value:canonical>?

🔗  Indicates that the display item on which this extension appears should be replaced with the referenced Questionnairesdc-questionnaire-subQuestionnaire(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	 <  An Extension; (xsd)extension:Extension>{0,0}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaire-subQuestionnaire; (xsd)url:string>
	 <  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)value:canonical>?

🔗  StructureMaps that have QuestionnaireResponses of this Questionnaire as 'source'- i.e. that can be used to create other artifacts from QuestionnaireResponses that are valid against this Questionnaire.sdc-questionnaire-targetStructureMap(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	 <  An Extension; (xsd)extension:Extension>{0,0}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaire-targetStructureMap; (xsd)url:string>
	 <  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)value:canonical>?

🔗  Specifies a reference to a contained resource template (or set of resources for a repeating item) to be extracted from this item once the QuestionnaireResponse is complete.sdc-questionnaire-templateExtract(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  An Extension; (xsd)extension:Extension>+
	 <  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 SHALL be a URI for the Structure Definition defining the extension. http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaire-templateExtract; (xsd)url:string>
	 ( <valueAddress:Address>
		 | <valueAge:Age>
		 | <valueAnnotation:Annotation>
		 | <valueAttachment:Attachment>
		 | <valueBase64Binary:base64Binary>
		 | <valueBoolean:boolean>
		 | <valueCanonical:canonical>
		 | <valueCode:code>
		 | <valueCodeableConcept:CodeableConcept>
		 | <valueCoding:Coding>
		 | <valueContactDetail:ContactDetail>
		 | <valueContactPoint:ContactPoint>
		 | <valueContributor:Contributor>
		 | <valueCount:Count>
		 | <valueDataRequirement:DataRequirement>
		 | <valueDate:date>
		 | <valueDateTime:dateTime>
		 | <valueDecimal:decimal>
		 | <valueDistance:Distance>
		 | <valueDosage:Dosage>
		 | <valueDuration:Duration>
		 | <valueExpression:Expression>
		 | <valueHumanName:HumanName>
		 | <valueId:id>
		 | <valueIdentifier:Identifier>
		 | <valueInstant:instant>
		 | <valueInteger:integer>
		 | <valueMarkdown:markdown>
		 | <valueMeta:Meta>
		 | <valueMoney:Money>
		 | <valueOid:oid>
		 | <valueParameterDefinition:ParameterDefinition>
		 | <valuePeriod:Period>
		 | <valuePositiveInt:positiveInt>
		 | <valueQuantity:Quantity>
		 | <valueRange:Range>
		 | <valueRatio:Ratio>
		 | <valueRelatedArtifact:RelatedArtifact>
		 | <valueResource:Resource>
		 | <valueSampledData:SampledData>
		 | <valueSignature:Signature>
		 | <valueString:string>
		 | <valueTime:time>
		 | <valueTiming:Timing>
		 | <valueTriggerDefinition:TriggerDefinition>
		 | <valueUnsignedInt:unsignedInt>
		 | <valueUri:uri>
		 | <valueUrl:url>
		 | <valueUsageContext:UsageContext>
		 | <valueUuid:uuid>){0,0}
	 <  A reference to a contained resource to use as a template to put into the output transaction bundle.; (xsd)template:sdc-questionnaire-templateExtract.template>
	 <  A fhirpath expression to evaluate to extract the value into the fullUrl property. If no value is evaluated, then the element is not extracted.; (xsd)fullUrl:sdc-questionnaire-templateExtract.fullUrl>?
	 <  A fhirpath expression to evaluate to extract the value into the ifNoneMatch property. If no value is evaluated, then the element is not extracted.; (xsd)resourceId:sdc-questionnaire-templateExtract.resourceId>?
	 <  A fhirpath expression to evaluate to extract the value into the ifNoneMatch property. If no value is evaluated, then the element is not extracted.; (xsd)ifNoneMatch:sdc-questionnaire-templateExtract.ifNoneMatch>?
	 <  A fhirpath expression to evaluate to extract the value into the ifModifiedSince property. If no value is evaluated, then the element is not extracted.; (xsd)ifModifiedSince:sdc-questionnaire-templateExtract.ifModifiedSince>?
	 <  A fhirpath expression to evaluate to extract the value into the ifMatch property. If no value is evaluated, then the element is not extracted.; (xsd)ifMatch:sdc-questionnaire-templateExtract.ifMatch>?
	 <  A fhirpath expression to evaluate to extract the value into the ifNoneExist property. If no value is evaluated, then the element is not extracted.; (xsd)ifNoneExist:sdc-questionnaire-templateExtract.ifNoneExist>?

🔗  A fhirpath expression to evaluate to extract the value into the fullUrl property. If no value is evaluated, then the element is not extracted.sdc-questionnaire-templateExtract.fullUrl(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	 <  An Extension; (xsd)extension:Extension>{0,0}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. fullUrl; (xsd)url:string>
	 <  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)value:string>

🔗  A fhirpath expression to evaluate to extract the value into the ifMatch property. If no value is evaluated, then the element is not extracted.sdc-questionnaire-templateExtract.ifMatch(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	 <  An Extension; (xsd)extension:Extension>{0,0}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. ifMatch; (xsd)url:string>
	 <  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)value:string>

🔗  A fhirpath expression to evaluate to extract the value into the ifModifiedSince property. If no value is evaluated, then the element is not extracted.sdc-questionnaire-templateExtract.ifModifiedSince(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	 <  An Extension; (xsd)extension:Extension>{0,0}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. ifModifiedSince; (xsd)url:string>
	 <  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)value:string>

🔗  A fhirpath expression to evaluate to extract the value into the ifNoneExist property. If no value is evaluated, then the element is not extracted.sdc-questionnaire-templateExtract.ifNoneExist(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	 <  An Extension; (xsd)extension:Extension>{0,0}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. ifNoneExist; (xsd)url:string>
	 <  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)value:string>

🔗  A fhirpath expression to evaluate to extract the value into the ifNoneMatch property. If no value is evaluated, then the element is not extracted.sdc-questionnaire-templateExtract.ifNoneMatch(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	 <  An Extension; (xsd)extension:Extension>{0,0}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. ifNoneMatch; (xsd)url:string>
	 <  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)value:string>

🔗  A fhirpath expression to evaluate to extract the value into the ifNoneMatch property. If no value is evaluated, then the element is not extracted.sdc-questionnaire-templateExtract.resourceId(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	 <  An Extension; (xsd)extension:Extension>{0,0}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. resourceId; (xsd)url:string>
	 <  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)value:string>

🔗  A reference to a contained resource to use as a template to put into the output transaction bundle.sdc-questionnaire-templateExtract.template(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	 <  An Extension; (xsd)extension:Extension>{0,0}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. template; (xsd)url:string>
	 <  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)value:Resource*>

🔗  Specifies a reference to a contained resource template to be extracted from this item once the QuestionnaireResponse is complete.sdc-questionnaire-templateExtractBundle(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	 <  An Extension; (xsd)extension:Extension>{0,0}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaire-templateExtractBundle; (xsd)url:string>
	 <  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)value:Bundle*>?

🔗  If value is of type 'string', then it is to be evaluated as a fhirpath expression. If a value of type 'Expression' is provided, only fhirpath expressions are supported, and the language MAY be omitted.sdc-questionnaire-templateExtractContext(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	 <  An Extension; (xsd)extension:Extension>{0,0}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaire-templateExtractContext; (xsd)url:string>
	 ( <valueExpression:Expression>
		 | <valueString:string>)?

🔗  Provides an expression to evaluate any value(s) to replace in the given template extraction context. If no result is evaluated, the element in the templated resource will be removed, and futher processing of it's children is not required.sdc-questionnaire-templateExtractValue(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	 <  An Extension; (xsd)extension:Extension>{0,0}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaire-templateExtractValue; (xsd)url:string>
	 <  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)value:string>?

🔗  Indicates whether the list of supported units (conveyed in other extensions) are the exhaustive list from which the user must choose or whether they're able to select alternate codes or specify a string.sdc-questionnaire-unitOpen(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	 <  An Extension; (xsd)extension:Extension>{0,0}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaire-unitOpen; (xsd)url:string>
	 <  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)value:code>

🔗  If the questionnaire-unit-open extension indicates that additional units other than the set of options provided for the question are allowed, this indicates the code system those units are expected to be drawn from.  This extension SHOULD be present on any question where questionare-unit-open allows additional coded values.sdc-questionnaire-unitSupplementalSystem(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	 <  An Extension; (xsd)extension:Extension>{0,0}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaire-unitSupplementalSystem; (xsd)url:string>
	 <  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)value:canonical>

🔗  When used with an item control that causes the question to appear as a column in a table, indicates the width to give to the column for this question. code missing = pixels; code = % = percentage.sdc-questionnaire-width(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	 <  An Extension; (xsd)extension:Extension>{0,0}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaire-width; (xsd)url:string>
	 <  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)value:Quantity>?

🔗  Indicates an extension that must be supported by the system presenting the instance for data capture or end-user consumption. If a system does not recognize the extension or cannot implement the functionality defined by the extension, it should display an error message or warning and refrain from presenting the instance to the user or using it when capturing data. This may point to extensions that control the appearance of data elements, control what value elements have, what elements are or are not available, what elements can or cannot be edited, or rules about how editing may occur. This extension does NOT apply when simply rendering a resource for publication purposes or for other purposes not intended for end-user data capture or data consumption.sdc-rendering-criticalExtension(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	 <  An Extension; (xsd)extension:Extension>{0,0}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-rendering-criticalExtension; (xsd)url:string>
	 <  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)value:canonical>

🔗  A record of a request for service such as diagnostic investigations, treatments, or operations to be performed.sdc-servicerequest(xsd)=
	 <#base:ServiceRequest>
	 <  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.; (xsd)id:string>?
	 <  The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.; (xsd)meta:Meta>?
	 <  A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. 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. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.; (xsd)implicitRules:uri>?
	 <  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).; (xsd)language:code>?
	 <  A human-readable narrative that contains a summary of the resource and can 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. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied).  This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.; (xsd)text: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. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.; (xsd)contained:Resource>*
	[]<  An Extension; (xsd)extension:Extension>+
	[]<  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 and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	[]<  Identifiers assigned to this order instance by the orderer and/or the receiver and/or order fulfiller. The identifier.type element is used to distinguish between the identifiers assigned by the orderer (known as the 'Placer' in HL7 v2) and the producer of the observations in response to the order (known as the 'Filler' in HL7 v2).  For further discussion and examples see the resource notes section below.; (xsd)identifier:Identifier>*
	[]<  The URL pointing to a FHIR-defined protocol, guideline, orderset or other definition that is adhered to in whole or in part by this ServiceRequest. Note: This is a business identifier, not a resource identifier (see [discussion](http://hl7.org/fhir/R4/resource.html#identifiers)).  It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types.  For example, multiple Patient and a Person resource instance might share the same social insurance number.; (xsd)instantiatesCanonical:canonical>*
	[]<  The URL pointing to an externally maintained protocol, guideline, orderset or other definition that is adhered to in whole or in part by this ServiceRequest. This might be an HTML page, PDF, etc. or could just be a non-resolvable URI identifier.; (xsd)instantiatesUri:uri>*
	[]<  Plan/proposal/order fulfilled by this request.; (xsd)basedOn:( <CarePlan>
		 | <MedicationRequest>
		 | <ServiceRequest>)>*
	[]<  The request takes the place of the referenced completed or terminated request(s).; (xsd)replaces:ServiceRequest*>*
	 <  A shared identifier common to all service requests that were authorized more or less simultaneously by a single author, representing the composite or group identifier. Requests are linked either by a "basedOn" relationship (i.e. one request is fulfilling another) or by having a common requisition. Requests that are part of the same requisition are generally treated independently from the perspective of changing their state or maintaining them after initial creation.; (xsd)requisition:Identifier>?
	 <  The status of the order. The status is generally fully in the control of the requester - they determine whether the order is draft or active and, after it has been activated, competed, cancelled or suspended. States relating to the activities of the performer are reflected on either the corresponding event (see [Event Pattern](http://hl7.org/fhir/R4/event.html) for general discussion) or using the [Task](http://hl7.org/fhir/R4/task.html) resource.; (xsd)status:code>
	 <  Whether the request is a proposal, plan, an original order or a reflex order. This element is labeled as a modifier because the intent alters when and how the resource is actually applicable.; (xsd)intent:code>
	[]<  A code that classifies the service for searching, sorting and display purposes (e.g. "Surgical Procedure"). There may be multiple axis of categorization depending on the context or use case for retrieving or displaying the resource.  The level of granularity is defined by the category concepts in the value set.; (xsd)category:CodeableConcept>*
	 <  Indicates how quickly the ServiceRequest should be addressed with respect to other requests.; (xsd)priority:code>?
	 <  Set this to true if the record is saying that the service/procedure should NOT be performed. If the element is present, the value must be 'false' ; (xsd)doNotPerform:boolean>?
	 <  A code that identifies a particular service (i.e., procedure, diagnostic investigation, or panel of investigations) that have been requested. Many laboratory and radiology procedure codes embed the specimen/organ system in the test order name, for example,  serum or serum/plasma glucose, or a chest x-ray. The specimen might not be recorded separately from the test code.; (xsd)code:CodeableConcept>
	[]<  Additional details and instructions about the how the services are to be delivered.   For example, and order for a urinary catheter may have an order detail for an external or indwelling catheter, or an order for a bandage may require additional instructions specifying how the bandage should be applied. For information from the medical record intended to support the delivery of the requested services, use the `supportingInformation` element.; (xsd)orderDetail:CodeableConcept>*
	 <  An amount of service being requested which can be a quantity ( for example $1,500 home modification), a ratio ( for example, 20 half day visits per month), or a range (2.0 to 1.8 Gy per fraction).; (xsd)quantity:( <Quantity>
		 | <Range>
		 | <Ratio>)>?
	 <  On whom or what the service is to be performed. This is usually a human patient, but can also be requested on animals, groups of humans or animals, devices such as dialysis machines, or even locations (typically for environmental scans).; (xsd)subject:( <Device>
		 | <Group>
		 | <Location>
		 | <Patient>)>
	 <  An encounter that provides additional information about the healthcare context in which this request is made.; (xsd)encounter:Encounter*>?
	 <  The date/time at which the requested service should occur.; (xsd)occurrence:( <dateTime>
		 | <Period>
		 | <Timing>)>?
	 <  If a CodeableConcept is present, it indicates the pre-condition for performing the service.  For example "pain", "on flare-up", etc.; (xsd)asNeeded:( <boolean>
		 | <CodeableConcept>)>?
	 <  When the request transitioned to being actionable.; (xsd)authoredOn:dateTime>?
	 <  The individual who initiated the request and has responsibility for its activation. This not the dispatcher, but rather who is the authorizer.  This element is not intended to handle delegation which would generally be managed through the Provenance resource.; (xsd)requester:( <Device>
		 | <Organization>
		 | <Patient>
		 | <Practitioner>
		 | <PractitionerRole>
		 | <RelatedPerson>)>
	 <  Desired type of performer for doing the requested service. This is a  role, not  a participation type.  In other words, does not describe the task but describes the capacity.  For example, “compounding pharmacy”, “psychiatrist” or “internal referral”.; (xsd)performerType:CodeableConcept>?
	 <  The desired performer for doing the requested service.  For example, the surgeon, dermatopathologist, endoscopist, etc. If multiple performers are present, it is interpreted as a list of *alternative* performers without any preference regardless of order.  If order of preference is needed use the [request-performerOrder extension](http://hl7.org/fhir/R4/extension-request-performerorder.html).  Use CareTeam to represent a group of performers (for example, Practitioner A *and* Practitioner B).; (xsd)performer:( <CareTeam>
		 | <Device>
		 | <HealthcareService>
		 | <Organization>
		 | <Patient>
		 | <Practitioner>
		 | <PractitionerRole>
		 | <RelatedPerson>)>?
	[]<  The preferred location(s) where the procedure should actually happen in coded or free text form. E.g. at home or nursing day care center.; (xsd)locationCode:CodeableConcept>*
	[]<  A reference to the the preferred location(s) where the procedure should actually happen. E.g. at home or nursing day care center.; (xsd)locationReference:Location*>*
	[]<  An explanation or justification for why this service is being requested in coded or textual form.   This is often for billing purposes.  May relate to the resources referred to in `supportingInfo`. This element represents why the referral is being made and may be used to decide how the service will be performed, or even if it will be performed at all.   Use `CodeableConcept.text` element if the data is free (uncoded) text as shown in the [CT Scan example](http://hl7.org/fhir/R4/servicerequest-example-di.html).; (xsd)reasonCode:CodeableConcept>*
	[]<  Indicates another resource that provides a justification for why this service is being requested.   May relate to the resources referred to in `supportingInfo`. This element represents why the referral is being made and may be used to decide how the service will be performed, or even if it will be performed at all.    To be as specific as possible,  a reference to  *Observation* or *Condition* should be used if available.  Otherwise when referencing  *DiagnosticReport*  it should contain a finding  in `DiagnosticReport.conclusion` and/or `DiagnosticReport.conclusionCode`.   When using a reference to *DocumentReference*, the target document should contain clear findings language providing the relevant reason for this service request.  Use  the CodeableConcept text element in `ServiceRequest.reasonCode` if the data is free (uncoded) text as shown in the [CT Scan example](http://hl7.org/fhir/R4/servicerequest-example-di.html).; (xsd)reasonReference:( <Condition>
		 | <DiagnosticReport>
		 | <DocumentReference>
		 | <Observation>)>*
	[]<  Insurance plans, coverage extensions, pre-authorizations and/or pre-determinations that may be needed for delivering the requested service.; (xsd)insurance:( <ClaimResponse>
		 | <Coverage>)>*
	[]<  Additional clinical information about the patient or specimen that may influence the services or their interpretations.     This information includes diagnosis, clinical findings and other observations.  In laboratory ordering these are typically referred to as "ask at order entry questions (AOEs)".  This includes observations explicitly requested by the producer (filler) to provide context or supporting information needed to complete the order. For example,  reporting the amount of inspired oxygen for blood gas measurements. To represent information about how the services are to be delivered use the `instructions` element.; (xsd)supportingInfo:Resource*>*
	[]<  One or more specimens that the laboratory procedure will use. Many diagnostic procedures need a specimen, but the request itself is not actually about the specimen. This element is for when the diagnostic is requested on already existing specimens and the request points to the specimen it applies to.    Conversely, if the request is entered first with an unknown specimen, then the [Specimen](http://hl7.org/fhir/R4/specimen.html) resource points to the ServiceRequest.; (xsd)specimen:Specimen*>*
	[]<  Anatomic location where the procedure should be performed. This is the target site. Only used if not implicit in the code found in ServiceRequest.code.  If the use case requires BodySite to be handled as a separate resource instead of an inline coded element (e.g. to identify and track separately)  then use the standard extension [procedure-targetBodyStructure](http://hl7.org/fhir/R4/extension-procedure-targetbodystructure.html).; (xsd)bodySite:CodeableConcept>*
	[]<  Any other notes and comments made about the service request. For example, internal billing notes.; (xsd)note:Annotation>*
	 <  Instructions in terms that are understood by the patient or consumer.; (xsd)patientInstruction:string>?
	[]<  Key events in the history of the request. This might not include provenances for all versions of the request – only those deemed “relevant” or important.
This SHALL NOT include the Provenance associated with this current version of the resource.  (If that provenance is deemed to be a “relevant” change, it will need to be added as part of a later update.  Until then, it can be queried directly as the Provenance that points to this version using _revinclude
All Provenances should have some historical version of this Request as their subject.; (xsd)relevantHistory:Provenance*>*
	[]<  Identifies a Questionnaire that is being asked to be completed; (xsd)questionnaire:sdc-servicerequest-questionnaire>+

🔗  Identifies a Questionnaire that is being asked to be completedsdc-servicerequest-questionnaire(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	 <  An Extension; (xsd)extension:Extension>{0,0}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-servicerequest-questionnaire; (xsd)url:string>
	 <  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).; (xsd)value:canonical>?

🔗  A task to be performed.sdc-task(xsd)=
	 <#base:Task>
	 <  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.; (xsd)id:string>?
	 <  The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.; (xsd)meta:Meta>?
	 <  A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. 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. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.; (xsd)implicitRules:uri>?
	 <  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).; (xsd)language:code>?
	 <  A human-readable narrative that contains a summary of the resource and can 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. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied).  This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.; (xsd)text: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. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.; (xsd)contained:Resource>*
	[]<  May be used to represent additional information that is not part of the basic definition of the resource. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	[]<  The business identifier for this task.; (xsd)identifier:Identifier>*
	 <  The URL pointing to a *FHIR*-defined protocol, guideline, orderset or other definition that is adhered to in whole or in part by this Task.; (xsd)instantiatesCanonical:canonical>?
	 <  The URL pointing to an *externally* maintained  protocol, guideline, orderset or other definition that is adhered to in whole or in part by this Task.; (xsd)instantiatesUri:uri>?
	[]<  BasedOn refers to a higher-level authorization that triggered the creation of the task.  It references a "request" resource such as a ServiceRequest, MedicationRequest, ServiceRequest, CarePlan, etc. which is distinct from the "request" resource the task is seeking to fulfill.  This latter resource is referenced by FocusOn.  For example, based on a ServiceRequest (= BasedOn), a task is created to fulfill a procedureRequest ( = FocusOn ) to collect a specimen from a patient.; (xsd)basedOn:Resource*>*
	 <  An identifier that links together multiple tasks and other requests that were created in the same context.; (xsd)groupIdentifier:Identifier>?
	[]<  Task that this particular task is part of. This should usually be 0..1.; (xsd)partOf:Task*>*
	 <  The current status of the task.; (xsd)status:code>
	 <  An explanation as to why this task is held, failed, was refused, etc. This applies to the current status.  Look at the history of the task to see reasons for past statuses.; (xsd)statusReason:CodeableConcept>?
	 <  Contains business-specific nuances of the business state.; (xsd)businessStatus:CodeableConcept>?
	 <  Indicates the "level" of actionability associated with the Task, i.e. i+R[9]Cs this a proposed task, a planned task, an actionable task, etc. This element is immutable.  Proposed tasks, planned tasks, etc. must be distinct instances.

In most cases, Tasks will have an intent of "order".; (xsd)intent:code>
	 <  Indicates how quickly the Task should be addressed with respect to other requests.; (xsd)priority:code>?
	 <  A name or code (or both) briefly describing what the task involves. The title (eg "My Tasks", "Outstanding Tasks for Patient X") should go into the code.; (xsd)code:CodeableConcept>
	 <  A free-text description of what is to be performed.; (xsd)description:string>?
	 <  The request being actioned or the resource being manipulated by this task. If multiple resources need to be manipulated, use sub-tasks.  (This ensures that status can be tracked independently for each referenced resource.).; (xsd)focus:sdc-servicerequest*>?
	 <  The entity who benefits from the performance of the service specified in the task (e.g., the patient).; (xsd)for:Resource*>?
	 <  The healthcare event  (e.g. a patient and healthcare provider interaction) during which this task was created.; (xsd)encounter:Encounter*>?
	 <  Identifies the time action was first taken against the task (start) and/or the time final action was taken against the task prior to marking it as completed (end).; (xsd)executionPeriod:Period>?
	 <  The date and time this task was created.; (xsd)authoredOn:dateTime>
	 <  The date and time of last modification to this task.; (xsd)lastModified:dateTime>?
	 <  The creator of the task.; (xsd)requester:( <Device>
		 | <Organization>
		 | <Patient>
		 | <Practitioner>
		 | <PractitionerRole>
		 | <RelatedPerson>)>
	[]<  The kind of participant that should perform the task.; (xsd)performerType:CodeableConcept>*
	 <  Individual organization or Device currently responsible for task execution. Tasks may be created with an owner not yet identified.; (xsd)owner:( <CareTeam>
		 | <Device>
		 | <HealthcareService>
		 | <Organization>
		 | <Patient>
		 | <Practitioner>
		 | <PractitionerRole>
		 | <RelatedPerson>)>?
	 <  Principal physical location where the this task is performed.; (xsd)location:Location*>?
	 <  A description or code indicating why this task needs to be performed. This should only be included if there is no focus or if it differs from the reason indicated on the focus.; (xsd)reasonCode:CodeableConcept>?
	 <  A resource reference indicating why this task needs to be performed. Tasks might be justified based on an Observation, a Condition, a past or planned procedure, etc.   This should only be included if there is no focus or if it differs from the reason indicated on the focus.    Use the CodeableConcept text element in `Task.reasonCode` if the data is free (uncoded) text.; (xsd)reasonReference:Resource*>?
	[]<  Insurance plans, coverage extensions, pre-authorizations and/or pre-determinations that may be relevant to the Task.; (xsd)insurance:( <ClaimResponse>
		 | <Coverage>)>*
	[]<  Free-text information captured about the task as it progresses.; (xsd)note:Annotation>*
	[]<  Links to Provenance records for past versions of this Task that identify key state transitions or updates that are likely to be relevant to a user looking at the current version of the task. This element does not point to the Provenance associated with the *current* version of the resource - as it would be created after this version existed.  The Provenance for the current version can be retrieved with a _revinclude.; (xsd)relevantHistory:Provenance*>*
	 <  If the Task.focus is a request resource and the task is seeking fulfillment (i.e. is asking for the request to be actioned), this element identifies any limitations on what parts of the referenced request should be actioned.; (xsd)restriction:sdc-task.restriction>?
	[]<  Additional information that may be needed in the execution of the task.; (xsd)input:sdc-task.input>*
	[]<  Outputs produced by the Task.; (xsd)output:sdc-task.output>*
	 <  Indicates the questionnaire to be completed.; (xsd)questionnaire:sdc-task.questionnaire>?
	[]<  Indicates an endpoint the form should be posted to on completion.; (xsd)responseEndpoint:sdc-task.responseEndpoint>*
	 <  Indicates the questionnaire response resulting from the request.; (xsd)response:sdc-task.response>?

🔗  Additional information that may be needed in the execution of the task.sdc-task.input(xsd)=
	 <#base:Task.input>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  A code or description indicating how the input is intended to be used as part of the task execution. If referencing a BPMN workflow or Protocol, the "system" is the URL for the workflow definition and the code is the "name" of the required input.; (xsd)type:CodeableConcept>
	 ( <valueAddress:Address>
		 | <valueAge:Age>
		 | <valueAnnotation:Annotation>
		 | <valueAttachment:Attachment>
		 | <valueBase64Binary:base64Binary>
		 | <valueBoolean:boolean>
		 | <valueCanonical:canonical>
		 | <valueCode:code>
		 | <valueCodeableConcept:CodeableConcept>
		 | <valueCoding:Coding>
		 | <valueContactDetail:ContactDetail>
		 | <valueContactPoint:ContactPoint>
		 | <valueContributor:Contributor>
		 | <valueCount:Count>
		 | <valueDataRequirement:DataRequirement>
		 | <valueDate:date>
		 | <valueDateTime:dateTime>
		 | <valueDecimal:decimal>
		 | <valueDistance:Distance>
		 | <valueDosage:Dosage>
		 | <valueDuration:Duration>
		 | <valueExpression:Expression>
		 | <valueHumanName:HumanName>
		 | <valueId:id>
		 | <valueIdentifier:Identifier>
		 | <valueInstant:instant>
		 | <valueInteger:integer>
		 | <valueMarkdown:markdown>
		 | <valueMeta:Meta>
		 | <valueMoney:Money>
		 | <valueOid:oid>
		 | <valueParameterDefinition:ParameterDefinition>
		 | <valuePeriod:Period>
		 | <valuePositiveInt:positiveInt>
		 | <valueQuantity:Quantity>
		 | <valueRange:Range>
		 | <valueRatio:Ratio>
		 | <valueRelatedArtifact:RelatedArtifact>
		 | <valueResource:Resource>
		 | <valueSampledData:SampledData>
		 | <valueSignature:Signature>
		 | <valueString:string>
		 | <valueTime:time>
		 | <valueTiming:Timing>
		 | <valueTriggerDefinition:TriggerDefinition>
		 | <valueUnsignedInt:unsignedInt>
		 | <valueUri:uri>
		 | <valueUrl:url>
		 | <valueUsageContext:UsageContext>
		 | <valueUuid:uuid>)

🔗  Outputs produced by the Task.sdc-task.output(xsd)=
	 <#base:Task.output>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  The name of the Output parameter.; (xsd)type:CodeableConcept>
	 ( <valueAddress:Address>
		 | <valueAge:Age>
		 | <valueAnnotation:Annotation>
		 | <valueAttachment:Attachment>
		 | <valueBase64Binary:base64Binary>
		 | <valueBoolean:boolean>
		 | <valueCanonical:canonical>
		 | <valueCode:code>
		 | <valueCodeableConcept:CodeableConcept>
		 | <valueCoding:Coding>
		 | <valueContactDetail:ContactDetail>
		 | <valueContactPoint:ContactPoint>
		 | <valueContributor:Contributor>
		 | <valueCount:Count>
		 | <valueDataRequirement:DataRequirement>
		 | <valueDate:date>
		 | <valueDateTime:dateTime>
		 | <valueDecimal:decimal>
		 | <valueDistance:Distance>
		 | <valueDosage:Dosage>
		 | <valueDuration:Duration>
		 | <valueExpression:Expression>
		 | <valueHumanName:HumanName>
		 | <valueId:id>
		 | <valueIdentifier:Identifier>
		 | <valueInstant:instant>
		 | <valueInteger:integer>
		 | <valueMarkdown:markdown>
		 | <valueMeta:Meta>
		 | <valueMoney:Money>
		 | <valueOid:oid>
		 | <valueParameterDefinition:ParameterDefinition>
		 | <valuePeriod:Period>
		 | <valuePositiveInt:positiveInt>
		 | <valueQuantity:Quantity>
		 | <valueRange:Range>
		 | <valueRatio:Ratio>
		 | <valueRelatedArtifact:RelatedArtifact>
		 | <valueResource:Resource>
		 | <valueSampledData:SampledData>
		 | <valueSignature:Signature>
		 | <valueString:string>
		 | <valueTime:time>
		 | <valueTiming:Timing>
		 | <valueTriggerDefinition:TriggerDefinition>
		 | <valueUnsignedInt:unsignedInt>
		 | <valueUri:uri>
		 | <valueUrl:url>
		 | <valueUsageContext:UsageContext>
		 | <valueUuid:uuid>)

🔗  Indicates the questionnaire to be completed.sdc-task.questionnaire(xsd)=
	 <#base:BackboneElement>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  A code or description indicating how the input is intended to be used as part of the task execution. If referencing a BPMN workflow or Protocol, the "system" is the URL for the workflow definition and the code is the "name" of the required input.; (xsd)type:CodeableConcept>
	 <  The value of the input parameter as a basic type.; (xsd)value:canonical>

🔗  Indicates the questionnaire response resulting from the request.sdc-task.response(xsd)=
	 <#base:BackboneElement>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  The name of the Output parameter.; (xsd)type:CodeableConcept>
	 <  The value of the Output parameter as a basic type.; (xsd)value:QuestionnaireResponse*>

🔗  Indicates an endpoint the form should be posted to on completion.sdc-task.responseEndpoint(xsd)=
	 <#base:BackboneElement>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  A code or description indicating how the input is intended to be used as part of the task execution. If referencing a BPMN workflow or Protocol, the "system" is the URL for the workflow definition and the code is the "name" of the required input.; (xsd)type:CodeableConcept>
	 <  The value of the input parameter as a basic type.; (xsd)value:url>

🔗  If the Task.focus is a request resource and the task is seeking fulfillment (i.e. is asking for the request to be actioned), this element identifies any limitations on what parts of the referenced request should be actioned.sdc-task.restriction(xsd)=
	 <#base:Task.restriction>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  Indicates the number of times the requested action should occur.; (xsd)repetitions:positiveInt>?
	 <  Over what time-period is fulfillment sought. Note that period.high is the due date representing the time by which the task should be completed.; (xsd)period:Period>?
	[]<  For requests that are targeted to more than on potential recipient/target, for whom is fulfillment sought?; (xsd)recipient:( <Group>
		 | <Organization>
		 | <Patient>
		 | <Practitioner>
		 | <PractitionerRole>
		 | <RelatedPerson>)>*

🔗  Specifies clinical/business/etc. metadata that can be used to retrieve, index and/or categorize an artifact. This metadata can either be specific to the applicable population (e.g., age category, DRG) or the specific context of care (e.g., venue, care setting, provider of care).sdc-usagecontext(xsd)=
	 <#base:UsageContext>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	 <  A code that identifies the type of context being specified by this usage context.; (xsd)code:Coding>
	 ( <valueCodeableConcept:CodeableConcept>
		 | <valueGroup:Group>
		 | <valueHealthcareService:HealthcareService>
		 | <valueInsurancePlan:InsurancePlan>
		 | <valueLocation:Location>
		 | <valueOrganization:Organization>
		 | <valuePlanDefinition:PlanDefinition>
		 | <valueQuantity:Quantity>
		 | <valueRange:Range>
		 | <valueResearchStudy:ResearchStudy>)
	 <  A value that defines the context specified in this context of use. The interpretation of the value is defined by the code.; (xsd)valueCodeableConcept:sdc-usagecontext.valueCodeableConcept>?
	 <  A value that defines the context specified in this context of use. The interpretation of the value is defined by the code.; (xsd)valueRange:sdc-usagecontext.valueRange>?

🔗  A value that defines the context specified in this context of use. The interpretation of the value is defined by the code.sdc-usagecontext.valueCodeableConcept(xsd)=
	 <#base:CodeableConcept>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  A reference to a code defined by a terminology system. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information.  Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.; (xsd)coding:sdc-usagecontext.valueCodeableConcept.coding>*
	 <  A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. Very often the text is the same as a displayName of one of the codings.; (xsd)text:string>?

🔗  A reference to a code defined by a terminology system. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information.  Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.sdc-usagecontext.valueCodeableConcept.coding(xsd)=
	 <#base:Coding>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	 <  The identification of the code system that defines the meaning of the symbol in the code. The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...).  OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously.; (xsd)system:uri>?
	 <  The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.; (xsd)version:string>?
	 <  A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).; (xsd)code>?
	 <  A representation of the meaning of the code in the system, following the rules of the system.; (xsd)display:string>?
	 <  Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.; (xsd)userSelected:boolean>?

🔗  A value that defines the context specified in this context of use. The interpretation of the value is defined by the code.sdc-usagecontext.valueRange(xsd)=
	 <#base:Range>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	 <  The low limit. The boundary is inclusive. If the low element is missing, the low boundary is not known.; (xsd)low:SimpleQuantity>?
	 <  The high limit. The boundary is inclusive. If the high element is missing, the high boundary is not known.; (xsd)high:SimpleQuantity>?

🔗  Sets expectations for SDC-conformant systems around value set support for representing permitted question answers.sdc-valueset(xsd)=
	 <#base:ValueSet>
	 <  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.; (xsd)id:string>?
	 <  The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.; (xsd)meta:Meta>?
	 <  A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. 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. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.; (xsd)implicitRules:uri>?
	 <  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).; (xsd)language:code>?
	 <  A human-readable narrative that contains a summary of the resource and can 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. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied).  This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.; (xsd)text: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. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.; (xsd)contained:Resource>*
	[]<  May be used to represent additional information that is not part of the basic definition of the resource. 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 can 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.; (xsd)extension:Extension>*
	[]<  An Extension; (xsd)modifierExtension:Extension>*
	 <  An absolute URI that is used to identify this value set when it is referenced in a specification, model, design or an instance; also called its canonical identifier. This SHOULD be globally unique and SHOULD be a literal address at which at which an authoritative instance of this value set is (or will be) published. This URL can be the target of a canonical reference. It SHALL remain the same when the value set is stored on different servers. Can be a urn:uuid: or a urn:oid: but real http: addresses are preferred.  Multiple instances may share the same URL if they have a distinct version.

The determination of when to create a new version of a resource (same url, new version) vs. defining a new artifact is up to the author.  Considerations for making this decision are found in [Technical and Business Versions](http://hl7.org/fhir/R4/resource.html#versions). 

In some cases, the resource can no longer be found at the stated url, but the url itself cannot change. Implementations can use the [meta.source](http://hl7.org/fhir/R4/resource.html#meta) element to indicate where the current master source of the resource can be found.; (xsd)url:uri>?
	[]<  A formal identifier that is used to identify this value set when it is represented in other formats, or referenced in a specification, model, design or an instance. Typically, this is used for identifiers that can go in an HL7 V3 II (instance identifier) data type, and can then identify this value set outside of FHIR, where it is not possible to use the logical URI.; (xsd)identifier:Identifier>*
	 <  The identifier that is used to identify this version of the value set when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the value set author and is not expected to be globally unique. For example, it might be a timestamp (e.g. yyyymmdd) if a managed version is not available. There is also no expectation that versions can be placed in a lexicographical sequence. There may be different value set instances that have the same identifier but different versions.  The version can be appended to the url in a reference to allow a reference to a particular business version of the value set with the format [url]|[version].; (xsd)version:string>?
	 <  A natural language name identifying the value set. This name should be usable as an identifier for the module by machine processing applications such as code generation. The name is not expected to be globally unique. The name should be a simple alphanumeric type name to ensure that it is machine-processing friendly.A name should be provided unless the value set is a contained resource (e.g. an anonymous value set in a profile). Most registries will require a name.; (xsd)name:string>?
	 <  A short, descriptive, user-friendly title for the value set. This name does not need to be machine-processing friendly and may contain punctuation, white-space, etc.; (xsd)title:string>?
	 <  The status of this value set. Enables tracking the life-cycle of the content. The status of the value set applies to the value set definition (ValueSet.compose) and the associated ValueSet metadata. Expansions do not have a state. Allows filtering of value sets that are appropriate for use versus not.See also the [valueset-workflowStatus](http://hl7.org/fhir/R4/extension-valueset-workflowstatus.html) extension for additional status information related to the editorial process.; (xsd)status:code>
	 <  A Boolean value to indicate that this value set is authored for testing purposes (or education/evaluation/marketing) and is not intended to be used for genuine usage. Allows filtering of value sets that are appropriate for use versus not.; (xsd)experimental:boolean>?
	 <  The date (and optionally time) when the value set was created or revised (e.g. the 'content logical definition'). Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the value set. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource.; (xsd)date:dateTime>?
	 <  The name of the organization or individual that published the value set. Usually an organization but may be an individual. The publisher (or steward) of the value set is the organization or individual primarily responsible for the maintenance and upkeep of the value set. This is not necessarily the same individual or organization that developed and initially authored the content. The publisher is the primary point of contact for questions or issues with the value set. This item SHOULD be populated unless the information is available from context.; (xsd)publisher:string>?
	[]<  Contact details to assist a user in finding and communicating with the publisher. May be a web site, an email address, a telephone number, etc.; (xsd)contact:ContactDetail>*
	 <  A free text natural language description of the value set from a consumer's perspective. The textual description specifies the span of meanings for concepts to be included within the Value Set Expansion, and also may specify the intended use and limitations of the Value Set. This description can be used to capture details such as why the value set was built, comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the value set as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context (e.g. the language of the value set is presumed to be the predominant language in the place the value set was created).The description is not intended to describe the semantics of the Value Set - there are no intrinsic semantics separate from the codes contained in its expansion. The description should capture its intended use, which is needed for ensuring integrity for its use in models across future changes. A description should be provided unless the value set is a contained resource (e.g. an anonymous value set in a profile). Most registries will require a description.; (xsd)description:markdown>?
	[]<  The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate value set instances. When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.; (xsd)useContext:UsageContext>*
	[]<  A legal or geographic region in which the value set is intended to be used. It may be possible for the value set to be used in jurisdictions other than those for which it was originally designed or intended.; (xsd)jurisdiction:CodeableConcept>*
	 <  If this is set to 'true', then no new versions of the content logical definition can be created.  Note: Other metadata might still change. Normally immutability is set to 'false', which is the default assumption if it is not populated.  Note that the implication is that if this is set to 'true', there may be only one ValueSet version for this definition. Immutability tends to be set to 'true' in one of two cases: - Where the value set, by the nature of its usage, cannot change.  For example "All specializations of ACT in ActClassCode" - Where there's no safe way to express the "Purpose" such that someone else could safely make changes to the value set definition. Source workflow control must guarantee that the same URI always yields the same definition.; (xsd)immutable:boolean>
	 <  Explanation of why this value set is needed and why it has been designed as it has. This element does not describe the usage of the value set. Instead, it provides traceability of ''why'' the resource is either needed or ''why'' it is defined as it is.  This may be used to point to source materials or specifications that drove the structure of this value set.; (xsd)purpose:markdown>?
	 <  A copyright statement relating to the value set and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the value set. nullFrequently, the copyright differs between the value set and the codes that are included. The copyright statement should clearly differentiate between these when required.; (xsd)copyright:markdown>?
	 <  A set of criteria that define the contents of the value set by including or excluding codes selected from the specified code system(s) that the value set draws from. This is also known as the Content Logical Definition (CLD).; (xsd)compose:sdc-valueset.compose>?
	 <  A value set can also be "expanded", where the value set is turned into a simple collection of enumerated codes. This element holds the expansion, if it has been performed. Expansion is performed to produce a collection of codes that are ready to use for data entry or validation. Value set expansions are always considered to be stateless - they are a record of the set of codes in the value set at a point in time under a given set of conditions, and are not subject to ongoing maintenance.

Expansion.parameter is  a simplified list of parameters - a subset of the features of the [Parameters](http://hl7.org/fhir/R4/parameters.html) resource.; (xsd)expansion:sdc-valueset.expansion>?
	[]<  Indicates an extension that must be supported by the system presenting the instance for data capture or end-user consumption. If a system does not recognize the extension or cannot implement the functionality defined by the extension, it should display an error message or warning and refrain from presenting the instance to the user or using it when capturing data. This may point to extensions that control the appearance of data elements, control what value elements have, what elements are or are not available, what elements can or cannot be edited, or rules about how editing may occur. This extension does NOT apply when simply rendering a resource for publication purposes or for other purposes not intended for end-user data capture or data consumption.; (xsd)rendering-criticalExtension:sdc-rendering-criticalExtension>*

🔗  A set of criteria that define the contents of the value set by including or excluding codes selected from the specified code system(s) that the value set draws from. This is also known as the Content Logical Definition (CLD).sdc-valueset.compose(xsd)=
	 <#base:ValueSet.compose>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  The Locked Date is  the effective date that is used to determine the version of all referenced Code Systems and Value Set Definitions included in the compose that are not already tied to a specific version. With a defined lockedDate the value set is considered "Locked". Otherwise, the value set may have different expansions as underlying code systems and/or value sets evolve.  The interpretation of lockedDate is often dependent on the context - e.g. a SNOMED CT derived value set with a lockedDate will have a different expansion in USA than in UK.  If a value set specifies a version for include and exclude statements, and also specifies a locked date, the specified versions need to be available that date, or the value set will not be usable.; (xsd)lockedDate:date>?
	 <  Whether inactive codes - codes that are not approved for current use - are in the value set. If inactive = true, inactive codes are to be included in the expansion, if inactive = false, the inactive codes will not be included in the expansion. If absent, the behavior is determined by the implementation, or by the applicable $expand parameters (but generally, inactive codes would be expected to be included). Note that in the FHIR terminology framework, "deprecated" does not mean inactive, but in some code systems, e.g. LOINC, "deprecated" does mean inactive. Code systems should define what codes are considered to be inactive. If this is not clearly defined (including in the FHIR code system resource), then all codes are assumed to be active.

The Value Set Definition specification defines an ActiveOnly element, which is the reverse of this element e.g. (ValueSet.compose.inactive=FALSE) is the same as (VSD.ActiveOnly=TRUE).; (xsd)inactive:boolean>?
	[]<  Include one or more codes from a code system or other value set(s). All the conditions in an include must be true. If a system is listed, all the codes from the system are listed. If one or more filters are listed, all of the filters must apply. If one or more value sets are listed, the codes must be in all the value sets. E.g. each include is 'include all the codes that meet all these conditions'.; (xsd)include:sdc-valueset.compose.include>+
	[]<  Exclude one or more codes from the value set based on code system filters and/or other value sets. Usually this is used to selectively exclude codes that were included by subsumption in the inclusions. Any display names specified for the codes are ignored.; (xsd)exclude:ValueSet.compose.include>*

🔗  Include one or more codes from a code system or other value set(s). All the conditions in an include must be true. If a system is listed, all the codes from the system are listed. If one or more filters are listed, all of the filters must apply. If one or more value sets are listed, the codes must be in all the value sets. E.g. each include is 'include all the codes that meet all these conditions'.sdc-valueset.compose.include(xsd)=
	 <#base:ValueSet.compose.include>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  An absolute URI which is the code system from which the selected codes come from. If there are no codes or filters, the entire code system is included. Note that the set of codes that are included may contain abstract codes. See ''Coding.system'' for further documentation about the correct value for the system element.; (xsd)system:uri>?
	 <  The version of the code system that the codes are selected from, or the special version '*' for all versions. This is used when selecting the descendants of a concept - they may change between versions. If no version is specified, then the exact contents of the value set might not be known until a context of use binds it to a particular version. The special value '*' means all versions; It is at server discretion regarding expansions and which versions must be supported.; (xsd)version:string>?
	[]<  Specifies a concept to be included or excluded. The list of concepts is considered ordered, though the order might not have any particular significance. Typically, the order of an expansion follows that defined in the compose element.; (xsd)concept:sdc-valueset.compose.include.concept>*
	[]<  Select concepts by specify a matching criterion based on the properties (including relationships) defined by the system, or on filters defined by the system. If multiple filters are specified, they SHALL all be true. Selecting codes by specifying filters based on properties is only possible where the underlying code system defines appropriate properties. Note that in some cases, the underlying code system defines the logical concepts but not the literal codes for the concepts. In such cases, the literal definitions may be provided by a third party.; (xsd)filter:sdc-valueset.compose.include.filter>*
	[]<  Selects the concepts found in this value set (based on its value set definition). This is an absolute URI that is a reference to ValueSet.url.  If multiple value sets are specified this includes the union of the contents of all of the referenced value sets. The value set URI is either a logical reference to a defined value set such as a [SNOMED CT reference set](http://hl7.org/fhir/R4/snomedct.html#implicit), or a direct reference to a value set definition using ValueSet.url. The reference might not refer to an actual FHIR ValueSet resource; in this case, whatever is referred to is an implicit definition of a value set that needs to be clear about how versions are resolved.; (xsd)valueSet:canonical>*

🔗  Specifies a concept to be included or excluded. The list of concepts is considered ordered, though the order might not have any particular significance. Typically, the order of an expansion follows that defined in the compose element.sdc-valueset.compose.include.concept(xsd)=
	 <#base:ValueSet.compose.include.concept>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  An Extension; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  Specifies a code for the concept to be included or excluded. Expressions are allowed if defined by the underlying code system.; (xsd)code>
	 <  The text to display to the user for this concept in the context of this valueset. If no display is provided, then applications using the value set use the display specified for the code by the system. The value set resource allows for an alternative display to be specified for when this concept is used in this particular value set. See notes in the value set narrative about the correct use of this element.; (xsd)display:sdc-valueset.compose.include.concept.display>?
	[]<  Additional representations for this concept when used in this value set - other languages, aliases, specialized purposes, used for particular purposes, etc. Concepts have both a ```display``` and an array of ```designation```. The display is equivalent to a special designation with an implied ```designation.use``` of "primary code" and a language equal to the [Resource Language](http://hl7.org/fhir/R4/resource.html#language).; (xsd)designation:sdc-valueset.compose.include.concept.designation>*
	 <  The label to list in front of a code when presenting a list of possible values in a questionnaire-like fashion. For questionnaires, see additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/rendering.html#valueset-label).; (xsd)conceptLabel:valueset-label>?
	 <  Identifies the relative order in which concepts within the value set should be presented to a user. The presence of a sort order implies that sort order is important.; (xsd)conceptConceptOrder:valueset-conceptOrder>?

🔗  The label to list in front of a code when presenting a list of possible values in a questionnaire-like fashion. For questionnaires, see additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/rendering.html#valueset-label).sdc-valueset.compose.include.concept.conceptLabel(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	 <  An Extension; (xsd)extension:Extension>{0,0}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. http://hl7.org/fhir/StructureDefinition/valueset-label; (xsd)url:string>
	 <  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R5/extensibility.html) for a list).; (xsd)value:sdc-valueset.compose.include.concept.conceptLabel.value[x]>

🔗  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R5/extensibility.html) for a list).sdc-valueset.compose.include.concept.conceptLabel.value[x](xsd)=
	 <#base:string>
	 <  unique id for the element within a resource (for internal references); (xsd)id:string>?
	[]<  An Extension; (xsd)extension:Extension>*
	 <  The actual value; (xsd)value:string>?
	 <  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.

For questionnaires, see additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/rendering.html#rendering-style).; (xsd)code-renderingStyle:rendering-style>?
	 <  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. Existing [restrictions on XHTML content](http://hl7.org/fhir/R4/narrative.html#security) apply. Note that using [markdown](http://hl7.org/fhir/extensions/5.1.0StructureDefinition-rendering-markdown.html) allows for greater flexibility of display. For questionnaires, see additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/rendering.html#rendering-xhtml).; (xsd)code-xhtml:rendering-xhtml>?

🔗  Additional representations for this concept when used in this value set - other languages, aliases, specialized purposes, used for particular purposes, etc. Concepts have both a ```display``` and an array of ```designation```. The display is equivalent to a special designation with an implied ```designation.use``` of "primary code" and a language equal to the [Resource Language](http://hl7.org/fhir/R4/resource.html#language).sdc-valueset.compose.include.concept.designation(xsd)=
	 <#base:ValueSet.compose.include.concept.designation>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  An Extension; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  The language this designation is defined for. In the absence of a language, the resource language applies.; (xsd)language:code>?
	 <  A code that represents types of uses of designations. If no use is provided, the designation can be assumed to be suitable for general display to a human user.; (xsd)use:Coding>?
	 <  The text value for this designation.; (xsd)value:string>
	 <  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.

For questionnaires, see additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/rendering.html#rendering-style).; (xsd)designation-renderingStyle:rendering-style>?
	 <  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. Existing [restrictions on XHTML content](http://hl7.org/fhir/R4/narrative.html#security) apply. Note that using [markdown](http://hl7.org/fhir/extensions/5.1.0StructureDefinition-rendering-markdown.html) allows for greater flexibility of display. For questionnaires, see additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/rendering.html#rendering-xhtml).; (xsd)designation-xhtml:rendering-xhtml>?

🔗  The text to display to the user for this concept in the context of this valueset. If no display is provided, then applications using the value set use the display specified for the code by the system. The value set resource allows for an alternative display to be specified for when this concept is used in this particular value set. See notes in the value set narrative about the correct use of this element.sdc-valueset.compose.include.concept.display(xsd)=
	 <#base:string>
	 <  unique id for the element within a resource (for internal references); (xsd)id:string>?
	[]<  An Extension; (xsd)extension:Extension>*
	 <  The actual value; (xsd)value:string>?
	 <  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.

For questionnaires, see additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/rendering.html#rendering-style).; (xsd)codeDisplay-renderingStyle:rendering-style>?
	 <  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. Existing [restrictions on XHTML content](http://hl7.org/fhir/R4/narrative.html#security) apply. Note that using [markdown](http://hl7.org/fhir/extensions/5.1.0StructureDefinition-rendering-markdown.html) allows for greater flexibility of display. For questionnaires, see additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/rendering.html#rendering-xhtml).; (xsd)codeDisplay-xhtml:rendering-xhtml>?

🔗  Select concepts by specify a matching criterion based on the properties (including relationships) defined by the system, or on filters defined by the system. If multiple filters are specified, they SHALL all be true. Selecting codes by specifying filters based on properties is only possible where the underlying code system defines appropriate properties. Note that in some cases, the underlying code system defines the logical concepts but not the literal codes for the concepts. In such cases, the literal definitions may be provided by a third party.sdc-valueset.compose.include.filter(xsd)=
	 <#base:ValueSet.compose.include.filter>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  A code that identifies a property or a filter defined in the code system.; (xsd)property:code>
	 <  The kind of operation to perform as a part of the filter criteria. In case filter.property represents a property of the system, the operation applies to the selected property. In case filter.property represents a filter of the system, the operation SHALL match one of the CodeSystem.filter.operator values.; (xsd)op:code>
	 <  The match value may be either a code defined by the system, or a string value, which is a regex match on the literal string of the property value  (if the filter represents a property defined in CodeSystem) or of the system filter value (if the filter represents a filter defined in CodeSystem) when the operation is 'regex', or one of the values (true and false), when the operation is 'exists'. Use regex matching with care - full regex matching on every SNOMED CT term is prohibitive, for example.; (xsd)value:string>

🔗  A value set can also be "expanded", where the value set is turned into a simple collection of enumerated codes. This element holds the expansion, if it has been performed. Expansion is performed to produce a collection of codes that are ready to use for data entry or validation. Value set expansions are always considered to be stateless - they are a record of the set of codes in the value set at a point in time under a given set of conditions, and are not subject to ongoing maintenance.

Expansion.parameter is  a simplified list of parameters - a subset of the features of the [Parameters](http://hl7.org/fhir/R4/parameters.html) resource.sdc-valueset.expansion(xsd)=
	 <#base:ValueSet.expansion>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  An Extension; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  An identifier that uniquely identifies this expansion of the valueset, based on a unique combination of the provided parameters, the system default parameters, and the underlying system code system versions etc. Systems may re-use the same identifier as long as those factors remain the same, and the expansion is the same, but are not required to do so. This is a business identifier. Typically, this uri is a UUID (e.g. urn:uuid:8230ff20-c97a-4167-a59d-dc2cb9df16dd).; (xsd)identifier:uri>?
	 <  The time at which the expansion was produced by the expanding system. This SHOULD be a fully populated instant, but in some circumstances, value sets are expanded by hand, and the expansion is published without that precision.; (xsd)timestamp:dateTime>
	 <  The total number of concepts in the expansion. If the number of concept nodes in this resource is less than the stated number, then the server can return more using the offset parameter. Paging only applies to flat expansions.; (xsd)total:integer>?
	 <  If paging is being used, the offset at which this resource starts.  I.e. this resource is a partial view into the expansion. If paging is not being used, this element SHALL NOT be present. Paging only applies to flat expansions. If a filter is applied, the count is the number of concepts that matched the filter, not the number of concepts in an unfiltered view of the expansion.; (xsd)offset:integer>?
	[]<  A parameter that controlled the expansion process. These parameters may be used by users of expanded value sets to check whether the expansion is suitable for a particular purpose, or to pick the correct expansion. The server decides which parameters to include here, but at a minimum, the list SHOULD include all of the parameters that affect the $expand operation. If the expansion will be persisted all of these parameters SHALL be included. If the codeSystem on the server has a specified version then this version SHALL be provided as a parameter in the expansion (note that not all code systems have a version).; (xsd)parameter:sdc-valueset.expansion.parameter>*
	[]<  The codes that are contained in the value set expansion.; (xsd)contains:sdc-valueset.expansion.contains>*
	 <  The logical URL of the ValueSet definition that was used to generate this expansion.; (xsd)expansionSource:valueset-expansionSource>?
	[]<  Optional Extension Element - found in all resources.; (xsd)expansionProperty:Extension>*

🔗  The codes that are contained in the value set expansion.sdc-valueset.expansion.contains(xsd)=
	 <#base:ValueSet.expansion.contains>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  An Extension; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  An absolute URI which is the code system in which the code for this item in the expansion is defined.; (xsd)system:uri>?
	 <  If true, this entry is included in the expansion for navigational purposes, and the user cannot select the code directly as a proper value. This should not be understood to exclude its use for searching (e.g. by subsumption testing). The client should know whether it is appropriate for the user to select an abstract code or not.; (xsd)abstract:boolean>?
	 <  If the concept is inactive in the code system that defines it. Inactive codes are those that are no longer to be used, but are maintained by the code system for understanding legacy data. It might not be known or specified whether an concept is inactive (and it may depend on the context of use). This should only have a value if the concept is inactive.; (xsd)inactive:boolean>?
	 <  The version of the code system from this code was taken. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. The exact value of the version string is specified by the system from which the code is derived.; (xsd)version:string>?
	 <  The code for this item in the expansion hierarchy. If this code is missing the entry in the hierarchy is a place holder (abstract) and does not represent a valid code in the value set.; (xsd)code>?
	 <  The recommended display for this item in the expansion.; (xsd)display:sdc-valueset.expansion.contains.display>?
	[]<  Additional representations for this item - other languages, aliases, specialized purposes, used for particular purposes, etc. These are relevant when the conditions of the expansion do not fix to a single correct representation. The designations provided must be based on the value set and code system definitions.; (xsd)designation:sdc-valueset.expansion.contains.designation>*
	[]<  Other codes and entries contained under this entry in the hierarchy. If the expansion uses this element, there is  no implication about the logical relationship between them, and the  structure cannot be used for logical inferencing. The structure  exists to provide navigational assistance for helping human users to  locate codes in the expansion.; (xsd)contains:ValueSet.expansion.contains>*
	 <  The label to list in front of a code when presenting a list of possible values in a questionnaire-like fashion. For questionnaires, see additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/rendering.html#valueset-label).; (xsd)expansionLabel:valueset-label>?
	 <  Identifies the relative order in which concepts within the value set should be presented to a user. The presence of a sort order implies that sort order is important.; (xsd)conceptConceptOrder:valueset-conceptOrder>?
	[]<  Optional Extension Element - found in all resources.; (xsd)containsProperty:Extension>*

🔗  Additional representations for this item - other languages, aliases, specialized purposes, used for particular purposes, etc. These are relevant when the conditions of the expansion do not fix to a single correct representation. The designations provided must be based on the value set and code system definitions.sdc-valueset.expansion.contains.designation(xsd)=
	 <#base:BackboneElement>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  An Extension; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  The language this designation is defined for. In the absence of a language, the resource language applies.; (xsd)language:code>?
	 <  A code that represents types of uses of designations. If no use is provided, the designation can be assumed to be suitable for general display to a human user.; (xsd)use:Coding>?
	 <  The text value for this designation.; (xsd)value:string>
	 <  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.

For questionnaires, see additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/rendering.html#rendering-style).; (xsd)expansionDesignation-renderingStyle:rendering-style>?
	 <  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. Existing [restrictions on XHTML content](http://hl7.org/fhir/R4/narrative.html#security) apply. Note that using [markdown](http://hl7.org/fhir/extensions/5.1.0StructureDefinition-rendering-markdown.html) allows for greater flexibility of display. For questionnaires, see additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/rendering.html#rendering-xhtml).; (xsd)expansionDesignation-xhtml:rendering-xhtml>?

🔗  The recommended display for this item in the expansion.sdc-valueset.expansion.contains.display(xsd)=
	 <#base:string>
	 <  unique id for the element within a resource (for internal references); (xsd)id:string>?
	[]<  An Extension; (xsd)extension:Extension>*
	 <  The actual value; (xsd)value:string>?
	 <  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.

For questionnaires, see additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/rendering.html#rendering-style).; (xsd)expansionDisplay-renderingStyle:rendering-style>?
	 <  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. Existing [restrictions on XHTML content](http://hl7.org/fhir/R4/narrative.html#security) apply. Note that using [markdown](http://hl7.org/fhir/extensions/5.1.0StructureDefinition-rendering-markdown.html) allows for greater flexibility of display. For questionnaires, see additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/rendering.html#rendering-xhtml).; (xsd)expansionDisplay-xhtml:rendering-xhtml>?

🔗  The label to list in front of a code when presenting a list of possible values in a questionnaire-like fashion. For questionnaires, see additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/rendering.html#valueset-label).sdc-valueset.expansion.contains.expansionLabel(xsd)=
	 <#base:Extension>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	 <  An Extension; (xsd)extension:Extension>{0,0}
	 <  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 SHALL be a URI for the Structure Definition defining the extension. http://hl7.org/fhir/StructureDefinition/valueset-label; (xsd)url:string>
	 <  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R5/extensibility.html) for a list).; (xsd)value:sdc-valueset.expansion.contains.expansionLabel.value[x]>

🔗  Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R5/extensibility.html) for a list).sdc-valueset.expansion.contains.expansionLabel.value[x](xsd)=
	 <#base:string>
	 <  unique id for the element within a resource (for internal references); (xsd)id:string>?
	[]<  An Extension; (xsd)extension:Extension>*
	 <  The actual value; (xsd)value:string>?
	 <  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.

For questionnaires, see additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/rendering.html#rendering-style).; (xsd)expansion-renderingStyle:rendering-style>?
	 <  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. Existing [restrictions on XHTML content](http://hl7.org/fhir/R4/narrative.html#security) apply. Note that using [markdown](http://hl7.org/fhir/extensions/5.1.0StructureDefinition-rendering-markdown.html) allows for greater flexibility of display. For questionnaires, see additional guidance and examples in the [SDC implementation guide](http://hl7.org/fhir/uv/sdc/rendering.html#rendering-xhtml).; (xsd)expansion-xhtml:rendering-xhtml>?

🔗  A parameter that controlled the expansion process. These parameters may be used by users of expanded value sets to check whether the expansion is suitable for a particular purpose, or to pick the correct expansion. The server decides which parameters to include here, but at a minimum, the list SHOULD include all of the parameters that affect the $expand operation. If the expansion will be persisted all of these parameters SHALL be included. If the codeSystem on the server has a specified version then this version SHALL be provided as a parameter in the expansion (note that not all code systems have a version).sdc-valueset.expansion.parameter(xsd)=
	 <#base:ValueSet.expansion.parameter>
	 <  Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.; (xsd)id:string>?
	[]<  May be used to represent additional information that is not part of the basic definition of the element. 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 can 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.; (xsd)extension:Extension>*
	[]<  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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). 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.; (xsd)modifierExtension:Extension>*
	 <  Name of the input parameter to the $expand operation; may be a server-assigned name for additional default or other server-supplied parameters used to control the expansion process. The names are assigned at the discretion of the server.; (xsd)name:string>
	 ( <valueBoolean:boolean>
		 | <valueCode:code>
		 | <valueDateTime:dateTime>
		 | <valueDecimal:decimal>
		 | <valueInteger:integer>
		 | <valueString:string>
		 | <valueUri:uri>)?