Current Build

Переводит команда Health Samurai . Приглашаем поучаствовать в русификации стандарта FHIR: GitHub , Email.

12.21 Ресурс SupplyRequest - Назначение

Orders and Observations Work GroupMaturity Level: 1 Trial UseSecurity Category: Patient Compartments: Device, Patient, Practitioner, RelatedPerson

Запись запроса на медикамент, вещество или устройство, используемое в здравоохранении.

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.

[todo: where to send input?]

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

На этот ресурс ссылается SupplyDelivery

Структура

ИмяФлагиКард.ТипОписание и ограниченияdoco
.. SupplyRequest TUDomainResourceЗапрос на медикамент, вещество или устройство
Элементы, определённые в прародителе: id, meta, implicitRules, language, text, contained, extension, modifierExtension
... identifier Σ0..*IdentifierBusiness Identifier for SupplyRequest
... status ?!Σ0..1codedraft | active | suspended +
SupplyRequestStatus (Required)
... category Σ0..1CodeableConceptВид поставки (центральная, неакционерная и т. д.)
Supply Type (Example)
... priority Σ0..1coderoutine | urgent | asap | stat
Request priority (Required)
... item[x] Σ1..1Медицинское средство, вещество или устройство, поставку которого запросили
SNOMED CT Supply Item (Example)
.... itemCodeableConceptCodeableConcept
.... itemReferenceReference(Medication | Substance | Device)
... quantity Σ1..1QuantityThe requested amount of the item indicated
... parameter 0..*BackboneElementOrdered item details
.... code 0..1CodeableConceptItem detail
.... value[x] 0..1Value of detail
..... valueCodeableConceptCodeableConcept
..... valueQuantityQuantity
..... valueRangeRange
..... valueBooleanboolean
... occurrence[x] Σ0..1Когда этот запрос должен быть выполнен
.... occurrenceDateTimedateTime
.... occurrencePeriodPeriod
.... occurrenceTimingTiming
... authoredOn Σ0..1dateTimeКогда был сделан запрос
... requester Σ0..1Reference(Practitioner | PractitionerRole | Organization | Patient | RelatedPerson | Device)Individual making the request
... supplier Σ0..*Reference(Organization | HealthcareService)Кто должен выполнить этот запрос
... reasonCode 0..*CodeableConceptThe reason Зачем был заказан этот предмет поставки
SupplyRequestReason (Example)
... reasonReference 0..*Reference(Condition | Observation | DiagnosticReport | DocumentReference)The reason Зачем был заказан этот предмет поставки
... deliverFrom 0..1Reference(Organization | Location)The origin of the supply
... deliverTo 0..1Reference(Organization | Location | Patient)The destination of the supply

doco Документация по этому формату

UML-диаграмма (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 serveridentifier : Identifier [0..*]Статус запроса на поставку (this element modifies the meaning of other elements)status : code [0..1] « Статус запроса на поставку. (Strength=Required)SupplyRequestStatus! »Категория поставки, например центральная, неакционерная и т. п. Используется для поддержания рабочих процессов, связанных с процессом поставкиcategory : CodeableConcept [0..1] « Категория запроса на поставку. (Strength=Example)SupplyType?? »Indicates how quickly this SupplyRequest should be addressed with respect to other requestspriority : 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 listitem[x] : Type [1..1] « CodeableConcept|Reference(Medication| Substance|Device); The item that was requested. (Strength=Example)SNOMEDCTSupplyItem?? »The amount that is being ordered of the indicated itemquantity : Quantity [1..1]Когда этот запрос должен быть выполненoccurrence[x] : Type [0..1] « dateTime|Period|Timing »Когда был сделан запросauthoredOn : dateTime [0..1]The device, practitioner, etc. who initiated the requestrequester : Reference [0..1] « Practitioner|PractitionerRole| Organization|Patient|RelatedPerson|Device »Кто должен выполнить этот запросsupplier : Reference [0..*] « Organization|HealthcareService »The reason Зачем был заказан этот предмет поставкиreasonCode : CodeableConcept [0..*] « The reason Зачем был заказан этот предмет поставки. (Strength=Example)SupplyRequestReason?? »The reason Зачем был заказан этот предмет поставкиreasonReference : Reference [0..*] « Condition|Observation| DiagnosticReport|DocumentReference »Where the supply is expected to come fromdeliverFrom : Reference [0..1] « Organization|Location »Where the supply is destined to godeliverTo : Reference [0..1] « Organization|Location|Patient »ParameterA code or string that identifies the device detail being assertedcode : CodeableConcept [0..1]The value of the device detailvalue[x] : Type [0..1] « CodeableConcept|Quantity|Range|boolean »Specific parameters for the ordered item. For example, the size of the indicated itemparameter[0..*]

XML-шаблон

<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 Вид поставки (центральная, неакционерная и т. д.) --></category>
 <priority value="[code]"/><!-- 0..1 routine | urgent | asap | stat -->
 <item[x]><!-- 1..1 CodeableConcept|Reference(Medication|Substance|Device) Медицинское средство, вещество или устройство, поставку которого запросили --></item[x]>
 <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 Когда этот запрос должен быть выполнен --></occurrence[x]>
 <authoredOn value="[dateTime]"/><!-- 0..1 Когда был сделан запрос -->
 <requester><!-- 0..1 Reference(Practitioner|PractitionerRole|Organization|
   Patient|RelatedPerson|Device) Individual making the request --></requester>
 <supplier><!-- 0..* Reference(Organization|HealthcareService) Кто должен выполнить этот запрос --></supplier>
 <reasonCode><!-- 0..* CodeableConcept The reason Зачем был заказан этот предмет поставки --></reasonCode>
 <reasonReference><!-- 0..* Reference(Condition|Observation|DiagnosticReport|
   DocumentReference) The reason Зачем был заказан этот предмет поставки --></reasonReference>
 <deliverFrom><!-- 0..1 Reference(Organization|Location) The origin of the supply --></deliverFrom>
 <deliverTo><!-- 0..1 Reference(Organization|Location|Patient) The destination of the supply --></deliverTo>
</SupplyRequest>

JSON-шаблон

{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 }, // Вид поставки (центральная, неакционерная и т. д.)
  "priority" : "<code>", // routine | urgent | asap | stat
  // item[x]: Медицинское средство, вещество или устройство, поставку которого запросили. One of these 2:
  "itemCodeableConcept" : { CodeableConcept },
  "itemReference" : { Reference(Medication|Substance|Device) },
  "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]: Когда этот запрос должен быть выполнен. One of these 3:
  "occurrenceDateTime" : "<dateTime>",
  "occurrencePeriod" : { Period },
  "occurrenceTiming" : { Timing },
  "authoredOn" : "<dateTime>", // Когда был сделан запрос
  "requester" : { Reference(Practitioner|PractitionerRole|Organization|
   Patient|RelatedPerson|Device) }, // Individual making the request
  "supplier" : [{ Reference(Organization|HealthcareService) }], // Кто должен выполнить этот запрос
  "reasonCode" : [{ CodeableConcept }], // The reason Зачем был заказан этот предмет поставки
  "reasonReference" : [{ Reference(Condition|Observation|DiagnosticReport|
   DocumentReference) }], // The reason Зачем был заказан этот предмет поставки
  "deliverFrom" : { Reference(Organization|Location) }, // The origin of the supply
  "deliverTo" : { Reference(Organization|Location|Patient) } // The destination of the supply
}

Turtle-шаблон

@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 Вид поставки (центральная, неакционерная и т. д.)
  fhir:SupplyRequest.priority [ code ]; # 0..1 routine | urgent | asap | stat
  # SupplyRequest.item[x] : 1..1 Медицинское средство, вещество или устройство, поставку которого запросили. One of these 2
    fhir:SupplyRequest.itemCodeableConcept [ CodeableConcept ]
    fhir:SupplyRequest.itemReference [ Reference(Medication|Substance|Device) ]
  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 Когда этот запрос должен быть выполнен. One of these 3
    fhir:SupplyRequest.occurrenceDateTime [ dateTime ]
    fhir:SupplyRequest.occurrencePeriod [ Period ]
    fhir:SupplyRequest.occurrenceTiming [ Timing ]
  fhir:SupplyRequest.authoredOn [ dateTime ]; # 0..1 Когда был сделан запрос
  fhir:SupplyRequest.requester [ Reference(Practitioner|PractitionerRole|Organization|Patient|RelatedPerson|Device) ]; # 0..1 Individual making the request
  fhir:SupplyRequest.supplier [ Reference(Organization|HealthcareService) ], ... ; # 0..* Кто должен выполнить этот запрос
  fhir:SupplyRequest.reasonCode [ CodeableConcept ], ... ; # 0..* The reason Зачем был заказан этот предмет поставки
  fhir:SupplyRequest.reasonReference [ Reference(Condition|Observation|DiagnosticReport|DocumentReference) ], ... ; # 0..* The reason Зачем был заказан этот предмет поставки
  fhir:SupplyRequest.deliverFrom [ Reference(Organization|Location) ]; # 0..1 The origin of the supply
  fhir:SupplyRequest.deliverTo [ Reference(Organization|Location|Patient) ]; # 0..1 The destination of the supply
]

Changes since R3

SupplyRequest
SupplyRequest.identifier
  • Max Cardinality changed from 1 to *
SupplyRequest.item[x]
  • Added Mandatory Element
SupplyRequest.quantity
  • 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
  • Added Element
SupplyRequest.orderedItem
  • deleted
SupplyRequest.requester.agent
  • deleted
SupplyRequest.requester.onBehalfOf
  • deleted
SupplyRequest.reason[x]
  • deleted

See the Full Difference for further information

This analysis is available as XML or JSON.

See R3 <--> R4 Conversion Maps (status = 1 test of which 1 fail to execute.)

Структура

ИмяФлагиКард.ТипОписание и ограниченияdoco
.. SupplyRequest TUDomainResourceЗапрос на медикамент, вещество или устройство
Элементы, определённые в прародителе: id, meta, implicitRules, language, text, contained, extension, modifierExtension
... identifier Σ0..*IdentifierBusiness Identifier for SupplyRequest
... status ?!Σ0..1codedraft | active | suspended +
SupplyRequestStatus (Required)
... category Σ0..1CodeableConceptВид поставки (центральная, неакционерная и т. д.)
Supply Type (Example)
... priority Σ0..1coderoutine | urgent | asap | stat
Request priority (Required)
... item[x] Σ1..1Медицинское средство, вещество или устройство, поставку которого запросили
SNOMED CT Supply Item (Example)
.... itemCodeableConceptCodeableConcept
.... itemReferenceReference(Medication | Substance | Device)
... quantity Σ1..1QuantityThe requested amount of the item indicated
... parameter 0..*BackboneElementOrdered item details
.... code 0..1CodeableConceptItem detail
.... value[x] 0..1Value of detail
..... valueCodeableConceptCodeableConcept
..... valueQuantityQuantity
..... valueRangeRange
..... valueBooleanboolean
... occurrence[x] Σ0..1Когда этот запрос должен быть выполнен
.... occurrenceDateTimedateTime
.... occurrencePeriodPeriod
.... occurrenceTimingTiming
... authoredOn Σ0..1dateTimeКогда был сделан запрос
... requester Σ0..1Reference(Practitioner | PractitionerRole | Organization | Patient | RelatedPerson | Device)Individual making the request
... supplier Σ0..*Reference(Organization | HealthcareService)Кто должен выполнить этот запрос
... reasonCode 0..*CodeableConceptThe reason Зачем был заказан этот предмет поставки
SupplyRequestReason (Example)
... reasonReference 0..*Reference(Condition | Observation | DiagnosticReport | DocumentReference)The reason Зачем был заказан этот предмет поставки
... deliverFrom 0..1Reference(Organization | Location)The origin of the supply
... deliverTo 0..1Reference(Organization | Location | Patient)The destination of the supply

doco Документация по этому формату

UML-диаграмма (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 serveridentifier : Identifier [0..*]Статус запроса на поставку (this element modifies the meaning of other elements)status : code [0..1] « Статус запроса на поставку. (Strength=Required)SupplyRequestStatus! »Категория поставки, например центральная, неакционерная и т. п. Используется для поддержания рабочих процессов, связанных с процессом поставкиcategory : CodeableConcept [0..1] « Категория запроса на поставку. (Strength=Example)SupplyType?? »Indicates how quickly this SupplyRequest should be addressed with respect to other requestspriority : 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 listitem[x] : Type [1..1] « CodeableConcept|Reference(Medication| Substance|Device); The item that was requested. (Strength=Example)SNOMEDCTSupplyItem?? »The amount that is being ordered of the indicated itemquantity : Quantity [1..1]Когда этот запрос должен быть выполненoccurrence[x] : Type [0..1] « dateTime|Period|Timing »Когда был сделан запросauthoredOn : dateTime [0..1]The device, practitioner, etc. who initiated the requestrequester : Reference [0..1] « Practitioner|PractitionerRole| Organization|Patient|RelatedPerson|Device »Кто должен выполнить этот запросsupplier : Reference [0..*] « Organization|HealthcareService »The reason Зачем был заказан этот предмет поставкиreasonCode : CodeableConcept [0..*] « The reason Зачем был заказан этот предмет поставки. (Strength=Example)SupplyRequestReason?? »The reason Зачем был заказан этот предмет поставкиreasonReference : Reference [0..*] « Condition|Observation| DiagnosticReport|DocumentReference »Where the supply is expected to come fromdeliverFrom : Reference [0..1] « Organization|Location »Where the supply is destined to godeliverTo : Reference [0..1] « Organization|Location|Patient »ParameterA code or string that identifies the device detail being assertedcode : CodeableConcept [0..1]The value of the device detailvalue[x] : Type [0..1] « CodeableConcept|Quantity|Range|boolean »Specific parameters for the ordered item. For example, the size of the indicated itemparameter[0..*]

XML-шаблон

<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 Вид поставки (центральная, неакционерная и т. д.) --></category>
 <priority value="[code]"/><!-- 0..1 routine | urgent | asap | stat -->
 <item[x]><!-- 1..1 CodeableConcept|Reference(Medication|Substance|Device) Медицинское средство, вещество или устройство, поставку которого запросили --></item[x]>
 <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 Когда этот запрос должен быть выполнен --></occurrence[x]>
 <authoredOn value="[dateTime]"/><!-- 0..1 Когда был сделан запрос -->
 <requester><!-- 0..1 Reference(Practitioner|PractitionerRole|Organization|
   Patient|RelatedPerson|Device) Individual making the request --></requester>
 <supplier><!-- 0..* Reference(Organization|HealthcareService) Кто должен выполнить этот запрос --></supplier>
 <reasonCode><!-- 0..* CodeableConcept The reason Зачем был заказан этот предмет поставки --></reasonCode>
 <reasonReference><!-- 0..* Reference(Condition|Observation|DiagnosticReport|
   DocumentReference) The reason Зачем был заказан этот предмет поставки --></reasonReference>
 <deliverFrom><!-- 0..1 Reference(Organization|Location) The origin of the supply --></deliverFrom>
 <deliverTo><!-- 0..1 Reference(Organization|Location|Patient) The destination of the supply --></deliverTo>
</SupplyRequest>

JSON-шаблон

{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 }, // Вид поставки (центральная, неакционерная и т. д.)
  "priority" : "<code>", // routine | urgent | asap | stat
  // item[x]: Медицинское средство, вещество или устройство, поставку которого запросили. One of these 2:
  "itemCodeableConcept" : { CodeableConcept },
  "itemReference" : { Reference(Medication|Substance|Device) },
  "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]: Когда этот запрос должен быть выполнен. One of these 3:
  "occurrenceDateTime" : "<dateTime>",
  "occurrencePeriod" : { Period },
  "occurrenceTiming" : { Timing },
  "authoredOn" : "<dateTime>", // Когда был сделан запрос
  "requester" : { Reference(Practitioner|PractitionerRole|Organization|
   Patient|RelatedPerson|Device) }, // Individual making the request
  "supplier" : [{ Reference(Organization|HealthcareService) }], // Кто должен выполнить этот запрос
  "reasonCode" : [{ CodeableConcept }], // The reason Зачем был заказан этот предмет поставки
  "reasonReference" : [{ Reference(Condition|Observation|DiagnosticReport|
   DocumentReference) }], // The reason Зачем был заказан этот предмет поставки
  "deliverFrom" : { Reference(Organization|Location) }, // The origin of the supply
  "deliverTo" : { Reference(Organization|Location|Patient) } // The destination of the supply
}

Turtle-шаблон

@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 Вид поставки (центральная, неакционерная и т. д.)
  fhir:SupplyRequest.priority [ code ]; # 0..1 routine | urgent | asap | stat
  # SupplyRequest.item[x] : 1..1 Медицинское средство, вещество или устройство, поставку которого запросили. One of these 2
    fhir:SupplyRequest.itemCodeableConcept [ CodeableConcept ]
    fhir:SupplyRequest.itemReference [ Reference(Medication|Substance|Device) ]
  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 Когда этот запрос должен быть выполнен. One of these 3
    fhir:SupplyRequest.occurrenceDateTime [ dateTime ]
    fhir:SupplyRequest.occurrencePeriod [ Period ]
    fhir:SupplyRequest.occurrenceTiming [ Timing ]
  fhir:SupplyRequest.authoredOn [ dateTime ]; # 0..1 Когда был сделан запрос
  fhir:SupplyRequest.requester [ Reference(Practitioner|PractitionerRole|Organization|Patient|RelatedPerson|Device) ]; # 0..1 Individual making the request
  fhir:SupplyRequest.supplier [ Reference(Organization|HealthcareService) ], ... ; # 0..* Кто должен выполнить этот запрос
  fhir:SupplyRequest.reasonCode [ CodeableConcept ], ... ; # 0..* The reason Зачем был заказан этот предмет поставки
  fhir:SupplyRequest.reasonReference [ Reference(Condition|Observation|DiagnosticReport|DocumentReference) ], ... ; # 0..* The reason Зачем был заказан этот предмет поставки
  fhir:SupplyRequest.deliverFrom [ Reference(Organization|Location) ]; # 0..1 The origin of the supply
  fhir:SupplyRequest.deliverTo [ Reference(Organization|Location|Patient) ]; # 0..1 The destination of the supply
]

Changes since Release 3

SupplyRequest
SupplyRequest.identifier
  • Max Cardinality changed from 1 to *
SupplyRequest.item[x]
  • Added Mandatory Element
SupplyRequest.quantity
  • 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
  • Added Element
SupplyRequest.orderedItem
  • deleted
SupplyRequest.requester.agent
  • deleted
SupplyRequest.requester.onBehalfOf
  • deleted
SupplyRequest.reason[x]
  • deleted

See the Full Difference for further information

This analysis is available as XML or JSON.

See R3 <--> R4 Conversion Maps (status = 1 test of which 1 fail to execute.)

 

See the Profiles & Extensions and the Альтернативные определения: Основное определение XML + JSON, XML Schema/Schematron + JSON Schema, ShEx (for Turtle) + see the extensions & the Анализ зависимостей

PathОписаниеТипСсылка
SupplyRequest.status Статус запроса на поставку.RequiredSupplyRequestStatus
SupplyRequest.category Категория запроса на поставку.ExampleSupplyType
SupplyRequest.priority Identifies the level of importance to be assigned to actioning the request.RequiredRequestPriority
SupplyRequest.item[x] The item that was requested.ExampleSNOMEDCTSupplyItem
SupplyRequest.parameter.code A code that identifies the device detail.НеизвестенНет сведений
SupplyRequest.reasonCode The reason Зачем был заказан этот предмет поставки.ExampleSupplyRequestReason

Параметры поиска для этого ресурса. Также к нему применяются общие параметры. Более подробную информацию о поиске в REST, обмене сообщениями и сервисах см. в разделе Поиск.

ИмяТипОпределениеВыражениеIn Common
categorytokenВид поставки (центральная, неакционерная и т. д.)SupplyRequest.category
datedateКогда был сделан запросSupplyRequest.authoredOn17 Resources
identifiertokenBusiness Identifier for SupplyRequestSupplyRequest.identifier30 Resources
requesterreferenceIndividual making the requestSupplyRequest.requester
(Practitioner, Organization, Device, Patient, PractitionerRole, RelatedPerson)
statustokendraft | active | suspended +SupplyRequest.status
subjectreferenceThe destination of the supplySupplyRequest.deliverTo
(Organization, Patient, Location)
supplierreferenceКто должен выполнить этот запросSupplyRequest.supplier
(Organization, HealthcareService)