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 81: | Line 81: | ||
* Have the characteristics of high cohesion & low coupling – need to explore whether coupling is good some places, not elsewhere – layers from Bo’s document | * Have the characteristics of high cohesion & low coupling – need to explore whether coupling is good some places, not elsewhere – layers from Bo’s document | ||
--> | --> | ||
| + | |||
| + | 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== | ==Expected implementations== | ||
Revision as of 19:30, 8 February 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
Ken to provide
Scope of coverage
- 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
Content sources
Example Scenarios
Resource Relationships
Timelines
May 2015 DSTU
gForge Users
cnanjo
