Release 4 5 Preview #2
This page is part of the FHIR Specification (v4.0.1: R4 - Mixed Normative and STU ). This is the current published version in it's permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions

12.21 12.25 Resource SupplyRequest - Content

Orders and Observations Work Group Maturity Level : 1   Trial Use Security Category : Patient Compartments : Device , Patient , Practitioner , RelatedPerson

A record of a request for a medication, substance or device used in the healthcare setting.

Trial-Use Note: In terms of scope and usage, the Orders and Observations workgroups wish to draw the attention of reviewers and implementers to the following issues and changes.

  1. We are seeking input from the implementation community on whether to combine SupplyRequest and DeviceRequest for R4.
  2. The parameters element was added to SupplyRequest for representing custom details for ordering devices.

Feedback is welcome here

This resource is a request resource from a FHIR workflow perspective - see Workflow . It is the intent of the Orders and Observation Workgroup to align this resource with the workflow pattern for request resources .

The scope of the SupplyRequest resource is for recording the request of supplies used in the healthcare process. This includes supplies specifically used in the treatment of patients as well as supply movement within an institution (transport a set of supplies from materials management to a service unit (nurse station). This resource does not include the provisioning of transportation services.

The SupplyRequest resource allows requesting only a single item. If a workflow requires requesting multiple items simultaneously, this is done using multiple instances of this resource. These instances can be linked in different ways, depending on the needs of the workflow. For guidance, refer to the Request pattern

Note that the SupplyRequest records the fact that a request was made. To actually act on that request, additional workflow beyond simply the existence of a SupplyRequest is required. This can be achieved by using an Task resource, with the SupplyRequest referenced from the Task.focus, or by using the SupplyRequest resource in the context of an messaging or service workflow where the request is explicit or implicit. The SupplyDelivery resource represents the fulfillment as a result of SupplyRequest being acted upon.

The SupplyRequest resource is used for inventory management . When requesting medication, substances and devices when there is a patient focus or instructions regarding their use, DeviceRequest or MedicationRequest should be used instead

This resource is referenced by SupplyDelivery .

This resource implements the Request pattern.

Structure

itemCodeableConcept CodeableConcept itemReference Reference ( Medication | Substance | Device )
Name Flags Card. Type Description & Constraints doco
. . SupplyRequest TU DomainResource Request for a medication, substance or device
Elements defined in Ancestors: id , meta , implicitRules , language , text , contained , extension , modifierExtension
. . . identifier Σ 0..* Identifier Business Identifier for SupplyRequest
. . . status ?! Σ 0..1 code draft | active | suspended +
SupplyRequestStatus ( Required )
. . . category Σ 0..1 CodeableConcept The kind of supply (central, non-stock, etc.)
Supply Type ( Example )
. . item[x] . item Σ 1..1 CodeableReference ( Medication | Substance | Device | DeviceDefinition ) Medication, Substance, or Device requested to be supplied
SNOMED CT Supply Item ( Example )
. . . quantity Σ 1..1 Quantity The requested amount of the item indicated
. . . parameter 0..* BackboneElement Ordered item details
. . . . code 0..1 CodeableConcept Item detail
. . . . value[x] 0..1 Value of detail
. . . . . valueCodeableConcept CodeableConcept
. . . . . valueQuantity Quantity
. . . . . valueRange Range
. . . . . valueBoolean boolean
. . . occurrence[x] Σ 0..1 When the request should be fulfilled
. . . . occurrenceDateTime dateTime
. . . . occurrencePeriod Period
. . . . occurrenceTiming Timing
. . . authoredOn Σ 0..1 dateTime When the request was made
. . . requester Σ 0..1 Reference ( Practitioner | PractitionerRole | Organization | Patient | RelatedPerson | Device ) Individual making the request
. . . supplier Σ 0..* Reference ( Organization | HealthcareService ) Who is intended to fulfill the request
. . reasonCode . reason 0..* CodeableConcept The reason why the supply item was requested SupplyRequestReason ( Example ) reasonReference 0..* Reference CodeableReference ( Condition | Observation | DiagnosticReport | DocumentReference ) The reason why the supply item was requested
SupplyRequestReason ( Example )
. . . deliverFrom 0..1 Reference ( Organization | Location ) The origin of the supply
. . . deliverTo 0..1 Reference ( Organization | Location | Patient ) The destination of the supply

doco Documentation for this format

UML Diagram ( Legend )

SupplyRequest ( DomainResource ) Business identifiers assigned to this SupplyRequest by the author and/or other systems. These identifiers remain constant as the resource is updated and propagates from server to server identifier : Identifier [0..*] Status of the supply request (this element modifies the meaning of other elements) status : code [0..1] « Status of the supply request. (Strength=Required) SupplyRequestStatus ! » Category of supply, e.g. central, non-stock, etc. This is used to support work flows associated with the supply process category : CodeableConcept [0..1] « Category of supply request. (Strength=Example) SupplyType ?? » Indicates how quickly this SupplyRequest should be addressed with respect to other requests priority : code [0..1] « Identifies the level of importance to be assigned to actioning the request. (Strength=Required) RequestPriority ! » The item that is requested to be supplied. This is either a link to a resource representing the details of the item or a code that identifies the item from a known list item[x] item : Type DataType [1..1] « CodeableConcept | Reference ( Medication | Substance | Device ); | DeviceDefinition ; The item that was requested. (Strength=Example) SNOMEDCTSupplyItem ?? » The amount that is being ordered of the indicated item quantity : Quantity [1..1] When the request should be fulfilled occurrence[x] : Type DataType [0..1] « dateTime | Period | Timing » When the request was made authoredOn : dateTime [0..1] The device, practitioner, etc. who initiated the request requester : Reference [0..1] « Practitioner | PractitionerRole | Organization | Patient | RelatedPerson | Device » Who is intended to fulfill the request supplier : Reference [0..*] « Organization | HealthcareService » The reason why the supply item was requested reasonCode reason : CodeableConcept DataType [0..*] « Condition | Observation | DiagnosticReport | DocumentReference ; The reason why the supply item was requested. (Strength=Example) SupplyRequestReason ?? » The reason why the supply item was requested reasonReference : Reference [0..*] « Condition | Observation | DiagnosticReport | DocumentReference » Where the supply is expected to come from deliverFrom : Reference [0..1] « Organization | Location » Where the supply is destined to go deliverTo : Reference [0..1] « Organization | Location | Patient » Parameter A code or string that identifies the device detail being asserted code : CodeableConcept [0..1] The value of the device detail value[x] : Type DataType [0..1] « CodeableConcept | Quantity | Range | boolean » Specific parameters for the ordered item. For example, the size of the indicated item parameter [0..*]

XML Template

<SupplyRequest xmlns="http://hl7.org/fhir"> doco
 <!-- from Resource: id, meta, implicitRules, and language -->
 <!-- from DomainResource: text, contained, extension, and modifierExtension -->
 <identifier><!-- 0..* Identifier Business Identifier for SupplyRequest --></identifier>
 <status value="[code]"/><!-- 0..1 draft | active | suspended + -->
 <category><!-- 0..1 CodeableConcept The kind of supply (central, non-stock, etc.) --></category>
 <priority value="[code]"/><!-- 0..1 routine | urgent | asap | stat -->
 <</item[x]>

 <item><!-- 1..1 CodeableReference(Device|DeviceDefinition|Medication|Substance) Medication, Substance, or Device requested to be supplied --></item>

 <quantity><!-- 1..1 Quantity The requested amount of the item indicated --></quantity>
 <parameter>  <!-- 0..* Ordered item details -->
  <code><!-- 0..1 CodeableConcept Item detail --></code>
  <value[x]><!-- 0..1 CodeableConcept|Quantity|Range|boolean Value of detail --></value[x]>
 </parameter>
 <occurrence[x]><!-- 0..1 dateTime|Period|Timing When the request should be fulfilled --></occurrence[x]>
 <authoredOn value="[dateTime]"/><!-- 0..1 When the request was made -->
 <|
   </requester>
 <</supplier>
 <</reasonCode>
 <|
   </reasonReference>
 <</deliverFrom>
 <</deliverTo>

 <requester><!-- 0..1 Reference(Device|Organization|Patient|Practitioner|
   PractitionerRole|RelatedPerson) Individual making the request --></requester>
 <supplier><!-- 0..* Reference(HealthcareService|Organization) Who is intended to fulfill the request --></supplier>
 <reason><!-- 0..* CodeableReference(Condition|DiagnosticReport|DocumentReference|
   Observation) The reason why the supply item was requested --></reason>
 <deliverFrom><!-- 0..1 Reference(Location|Organization) The origin of the supply --></deliverFrom>
 <deliverTo><!-- 0..1 Reference(Location|Organization|Patient) The destination of the supply --></deliverTo>

</SupplyRequest>

JSON Template

{doco
  "resourceType" : "SupplyRequest",
  // from Resource: id, meta, implicitRules, and language
  // from DomainResource: text, contained, extension, and modifierExtension
  "identifier" : [{ Identifier }], // Business Identifier for SupplyRequest
  "status" : "<code>", // draft | active | suspended +
  "category" : { CodeableConcept }, // The kind of supply (central, non-stock, etc.)
  "priority" : "<code>", // routine | urgent | asap | stat
  
  " },
  " },

  "item" : { CodeableReference(Device|DeviceDefinition|Medication|Substance) }, // R!  Medication, Substance, or Device requested to be supplied

  "quantity" : { Quantity }, // R!  The requested amount of the item indicated
  "parameter" : [{ // Ordered item details
    "code" : { CodeableConcept }, // Item detail
    // value[x]: Value of detail. One of these 4:
    "valueCodeableConcept" : { CodeableConcept }
    "valueQuantity" : { Quantity }
    "valueRange" : { Range }
    "valueBoolean" : <boolean>
  }],
  // occurrence[x]: When the request should be fulfilled. One of these 3:
  "occurrenceDateTime" : "<dateTime>",
  "occurrencePeriod" : { Period },
  "occurrenceTiming" : { Timing },
  "authoredOn" : "<dateTime>", // When the request was made
  "|
   
  "
  "
  "|
   
  "
  "

  "requester" : { Reference(Device|Organization|Patient|Practitioner|
   PractitionerRole|RelatedPerson) }, // Individual making the request
  "supplier" : [{ Reference(HealthcareService|Organization) }], // Who is intended to fulfill the request
  "reason" : [{ CodeableReference(Condition|DiagnosticReport|DocumentReference|
   Observation) }], // The reason why the supply item was requested
  "deliverFrom" : { Reference(Location|Organization) }, // The origin of the supply
  "deliverTo" : { Reference(Location|Organization|Patient) } // The destination of the supply

}

Turtle Template

@prefix fhir: <http://hl7.org/fhir/> .doco
[ a fhir:SupplyRequest;
  fhir:nodeRole fhir:treeRoot; # if this is the parser root
  # from Resource: .id, .meta, .implicitRules, and .language
  # from DomainResource: .text, .contained, .extension, and .modifierExtension
  fhir:SupplyRequest.identifier [ Identifier ], ... ; # 0..* Business Identifier for SupplyRequest
  fhir:SupplyRequest.status [ code ]; # 0..1 draft | active | suspended +
  fhir:SupplyRequest.category [ CodeableConcept ]; # 0..1 The kind of supply (central, non-stock, etc.)
  fhir:SupplyRequest.priority [ code ]; # 0..1 routine | urgent | asap | stat
  # . One of these 2
    fhir: ]
    fhir:) ]

  fhir:SupplyRequest.item [ CodeableReference(Device|DeviceDefinition|Medication|Substance) ]; # 1..1 Medication, Substance, or Device requested to be supplied

  fhir:SupplyRequest.quantity [ Quantity ]; # 1..1 The requested amount of the item indicated
  fhir:SupplyRequest.parameter [ # 0..* Ordered item details
    fhir:SupplyRequest.parameter.code [ CodeableConcept ]; # 0..1 Item detail
    # SupplyRequest.parameter.value[x] : 0..1 Value of detail. One of these 4
      fhir:SupplyRequest.parameter.valueCodeableConcept [ CodeableConcept ]
      fhir:SupplyRequest.parameter.valueQuantity [ Quantity ]
      fhir:SupplyRequest.parameter.valueRange [ Range ]
      fhir:SupplyRequest.parameter.valueBoolean [ boolean ]
  ], ...;
  # SupplyRequest.occurrence[x] : 0..1 When the request should be fulfilled. One of these 3
    fhir:SupplyRequest.occurrenceDateTime [ dateTime ]
    fhir:SupplyRequest.occurrencePeriod [ Period ]
    fhir:SupplyRequest.occurrenceTiming [ Timing ]
  fhir:SupplyRequest.authoredOn [ dateTime ]; # 0..1 When the request was made
  fhir:
  fhir:
  fhir:
  fhir:
  fhir:
  fhir:

  fhir:SupplyRequest.requester [ Reference(Device|Organization|Patient|Practitioner|PractitionerRole|RelatedPerson) ]; # 0..1 Individual making the request
  fhir:SupplyRequest.supplier [ Reference(HealthcareService|Organization) ], ... ; # 0..* Who is intended to fulfill the request
  fhir:SupplyRequest.reason [ CodeableReference(Condition|DiagnosticReport|DocumentReference|Observation) ], ... ; # 0..* The reason why the supply item was requested
  fhir:SupplyRequest.deliverFrom [ Reference(Location|Organization) ]; # 0..1 The origin of the supply
  fhir:SupplyRequest.deliverTo [ Reference(Location|Organization|Patient) ]; # 0..1 The destination of the supply

]

Changes since R3

SupplyRequest
SupplyRequest.identifier Max Cardinality changed from 1 to * SupplyRequest.status
  • Change value set from http://hl7.org/fhir/ValueSet/supplyrequest-status http://hl7.org/fhir/ValueSet/supplyrequest-status|4.0.0 to http://hl7.org/fhir/ValueSet/supplyrequest-status|4.0.1 http://hl7.org/fhir/ValueSet/supplyrequest-status|4.4.0
SupplyRequest.priority
  • Change value set from http://hl7.org/fhir/ValueSet/request-priority http://hl7.org/fhir/ValueSet/request-priority|4.0.0 to http://hl7.org/fhir/ValueSet/request-priority|4.0.1 SupplyRequest.item[x] Added Mandatory Element http://hl7.org/fhir/ValueSet/request-priority|4.4.0
SupplyRequest.quantity SupplyRequest.item
  • Added Mandatory Element
SupplyRequest.parameter Added Element SupplyRequest.parameter.code Added Element SupplyRequest.parameter.value[x] Added Element SupplyRequest.requester Type changed from BackboneElement to Reference(Practitioner | PractitionerRole | Organization | Patient | RelatedPerson | Device) SupplyRequest.supplier Type Reference: Added Target Type HealthcareService SupplyRequest.reasonCode Added Element SupplyRequest.reasonReference SupplyRequest.reason
  • Added Element
SupplyRequest.orderedItem deleted SupplyRequest.requester.agent SupplyRequest.item[x]
  • deleted
SupplyRequest.requester.onBehalfOf SupplyRequest.reasonCode
  • deleted
SupplyRequest.reason[x] SupplyRequest.reasonReference
  • deleted

See the Full Difference for further information

This analysis is available as XML or JSON .

See R3 <--> R4 Conversion Maps (status = 1 test that all execute ok. All tests pass round-trip testing and 1 r3 resources are invalid (0 errors). )

Structure

itemCodeableConcept CodeableConcept itemReference Reference ( Medication | Substance | Device )
Name Flags Card. Type Description & Constraints doco
. . SupplyRequest TU DomainResource Request for a medication, substance or device
Elements defined in Ancestors: id , meta , implicitRules , language , text , contained , extension , modifierExtension
. . . identifier Σ 0..* Identifier Business Identifier for SupplyRequest
. . . status ?! Σ 0..1 code draft | active | suspended +
SupplyRequestStatus ( Required )
. . . category Σ 0..1 CodeableConcept The kind of supply (central, non-stock, etc.)
Supply Type ( Example )
. . item[x] . item Σ 1..1 CodeableReference ( Medication | Substance | Device | DeviceDefinition ) Medication, Substance, or Device requested to be supplied
SNOMED CT Supply Item ( Example )
. . . quantity Σ 1..1 Quantity The requested amount of the item indicated
. . . parameter 0..* BackboneElement Ordered item details
. . . . code 0..1 CodeableConcept Item detail
. . . . value[x] 0..1 Value of detail
. . . . . valueCodeableConcept CodeableConcept
. . . . . valueQuantity Quantity
. . . . . valueRange Range
. . . . . valueBoolean boolean
. . . occurrence[x] Σ 0..1 When the request should be fulfilled
. . . . occurrenceDateTime dateTime
. . . . occurrencePeriod Period
. . . . occurrenceTiming Timing
. . . authoredOn Σ 0..1 dateTime When the request was made
. . . requester Σ 0..1 Reference ( Practitioner | PractitionerRole | Organization | Patient | RelatedPerson | Device ) Individual making the request
. . . supplier Σ 0..* Reference ( Organization | HealthcareService ) Who is intended to fulfill the request
. . reasonCode . reason 0..* CodeableConcept The reason why the supply item was requested SupplyRequestReason ( Example ) reasonReference 0..* Reference CodeableReference ( Condition | Observation | DiagnosticReport | DocumentReference ) The reason why the supply item was requested
SupplyRequestReason ( Example )
. . . deliverFrom 0..1 Reference ( Organization | Location ) The origin of the supply
. . . deliverTo 0..1 Reference ( Organization | Location | Patient ) The destination of the supply

doco Documentation for this format

UML Diagram ( Legend )

SupplyRequest ( DomainResource ) Business identifiers assigned to this SupplyRequest by the author and/or other systems. These identifiers remain constant as the resource is updated and propagates from server to server identifier : Identifier [0..*] Status of the supply request (this element modifies the meaning of other elements) status : code [0..1] « Status of the supply request. (Strength=Required) SupplyRequestStatus ! » Category of supply, e.g. central, non-stock, etc. This is used to support work flows associated with the supply process category : CodeableConcept [0..1] « Category of supply request. (Strength=Example) SupplyType ?? » Indicates how quickly this SupplyRequest should be addressed with respect to other requests priority : code [0..1] « Identifies the level of importance to be assigned to actioning the request. (Strength=Required) RequestPriority ! » The item that is requested to be supplied. This is either a link to a resource representing the details of the item or a code that identifies the item from a known list item[x] item : Type DataType [1..1] « CodeableConcept | Reference ( Medication | Substance | Device ); | DeviceDefinition ; The item that was requested. (Strength=Example) SNOMEDCTSupplyItem ?? » The amount that is being ordered of the indicated item quantity : Quantity [1..1] When the request should be fulfilled occurrence[x] : Type DataType [0..1] « dateTime | Period | Timing » When the request was made authoredOn : dateTime [0..1] The device, practitioner, etc. who initiated the request requester : Reference [0..1] « Practitioner | PractitionerRole | Organization | Patient | RelatedPerson | Device » Who is intended to fulfill the request supplier : Reference [0..*] « Organization | HealthcareService » The reason why the supply item was requested reasonCode reason : CodeableConcept DataType [0..*] « Condition | Observation | DiagnosticReport | DocumentReference ; The reason why the supply item was requested. (Strength=Example) SupplyRequestReason ?? » The reason why the supply item was requested reasonReference : Reference [0..*] « Condition | Observation | DiagnosticReport | DocumentReference » Where the supply is expected to come from deliverFrom : Reference [0..1] « Organization | Location » Where the supply is destined to go deliverTo : Reference [0..1] « Organization | Location | Patient » Parameter A code or string that identifies the device detail being asserted code : CodeableConcept [0..1] The value of the device detail value[x] : Type DataType [0..1] « CodeableConcept | Quantity | Range | boolean » Specific parameters for the ordered item. For example, the size of the indicated item parameter [0..*]

XML Template

<SupplyRequest xmlns="http://hl7.org/fhir"> doco
 <!-- from Resource: id, meta, implicitRules, and language -->
 <!-- from DomainResource: text, contained, extension, and modifierExtension -->
 <identifier><!-- 0..* Identifier Business Identifier for SupplyRequest --></identifier>
 <status value="[code]"/><!-- 0..1 draft | active | suspended + -->
 <category><!-- 0..1 CodeableConcept The kind of supply (central, non-stock, etc.) --></category>
 <priority value="[code]"/><!-- 0..1 routine | urgent | asap | stat -->
 <</item[x]>

 <item><!-- 1..1 CodeableReference(Device|DeviceDefinition|Medication|Substance) Medication, Substance, or Device requested to be supplied --></item>

 <quantity><!-- 1..1 Quantity The requested amount of the item indicated --></quantity>
 <parameter>  <!-- 0..* Ordered item details -->
  <code><!-- 0..1 CodeableConcept Item detail --></code>
  <value[x]><!-- 0..1 CodeableConcept|Quantity|Range|boolean Value of detail --></value[x]>
 </parameter>
 <occurrence[x]><!-- 0..1 dateTime|Period|Timing When the request should be fulfilled --></occurrence[x]>
 <authoredOn value="[dateTime]"/><!-- 0..1 When the request was made -->
 <|
   </requester>
 <</supplier>
 <</reasonCode>
 <|
   </reasonReference>
 <</deliverFrom>
 <</deliverTo>

 <requester><!-- 0..1 Reference(Device|Organization|Patient|Practitioner|
   PractitionerRole|RelatedPerson) Individual making the request --></requester>
 <supplier><!-- 0..* Reference(HealthcareService|Organization) Who is intended to fulfill the request --></supplier>
 <reason><!-- 0..* CodeableReference(Condition|DiagnosticReport|DocumentReference|
   Observation) The reason why the supply item was requested --></reason>
 <deliverFrom><!-- 0..1 Reference(Location|Organization) The origin of the supply --></deliverFrom>
 <deliverTo><!-- 0..1 Reference(Location|Organization|Patient) The destination of the supply --></deliverTo>

</SupplyRequest>

JSON Template

{doco
  "resourceType" : "SupplyRequest",
  // from Resource: id, meta, implicitRules, and language
  // from DomainResource: text, contained, extension, and modifierExtension
  "identifier" : [{ Identifier }], // Business Identifier for SupplyRequest
  "status" : "<code>", // draft | active | suspended +
  "category" : { CodeableConcept }, // The kind of supply (central, non-stock, etc.)
  "priority" : "<code>", // routine | urgent | asap | stat
  
  " },
  " },

  "item" : { CodeableReference(Device|DeviceDefinition|Medication|Substance) }, // R!  Medication, Substance, or Device requested to be supplied

  "quantity" : { Quantity }, // R!  The requested amount of the item indicated
  "parameter" : [{ // Ordered item details
    "code" : { CodeableConcept }, // Item detail
    // value[x]: Value of detail. One of these 4:
    "valueCodeableConcept" : { CodeableConcept }
    "valueQuantity" : { Quantity }
    "valueRange" : { Range }
    "valueBoolean" : <boolean>
  }],
  // occurrence[x]: When the request should be fulfilled. One of these 3:
  "occurrenceDateTime" : "<dateTime>",
  "occurrencePeriod" : { Period },
  "occurrenceTiming" : { Timing },
  "authoredOn" : "<dateTime>", // When the request was made
  "|
   
  "
  "
  "|
   
  "
  "

  "requester" : { Reference(Device|Organization|Patient|Practitioner|
   PractitionerRole|RelatedPerson) }, // Individual making the request
  "supplier" : [{ Reference(HealthcareService|Organization) }], // Who is intended to fulfill the request
  "reason" : [{ CodeableReference(Condition|DiagnosticReport|DocumentReference|
   Observation) }], // The reason why the supply item was requested
  "deliverFrom" : { Reference(Location|Organization) }, // The origin of the supply
  "deliverTo" : { Reference(Location|Organization|Patient) } // The destination of the supply

}

Turtle Template

@prefix fhir: <http://hl7.org/fhir/> .doco
[ a fhir:SupplyRequest;
  fhir:nodeRole fhir:treeRoot; # if this is the parser root
  # from Resource: .id, .meta, .implicitRules, and .language
  # from DomainResource: .text, .contained, .extension, and .modifierExtension
  fhir:SupplyRequest.identifier [ Identifier ], ... ; # 0..* Business Identifier for SupplyRequest
  fhir:SupplyRequest.status [ code ]; # 0..1 draft | active | suspended +
  fhir:SupplyRequest.category [ CodeableConcept ]; # 0..1 The kind of supply (central, non-stock, etc.)
  fhir:SupplyRequest.priority [ code ]; # 0..1 routine | urgent | asap | stat
  # . One of these 2
    fhir: ]
    fhir:) ]

  fhir:SupplyRequest.item [ CodeableReference(Device|DeviceDefinition|Medication|Substance) ]; # 1..1 Medication, Substance, or Device requested to be supplied

  fhir:SupplyRequest.quantity [ Quantity ]; # 1..1 The requested amount of the item indicated
  fhir:SupplyRequest.parameter [ # 0..* Ordered item details
    fhir:SupplyRequest.parameter.code [ CodeableConcept ]; # 0..1 Item detail
    # SupplyRequest.parameter.value[x] : 0..1 Value of detail. One of these 4
      fhir:SupplyRequest.parameter.valueCodeableConcept [ CodeableConcept ]
      fhir:SupplyRequest.parameter.valueQuantity [ Quantity ]
      fhir:SupplyRequest.parameter.valueRange [ Range ]
      fhir:SupplyRequest.parameter.valueBoolean [ boolean ]
  ], ...;
  # SupplyRequest.occurrence[x] : 0..1 When the request should be fulfilled. One of these 3
    fhir:SupplyRequest.occurrenceDateTime [ dateTime ]
    fhir:SupplyRequest.occurrencePeriod [ Period ]
    fhir:SupplyRequest.occurrenceTiming [ Timing ]
  fhir:SupplyRequest.authoredOn [ dateTime ]; # 0..1 When the request was made
  fhir:
  fhir:
  fhir:
  fhir:
  fhir:
  fhir:

  fhir:SupplyRequest.requester [ Reference(Device|Organization|Patient|Practitioner|PractitionerRole|RelatedPerson) ]; # 0..1 Individual making the request
  fhir:SupplyRequest.supplier [ Reference(HealthcareService|Organization) ], ... ; # 0..* Who is intended to fulfill the request
  fhir:SupplyRequest.reason [ CodeableReference(Condition|DiagnosticReport|DocumentReference|Observation) ], ... ; # 0..* The reason why the supply item was requested
  fhir:SupplyRequest.deliverFrom [ Reference(Location|Organization) ]; # 0..1 The origin of the supply
  fhir:SupplyRequest.deliverTo [ Reference(Location|Organization|Patient) ]; # 0..1 The destination of the supply

]

Changes since Release 3

SupplyRequest
SupplyRequest.identifier Max Cardinality changed from 1 to * SupplyRequest.status
  • Change value set from http://hl7.org/fhir/ValueSet/supplyrequest-status http://hl7.org/fhir/ValueSet/supplyrequest-status|4.0.0 to http://hl7.org/fhir/ValueSet/supplyrequest-status|4.0.1 http://hl7.org/fhir/ValueSet/supplyrequest-status|4.4.0
SupplyRequest.priority
  • Change value set from http://hl7.org/fhir/ValueSet/request-priority http://hl7.org/fhir/ValueSet/request-priority|4.0.0 to http://hl7.org/fhir/ValueSet/request-priority|4.0.1 SupplyRequest.item[x] Added Mandatory Element http://hl7.org/fhir/ValueSet/request-priority|4.4.0
SupplyRequest.quantity SupplyRequest.item
  • Added Mandatory Element
SupplyRequest.parameter Added Element SupplyRequest.parameter.code Added Element SupplyRequest.parameter.value[x] Added Element SupplyRequest.requester Type changed from BackboneElement to Reference(Practitioner | PractitionerRole | Organization | Patient | RelatedPerson | Device) SupplyRequest.supplier Type Reference: Added Target Type HealthcareService SupplyRequest.reasonCode Added Element SupplyRequest.reasonReference SupplyRequest.reason
  • Added Element
SupplyRequest.orderedItem deleted SupplyRequest.requester.agent SupplyRequest.item[x]
  • deleted
SupplyRequest.requester.onBehalfOf SupplyRequest.reasonCode
  • deleted
SupplyRequest.reason[x] SupplyRequest.reasonReference
  • deleted

See the Full Difference for further information

This analysis is available as XML or JSON .

See R3 <--> R4 Conversion Maps (status = 1 test that all execute ok. All tests pass round-trip testing and 1 r3 resources are invalid (0 errors). )

 

See the Profiles & Extensions and the alternate definitions: Master Definition XML + JSON , XML Schema / Schematron + JSON Schema , ShEx (for Turtle ) + see the extensions , the spreadsheet version & the dependency analysis a

Path Definition Type Reference
SupplyRequest.status Status of the supply request. Required SupplyRequestStatus
SupplyRequest.category Category of supply request. Example SupplyType
SupplyRequest.priority Identifies the level of importance to be assigned to actioning the request. Required RequestPriority
SupplyRequest.item[x] SupplyRequest.item The item that was requested. Example SNOMEDCTSupplyItem
SupplyRequest.parameter.code A code that identifies the device detail. Unknown No details provided yet
SupplyRequest.reasonCode SupplyRequest.reason The reason why the supply item was requested. Example SupplyRequestReason

Search parameters for this resource. The common parameters also apply. See Searching for more information about searching in REST, messaging, and services.

Name Type Description Expression In Common
category token The kind of supply (central, non-stock, etc.) SupplyRequest.category
date N date When the request was made SupplyRequest.authoredOn 17 Resources
identifier token Business Identifier for SupplyRequest SupplyRequest.identifier 30 Resources
requester reference Individual making the request SupplyRequest.requester
( Practitioner , Organization , Device , Patient , PractitionerRole , RelatedPerson )
status N token draft | active | suspended + SupplyRequest.status
subject reference The destination of the supply SupplyRequest.deliverTo
( Organization , Patient , Location )
supplier reference Who is intended to fulfill the request SupplyRequest.supplier
( Organization , HealthcareService )