Stream: implementers
Topic: Bundle.entry.response.outcome
Michel Rutten (Jan 11 2018 at 15:56):
According to the documentation, Bundle.entry.response.outcome contains an OperationOutcome:
http://hl7.org/fhir/bundle-definitions.html#Bundle.entry.response.outcome
What is the reason this element is defined with type Resource instead of type OperationOutcome?
Lloyd McKenzie (Jan 11 2018 at 19:25):
OperationOutcome isn't a defined data type (none of the resources are). It could be Resource(OperationOutcome) though
Grahame Grieve (Jan 11 2018 at 20:26):
methodogical limitation - can you create a task for that pleease
Michel Rutten (Jan 12 2018 at 09:23):
Michel Rutten (Jan 12 2018 at 09:27):
So IIUC, you can define an element with datatype Resource, but not with any of the concrete resource types? I wasn't aware of that. Bit surprising, as it is allowed for a profile to further constrain an element of type Resource to a concrete Resource profile, e.g. constrain bunde.entry.resource to Patient.
Lloyd McKenzie (Jan 12 2018 at 15:38):
That's profile, not type
Michel Rutten (Jan 12 2018 at 16:23):
Yes, I see the (subtle) difference. It's just that I never realized this "axiom" exists.
Lloyd McKenzie (Jan 12 2018 at 17:01):
One reason for keeping the resources out of the types is that it makes it easier to handle new resources in a generic manner
Last updated: Apr 12 2022 at 19:14 UTC
