Task interactions
Assume that Order.target will be reference(Organization|Practitioner). Is it wise to allow Practitioner as recipient organisations may need to route to the appropriate person e.g. when staff on leave? This will depend on how it’s handled in the recipient system but could create clinical safety risk.
Does the task-description extension provide anything that couldn’t be handled by populating the order.text.div (i.e. the resource narrative)? The description is not computable, anyway.
After recent discussions with system users they felt that tools to curate inbound messages are weak in existing systems (e.g. it’s not possible to prioritise lab results with out of range values). They proposed that an indicative date & priority on the inbound order would be very useful. I think priority would be covered by the reason codes.
The example order doesn’t have order.detail so would not be a valid Order. I think you’ve identified a case for a generic Order that doesn’t relate to another resource.
Should these points be raised with the FHIR team?