Stream: implementers
Topic: can uploader set metadata profile
Brian Reinhold (Nov 24 2017 at 20:12):
I have gotten conflicting information about the setting of the meta.profile element. I would have thought that an uploader creating a resource that follows a certain profile would populate the meta.profile element with the profile it is following. But I have been told that the server might change that value. Is this true? I would think that a reader would want to examine the meta.profile values and take advantage of any additional knowledge it may have regarding a certain profile.
So my question is, can I safely set the meta.profile value, upload the resource, and rely on that field being present for a consumer of the resource?
Grahame Grieve (Nov 24 2017 at 21:34):
Resource.meta.profile is a claim that a resource meets a profile.
Grahame Grieve (Nov 24 2017 at 21:35):
Servers are allowed to remove claims, and/or add additional claims
Grahame Grieve (Nov 24 2017 at 21:35):
claims SHOULD be true, of course. but that doesn't mean they are
Grahame Grieve (Nov 24 2017 at 21:35):
You'll have to define 'safe' before we could know what safe means.
Grahame Grieve (Nov 24 2017 at 21:36):
but in principle, you should always use the data - the codes, etc - to decide how to handle resources.
Lloyd McKenzie (Nov 24 2017 at 22:48):
Technically you can't rely on any data being persisted by a server, as servers are allowed to choose which elements they support and which they don't. So technically, some systems could throw away Patient.name - and there are use-cases where that would be a valid thing for them to do. There's a whole section on Variations between Submitted and Retrieved Data in the spec that talks about some of this.
Last updated: Apr 12 2022 at 19:14 UTC
