NIH | National Cancer Institute | NCI Wiki  

Error rendering macro 'rw-search'

null

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin
Wiki Markup
{scrollbar:icons=false}

Page info
title
title

Summary
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
Capabilities
Requirements traceability

Requirement

Source

Capability

Support Reusable Modules / Sections of Forms

Gap Analysis::Interface::

Anchor
_16_5_1_24a0131_1283084945250_557951_4311
_16_5_1_24a0131_1283084945250_557951_4311
150 - Reusable Modules and Sections of Forms

formLibrary,

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
_16_5_1_24a0131_1283090023842_213150_4485
Artifact Lifecycle Management

formLibrary,

Anchor
EAID_0D52C80D_A20A_4090_9929_3458F8909226
EAID_0D52C80D_A20A_4090_9929_3458F8909226
formLibrary
Description

Support Reusable Modules / Sections of Forms

Requirements addressed
Overview of possible operations

To be provided.

Wiki Markup
{scrollbar:icons=false}