The following components or attributes of an archetype need to be considered at each stage of development. In this way, at final publication, we will have a consistent and high quality archetype. At all times, remember that the archetype is designed for a universal use case, and specific details that are appropriate for a particular health domain or clinical purpose can and should be constrained and represented in a template.
The approach to design scope is intended to be broad and as inclusive as is deemed sensible. The intent for a maximum data set in an archetype is ideal but may be overwhelming for some clinical concepts, and a more pragmatic decision may be to keep the scope based on what most users will require in the first instance, with slots for specialised content elements or those for other peripheral purposes, such as reporting, that can be used wherever needed.. This will help to keep the focus of the archetype on the most commonly used and core clinical concepts and not be overloaded with data elements that are uncommonly used.
Consider each of the following details when submitting an archetype to CKM - whether for the initial archetype upload, or submitting archetypes for review or publication:
...