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

Conformance-sdc-form-receiver

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

SDC Form Receiver

(Requirements Definition)

Published: 2014-07-06 (draft)

Published by: U.S. Office of the National Coordinator (ONC)

This profile defines the expected capabilities of the SDC Form Receiver role when conforming to the S&I Framework's Structured Data Capture FHIR implementation guide. This role is responsible for storing and returning completed and partially-completed forms.

General

FHIR Version: 0.2
Supported formats: xml, json

REST behavior

Security:

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

Summary

Resource Search Read Read Version Instance History Resource History Validate Create Update Delete
QuestionnaireAnswers Yes Yes Yes Yes Yes Yes


QuestionnaireAnswers

Interactions

Name Description
  search-type

Allows a user to search for existing completed or partially-completed forms. Generally used to find partially-completed forms for update.
  create

Allows recording a completed or partially-completed form
  update

Allows updating an existing completed or partially-completed form. (Systems may place rules on who can update forms and under what circumstances.)
  delete

Allows removal of a completed form from a repository. Note that the removal may be logical rather than physical. Some systems may have rules for who can remove a completed form and under what circumstances.
  history-instance

Allows review of prior versions of an answer set - allows reversion to previously recorded versions
  validate

Allows checking an answer set for validity against submission rules without persisting any data

Search

Supported Includes: QuestionnaireAnswers.questionnaire Questionnaire.group.question.options

Parameter Type Definition & Chaining
author token
authored date
questionnaire token
status token
subject token
encounter token

 

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.