This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "ProcedureRequest FHIR Resource Proposal"

From HL7Wiki
Jump to navigation Jump to search
 
Line 3: Line 3:
 
<div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div>
 
<div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div>
 
<div style="background:#F0F0F0">
 
<div style="background:#F0F0F0">
This page documents a [[:category:Pending FHIR Resource Proposal|Pending]] [[:category:FHIR Resource Proposal|FHIR Resource Proposal]]
+
This page documents a [[:category:Approved FHIR Resource Proposal|Approved]] [[:category:FHIR Resource Proposal|FHIR Resource Proposal]]
 
</div>
 
</div>
 
</div>
 
</div>
 
[[Category:FHIR Resource Proposal]]
 
[[Category:FHIR Resource Proposal]]
[[Category:Pending FHIR Resource Proposal]]
+
[[Category:Approved FHIR Resource Proposal]]
  
  

Latest revision as of 20:48, 8 April 2015



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