Structured Data Capture
4.0.0 - STU 4 International flag

Structured Data Capture, published by HL7 International / FHIR Infrastructure. This guide is not an authorized publication; it is the continuous build for version 4.0.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/sdc/ and changes regularly. See the Directory of published versions

CapabilityStatement: SDC Form Receiver

Official URL: http://hl7.org/fhir/uv/sdc/CapabilityStatement/sdc-form-receiver Version: 4.0.0
Standards status: Trial-use Maturity Level: 4 Computable Name: SDCFormReceiver
Other Identifiers: OID:2.16.840.1.113883.4.642.40.17.13.5

This profile defines the expected capabilities of the SDC Form Receiver role when conforming to implementation guide. This role is responsible for accepting and processing completed and partially-completed forms. It only exposes a single operation endpoint - the one needed to 'process' a completed QuestionnaireResponse

Raw OpenAPI-Swagger Definition file | Download

SDC Form Receiver

  • Implementation Guide Version: 4.0.0
  • FHIR Version: 4.0.1
  • Supported Formats: xml, json
  • Published on: 2014-07-06
  • Published by: HL7 International / FHIR Infrastructure

Note to Implementers: FHIR Capabilities

Any FHIR capability may be 'allowed' by the system unless explicitly marked as 'SHALL NOT'. A few items are marked as MAY in the Implementation Guide to highlight their potential relevance to the use case.

FHIR RESTful Capabilities

REST Configuration: 1

Mode: server

Security

Implementations must meet the general security requirements documented in this implementation guide.html.

Summary of System-wide Operations
ConformanceOperationDocumentation
SHALL$process-response

Allows submitting a completed form

REST Configuration: 2

Mode: client

Capabilities by Resource/Profile

Summary

The summary table lists the resources that are part of this configuration, and for each resource it lists:

  • The relevant profiles (if any)
  • The interactions supported by each resource (Read, Search, Update, and Create, are always shown, while VRead, Patch, Delete, History on Instance, or History on Type are only present if at least one of the resources has support for them.
  • The required, recommended, and some optional search parameters (if any).
  • The linked resources enabled for _include
  • The other resources enabled for _revinclude
  • The operations on the resource (if any)
Resource TypeProfileRSUCSearches_include_revincludeOperations
QuestionnaireResponsehttp://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaireresponse$extract

Resource Conformance: MAY QuestionnaireResponse
Profile Conformance
SHALL
Reference Policy

Interaction summary

    Documentation

    Perform operations based on the received response

    Extended Operations
    ConformanceOperationDocumentation
    MAY$extract

    Convert completed form to resources