Stream: implementers
Topic: ServiceRequest.quantity
Craig Newman (Mar 07 2019 at 14:30):
The definition of ServiceRequest.quantity is "An amount of service being requested which can be a quantity ( for example $1,500 home modification), a ratio ( for example, 20 half day visits per month), or a range (2.0 to 1.8 Gy per fraction)." but I'm having trouble understanding what an "amount of service" is. Is this the amount of service done per instance of the service (a 20 min physiotherapy session) or the total number of services requested (5 physiotherapy sessions total) or something else completely? Does it vary depending on the intent (original-order versus instance-order) or the data type chosen for occurrence[x] (a single date/time versus a complex timing). None of the ServiceRequest example I looked at included quantity. Any insight would be appreciated.
Lloyd McKenzie (Mar 07 2019 at 15:01):
Agree that clarification (and examples) would be useful. Can you submit a change request.
Lloyd McKenzie (Mar 07 2019 at 15:01):
@Michelle (Moseman) Miller
Craig Newman (Mar 07 2019 at 15:10):
Happy to submit a change request. The examples I gave (a 20 min session or 5 sessions) seem to fit better OccurrenceTiming (.repeat.duration and .repeat.count respectively. So I'm still not sure what the .quantity clarification would be.
In v2, there is a quantity field (TQ1-1) which is "This field specifies the numeric quantity of the service that should be provided at each service interval. For example, if two blood cultures are to be obtained every 4 hours, the quantity would be '2', or if three units of blood are to be typed and cross-matched, the quantity would be '3'. The default value for this field is '1'.".
I'm not sure I understand the first v2 example but the second one seems clearer. Is this the intent of ServiceRequest.quantity?
Craig Newman (Mar 07 2019 at 15:15):
https://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=20510 created
Last updated: Apr 12 2022 at 19:14 UTC
