Stream: committers
Topic: Request Pattern
Grahame Grieve (Dec 04 2016 at 05:30):
I'd like every resource the follows the request pattern to contain some boilerplate texts in the background and context about why the cardinality of the reqeusting works the way it does. Witness the FAQ on the implementers channel right now.
Grahame Grieve (Dec 04 2016 at 05:30):
@Lloyd McKenzie can you draft something?
Lloyd McKenzie (Dec 05 2016 at 02:32):
There's already supposed to be boiler plate text indicating adherence to the Request pattern. Do we really want to explain cardinalities on each resource?
Grahame Grieve (Dec 05 2016 at 02:33):
I think the idea that you need a request for each line item, and how that's resolved, yes. Because it's for sure a big time FAQ
Grahame Grieve (Dec 05 2016 at 02:35):
The XXRequest resource allows for a single item to be requested. Business workflows that cover multiple items in a single 'request' are actually considered to be a set of XXRequest resources linked by a ZZZZZZZZZZZ
Grahame Grieve (Dec 05 2016 at 02:35):
something like that, no more
Lloyd McKenzie (Dec 05 2016 at 02:39):
Ah, well that's only an issue for a few of the request resources - principly DiagnosticRequest and MedicationRequest. It's not common practice in other areas. There is a section in the Request notes that talks about how to group multiple requests that could be referenced - http://build.fhir.org/request.html#compound
Grahame Grieve (Dec 05 2016 at 02:42):
SupplyRequest too. The sentence could reference the compound section, but my concern is, people don't read that bit, and the question of multiple items is clearly scope related
Lloyd McKenzie (Dec 05 2016 at 02:45):
So perhaps:
The xxx resource allows requesting only a single item. If a workflow requires requesting multiple items simultaneously, this must be done using multiple instances of this resource. These instances can be linked in different ways, depending on the needs of the workflow. For guidance, refer to <a href="http://build.fhir.org/request.html#compound">the Request pattern</a>
Grahame Grieve (Dec 05 2016 at 02:46):
sure that would make me very happy
Lloyd McKenzie (Dec 05 2016 at 02:48):
Well, that's the ongoing objective all all editors ;)
Grahame Grieve (Dec 05 2016 at 02:48):
@Melva Peters @Michelle (Moseman) Miller @John Hatem @Eric Haas @Rob Hausam @Hans Buitendijk any objections if I add Lloyds' sentence to the Scope and Usage section of MedicationRequest, DiagnosticRequest, and SupplyRequest?
Eric Haas (Dec 05 2016 at 04:32):
np
Melva Peters (Dec 05 2016 at 14:47):
np
Michelle (Moseman) Miller (Dec 05 2016 at 19:57):
np
Rob Hausam (Dec 05 2016 at 22:57):
np
Grahame Grieve (Dec 05 2016 at 23:09):
thanks all
Last updated: Apr 12 2022 at 19:14 UTC
