-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
meta.lastUpdate Relevanz unklar - PTDATA-1002 #285
Comments
siehe PTDATA-1002 |
f-peverali
changed the title
meta.lastUpdate Relevanz unklar
meta.lastUpdate Relevanz unklar - PTDATA-1002
Apr 29, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Nirgends im ISiK-IG steht, ob lastUpdate gesetzt werden muss oder nicht. In der FHIR Core Spec ist das zwar an vielen Stellen konkret gefordert:
z.B. bei CREATE: "The server SHALL populate the id, meta.versionId and meta.lastUpdated with the new correct values."
bei UPDATE: "If the server supports versions, it SHALL populate the meta.versionId and meta.lastUpdated with the new correct values. ervers that do not support versioning SHALL ensure that Resource.meta.versionId is not present on resources they return, and SHALL update the value of Resource.meta.lastUpdated correctly."
Allerdings fordern wir bei ISiK Basis zwingend nur die READ-Interaktion. Jedoch auch für diese gilt: "Servers SHOULD return an ETag header with the versionId of the resource (if versioning is supported) and a Last-Modified header." und "The Last-Modified header should come from .meta.lastUpdated"
Die serverseitig korrekte Implementierung von LastUpdate sollte im ISiK-Kontext konkret gefordert und in den Testszenarien überprüft werden.
The text was updated successfully, but these errors were encountered: