Submit Health Event Response - Bundle.entry.response element about ddcc HOT 2 OPEN

I think the FHIR spec is a little vague on some of these and the elements aren't required by a invariant or cardinality. I believe the intention is that those fields should be based on the underlying requirements of the request. So for POST (create), location SHALL be there, but ETag is a SHOULD (if versioning is supported). The wording for PUT (update) is also problematic, as it seems to require etag and lastModified, but the wording could be clearer and it doesn't call out if you don't support versioning. It also says for create from update, location SHOULD be provided.

However, this transaction is of operations and for the return value of the generateHealthCertificate operation, location and etag don't make sense as the resource returned isn't being created locally (and perhaps not at all in some implementations). I think it makes sense if there is a repository that the location be set, but I don't think we can require it. Also, since it's a new document, the version (if supported) would always be 1, so the etag isn't particularly helpful, but again in those cases with no repository or no versioning it wouldn't be available.

I think perhaps one change that would help is to set the url in the request for Submit Health Event Request to make this more clear.

from ddcc.

Both explanations for location and etag not being required make sense to me. Thank you for the detailed explanation!

from ddcc.