Page History

Page info
title title

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

...

• Description will change over time and its contents will reflect changing needs and context. This is elaborated in the inherited Change profile.
• Description makes use of defined semantics, where the semantics may be used for categorization or providing other property and value information for description classes. This is elaborated in the inherited Semantic Model profile.
• Descriptions include reference to policies defining conditions of use and optionally contracts representing agreement on policies and other conditions. This is elaborated in the inherited Policy profile.
• Descriptions include references to metrics which describe the operational characteristics of the subjects being described. This is elaborated in the inherited Metrics profile.
• Descriptions of the interactions are important for enabling auditability and repeatability, thereby establishing a context for results and support for understanding observed change in performance or results. This is elaborated in the inherited Interaction profile.
• Descriptions may capture very focused information subsets or can be an aggregate of numerous component descriptions. Service description is an example of a likely aggregate for which manual maintenance of all aspects would not be feasible. This is elaborated in the inherited Composition profile.
• Descriptions provide up-to-date information on what a resource is, the conditions for interacting with the resource, and the results of such interactions. As such, the description is the source of vital information in establishing willingness to interact with a resource, reachability to make interaction possible, and compliance with relevant conditions of use. This is elaborated in the inherited Interoperability profile.

Functional Profile

• 5.2.5.4.1 - Governance Processes Sept. 6, 2010 The BIG Health vision brings a lot more stakeholders into the KR. Each of these has their own governance processes in respect to metadata and terminology. At a minimum the KR has to be aware of these processes, and their outcomes, to be able to express the status of metadata definitions and terminology concepts it contains. Some stakeholders expressed the wish to manage their governance processes within the KR.5.2.
• 5.4.2 - Services Sept. 6, 2010 Users expressed requirements that suggest caBIG services are not sufficiently described to determine if they meets a user’s requirements or are interoperable with other services. These requirements are deemed applicable to future KR services.