SIMPLIFIER.NET - FHIRPath Playground

FHIRPath

If you Log in or sign up, you can edit this script yourself.

{
  "resourceType": "OperationDefinition",
  "id": "StructureDefinition-questionnaire",
  "meta": {
    "lastUpdated": "2017-04-18T21:44:43.294+00:00"
  },
  "text": {
    "status": "generated",
    "div": "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n            <h2>Build Questionnaire</h2>\n            <p>OPERATION: Build Questionnaire</p>\n            <p>The official URL for this operation definition is: </p>\n            <pre>http://hl7.org/fhir/OperationDefinition/StructureDefinition-questionnaire</pre>\n            <div>\n              <p>Generates a \n                <a href=\"questionnaire.html\">Questionnaire</a> instance  based on a specified \n                <a href=\"structuredefinition.html\">StructureDefinition</a>, creating questions for each core element or extension element found in the \n                <a href=\"structuredefinition.html\">StructureDefinition</a>.    If the operation is not called at the instance level, one of the \n                <em>identifier</em>, \n                <em>profile</em> or \n                <em>url</em> 'in' parameters must be provided. If more than one is specified, servers may raise an error or may resolve with the parameter of their choice. If called at the instance level, these parameters will be ignored. The response will contain a \n                <a href=\"questionnaire.html\">Questionnaire</a> instance based on the specified \n                <a href=\"structuredefinition.html\">StructureDefinition</a> and/or an \n                <a href=\"operationoutcome.html\">OperationOutcome</a> 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 &quot;must support&quot; 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 &quot;non-core&quot; resources with minimal development effort.\n              </p>\n\n            </div>\n            <p>URL: [base]/StructureDefinition/$questionnaire</p>\n            <p>URL: [base]/StructureDefinition/[id]/$questionnaire</p>\n            <p>Parameters</p>\n            <table class=\"grid\">\n              <tr>\n                <td>\n                  <b>Use</b>\n                </td>\n                <td>\n                  <b>Name</b>\n                </td>\n                <td>\n                  <b>Cardinality</b>\n                </td>\n                <td>\n                  <b>Type</b>\n                </td>\n                <td>\n                  <b>Binding</b>\n                </td>\n                <td>\n                  <b>Documentation</b>\n                </td>\n              </tr>\n              <tr>\n                <td>IN</td>\n                <td>identifier</td>\n                <td>0..1</td>\n                <td>uri</td>\n                <td/>\n                <td>\n                  <div>\n                    <p>A logical profile identifier (i.e. 'StructureDefinition.identifier''). The server must know the profile or be able to retrieve it from other known repositories.</p>\n\n                  </div>\n                </td>\n              </tr>\n              <tr>\n                <td>IN</td>\n                <td>profile</td>\n                <td>0..1</td>\n                <td>string</td>\n                <td/>\n                <td>\n                  <div>\n                    <p>The \n                      <a href=\"structuredefinition.html\">StructureDefinition</a> is provided directly as part of the request. Servers may choose not to accept profiles in this fashion\n                    </p>\n\n                  </div>\n                </td>\n              </tr>\n              <tr>\n                <td>IN</td>\n                <td>url</td>\n                <td>0..1</td>\n                <td>uri</td>\n                <td/>\n                <td>\n                  <div>\n                    <p>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.</p>\n\n                  </div>\n                </td>\n              </tr>\n              <tr>\n                <td>IN</td>\n                <td>supportedOnly</td>\n                <td>0..1</td>\n                <td>boolean</td>\n                <td/>\n                <td>\n                  <div>\n                    <p>If true, the questionnaire will only include those elements marked as &quot;mustSupport='true'&quot; in the StructureDefinition.</p>\n\n                  </div>\n                </td>\n              </tr>\n              <tr>\n                <td>OUT</td>\n                <td>return</td>\n                <td>1..1</td>\n                <td>Questionnaire</td>\n                <td/>\n                <td>\n                  <div>\n                    <p>The questionnaire form generated based on the StructureDefinition.</p>\n\n                  </div>\n                </td>\n              </tr>\n            </table>\n            <div>\n              <p>\n                <strong>Open Issue</strong>: Ideally, extensions should be populated in the generated \n                <a href=\"questionnaire.html\">Questionnaire</a> that will support taking \n                <a href=\"questionnaireresponse.html\">QuestionnaireResponse</a> resources generated from the Questionnaire and turning them back into the appropriate resources.\n              </p>\n\n            </div>\n          </div>"
  },
  "url": "http://hl7.org/fhir/OperationDefinition/StructureDefinition-questionnaire",
  "name": "Build Questionnaire",
  "status": "draft",
  "kind": "operation",
  "date": "2017-04-18T21:44:43+00:00",
  "publisher": "HL7 (FHIR Project)",
  "contact": [
    {
      "telecom": [
        {
          "system": "url",
          "value": "http://hl7.org/fhir"
        },
        {
          "system": "email",
          "value": "fhir@lists.hl7.org"
        }
      ]
    }
  ],
  "description": "Generates a [Questionnaire](questionnaire.html) instance  based on a specified [StructureDefinition](structuredefinition.html), creating questions for each core element or extension element found in the [StructureDefinition](structuredefinition.html).    If the operation is not called at the instance level, one of the *identifier*, *profile* or *url* 'in' parameters must be provided. If more than one is specified, servers may raise an error or may resolve with the parameter of their choice. If called at the instance level, these parameters will be ignored. The response will contain a [Questionnaire](questionnaire.html) instance based on the specified [StructureDefinition](structuredefinition.html) and/or an [OperationOutcome](operationoutcome.html) 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.",
  "code": "questionnaire",
  "comment": "**Open Issue**: Ideally, extensions should be populated in the generated [Questionnaire](questionnaire.html) that will support taking [QuestionnaireResponse](questionnaireresponse.html) resources generated from the Questionnaire and turning them back into the appropriate resources.",
  "resource": [
    "StructureDefinition"
  ],
  "system": false,
  "type": true,
  "instance": true,
  "parameter": [
    {
      "name": "identifier",
      "use": "in",
      "min": 0,
      "max": "1",
      "documentation": "A logical profile identifier (i.e. 'StructureDefinition.identifier''). The server must know the profile or be able to retrieve it from other known repositories.",
      "type": "uri"
    },
    {
      "name": "profile",
      "use": "in",
      "min": 0,
      "max": "1",
      "documentation": "The [StructureDefinition](structuredefinition.html) is provided directly as part of the request. Servers may choose not to accept profiles in this fashion",
      "type": "string",
      "searchType": "token"
    },
    {
      "name": "url",
      "use": "in",
      "min": 0,
      "max": "1",
      "documentation": "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.",
      "type": "uri"
    },
    {
      "name": "supportedOnly",
      "use": "in",
      "min": 0,
      "max": "1",
      "documentation": "If true, the questionnaire will only include those elements marked as \"mustSupport='true'\" in the StructureDefinition.",
      "type": "boolean"
    },
    {
      "name": "return",
      "use": "out",
      "min": 1,
      "max": "1",
      "documentation": "The questionnaire form generated based on the StructureDefinition.",
      "type": "Questionnaire"
    }
  ]
}

name : Build Questionnaire

{

}