As noted when we deferred this issue initially... ServiceCategory and Type are both only example bindings, so you may use your own terminologies as appropriate in your use cases and jurisdiction. We have considered this suggestion for R5 and note that this content is highly likely commercial in nature and thus not suitable for use as an example binding (as IP rights would be an issue). The existing Service Category ValueSet provides a similar set of values (and expect is localised anyway) The service type list you provided is a hierarchical lists which would be beneficial for a sample, however the IP issues prevent us using it.