Stream: implementers
Topic: Batch and references
Jenni Syed (May 04 2018 at 20:17):
I'm reading the batch section of the ballot and this statement is included: "Static references within a Bundle.entry.resource to another Bundle.entry.resource that is being created within the batch are considered to be non-conformant."
Does this mean no references to any resources within the same batch are allowed?
Josh Mandel (May 04 2018 at 20:18):
I think that's right; if you need to post a graph, the idea would be to use a transaction instead of a batch.
Jenni Syed (May 04 2018 at 20:19):
I think it's the "static" that's confusing since we don't use that terminology anywhere else :)
Josh Mandel (May 04 2018 at 20:20):
Agreed -- I would have interpreted this the same way if "static" was removed ("References within a Bundle...")
Jenni Syed (May 04 2018 at 20:20):
But, then, implications would be (for @Josh Mandel interpretation) that I cannot modify a patient record at the same time as I modify some of the other data? Even if I don't care if both succeed?
Jenni Syed (May 04 2018 at 20:20):
I think I can understand the goal of simplification :)
Jenni Syed (May 04 2018 at 20:20):
because these scenarios could get ridiculously complex
Josh Mandel (May 04 2018 at 20:21):
Let's see -- you want a with:
1. Change Patient A's phone number
2. Create a new Observation about Patient B
that meets what you just asked about and seems OK.
Jenni Syed (May 04 2018 at 20:21):
yes, but would seem to break the rule
Josh Mandel (May 04 2018 at 20:21):
Where?
Jenni Syed (May 04 2018 at 20:22):
oh no, sorry
Josh Mandel (May 04 2018 at 20:22):
No resources are being "created" in this batch.
Jenni Syed (May 04 2018 at 20:22):
My example would be:
1) Change patient A's phone number
2) Change patient A's med order
Josh Mandel (May 04 2018 at 20:22):
I think that's OK too. No resources are being created.
Jenni Syed (May 04 2018 at 20:22):
that would require the med order to reference patient a
Josh Mandel (May 04 2018 at 20:23):
That's OK, if Patient A already exists (so batch item 1 is an update rather than a create).
Jenni Syed (May 04 2018 at 20:23):
which is also in the batch. I agree that it seems ok, but seems to violate that restriction
Jenni Syed (May 04 2018 at 20:23):
It doesn't say that the resource has to exist already or not, right?
Jenni Syed (May 04 2018 at 20:23):
that restriction is completely unqualified
Josh Mandel (May 04 2018 at 20:23):
to another Bundle.entry.resource that is being created within the batch
Jenni Syed (May 04 2018 at 20:23):
oh. duh
Jenni Syed (May 04 2018 at 20:24):
ok. I think I am reading too many specs today :)
Jenni Syed (May 04 2018 at 20:24):
I may make a comment about that "static" qualifier though
Josh Mandel (May 04 2018 at 20:31):
Agreed -- I have no gloss on that.
Jenni Syed (May 04 2018 at 20:34):
Grahame Grieve (May 05 2018 at 04:58):
yes that's not a useful word in that sentence
Last updated: Apr 12 2022 at 19:14 UTC
