Stream: implementers
Topic: tags
David Hay (Jul 07 2016 at 20:55):
Are there any existing tags that a server can use to indicate that a particular resource cannot be updated?
Grahame Grieve (Jul 07 2016 at 21:04):
not that I can see
Eric Haas (Jul 07 2016 at 22:24):
More tag questions. Can tags be used to categorize resources right? and so why not use them instead of inline category codes for query? ( I asked this before but I forgot the answer :-( ) If we have both then maybe some guidance around using one verses the other is needed?
James Agnew (Jul 07 2016 at 22:34):
One disadvantage to using tags would be that the existing category field is a CodeableConcept, so there are existing semantics for putting your category codes into valuesets and searching based on those valuesets, or based on other valuesets containing those same codes.
Grahame Grieve (Jul 07 2016 at 22:35):
there's restrictions around the content of tags. It must be safe to ignore them, or to change them without changing the meaning of the content
Eric Haas (Jul 07 2016 at 22:40):
Observation.category doesn't change the content. If I mis-categorize a BP as Lab is still a BP. I can ignore the category and look at the code - which is Rob's argument all along. What I'm saying is that .category is really a convenience for sort and searching.
Eric Haas (Jul 07 2016 at 22:41):
This is no different than a tag really.
Eric Haas (Jul 07 2016 at 22:42):
@James Agnew can't I do the same with tags which are codes too?
James Agnew (Jul 07 2016 at 22:44):
Actually... I suppose you could. Technically I suppose you should be allowed to say Observation?_tag:in=http://some_tag_valueset
That never occurred to me as something that would be legal to do.
Grahame Grieve (Jul 07 2016 at 22:46):
well, tags cannot be just text. It's a lot harder to properly value set tags - mainly by intent. Tags can be changed much more easily, and are not part of the signature. It's true that we might be able to achieve the same outcomes as category using tags, but I think it would be a harder way to get to the sam epalce
Lloyd McKenzie (Jul 07 2016 at 22:47):
If they're in tags, no-one will remember to populate them is the main reason I think. Also, it's much harder to use profiling or the spec to enforce they must be present or to constrain their values.
Eric Haas (Jul 07 2016 at 22:53):
Sounds a little hand wavy. I'm not sure whether we should give some guidance or not. let this sleeping dog lie.
James Agnew (Jul 07 2016 at 22:54):
What kind of guidance? "don't put things in tags that clearly have an appropriate field in the resource"? :)
Grahame Grieve (Jul 07 2016 at 23:49):
yes that's a good piece of guidance
Brian Postlethwaite (Jul 08 2016 at 06:17):
And tag changes don't flow in the history, so no good for subscriptions.
Last updated: Apr 12 2022 at 19:14 UTC
