Assets

There are a number of different types of assets referred to within the CKM environment:

• Primary Asset - An archetype, template or terminology sub-set;

• Secondary Asset - Artefacts that are generated directly from one of the Primary Assets. For example: a mindmap of an archetype; and

• Related Asset - Artefacts that add support to the primary assets, but are manually uploaded in association with the primary asset. For example: design or reference documentation or sample data.

In addition, in Projects, the primary assets can be owned or referenced:

• Owned Asset - An archetype, template or termset that is that is the responsibility of a specific project or incubator. All modifications to an owned asset are managed by the Project Editor or the Incubator owner.

• Referenced Asset - An archetype, template or terminology sub-set that is used, or referenced, within a project or incubator, yet the asset is owned/controlled by another project or incubator. Modifications to the referenced asset needs to be negotiated with the project/incubator which owns and manages the asset.

Roles

• Clinical Knowledge Administrator - A registered user who has the highest level of responsibility for management of all knowledge-related aspects within a CKM domain. CKAs have the responsibility to manage the library of all clinical assets, CKM processes for review and output generation, governance and distribution.

• Editor - A registered user who has responsibility for all of the owned assets within a defined Project or Incubator, including the facilitation of Editorial reviews. 

• Registered User - Any person who formally registers within a CKM domain. Registration gives the user privileges which enable them to participate in CKM activities such as Discussion Forums and Reviews of assets.

CKM Governance Structure

• Domain - A domain is the foundation governance structure with the Clinical Knowledge Manager. Each stand-alone instance of CKM currently operates as a single domain. For example:

• • openEHR international domain -- www.openEHR.org/knowledge

• • Australia's domain under the auspice of the Australian Digital Health Agency --  http://dcm.nehta.org.au/ckm/

• Sub-domain - Sub-domains are an organisational sub-group, within a domain that will have responsible for a sub-set of one or more primary assets and their related assets, within that domain. A sub-domain may be used as the library for a specific jurisdiction or an organisation-based activity - clearly identifiable within the domain instance. It allows for assets to be grouped logically or practically and may enable some degree of preliminary or independent work to occur under the direction of a jurisdiction or organisation, but still within the context and overall governance of the domain as a whole. Clinical Knowledge Administrators can set up one or more sub-domains in a similar manner to creating named folders, and each sub-domain can contain one or more projects.

• Projects - Projects are a finer-grained organisational sub-group, within a sub-domain. They are used to facilitate formal collaboration, publication, distribution and maintenance of primary assets for a specific clinical purpose or scenario, and operate under the oversight of a sub-domain. Each project comprises a collection of one or more models and a project team. Examples of Projects include: to create a Discharge Summary document; a laboratory report message; or a data entry screen. 

• Incubator - Incubators are used to facilitate informal collaboration, innovation and development of new or immature assets in an informal and ungoverned space within the CKM. If assets are developed and refined to meet requirements stipulated by the domain's Clinical Knowledge Administrator, theycan be promoted into the governed environment as part of that Project, with permission from the Project's Lead/Editors.