Structured Data Capture
4.0.0-ballot - STU 4 ballot 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-ballot 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 Filler

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

This profile defines the expected capabilities of the ''SDC Form Filler'' role when conforming to the S&I Framework's [[index.html Structured Data Capture FHIR implementation guide]]. This role is responsible for retrieving pre-defined forms, requesting pre-population of forms and/or auto-populating forms, guiding the user through verifying populated data and submitting completed or partially-completed forms.
Note that Form Fillers may also take on the role of [[CapabilityStatement-sdc-form-archiver.html
Form Archiver]] if they have a requirement to retain the completed version of a form (and potentially the source data that was used to complete it).

Raw OpenAPI-Swagger Definition file | Download

Generated Narrative: CapabilityStatement sdc-form-filler

SDC Form Filler

  • Implementation Guide Version: 4.0.0-ballot
  • FHIR Version: 1.0.0
  • Supported Formats: xml, json
  • Supported Patch Formats:
  • 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

Mode: client

The [[Questionnaire]], [[ValueSet]] and [[CodeSystem]] resources are retrieved to allow the system to guide the user through the entry process. The [[Binary]] and [[DocumentReference]] resources allow the system to find existing clinical documents that can be within the pre-population process. (Support for retrieval operations on these resources is optional as the relevant CDA or FHIR structures may also be directly generated by the ''Form Filler'' itself.) Finally, the [[QuestionnaireResponse]] resource is used to record the populated form.<br/>Note: Form Fillers that support the 'populate' operation will need to be capable of consuming and rendering a partially completed QuestionnaireResponse in the same manner as if they had retrieved such a QuestionnaireResponse from a ''Form Response Manager''

Security

Implementations must meet the general security requirements documented in the [[security.html|SDC implementation guide]].

Summary of System-wide Interactions

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 Conformance: SHALL Questionnaire

Base System Profile
SDC Base Questionnaire
Profile Conformance
SHALL
Reference Policy

Interaction summary
  • SHALL support
    search-type

    Allows discovery of existing questionnaires to be completed

  • SHOULD support
    read

    Allows retrieval of a specific questionnaire by id. Allows systems to maintain a 'favorites' list of forms and retrieve them by id.

  • MAY support
    history-instance

    Allows review of changes made to a questionnaire over time. Of interest to some systems, but probably not most.

    vread

    Allows retrieval of a historical version of a questionnaire. Most systems will make use of the current version only.

Resource Conformance: SHALL ValueSet

Base System Profile
SDC Value Set
Profile Conformance
SHALL
Reference Policy

Interaction summary
  • SHALL support
    read

    Allows retrieval of a specific value set by id (as referenced in a Questionnaire)

  • SHOULD support
    vread

    Allows retrieval of a specific version of a value set (as referenced in a Questionnaire)

  • MAY support
    history-instance

    Allows review of changes to a value set over time. Of interest to some systems, but probably not most.

Resource Conformance: SHALL CodeSystem

Base System Profile
SDC Code System
Profile Conformance
SHALL
Reference Policy

Interaction summary
  • SHALL support
    read

    Allows retrieval of a specific code system by id (as referenced by a ValueSet used in a Questionnaire)

  • SHOULD support
    vread

    Allows retrieval of a specific version of a code system (as referenced by a ValueSet used in a Questionnaire)

  • MAY support
    history-instance

    Allows review of changes to a code system over time. Of interest to some systems, but probably not most.

Resource Conformance: SHALL QuestionnaireResponse

Profile Conformance
SHALL
Reference Policy

Interaction summary
  • SHALL support
    search-type

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

    read

    Allows retrieval of a specific QuestionnaireResponse by id.

    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.

  • SHOULD support
    history-instance

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

Resource Conformance: SHOULD DocumentReference

Core FHIR Resource
DocumentReference
Reference Policy
Interaction summary
  • SHOULD support
    search-type

    Allows discovery of existing documents that may be included in a form pre-population request

Resource Conformance: SHOULD Binary

Core FHIR Resource
Binary
Reference Policy
Interaction summary
  • SHOULD support
    read

    Allows retrieval of a specific binary (as pointed to by a DocumentReference)

  • MAY support
    vread

    Allows retrieval of a historical version of a binary. In general, the most recent version would be appropriate, but some may prefer to use the specific version referenced by a DocumentReference.

Operations

Use