Stream: implementers
Topic: Version id
Anders Almås (Apr 24 2018 at 13:00):
Hi.
I have a question about the versionid in the meta-tag.. Is this one necessary when one wants allow different versions of a profile on the server? Is it a best practice to always include this in meta-tag? How should one set this tag? I can't do it when I do profiling in Forge. I am only able to do that in a texteditor. I hope someone can clarify this for me.
Michel Rutten (Apr 24 2018 at 13:09):
Hello @Anders Almås, by default, Forge hides some common elements inherited from (Domain)Resource, such as Resource.meta. The Options menu provides a configuration setting "Show common resource elements" that controls this behavior.
Note that the .meta.profile element represents a profile claim on a resource instance. In other words, this states that the instance claims to conform to the referenced profile. However this is just a claim and should always be verified (by a FHIR server).
If you want to constrain your server to only accept resources that conform to a specific (set of) profiles, then your server can advertise this behavior by means of the server CapabilityStatement.
Christiaan Knaap (Apr 24 2018 at 14:40):
And if you want to designate different versions of a profile, use the StructureDefinition.version attribute. That is meant for 'business version'.
The meta.versionId will be assigned by the server whenever you create or update the StructureDefinition on it.
Last updated: Apr 12 2022 at 19:14 UTC
