The purposeOfUse value set is incoherent. It contains a bunch of codes that aren't "reasons" at all, contains duplicates, has no clear boundaries between concepts and is far too large (and unstable) for implementers to be able to reasonably map to it. There's no chance that there's anywhere close to global agreement that this is a good and proper value set that everyone must map to for interoperability. The binding needs to drop to example and the value set simplified to a small set of codes that shows the breadth of concepts that might appear as reasons. As an aside, "reason for event" and "purpose of use" are completely different things anyhow. (PurposeOfUse is what you're allowed to do with data once you have it, not why a particular event - even a query - happened.)

(Comment 77 - imported by: Ron G. Parker)