Generated Narrative: CapabilityStatement sdc-form-fill-manager SDC Form Fill Manager Implementation Guide Version: 4.0.0 FHIR Version: 4.0.1 Supported Formats: xml, json 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: server The primary focus of the repository is providing access to Questionnaires. However, ValueSets, CodeSystems, Librarys, ConceptMaps and other resources are also relevant in their support of Questionnaire functionality. Some forms will opt to have some or all of these additional resources managed as 'contained' resources, meaning there won't be a need for them to be independently managed on the Form Fill Manager. However, systems should support resource re-use across forms, meaning that support for maintenance of these ancillary resources is still helpful. (Version-specific referencing can be used to avoid referenced resources from changing independent of the referencing Questionnaire.) Security Implementations must meet the general security requirements documented in this implementation guide.html. 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 Type Profile R S U C Searches _include _revinclude Operations Questionnaire http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaire Y Y url, version, status, experimental, context-type-quantity, context-type-value, date, description, identifier, publisher, questionnaire-code, subject-type, title, effective, jurisdiction, assemble-expectation $next-question, $populate ValueSet http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-valueset y? Y url, version $expand, $validate code CodeSystem http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-codesystem Y Y url, version Library http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-library y? Y url, version StructureMap http://hl7.org/fhir/StructureDefinition/StructureMap y? Y url, version StructureDefinition http://hl7.org/fhir/StructureDefinition/StructureDefinition y? Y url, version ConceptMap http://hl7.org/fhir/StructureDefinition/ConceptMap y? Y experimental, url, version, status, source-system, target-system, source-uri, target-uri Resource Conformance: SHALL Questionnaire Base System Profile SDC Base Questionnaire Profile Conformance SHALL Reference Policy Interaction summary SHALL support search-type Allows a user to search for existing forms read Allows retrieval of a detailed Questionnaire if search only returns summary Documentation Form mamagers are responsible for handling forms. Search Parameters Conformance Parameter Type Documentation SHALL url uri SHALL version token SHALL status token SHALL experimental token SHOULD context-type-quantity composite SHOULD context-type-value composite SHOULD date date SHOULD description string SHOULD identifier token SHOULD publisher string SHOULD questionnaire-code token SHOULD subject-type token SHOULD title string SHOULD effective date MAY jurisdiction token MAY assemble-expectation token Extended Operations Conformance Operation Documentation SHOULD $next-question Needed for adaptive forms MAY $populate Usefulness depends on whether fillers tend to perform population themselves Resource Conformance: SHALL ValueSet Base System Profile SDC Value Set Profile Conformance SHALL Reference Policy Interaction summary SHALL support search-type Allows discovery of existing value sets for use in authoring questionnaires MAY support read Needed if a server's default search behavior doesn't return the full resource Documentation Needed if Questionnaire valuesets will be stored on the form server as opposed to a separate terminology service. Search Parameters Conformance Parameter Type Documentation SHALL url uri SHALL version token Extended Operations Conformance Operation Documentation SHOULD $expand Needed if expansion isn't handled locally or via independent terminology servers SHOULD $validate code Needed if expansion isn't handled locally or via independent terminology servers Resource Conformance: SHOULD CodeSystem Base System Profile SDC Code System Profile Conformance SHALL Reference Policy Interaction summary SHALL support search-type Allows discovery of existing code systems for use in authoring questionnaires read Allows retrieval of a specific code system referenced within a questionnaire Documentation Needed if Questionnaire codes will be stored on the form server as opposed to a separate terminology service. Search Parameters Conformance Parameter Type Documentation SHALL url uri SHALL version token Resource Conformance: SHOULD Library Base System Profile SDC Library Profile Conformance SHALL Reference Policy Interaction summary SHALL support search-type Needed to retrieve library based on canonical reference MAY support read Useful if a server doesn't return full data in a search Documentation Needed for certain types of population and extraction Search Parameters Conformance Parameter Type Documentation SHALL url uri SHALL version token Resource Conformance: MAY StructureMap Base System Profile StructureMap Profile Conformance SHALL Reference Policy Interaction summary SHALL support search-type Needed to retrieve structure map based on canonical reference MAY support read Useful if a server doesn't return full data in a search Documentation Needed if performing map-based population or extraction Search Parameters Conformance Parameter Type Documentation SHALL url uri SHALL version token Resource Conformance: MAY StructureDefinition Base System Profile StructureDefinition Profile Conformance SHALL Reference Policy Interaction summary SHALL support search-type Needed to retrieve structure definition based on canonical reference MAY support read Useful if a server doesn't return full data in a search Documentation Needed if performing map-based population or map or definition-based extraction Search Parameters Conformance Parameter Type Documentation SHALL url uri SHALL version token Resource Conformance: MAY ConceptMap Base System Profile ConceptMap Profile Conformance SHALL Reference Policy Interaction summary SHALL support search-type Needed to retrieve concept map based on various criteria MAY support read Useful if a server doesn't return full data in a search Documentation May be needed for code conversion during population or extraction Search Parameters Conformance Parameter Type Documentation SHALL experimental token SHALL url uri SHALL version token SHALL status token SHALL source-system uri SHALL target-system uri SHOULD source-uri reference SHOULD target-uri reference
This profile defines the expected capabilities of the *SDC Form Fill Manager* role when conforming to this implementation guide. This role is responsible for maintaining a repository of form definitions for retrieval by form fillers possibly also supporting pre-population of form data.
The primary focus of the repository is providing access to [Questionnaire]s. However, [ValueSet]s, [CodeSystem]s, [Library]s, [ConceptMap]s and other resources are also relevant in their support of Questionnaire functionality. Some forms will opt to have some or all of these additional resources managed as 'contained' resources, meaning there won't be a need for them to be independently managed on the Form Fill Manager. However, systems should support resource re-use across forms, meaning that support for maintenance of these ancillary resources is still helpful. (Version-specific referencing can be used to avoid referenced resources from changing independent of the referencing [Questionnaire].)
Implementations must meet the [general security requirements](security.html) documented in this implementation guide.html.
Form mamagers are responsible for handling forms.
Allows a user to search for existing forms
Allows retrieval of a detailed Questionnaire if search only returns summary
Usefulness depends on whether fillers tend to perform population themselves
Needed if Questionnaire valuesets will be stored on the form server as opposed to a separate terminology service.
Allows discovery of existing value sets for use in authoring questionnaires
Needed if a server's default search behavior doesn't return the full resource
Needed if expansion isn't handled locally or via independent terminology servers
Needed if Questionnaire codes will be stored on the form server as opposed to a separate terminology service.
Allows discovery of existing code systems for use in authoring questionnaires
Allows retrieval of a specific code system referenced within a questionnaire
Needed for certain types of population and extraction
Useful if a server doesn't return full data in a search
Needed to retrieve library based on canonical reference
Needed if performing map-based population or extraction
Needed to retrieve structure map based on canonical reference
Needed if performing map-based population or map or definition-based extraction
Needed to retrieve structure definition based on canonical reference
May be needed for code conversion during population or extraction
Needed to retrieve concept map based on various criteria