-
Type:
Change Request
-
Resolution: Persuasive with Modification
-
Priority:
Very Low
-
FHIR Core (FHIR)
-
DSTU1 [deprecated]
-
Patient Care
-
ProcedureRequest (see ServiceRequest) [deprecated]
-
4.9.1
-
-
Elaine/Stephen: 6-0-0
-
Clarification
-
Non-compatible
-
DSTU1 [deprecated]
Existing Wording
The procedure request may represent an order that is entered by a practitioner in a CPOE system as well as a proposal made by a clinical decision support system (CDSS) based on a patient's clinical record and context of care. Planned procedures may also be represented by this resource (though this use case is still being discussed and will need to be validated by Patient Care and Orders and Observation).
Comments
Conflating actual orders entered by practitioners with proposals for orders from CDS does not sound like a good idea. Surely there should be somedistinction between them. If/when the proposal is accepted and an order is actually placed, then the order should be created and the proposal should still remain as a separate entity to preserve the thread of logic that led to the order (and as a safeguard). Section 4.9.2 acknowledges that more work distinguishing these is necessary.
Grahame's Comments
no opinion
- is voted on by
-
BALLOT-181 Negative - David Tao : 2015-Jan-FHIR R1
- Balloted