Draft Term Bindings for Published Archetypes

Hi all,

With more and more published archetypes in CKM, there has been an increasing concern regarding PUBLISHED archetypes that it may not be immediately clear that the term bindings associated with an archetype are often not yet reviewed, and typically haven’t been.

I’ve been exploring ways to address this, to make it less likely that term bindings are not mistakenly assumed to be officially published alongside the archetype’s content: For published archetypes, we could add the (e.g.) draft status icon adjacent to the term binding in combination with a tooltip:

Any feedback much appreciated.

6 Likes

Nice - the pop-overs work well.

1 Like

Are you trying to track lifecycle at an individual binding level, or at a group (e.g. ‘snomed-ct’) level? Where would you maintain the lifecycle status - in CKM I guess, but then how does a tool user who reviews (and maybe approves somehow) some bindings communicate their disposition, since there are no fields inside an archetype to indicate review status of bindings?

2 Likes

At group level.

Yes, this is in CKM - see the status tab of e.g. Observation Archetype: Braden scale [openEHR Clinical Knowledge Manager]

And yes, there are terminology reviews available in CKM and at the end you can set the status of that terminology accordingly. This is the status I am referring to here to clearly communicate that while the archetype content has been published, the bindings have not. It has been common practice to keep the publication processes for the content separate from the terminology bindings (and translations as well) - completely different skill sets.

As far as I know there is no field in the archetype directly to indicate the publication status of a terminology binding group (or translation for that matter).

I’ve worried about this a lot, so I’d very much welcome this change! :star_struck:

1 Like

I think we should think about defining some annotations or even a new section in ADL for this, because otherwise this lifecycle info is stuck inside CKM, but can’t easily be seen once archetypes are downloaded or exported.

1 Like