See https://interweavedigital.atlassian.net/browse/ICR-5865
In certain circumstances an OperationOutcome is included as a Contained Resource. From a purest perspective these are not always fully-compliant with the FHIR Specification ... (e.g. unsuccessful PIX Registrations:
Constraint dom-4 states: If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated
Constraint dom-3 states: If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource
Resources shall always have a known identity (“id”) except for the special case when a new resource is being sent to a server to assign an identity (create interaction)
Suggest that the above constraints are considered whenever there are any new features (or re-design of current features) that Contain an OperationOutcome in another Resource