Page History

...

• Semantic Infrastructure Users and Roles
• Functional Requirements
  • Artifact Management
    • Static Models
    • Behavioral Models
    • Forms
    • Specification Content
  • Services Lifecycle Management Service Discovery & Governance
    • Discovery
    • Lifecycle Management
    • Governance
  • Case Report Form Modeling
    • Form template authoring
  • Conformance Testing
  • P/S/T & Terminology Integration
    

...

This section includes:

• Artifact Management
• Service Lifecycle Management Service Discovery and Governance
• Forms Defintion & Modeling
• Conformance Testing
• P/S/T & Terminology Integration

...

Establish Service policies: Access control, the visibility and access to service metadata for sharing and reuse by using role-based access. Using the access-control editor, you can easily set up access-control rules that align with your business. Better policy management with WebSphere Service Registry and Repository lets you track and govern your run-time policies while establishing contractual and enforceable relationships between various run-time policies and associated servicesService policies help establish constraints on the service specifications and mandate an approach. Policies can be specified around governance, access control and other design/runtime constraints.

Governance: This includes predefined templates, workflows, and governance policies for governing the service lifecycle. ThAn approval and review process for service specifications and the ability to promote services through the stages of the service lifecycle

Better Discovery: Complex search that offers a natural and Better Discovery: Complex search that 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. The service lifecycleVendors and external implementators are expected to leverage the caEHR service specifications and there is currently no infrastructure that allows easy discovery and consumption of this information.

CBIIT Projects: CBIIT has adopted SOA. Service lifecycle management and governance are industry best practices for all organizations adopting SOA. Better service discovery and reuse improves productivity, avoids redundancy and makes it easier for the CBIIT enteprise architecture governance team to manage NCI's enterprise service services portfolio:

Life Sciences: Service discovery based on a rich metadata and semantics of the underlying data play a critical role in developing research pipelines. Reseach pipeline are developed by stringing services together to achieve a research objective. Example, ..

Other National Initiatives: All EHR vendors and national initiatives rely on a services paradigm for integration and interoperability. A standadized services metamodel makes it easier for participating organization to discover and reuse services.Other National Initiatives:

caGRID 2.0 P/S/T: The caGRID 2.0 P/S/T T provides a runtime registry for service discovery. This service registry relies on . This capability helps you optimize the use of services in an SOA by exchanging rich service metadata with runtime service registry. a small subset of information for discovery. The semantic infrastructure provides a mechanism to leverage rich service and artifact metadata to extend this capability.

Forms Definition & Modeling

...