SDC System for archiving and retrieving the completed forms

SDC Form authoring system

SDC System for completing forms

SDC Repository for forms

SDC Repository for completed forms

SDC Form response management system

Returns the next question or set of questions for an adaptive questionnaire

The $assemble operation takes a modular questionnaire (one that references sub-questionnaires and/or relies on definition elements to contain the content for item definitions) and produces the equivalent fully-inline Questionnaire. Full details on the process can be found here.

Generates an HTML representation of the Questionnaire as a form, possibly partially populated with data

Generates a QuestionnaireResponse from a Questionnaire, possibly with data partially populated

Generates a link to an HTML page that can be used to complete the Questionnaire, possibly partially populated with data

Allows submission of a QuestionnaireRespone for 'processing' by the target server

Converts a QuestionnaireResponse to a clinical or administrative resource or a Transaction Bundle of them

Allows searching by 'assembledFrom' extension on a Questionnaire

Allows searching by 'assemble-expectation' extension on a Questionnaire

Allows searching by 'definition' element within a Questionnaire's items

Data element SDC Profile Example

An example library of questions showing how questions can be compiled into a library for use by modular questionnaires

Complex definition-based extraction example

Complex StructureMap extraction questionnaire example

Complex template-based extraction example

Example Questionnaire demonstrating extraction using the template approach

Defines common elements for all SDC Questionnaires (regular or adaptive).

Defines common elements for all SDC Questionnaire Responses (regular or adaptive).

Defines the metadata that should be present when embedding a adaptive Questionnaire as part of a QuestionnaireResponse

Describes the elements that should be exposed in a response to a search for adaptive questionnaires.

Defines how the questionnaire response resource is used to reflect form data within the ONC's Structured Data Capture standard.

Defines additional capabilities for controlling data entry and calculating values within the questionnaire.

Defines additional capabilities for controlling the rendering of the questionnaire.

Defines elements that allow conversion of a QuestionnaireResponse to a FHIR resource or Bundle of FHIR resources using the Definition-based extraction mechanism

Defines elements that allow conversion of a QuestionnaireResponse to an Observation resource or Bundle of Observation resources using the Observation-based extraction mechanism

Defines elements that allow conversion of a QuestionnaireResponse to a FHIR resource or Bundle of FHIR resources using the StructureMap-based extraction mechanism

Defines elements that allow conversion of a QuestionnaireResponse to a FHIR resource or Bundle of FHIR resources using the Template-based extraction mechanism

Profile used to validate the parameters that are the input of the 'next question' adaptive questionnaire operation

Profile used to validate the parameters that are the output of the 'next question' adaptive questionnaire operation

Defines elements that support auto-population and pre-population of questionnaires using the Expression-based population mechanism

Defines elements that support auto-population and pre-population of questionnaires using the Observation-based population mechanism

Defines elements that support auto-population and pre-population of questionnaires using the StructureMap-based population mechanism

Profile used to validate the parameters that are the input of the $populate, $populate-html, and $populate-link questionnaire operations

Profile used to validate the parameters that are the output of the $populate questionnaire operation

Profile used to validate the parameters that are the output of the $populate-link questionnaire operation

Profile used to validate the parameters that are the output of the $populate-link questionnaire operation

Defines how ServiceRequest is used to ask for a Questionnaire to be completed

Profile used to validate the parameters that are the output of the 'assemble' questionnaire operation

Profile used to validate the parameters that are the input of the 'extract' questionnaire response operation

Profile used to validate the parameters that are the input of the 'process response' questionnaire operation

Sets minimum expectations for questionnaire support for SDC-conformant systems for 'standard' (non-adaptive) Questionnaires, regardless of which SDC capabilities they're making use of.

Defines how CodeSystem is used to reflect code lists found in data element defintions and form definitions to be used within the ONC's Structured Data Capture standard.

Defines how a Library is used as a logic computable library within the ONC's Structured Data Capture standard.

Indicates expectations for questionnaires that draw their item content (not just codes) from other resources

Defines how the questionnaire response resource is used to reflect form data within SDC for 'standard' (i.e. non-adaptive) forms.

Defines how ValueSet is used to reflect code lists found in data element defintions and form definitions to be used within the ONC's Structured Data Capture standard.

Describes the elements that should be exposed in a response to a search for questionnaires.

Defines how Task is used to ask for a Questionnaire to be completed

Constraints on the codes and values of UsageContext to help ensure consistent usage in SDC Questionnaires

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

An expression (FHIRPath, CQL or FHIR Query) that resolves to a list of permitted answers for a question item.

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.

This extension, used on a subQuestionnaire, indicates a FHIRPath variable that must be present in context when the subQuestionnaire is referenced.

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.

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

Calculated value for a question answer as determined by an evaluated expression

A FHIRPath or CQL Expression, or FHIR Query that resolves to a list of candidate answers (usually based on other answers in the questionnaire or based on information within the health record) for the question item or that establishes context for a group item

Provides guidelines for rendering multi-column choices

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 questionnaire-unit-open allows additional coded values.

Indicates that the child items of an item are displayed in collapsible form (either collapsed or expanded)

An expression that returns a boolean value for whether to enable the item

The base URL for the server(s) 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.

An indication of how the user should be prompted for answers when completing a QuestionnaireResponse

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 within that transaction bundle (via fhirpath expressions).

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.

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.

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. This extension is deprecated in favor of the DefinitionExtractExtension extension.

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)

Indicates the Observation.category value(s) that should appear on extracted Observations for the entire Questionnaire or for the current item and descendant items.

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.

Specifies a reference to a contained transaction bundle resource template to be extracted from this item once the QuestionnaireResponse is complete. The template will be cloned into the output extraction bundle, and any template values will be replaced with the values from the QuestionnaireResponse.

Establishes mapping context for replacing template content based on a fhirpath expression. This will be used by any child properties as the context for any other templateExtractContext or templateExtractValue extensions. If the name property on an expression is included, it will be also available to child extension evaluation. If the expression evaluates to no results, then this element in the templated resource will be removed, and futher processing of it's children is not required.

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.

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. The template will be cloned into the output extraction bundle, and any template values will be replaced with the values from the QuestionnaireResponse. Optionally the fullUrl and other Bundle.entry.request properties can be also included.

Initial value for a question answer as determined by an evaluated expression

If present and true, indicates that the item indicates a different subject for this group

If present and true, indicates that the item establishes a different subject for the group in a response

Media to render/make available as an accompaniment to a specific answer option.

Media to render/make available accompanying the question being asked or group or display item being rendered.

Specifies a query that identifies the resource (or set of resources for a repeating item) that should be used to populate this Questionnaire or Questionnaire.item on initial population.

For string or text items, indicates the 'keyboard type' that should be used by the user interface to guide entry. It does not dictate any specific functionality, it is only used as a hint to input devices that may have special keyboard modes available.

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.

Resources that provide context for form processing logic (pre-population, flow-control, drop-down selection, etc.) when creating/displaying/editing a QuestionnaireResponse

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. This can be direct (if the Reference is to a Questionnaire) or indirect via mapping if the Reference is to some other sort of resource.

The inclusive upper bound on the range of allowed values for a 'quantity' type question

The inclusive lower bound on the range of allowed values for a 'quantity' type question

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.

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 set to true, it means that the system displaying the form (or the individual encoding the form for data capture) can choose to omit the item from display to the user.

Indicates the types of resources that can record answers to a Questionnaire

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

Indicates if a questionnaire is adaptive - either set to true or set the base URL of the server that can perform the nextQuestion operation of the questionnaire

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.

Identifies a Questionnaire that is being asked to be completed

Provides a short text for an item. This element is useful for items that require a shorter text when rendered (e.g. when item is displayed on a mobile phone).

A Batch Bundle containing a set of queries that should be executed to provide source data for a StructureMap to create a populated QuestionnaireResponse

StructureMaps that produce QuestionnaireResponses for this Questionnaire as 'target' - i.e. that can be used to create QuestionnaireResponses that are valid against this Questionnaire.

Indicates that the display item on which this extension appears should be replaced with the referenced Questionnaire

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.

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.

An example value set (using fake codes) used by a modular Questionnaire

The list of mime types that identify mapping languages supported by DEX.

Defines the set of codes used to specify the relationship type for extracted Observations.

Defines codes describing how a Questionnaire relates to the 'assemble' process

Species for defining the context of Questionnaires

Defines mechanisms of capturing data in a QuestionnaireResponse

Defines mechanisms of displaying child items in collapsible form

For string or text items, indicates the 'keyboard type' that should be used by the user interface to guide entry.

The standard context for Questionnaire at launch time

List of resource types that can record answers to a Questionnaire.

Codes that describe the types of constraints possible on a question item that has a list of permitted answers [Note: This is a clone of QuestionnaireAnswerConstraint valueset from R5 (adopting R5 capability)]

The codes allowed for an SDC Task seeking completion of a Questionnaire

The answer list for question 1 on the AHRQ 'Medication or Other Substance' form

A set of codes that reflect the relevance of the Questionnaire to the $assemble operation - specifically, whether the form needs to be assembled, whether the form can be referenced as a subQuestionnaire and whether the form can be used as the 'root' of a QuestionnaireResponse.

Codes used in the congestive heart failure pathway. Ideally these shouldn't exist, but where I couldn't find an appropriate code in a standard terminology, I defined codes here.

Defines mechanisms of displaying child items in collapsible form

Defines mechanisms of capturing data in a QuestionnaireResponse

For string or text items, indicates the 'keyboard type' that should be used by the user interface to guide entry.

The standard context for Questionnaire at launch time

Defines the codes used to specify the relationship type in the ObservationExtractExtension.

Codes that describe the types of constraints possible on a question item that has a list of permitted answers [Note: This is a clone of QuestionnaireAnswerConstraint codesystem from R5 (adopting R5 capability)]

The answer list for questions 1 through 9 on the Patient Health Questionnaire (9 item) form

Defines codes defined within the SDC implementation guide that are expected to migrate elsewhere in future releases

An example of a StructureMap used to support extraction from a QuestionnaireResponse

An example of a StructureMap used to support population of a QuestionnaireResponse from a search bundle

A StructureMap instance that represents the resource that transforms a specific question and answer from the LOINC Hunger Vital Sign [HVS] questionnaire (LOINC code 88121-9) into a corresponding Observation (SDOHCC Observation response Hunger Vital Sign Q3 Example) and derived Condition (SDOHCC Condition Food Insecurity Example).

Logic for an example congestive heart failure pathway

Shows the result of performing a $assemble operation on the modular-root questionnaire

Shows the request payload when invoking a populate operation

Shows the response payload when invoking a populate operation

Shows the response payload when invoking a populate-html operation

Shows the response payload when invoking a populate-link operation

Example modular questionnaire - root of a questionnaire that references other questionnaires and element definitions

A sample Questionnaire that shows the use of the isSubject extension to flag a subject change within a Questionnaire.

Example questionnaire module - represents a patient's contacts and is itself a modular questionnaire that references other questionnaires and element definitions

Example questionnaire module - Used to represent a patient or other human name as an example of a Questionnaire that can be referenced by other Questionnaires. It is itself modular in that it relies on external element definitions

Example of a QuestionnaireResponse for a multi-subject Questionnaire

This is a Questionnaire example of how to expose an adaptive form in a registry.

A sample questionnaire using itemMedia and itemAnswerMedia extensions.

A sample questionnaire using context-based population and extraction

Shows a ServiceRequest soliciting completion of a questionnaire

Shows how completion of a questionnaire can be solicited with Task pointing to a ServiceRequest

Example of a child questionnaire based on a parent

Example of a parent questionnaire that sets derivation expectations

An example showing the result of a StructureMap-based population operation

An example of a Batch response containing search results used as an input to a map-based population process

A test form that has one of each data type included, useful in checking compatibility against.

A test form with a FHIRPath based prepopulation example that includes a candidate expression.

A test form that has a variety of enable when scenarios for testing.

A test form with a FHIRPath based prepopulation simple example.

A test form with that uses initial values.

A test form with a question that has multiple initial values.

A test form with repeatable nested groups.

A test form with required fields.

A test form with a FhirPath based prepopulation and StructureMap population that leverages a source query to extract data outside the launch context.

Demo questionnaire showing most of the advanced form behavior capabilities of SDC. Each example here is itemized in the Examples page.

Demo questionnaire showing most of the advanced rendering capabilities of SDC. Each example here is itemized in the Examples page.

Set of several examples - medication, AHRQ and NCI forms

Example to indicate the resources to make available for display to the user to aid in answering the question.

Example on how to use item weight and contraints in a Questionnaire.

Example questionnaire that shows how to display answer options as images using the rendering-xhtml extension.

A made-up form for calculating the 10-year-risk of Hard Coronary Heart Disease. It shows how variables and calculatedExpression can be used to compute for the risk probability.

A hunger vital signs form (showing calculatedExpression selecting a value from a list).

LOINC perspective on the AHRQ form found in the SDC - Combination set of questionnaires

LOINC US Surgeon General family history including data elements and value sets.

Patient Health Questionnaire (9 Item) including contained value sets and calculatedExpression

Patient Health Questionnaire using a cqf-expression defined in an SDC Library

Cancer pathology questionnaire with flow-control extensions

Example response to the Adaptive SDC-PHQ9 questionnaire

Example responses to the questionnaire found in the SDC - Combination list of questionnaires

Example response to te LOINC AHRQ questionnaire.

Example response to the SDC-LOINC USSG Family History questionnaire

Example response to the SDC-PHQ9 questionnaire

A weight and height panel (from LOINC) with a FHIRPath rule for calculating the BMI.

Example Questionnaire that shows both definition-based population and StructureMap-based extraction

Shows how completion of a questionnaire can be solicited with Task alone