This page is part of the FHIR Specification (v0.0.82: DSTU 1). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions
This is the narrative for the resource. See also the XML or JSON format.
(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 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.
FHIR Version: | 0.2 |
---|---|
Supported formats: | xml, json |
The Questionnaire and ValueSet 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 QuestionnaireAnswer resource is used to record the populated form.
Security:
Implementations must meet the general security requirements documented in the SDC implementation guide.
Resource | Search | Read | Read Version | Instance History | Resource History | Validate | Create | Update | Delete |
---|---|---|---|---|---|---|---|---|---|
Questionnaire | SHALL | SHOULD | MAY | MAY | |||||
ValueSet | SHALL | SHOULD | MAY | ||||||
QuestionnaireAnswers | SHALL | SHOULD | SHOULD | SHALL | SHALL | SHALL | |||
DocumentReference | SHOULD | ||||||||
Binary | SHOULD | MAY |
Operations: populateMAY
Name | Conformance | Description |
---|---|---|
search-type | SHOULD |
Allows discovery of existing documents that may be included in a form pre-population request |
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.