2nd DSTU Draft For Comment

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

Operation-structuredefinition-questionnaire

This is the narrative for the resource. See also the XML or JSON format.

Build Questionnaire

OPERATION: Build Questionnaire

Generates a Questionnaire instance based on a specified Profile, creating questions for each core element or extension element found in the StructureDefinition.

If the operation is not called at the instance level, one of the identifier, profile or url 'in' parameters must be provided. (If called at the instance level, these parameters will be ignored. If more than one is specified, servers may raise an error or may resolve with the parameter of their choice.)

The response will contain a Questionnaire instance based on the specified Profile and/or an OperationOutcome resource with errors or warnings.

Nested groups are used to handle complex structures and data types. If the 'supportedOnly' parameter is set to true, only those elements marked as "must support" will be included.

This operation is intended to enable auto-generation of simple interfaces for arbitrary profiles. The 'questionnaire' approach to data entry has limitations that will make it less optimal than custom-defined interfaces. However, this function may be useful for simple applications or for systems that wish to support "non-core" resources with minimal development effort.

URL: [base]/StructureDefinition/$Build Questionnaire

URL: [base]/StructureDefinition/[id]/$Build Questionnaire

Parameters

UseNameCardinalityTypeDocumentation
INidentifier0..1uri

A logical profile identifier (i.e. 'StructureDefinition.identifier''). The server must know the profile or be able to retrieve it from other known repositories.

INprofile0..1token

The Profile is provided directly as part of the request. Servers may choose not to accept profiles in this fashion

INurl0..1uri

The profile's official url (i.e. 'StructureDefinition.url'). The server must know the profile or be able to retrieve it from other known repositories.

INsupportedOnly0..1boolean

If true, the questionnaire will only include those elements marked as "mustSupport='true'" in the StructureDefinition.

OUTreturn1..1Questionnaire

The questionnaire form generated based on the StructureDefinition.

Open Issue: Ideally, extensions should be populated in the generated Questionnaire that will support taking QuestionnaireAnswers resources generated from the Questionnaire and turning them back into the appropriate resources.

 

Usage note: every effort has been made to ensure that the examples are correct and useful, but they are not a normative part of the specification.