FHIR Chat · Order of resource in "entry" Bundle · implementers

Stream: implementers

Topic: Order of resource in "entry" Bundle


view this post on Zulip Dongtu (Jul 26 2019 at 05:27):

In a HL7 Message bundle. Does It have rules of display order of resources? Resources can be added according to user needs or must follow a specified structure

For example: There are patient information messages including resources: MessageHeader, Patient, Coverage. Since business requirements require additional diagnostic information. Can I specify just drag resources Observation, DiagnosticReport, etc. into it without worrying about the order of expression.

view this post on Zulip Richard Townley-O'Neill (Jul 26 2019 at 06:11):

As I read the docco, in a message bundle the first resource has to be a MessageHeader, after that the FHIR spec says nothing. The contents can be ordered any way the sender likes.

view this post on Zulip Dongtu (Jul 26 2019 at 06:51):

Does It depends on recived server?

view this post on Zulip Dongtu (Jul 26 2019 at 06:51):

I also think that

view this post on Zulip Dongtu (Jul 26 2019 at 07:31):

If my system don't care MessageHeader. Can I remove MessageHeader resource from sending bundle message?
Because when receive msg It use my validate system and when response I use OperatorOutcome resource.

view this post on Zulip Grahame Grieve (Jul 26 2019 at 10:34):

then it would not be a message

view this post on Zulip Dongtu (Jul 26 2019 at 12:05):

Why? sorry can you explane more detail? I think it still bundle message

view this post on Zulip Lloyd McKenzie (Jul 26 2019 at 14:40):

If it's a Message, then the submission must have a MessageHeader resource as the first entry in the Bundle. If not, then it can't be a conformant FHIR message. If you're just wanting to send a Bundle of stuff and get it validated, look at using the $validate operation or some other mechanism. Messaging is a specific FHIR protocol and imposes certain expectations if you want to claim to be using it.


Last updated: Apr 12 2022 at 19:14 UTC