Loading...

XML

Word

Printable

JSON

Specification:

FHIR Core (FHIR)
Raised in Version:

STU3
Work Group:

FHIR Infrastructure
Related URL:
http://build.fhir.org/request.html#12.3.1
Related Page(s):

Workflow
Related Section(s):
12.3.1
Grouping:
- Workflow
Resolution Description:

Hide

Will change "proposals for action to occur, recommendations" to "proposals/recommendations for actions to occur,"

Recommendations are sometimes interpreted as being slightly different from proposal in that a recommendation is a proposal targeted for someone else to do. However, a recommendation is a type of proposal. We include both words because we want people searching for either word to find the content.

Show
Will change "proposals for action to occur, recommendations" to "proposals/recommendations for actions to occur," Recommendations are sometimes interpreted as being slightly different from proposal in that a recommendation is a proposal targeted for someone else to do. However, a recommendation is a type of proposal. We include both words because we want people searching for either word to find the content.
Resolution Vote:
Reinhard Egelkraut/John Hatem: 4-0-0
Change Category:
Clarification
Change Impact:
Non-substantive
Applied for Version:

STU3

The notion of "request" encompasses all types of orders ... as well as proposals *for action to occur, *recommendations, ...

Are there any significant differences between proposals *and *recommendations?