SDC Form authoring system

SDC Form response management system

SDC System for completing forms

SDC Repository for forms

SDC Repository for completed forms

SDC System for archiving and retrieving the completed forms

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

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

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

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

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.

Allows searching by ‘definition’ element within a Questionnaire’s items

Allows searching by ‘assembledFrom’ extension on a Questionnaire

Allows searching by ‘assemble-expectation’ extension on a Questionnaire

Data element SDC Profile Example

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

Sets expectations for SDC-conformant systems around how to create questionnaires

Defines properties that must be supported for systems that support searching for and returning Questionnaires

Defines additional capabilities for controlling the rendering of the questionnaire.

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

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 Expression-based population mechanism.

Defines elements that support auto-population and pre-population of questionnaires using the StructureMap-based population 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 Definition-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 the metadata that should be present to embedding an adaptive Questionnaire as part of a QuestionnaireResponse

Defines the metadata that should be present to support searching for adaptive questionnaires.

Sets expectations for SDC-conformant systems around how to create responses to questionnaires.

Represents a response to a questionnaire that is dynamically built as each question is answered.

Sets expectations for SDC-conformant systems around the definition of value sets for use with questionnaires.

Sets expectations for SDC-conformant systems around the definition of code systems to provide values for choices within questionnaires.

Sets expectations for SDC-conformant systems around the definition of libraries to provide logical expressions within questionnaires.

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 input of the ‘extract’ questionnaire operation

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

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

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

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

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

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

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

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

The base URL for the server to which questionnaire response associated with this questionnaire should be submitted

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

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

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

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

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

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.

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

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.

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

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

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

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.

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

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

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.

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

Provides guidelines for rendering multi-column choices

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

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.

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

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

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

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.

Specifies a query that identifies the resource (or set of resources for a repeating item) to be extracted from this item once the QuestionnaireResponse is complete.

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 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 produce QuestionnaireResponses for this Questionnaire as ‘target’ - i.e. that can be used to create QuestionnaireResponses that are valid against this Questionnaire.

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.

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

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

Identifies a Questionnaire that is being asked to be completed

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.

Indicates a variable that must be available on any node that is referencing the Questionnaire as a sub-questionnaire

This indicates that the element containing this extension has some sort of expression that makes reference to the specified contained resource.

Indicates the Questionnaire a variable that must be available on any node that is referencing the Questionnaire as a sub-questionnaire

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

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

Species for defining the context of Questionnaires

Defines standard context of Questionnaires at launch time

Defines mechanisms of capturing data in a QuestionnaireResponse

Defines mechanisms of displaying child items in collapsible form

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

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

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

Defines codes describing how a Questionnaire relates to the ‘assemble’ process

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

Defines standard context of Questionnaires at launch time

Defines mechanisms of capturing data in a QuestionnaireResponse

Defines mechanisms of displaying child items in collapsible form

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.

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

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

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.

A map that converts an SDOCC hunger vital sign questionnaire to a Bundle of Conditions and Observations

Set of several examples - medication, AHRQ and NCI forms

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

Cancer pathology questionnaire with flow-control extensions

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

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

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

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

A sample questionnaire using itemMedia and itemAnswerMedia extensions.

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

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

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

Example on how to use ordinal value and contraints in a Questionnaire.

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

A test form with repeatable nested groups.

A test form with required fields.

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

A sample questionnaire using context-based population and extraction

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

A test form with a FHIRPath based prepopulation simple example.

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

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

A test form with that uses initial values.

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

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

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

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

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

An example of a StructureMap used to support the population of a QuestionnaireResponse from queried data

Example response to the SDC-LOINC USSG Family History questionnaire

Example response to the SDC-PHQ9 questionnaire

Example response to te LOINC AHRQ questionnaire.

Example of a QuestionnaireResponse for a multi-subject Questionnaire

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

Example response to the Adaptive SDC-PHQ9 questionnaire

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

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

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

Logic for an example congestive heart failure pathway

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

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

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

Shows a ServiceRequest soliciting completion of a questionnaire

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

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

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