This wiki has undergone a migration to Confluence found Here

Difference between revisions of "ProcedureRequest FHIR Resource Proposal"

From HL7Wiki
Jump to navigation Jump to search
Line 102: Line 102:
  
 
Are there any source specifications that you wish to consult but are concerned about access to or expertise to consider? -->
 
Are there any source specifications that you wish to consult but are concerned about access to or expertise to consider? -->
 +
 +
None
  
 
==Example Scenarios==
 
==Example Scenarios==

Revision as of 19:31, 8 February 2015



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

  • Clinical Decision Support Systems
  • Quality Improvement Platforms

Content sources

None

Example Scenarios

Resource Relationships

Timelines

May 2015 DSTU

gForge Users

cnanjo