Identifying complex knowledge artefacts

Based on a lot of experience, thinking and gnashing of teeth of colleagues Ian McNicoll, Heather Leslie, Sebastian Garde who work on the Ocean Clinical Knowledge Manager (CKM) product, as well as many others using archetypes and archetype tools more generally, I have produced a major update to the openEHR Knowledge Artefact Identification specification draft, here.

Lifecycle management with versioning.

This specification is designed to answer the following needs for complex, designed artefacts like archetypes, templates and terminology subsets:

  • ‘ontological’ (human readable) archetype, template and subset identifiers
  • machine identifiers
  • references to identified artefacts from other artefacts
  • recording knowledge artefact ids in data
  • lifecycle management and states;
  • dealing with transfer and forking;
  • supporting integrity and non-repudiation.

It combines the concept of lifecycle management for knowledge artefacts with a solid versioning model, mostly lifted from the excellent specification at

I have taken a lot of care to ensure this specification works equally well with artefacts produced by other organisations, particular non-openEHR archetypes and similar models. It now needs community input and feedback… i.e. feel free to pull it to pieces.

About wolandscat

I work on semantic architectures for interoperability of information systems. Much of my time is spent studying biomedical knowledge using methods from philosophy, particularly ontology and epistemology.
This entry was posted in Computing, Health Informatics, openehr and tagged , , , , , . Bookmark the permalink.

1 Response to Identifying complex knowledge artefacts

  1. Koray Atalag says:

    Great stuff Tom – long waited for by the community.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s