Details
-
Change Request
-
Resolution: Persuasive
-
Medium
-
FHIR Core (FHIR)
-
R4
-
Clinical Decision Support
-
RequestOrchestration (was RequestGroup)
-
-
Juliet Rubini/Stan Rankins: 12-0-1
-
Enhancement
-
Non-substantive
Description
Based on https://jira.hl7.org/browse/FHIR-38869:
Add the following into the 'Notes' section of RequestOrchestration:
Documenting Choices
A RequestOrchestration can be used to document (wholly or in part) options that are to be chosen by the order filler when actually delivering care. There is no expectation for systems that fulfill a RequestOrchestration to specifically document which choices were made among the options defined. However, if this is needed, it could be accomplished with a 'filler-order' RequestOrchestration basedOn the 'original-order' RequestOrchestration that narrows the order to reflect the filling clinician's choices.
NOTE: The 'intent' of the requests referenced by a RequestOrchestration are never changed from Option to Order or some other value to convey 'selection'.
Completion
A RequestOrchestration is deemed to be complete when the requirements of the request options needed to satisfy at least one path through the overall request have been met or when the author of the RequestOrchestration deems it to be sufficiently complete.
Attachments
Issue Links
- relates to
-
FHIR-38869 RequestOrchestration behavior underdefined
- Published