Page History

...

Link to use case: the services may be located at an institution or hosted externally by service providers.

...

Forms Definition & Modeling

Forms  Case Report Forms are the primarily channel for capturing information in healthcare and clinical domain. Forms also play a key role in information exchange and are critical to supporting interoperability in healthcare.

A form by contrast to a Document is a construct which differs from a document, a document is used to capture the captures information in the document.  A  A form defines skip patterns, validation rules, and any other aspect required to render or capture information for a document

A document is specifically a clinical document which represents information about a clinical activity.  The document contains the specific information gained during that clinical activity and supports the broader definitions of Document and Clinical Documentation.  This includes the ability to a document.  Documents can be transformed into human readable formforms, and be transferred, or transmitted for use 

This is a transactional database that contains the component definitions of the documentation process.  This includes the core form definitions which will be represented using XML.

This data will likely contain a number of different components, however, the primary elements will focus on two structures.  One is the form definition that contains the layout and definition with rules for validation, bindings to pick lists, and skip patterns.  The second  is the schema definition that is required to capture and represent the data

Conformance Testing

Human semantics include metadata about a service that is meant to be displayed via a user interface, for example, a description of the operations defined on a service. Computable semantics are metadata that are added to a service primarily in order to facilitate service orchestration and choreography, and to specify precisely the semantic meaning of data in order to allow interpretation and reasoning. Services in the ecosystem must have both types of metadata in order to facilitate tools for the platform and enable working interoperability.

...

use across different systems.

Based on the use-cases the key forms requirements include:

• Tools and Services for defining form templates
• Ability to leverage models and reusable components for defining the forms
• User friendly modeling tools that support rich semantics 

The requirements listed above are derived from the following use cases in the previous section:

• caEHR
• ONC and Other external EHR adopters
• Clinical Trails
  

Conformance Testing

Services specifications developed by NCI and the community have to be testable to ensure that the implementation is conformant with the specification.

Conformance Testing leverages the artifact and service metadata to validate that an implementation adequately addresses the requirements stated in the service specification. An example of service requirement is the ability to specify a response time during design time and validate that this response time is valid for an implementation of the service, additional test points include binding to specific terminologies, domain models, etc.

Conformance testing ensures interoperability by ensuring that

The requirements listed above are derived from the following use cases in the previous section:

• CBIIT's adoption of ECCF: ECCF requires all specification developers to make conformance statements, this also provides a mechanism for external validators to
  

Service Generation

Service Discovery & Utilization

...