This wiki has undergone a migration to Confluence found Here
Difference between revisions of "ProcedureRequest FHIR Resource Proposal"
Jump to navigation
Jump to search
| Line 55: | Line 55: | ||
As a rule, resources should encompass all of these aspects. | As a rule, resources should encompass all of these aspects. | ||
--> | --> | ||
| + | |||
| + | Procedure Request is a record of a request for a procedure to be performed. It can be used to represent a procedure that is planned, that is proposed, or that is ordered. | ||
| + | |||
| + | 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 (CDS) system based | ||
| + | on a patient's clinical record and context of care. Planned procedures may also be | ||
| + | represented by this resource. | ||
* Subject: Human and non-human living and non-living (e.g., a human patient, a veterinary patient, ground water testing) | * Subject: Human and non-human living and non-living (e.g., a human patient, a veterinary patient, ground water testing) | ||
Revision as of 00:49, 20 March 2015
This page documents a Pending FHIR Resource Proposal
Contents
- 1 ProcedureRequest
- 1.1 Owning committee name
- 1.2 Contributing or Reviewing Work Groups
- 1.3 FHIR Resource Development Project Insight ID
- 1.4 Scope of coverage
- 1.5 RIM scope
- 1.6 Resource appropriateness
- 1.7 Expected implementations
- 1.8 Content sources
- 1.9 Example Scenarios
- 1.10 Resource Relationships
- 1.11 Timelines
- 1.12 gForge Users
ProcedureRequest
Owning committee name
Clinical Quality Information Work Group
Contributing or Reviewing Work Groups
FHIR Resource Development Project Insight ID
1125
Scope of coverage
Procedure Request is a record of a request for a procedure to be performed. It can be used to represent a procedure that is planned, that is proposed, or that is ordered.
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 (CDS) system based
on a patient's clinical record and context of care. Planned procedures may also be
represented by this resource.
- Subject: Human and non-human living and non-living (e.g., a human patient, a veterinary patient, ground water testing)
- Disciplines: Cross discipline
- Delivery environment: Clinical Decision Support
- Locale: International Realm
RIM scope
Lloyd to provide
Resource appropriateness
Must
- Represents a request for a procedure and captures the following modalities: Recommended, Planned, Proposed, Ordered
- ProcedureRequests can be tracked with distinct, reliable, unique ids
- Procedure requests are common outputs to Clinical Decision Support systems and are also often included in care plans.
Should
- In order to achieve interoperability of exchange of clinical knowledge artifacts or clinical guidance, a common core definition of ProcedureRequest is required.
Expected implementations
- Clinical Decision Support Systems
- Quality Improvement Platforms
Content sources
None
Example Scenarios
A CDS system receives as input relevant information pertaining to the patient's medical record and context of care. Based on the input received by the CDS system recommends a particular procedure be performed.
Resource Relationships
- Procedure (that resulted from the request)
- Observation (pertinent to the decision to propose the procedure)
- Condition (pertinent to the decision to propose the procedure)
- Other relevant clinical statements pertinent to the decision to propose the procedure
- BodySite
- Performer of the procedure
- Subject (generally the patient)
Please refer to proposed resource: http://hl7-fhir.github.io/procedurerequest.html
Timelines
May 2015 DSTU
gForge Users
cnanjo
