Details
-
Change Request
-
Resolution: Not Persuasive
-
Medium
-
FHIR Core (FHIR)
-
R6
-
Orders & Observations
-
DeviceRequest (was DeviceUseRequest)
MedicationRequest
NutritionOrder (was NutritionRequest)
ServiceRequest (Diagnostic/Procedure/ReferralRequest)
SupplyRequest -
-
Marti Velezis / JD Nolen : 4 - 0 - 1
Description
There seems to be some variation in how we record why a request is being made (reason), and how we record "on demand" usage. It isn't clear that this variation is intentional, rather than just separate evolution.
Do all the resources need a boolean asNeeded?
Do they need an asNeededCodableConcept or asNeededFor? Is the meaning the same? Is the intent "as needed when" rather than "as needed for"?
Is it clear about how "as needed" is distinct from the reason for the request?
Suggest using the same structure and definitions across all resources.
Attachments
Issue Links
- relates to
-
FHIR-26674 clarify description of asNeeded element to help differentiate from reason element
- Resolved - change required