Stream: implementers
Topic: OrderItem in SupplyReq
Jose Montoya (Dec 03 2016 at 22:12):
It's a single resource as it stands. Should it not be an array? Allowing us to order a variable amount of items in the same request?
Jose Montoya (Dec 03 2016 at 22:12):
http://build.fhir.org/supplyrequest.html#resource
Eric Haas (Dec 04 2016 at 07:11):
Think of it as a line item on a paper order form. Same a DiagnosticRequest, and MedicationRequest one item one request.
Jose Montoya (Dec 04 2016 at 20:08):
So for me to order 20
Jose Montoya (Dec 04 2016 at 20:09):
So for me to order 20x of anything I have to send 20 supply requests?
Jose Montoya (Dec 04 2016 at 20:49):
So grouping item just as you mentioned for diagReq
Eric Haas (Dec 04 2016 at 21:41):
20 different things. We may need a quantity element. @Jose Costa Teixeira have you looked at this?
Jose Montoya (Dec 04 2016 at 21:42):
Right, so I can see when you're requesting 5 different type of items, but requesting 20x of the same item then quantity element makes sense.
Jose Costa Teixeira (Dec 04 2016 at 21:54):
I think we may need both:
1. a mechanism to request 5 different things. This should not be only for supply, but for any request, I guess.
2. The quantity to order. I will look into it tomorrow, but seems that quantity will be one element to add.
Jose Montoya (Dec 04 2016 at 21:57):
That seems like the most convenient way to handle requests imo. But seems it would contradict the "Request Pattern" where you have individual requests grouped together.
Eric Haas (Dec 04 2016 at 22:59):
yes @Jose Costa Teixeira can only request a single thing like in meds. you group them with the groupID or Requestion number. That makes composite orders splittable downstream
Last updated: Apr 12 2022 at 19:14 UTC
