| Name | Flags | Card. | Type |
Description & Constraints
|
|---|---|---|---|---|
ServiceRequest
|
ServiceRequest | |||
Slices for extension
|
Slice: Unordered, Open by value:url | |||
directedBy
|
0..* | CodeableConcept |
Self-Directed Service Indicator
URL: http://hl7.org/fhir/us/eLTSS/StructureDefinition/eltss-directedBy |
|
|
resource-pertainsToGoal
|
S | 0..* | Reference ( Goal ) |
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. URL: http://hl7.org/fhir/StructureDefinition/resource-pertainsToGoal |
basedOn
|
Reference (CarePlan_eltss | ServiceRequest_eltss | MedicationRequest ) | |||
|
replaces
|
Reference (ServiceRequest_eltss) | |||
code
|
Service Name Binding: todo ( preferred ): Use HCPCS (https://www.cms.gov/Medicare/Coding/MedHCPCSGenInfo/) code + modifiers or free text. |
|||
Slices for quantity[x]
|
Service Unit Quantity + Unit Type + Time Interval
Slice: Unordered, Open by type:$this |
|||
quantity[x]:quantityQuantity
|
0..1 | Quantity | ||
unit
|
UCUM codes are very useful here | |||
quantity[x]:quantityRatio
|
0..1 | Ratio | ||
numerator
|
||||
unit
|
UCUM codes are very useful here | |||
|
denominator
|
||||
|
unit
|
UCUM codes are very useful here | |||
|
subject
|
Reference (Patient_eltss | Group | US Core Implantable Device Profile | Device | Location_eltss) | |||
|
encounter
|
Reference (US Core Encounter Profile) | |||
|
Slices for occurrence[x]
|
Service Start + End Date
Slice: Unordered, Open by type:$this |
|||
|
occurrence[x]:occurrencePeriod
|
0..1 | Period | 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. | |
|
occurrence[x]:occurrenceTiming
|
0..1 | Timing | 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 occuranceTiming.boundsPeriod of May 31, 2023 to June 23, 2023 on occuranceTiming.dayOfWeek = Mon and Wed at occuranceTiming.timeOfDay = 3 pm. | |
|
requester
|
Reference (Practitioner_eltss | US Core PractitionerRole Profile | Patient_eltss | US Core Organization Profile | RelatedPerson | US Core Implantable Device Profile | Device ) | |||
|
performer
|
Reference (Practitioner_eltss | US Core PractitionerRole Profile | Patient_eltss | US Core Organization Profile | RelatedPerson | US Core Implantable Device Profile | Device | US Core CareTeam Profile | HealthcareService ) | Service Provider Name + Phone + Relationship | ||
|
locationReference
|
Reference (Location_eltss) | Service Delivery Address | ||
|
reasonReference
|
Reference (Condition_eltss | Observation_eltss | US Core DiagnosticReport Profile for Report and Note Exchange | US Core DocumentReference Profile) | |||
|
insurance
|
Service Funding Source | |||
|
note
|
Service Comment | |||
|
Documentation for this format
|
||||