We will define a 'category' element as 0..* CodeableConcept, unbound on the Request, Event and Definition patterns Short: [High level categorization of x " Long: Partitions the x into one or more categories that can be used to filter searching, to govern access control and/or to guide system behavior. Comment: Categorization might be done automatically (inferred by code) or manually by user assertion.  The absence of a category may limit the ability to determine when the element should be handled, so strong consideration should be given to how systems will be able to determine category values for legacy data and how data that cannot be categorized will be handled.  As well, some categories may not be mutually exclusive, so systems should prepare for multiple declared categories - even within a single category 'axis'. In general, there should not be a 'strong' binding ('required' or 'extensible') on the category element overall.  Instead, the element can be sliced and bindings can be asserted that apply to particular repetitions. Will also add an additional comment on the 'Definition' element: "usageContext and jurisdiction can be seen as 'types' of categorization.  The category element should only be used when the type of categorization is not one that would easily be expressed through jurisdiction or usage.