Stream: workflow
Topic: definitions and requests
Josh Mandel (May 10 2017 at 08:19):
an activity definition provides a reusable template that can be used to construct specific request resources
Does this imply that the (relevant) details from a Definition should be copied into a given Request? Or does the Request just point back tot he definition, and consumers are supposed to follow the link to understand these details? In other words: when a Request points back to a Definition, is this just "FYI, this was the template used to create this request", or is it "For all of the details of what's being requested, you'll need to read this Definition"?
Lloyd McKenzie (May 10 2017 at 08:24):
Either approach is permitted. In general, copying the content is generally preferred to minimize the number of resources that need to be retrieved to get the full picture. But it's legitimate to have an order that just says "Run protocol XYZ for patient John Smith starting tomorrow"
Last updated: Apr 12 2022 at 19:14 UTC
