Stream: cds hooks
Topic: Prefetch Examples
Bryn Rhodes (Oct 02 2018 at 18:59):
MedicationRequest?id={{context.orders.MedicationRequest.id}}
&_include=MedicationRequest:patient
&_include=MedicationRequest:intended-dispenser
&_include=MedicationRequest:requester:Practitioner
&_include=MedicationRequest:medication
&_include=MedicationRequest:on-behalf
&_include=MedicationRequest:insurance:Coverage
Robert Sax (Oct 03 2018 at 12:59):
is that valid per the spec?
Jens Villadsen (Oct 03 2018 at 13:08):
if you put an underscore before the id (_id) its a little more valid ;)
Bryn Rhodes (Oct 03 2018 at 13:13):
No, sorry, this needs some context, I posted this yesterday as a way to distribute the example for a discussion about Github issue #377 during the CDS Quarter at the WGM here in Baltimore.
Bryn Rhodes (Oct 03 2018 at 13:17):
In addition to the _id (thanks @Jens Villadsen :)), the prefetch token would not currently be allowed by the specification. #377 is a proposal to expand that functionality and this is an example of what it would look like with the expanded support.
Isaac Vetter (Oct 03 2018 at 15:05):
The emphasis on _include sure is concerning.
Lloyd McKenzie (Oct 03 2018 at 15:31):
Include is CRD's use-case. Obviously the root resource isn't needed because it's already in context.
Jeffrey Danford (Oct 08 2018 at 21:40):
I'm concerned about the sheer number of resources being requested. Does the use case require everything in each of the included resources, or just a few pieces of information from each one?
Lloyd McKenzie (Oct 08 2018 at 23:08):
Exactly how much may vary somewhat by payer. However, in general, knowing the patient's coverage, who's ordering the service (individual and organization), who's to perform the service (individual and organization), where the service is to be performed and the specific nature of the service can all be relevant to determining coverage expectations
Last updated: Apr 12 2022 at 19:14 UTC
