Open lmckenzi opened 6 years ago
Poking on this one to see if we can get discussion started. It would now be relevant to order-select and order-sign hooks. The DeviceUseRequest resources is there for DSTU2 but the equivalent isn't present in STU3 or R4 and the others are needed for all 3 versions.
It's possible we could exclude SupplyRequest for STU3 and R4 as it's no longer patient-centric in those releases.
These are also patient-centric requests. DeviceRequest and SupplyRequest are needed by Davinci. DeviceRequest is going to subsume VisionPrescription but is also used for prosthetics, pacemakers, etc. where hooks may be relevant for research, enforcing best practice, interaction with payers. SupplyRequest will be relevant for coverage requirements but is also possibly relevant for other types of decision support.
Task and CommunicationRequest aren't needed by DaVinci. However, a request to cancel/suspend an order or a request to share information with someone else both seem like orders that might reasonably trigger decision support, so we might as well be thorough
Across versions, this would be: R4: DeviceRequest, SupplyRequest, CommunicationRequest, Task STU3: DeviceRequest, SupplyRequest, CommunicationRequest, Task DSTU2: DeviceUseRequest, SupplyRequest, CommunicationRequest, Order