ServiceRequest_eltss

ServiceRequest_eltss

activeeLTSS2.0.0resource34 key elements

ServiceRequest resource mapping for eLTSS

Metadata

hl7.org/fhir
Canonical URL
http://hl7.org/fhir/us/eltss/StructureDefinition/ServiceRequest-eltss
ID
ServiceRequest-eltss
Type
Base Definition
us-core-servicerequest
Derivation
constraint
Mandatory and Must-Support Elements

Elements with cardinality > 0 or marked as Must Support (S)

PathCard.TypeFlagsDescription
:resource-pertainsToGoal0..*
Extension
S
The resource-pertainsToGoal relates the resource to the goal(s) that pertain to it. Whenever there is a goal associated with a health concern or problem, this extension should be present and populated in activity (event or intent) resources.
code.coding
S
code.coding.system
S
code.coding.code
S
code.text
S
quantity[x]
S
Service Unit Quantity + Unit Type + Time Interval
:quantityQuantity0..1
Quantity
S
quantity[x].value
S
quantity[x].unit
S
UCUM codes are very useful here. But, if the concept maps to the unity unit in UCUM, then it is likely appropriate to choose a specific concept from another system. Use quanitityRatio when appropriate (such as in sessions per week) instead of quantityQuantity.
quantity[x].system
S
quantity[x].code
S
:quantityRatio0..1
Ratio
S
quantity[x].numerator
S
quantity[x].numerator.value
S
quantity[x].numerator.unit
S
UCUM codes are very useful here, but also coded numerators could be used for something like: sessions per week. See the Implementation guidance section
quantity[x].numerator.system
S
quantity[x].numerator.code
S
quantity[x].denominator
S
quantity[x].denominator.value
S
quantity[x].denominator.unit
S
UCUM codes are very useful here
quantity[x].denominator.system
S
quantity[x].denominator.code
S
:occurrencePeriod0..1
Period
S
Use this when the quantity is meant to be performed within a defined, simple start and end date. E.g. For May 31,2023 to June 10, 2023 give ServicePlan.quantity of 5 [USD]/day.
:occurrenceTiming0..1
Timing
S
Please consider using this for timing information that fluctuates or is sufficiently complex. You will need to calculate end-date, or use occurrenceTiming.boundsPeriod to ascribe a start and end date. E.g. Give ServicePlan.quantity 5 with unit=[USD]/day with the occurrenceTiming.boundsPeriod of May 31, 2023 to June 23, 2023 on occurrenceTiming.dayOfWeek = Mon and Wed at occurrenceTiming.timeOfDay = 3 pm.
occurrence[x].repeat
S
occurrence[x].repeat.bounds[x]
S
:boundsPeriod0..1
Period
S
occurrence[x].repeat.bounds[x].start
S
occurrence[x].repeat.bounds[x].end
S
performer
Reference
S
Service Provider Name + Phone + Relationship
locationReference
Reference
S
Service Delivery Address
insurance
Reference
S
Service Funding Source
supportingInfo
S
note
S
Service Comment