Page History

{scrollbar:icons=false}

h4. {page-info:title}

h5. Summary

h6. Description of the profile

Form Templates

Tools and services for defining form templates.  Includes capabilities for
* Leveraging models and reusable segments
* Hiding complexity of underlying semantics


h6. Capabilities


* [formLibrary|#EAID_0D52C80D_A20A_4090_9929_3458F8909226]

h5. Requirements traceability

|| Requirement || Source || Capability ||
| Support Reusable Modules / Sections of Forms | Gap Analysis::Interface::{anchor:_16_5_1_24a0131_1283084945250_557951_4311}150 - Reusable Modules and Sections of Forms | [formLibrary|#EAID_0D52C80D_A20A_4090_9929_3458F8909226], |
| Artifact lifecycle management and metadata requirements include the ability to:       * Manage lifecycle, governance and versioning of the models, content and forms      * Establish relationships and dependencies between models, content and forms          * Determine provenance, jurisdiction, authority and intellectual property          * Create represention and views of the information, realized through the appropriate transforms          * Provide access control and other security constraints          * Create annotations for better discovery and searching of artifacts          * Develop usage scenarios and context for the information          * Provide terminology and value set binding  The artifacts are bound to the services via the service metadata. The service metadata combined with the artifacts and supporting metadata provide a comprehensive service specification.    The artifact management requirements listed above are derived from the following use cases:   * _caEHR_: The caEHR project has adopted ECCF for specifications and CDA documents for interoperability. The caEHR project requirements include the need for an infrastructure for managing all the artifacts generated during specification process, including HL7 models and documents. The caEHR project also intends to publish these artifacts for the community and vendors. The infrastructure needs to support better discovery, making all the relevant information available in the right context.   * _ONC and other external EHR adopters_: ONC has adopted CCD and CCR for meaningful use. All national EHR implementations are expected to support forms and the semantics of these forms play a critical role in interoperability. The semantic infrastructure must provide a mechanism to create, store and manage these forms.   * _Clinical Trials_: Clinical trials use forms to capture clinical information, and the semantics captured by these forms are critical for interoperability and reporting. The semantic infrastructure must provide a mechanism to manage the lifecycle of these forms. | Semantic Infrastructure Requirements::Artifact Management::{anchor:_16_5_1_24a0131_1283090023842_213150_4485}Artifact Lifecycle Management | [formLibrary|#EAID_0D52C80D_A20A_4090_9929_3458F8909226], |


h5. {anchor:EAID_0D52C80D_A20A_4090_9929_3458F8909226}formLibrary


h6. Description

Support Reusable Modules / Sections of Forms

h6. Requirements addressed

* [150 - Reusable Modules and Sections of Forms|#_16_5_1_24a0131_1283084945250_557951_4311]
* [Artifact Lifecycle Management|#_16_5_1_24a0131_1283090023842_213150_4485]

h6. Overview of possible operations

To be provided.

{scrollbar:icons=false}