 |
Page History
...
Enable Better Discovery: Complex search offers a natural and user-friendly way to find services by progressively refining search results using a variety of criteria including attributes, artifacts, classification, usage scenarios, and dependencies. This includes runtime contract discovery, a powerful query mechanism that allows either the service orchestrator or a program to find the services that best fit the requirements of a given process. This increases both runtime and design time flexibility by enabling selection of services based on computable metadata.
_The requirements listed above are derived from the following use cases in the previous section: _
caEHR: The caEHR project is developing service specifications and lacks the infrastructure to govern these services. Vendors and external implementations are expected to leverage the caEHR service specifications and there is currently no infrastructure that allows easy discovery and consumption of this information.
...
Other National Initiatives: All EHR vendors and national initiatives rely on a services paradigm for integration and interoperability. A standardized services metamodel makes it easier for participating organization to discover and reuse services.
caGRID 2.0 Platform: * The caGRID 2.0 Platform provides a runtime registry for service discovery. This service registry relies on a small subset of information for discovery. The semantic infrastructure provides a mechanism to leverage rich service and artifact metadata to extend this capability.
...
Case Report Forms are the primarily primary channel for capturing information in the healthcare and clinical domain. Forms also play a key role in information exchange and are critical to supporting interoperability in healthcare.
A form differs from a document; , in that a document is used to capture information. A , while a form defines skip patterns, validation rules, and any other aspect aspects required to capture or render or capture information for a document.
A document in this context 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 a document. Documents can be transformed into human readable forms, and be transferred , or transmitted for use across different systems.
Based on the use - cases the key forms requirements include:
- Tools and Services services for defining form templates
- Ability to leverage models and reusable segments for defining these forms
- User friendly tools that hide the complexity of the underlying semantics
...
Services specifications developed by NCI and the community have to be testable to ensure that the implementation is conformant with conforms to 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 in the specification (design time) and validate that this response time is valid for an implementation of the service, additional . Aadditional test points include but are not limited to binding to specific terminologies , and domain models, etc.
Conformance testing allows both CBIIT and other HL7 SAIF adopters to validate specifications.
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, the conformance testing framework leverages these conformance statements to generate validation tests.
Other National Initiatives: Other national organizations like NIST are adopting a similar approach to conformance testing.
caGRID 2.0 Platform and Terminology Integration
...
