Structured Data Capture
3.0.0-preview - STU 3 International flag

This page is part of the Structured Data Capture FHIR IG (v3.0.0-preview: STU 3 Draft) based on FHIR R4. The current version which supercedes this version is 3.0.0. For a full list of available versions, see the Directory of published versions

CapabilityStatement: SDC Form Filler

Official URL: http://hl7.org/fhir/uv/sdc/CapabilityStatement/sdc-form-filler Version: 3.0.0-preview
Standards status: Trial-use Maturity Level: 3 Computable Name: SDCFormFiller

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

SDC Form Filler

(Requirements Definition Capability Statement)

Canonical URL: http://hl7.org/fhir/uv/sdc/CapabilityStatement/sdc-form-filler Published: 2014-07-06 (draft)

Published by: HL7 International - FHIR Infrastructure

This profile defines the expected capabilities of the SDC Form Filler role when conforming to the S&I Framework's 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 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).

General

FHIR Version: 1.0.0
Supported formats: xml, json

REST client behavior

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.

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 SDC implementation guide.

Resource summary

Resource Search Read Read Version Instance History Resource History Create Update Delete Operations
Questionnaire (Profile) SHALL SHOULD MAY MAY
ValueSet (Profile) SHALL SHOULD MAY
CodeSystem (Profile) SHALL SHOULD MAY
QuestionnaireResponse (Profile) SHALL SHALL SHOULD SHALL SHALL SHALL
DocumentReference SHOULD
Binary SHOULD MAY

Operations:



Questionnaire

Profile: http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaire

Interactions

Name Conformance Description
  search-type SHALL

Allows discovery of existing questionnaires to be completed
  read SHOULD

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

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

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


ValueSet

Profile: http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-valueset

Interactions

Name Conformance Description
  read SHALL

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

Allows retrieval of a specific version of a value set (as referenced in a Questionnaire)
  history-instance MAY

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


CodeSystem

Profile: http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-codesystem

Interactions

Name Conformance Description
  read SHALL

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

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

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


QuestionnaireResponse

Profile: http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaireresponse

Interactions

Name Conformance Description
  search-type SHALL

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

Allows retrieval of a specific QuestionnaireResponse by id.
  create SHALL

Allows recording a completed or partially-completed form
  update SHALL

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

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 SHOULD

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


DocumentReference

Interactions

Name Conformance Description
  search-type SHOULD

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


Binary

Interactions

Name Conformance Description
  read SHOULD

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

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.