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

Difference between revisions of "SupplyRequest FHIR Resource Proposal"

From HL7Wiki
Jump to navigation Jump to search
Line 32: Line 32:
 
==Committee Approval Date:==
 
==Committee Approval Date:==
 
<!--Please enter the date that the committee approved this Resource proposal -->
 
<!--Please enter the date that the committee approved this Resource proposal -->
Feb 18, 2016
+
8/4/2016 ( OO Call )
  
 
==Interested Work Groups==
 
==Interested Work Groups==

Revision as of 17:30, 4 August 2016



SupplyRequest

Owning committee name

Orders & Observations WG

Committee Approval Date:

8/4/2016 ( OO Call )

Interested Work Groups

  • Pharmacy
  • Devices
  • Patient Care
  • HSI

FHIR Resource Development Project Insight ID

952

Scope of coverage

DEFINITION SupplyRequest: The scope of the SupplyRequest resource is for recording the request of supplies and logistics of movement of the supply item used in the healthcare process. This includes supply movement between institutions and within an institution (e.g. transport a set of supplies from materials management to a service unit like a nurse's station). This resource does not include the provisioning of transportation services. The SupplyRequest resource may be used to request medication, substances and devices when handling them generically (as any other supply) rather than being associated with a patient or having patient specific instructions. When requests are for things associated with a patient, then use DeviceUseRequest or MedicationOrder.

Examples:

  • ordering a case of 60 cc syringes
  • ordering a box of medication for floor stock
  • ordering a bottle of contrast for Radiology
  • ordering a ingredients for compounding medications

RIM scope

  • Role: Supply (classCode=SPLY, moodCode=RQO )

Resource appropriateness

Resource to record the request(order) of materials, devices, medications ward, central supply etc are necessary in healthcare.

Expected implementations

  • Required for CCDA
  • Record request substance and medications when context is generic -i.e. not specifically tied to a patient record.

Content sources

  • HL7 v3 Pharmacy Standard
  • HL7 v2.x
  • HL7 v3 Diet and Nutrition DAM
  • IHE Pharmacy(PHARM) White Paper, Supply of Products for Healthcare


Example Scenarios

see above

Resource Relationships

  • Task
  • SupplyDelivery
  • Device
  • Medication
  • Substance
  • Contract
  • CarePlan
  • ClinicalImpression

Timelines

  • STU3 Ballot

gForge Users

  • Eric Haas
  • Patrick Loyd
  • Jose Costa Teixeira


Issues

  1. Align with Workflow Project
  2. RIM mappings needs completion and review
  3. Should look at IHE, NCPDP, probably OpenEHR,V2 CH4, CH17, X12, jurisdictional specifications (e.g. Vision dispense for pan-Canadian claims) -Will be part of QA