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
| Official URL: http://hl7.org/fhir/uv/sdc/CapabilityStatement/sdc-form-archiver | Version: 4.0.0 | |||
| Standards status: Trial-use Active as of 2015-09-03 | Maturity Level: 4 | Computable Name: SDCFormArchiver | ||
| Other Identifiers: OID:2.16.840.1.113883.4.642.40.17.13.1 | ||||
This profile defines the expected capabilities of the SDC Form Archiver role when conforming to this implementation guide. This role is responsible for persisting (archiving) completed or partially completed forms QuestionnaireResponse resource instances). These instances may be submitted individually or in a bundle together with Provenance information providing details about the completion of the questionnaire response. In some cases Binary or DocumentReference resources might also be submitted to convey source information used in the population of the questionnaire response. &$xa;The purpose of this role is to capture "work in progress" for archival reasons. There is no expectation that submitted form data is subsequently made available for retrieval (at least not in the same format), though it might be made available through out-of-band mechanisms.
Raw OpenAPI-Swagger Definition file | Download
xml, jsonNote 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.
clientThe QuestionnaireResponse may be sent as a single instance or as a FHIR Bundle also containing Provenance resources providing details on the sources of information. A Bundle submission might also include Binary and/or DocumentReference instances referring to the data used to populate the form. A Form Archiver must support persisting, searching and retrieving those resources.
Implementations must meet the general security requirements documented in this implementation guide.html.
transactioninteraction described as follows:Allows submission of a QuestionnaireResponse together with Provenance and other supporting resources as a single unit of work.
The summary table lists the resources that are part of this configuration, and for each resource it lists:
_include_revinclude| Resource Type | Profile | R | S | U | C | D | Searches | _include | _revinclude | Operations |
|---|---|---|---|---|---|---|---|---|---|---|
| QuestionnaireResponse | http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaireresponse | Y | Y | y? | ||||||
| Provenance | http://hl7.org/fhir/StructureDefinition/Provenance | Y |
createAllows archiving (storing) a completed or partially-completed form
updateAllows updating a previously archived form. (Systems may place rules on who can update forms and under what circumstances).
deleteAllows removal of an archived form from a repository. Note that the removal may be logical rather than physical. Some systems may have rules for who can remove a submitted response and under what circumstances.
The primary focus of a form archiver is storing QuestionnaireResponses.
createAllows submitting a Provenance record associated with a particular QuestionnaireResponse.
Captures metadata about the creation/changing of QuestionnaireResponses.