Keywords in archetypes sometimes incorrectly represented

I recently noticed that some archetypes have keywords formatted as a single String whose contents include commas. E.g. this from CLUSTER.person:

keywords = <"provider, carer, staff, healthcare professional, relative, next-of-kin, practitioner, witness, friend, neighbour, child, family, sibling, parent, individual", ...>

Depending on what tools do with this, the entire string will be understood as a keyword, and will never be directly matched in a search; only wildcard matching will work.

The correct form is the following, as from CLUSTER.problem_qualifier.

keywords = <"problem", "active", "inactive", "status", "episode", "diagnosis">

I’d suggest that as tools (including CKM) and organisations rely more on tools for discovery, this problem could be rectified by an automated sweep through CKM archetypes to correct the problem.