Work flow resources

I think the request is to link to the 'dispense' of a particular prescription as establishing the 'timing' for an Observation. I don't think the ability to capture that sort of linkage as a 'discrete' data element is something widely supported by community dispensing systems, nor EHR order entry systems. You certainly *could* define an extension for it. However, from a practical perspective, I'd put a comment in the dispensing notes and/or in the code.text for the ServiceRequest. Those elements are widely supported and are probably 'good enough' to achieve your objective.

Within the carePlan is a Reference which can be a reference to a medicationRequest. There is also a product[x] which can reference a Medication.

The serviceRequest has a basedOn which can reference a MedicationRequest.

This is in a prescription situation and the ideal servicerequest time is when a script for a particular medication is dispensed. I can't see where a medication can be obviously specified so, if there isn't a place where FHIR has that option, I assume I have to make up how to specify that?

Many thanks. There are a number of different circumstances I've got to handle and I couldn't see the trees for the forest, but you've outlined how I might approach any of them now.

Typically you'd have a CarePlan that would say something like "Test every month to monitor progress". If you're needing someone else to do the testing, you could create either a ServiceRequest (could be one that specifies the repeat pattern) or a set of Tasks (one for each occurrence) to trigger that occurring

I am linking Observations to Goals but am not clear what the best workflow resources to use are. If a Goal gets created, lasts for 3 months but needs attention every month and at the end, Should this be monitored by a Task or a Careplan. There is clearly both a request and event component in the process.