Electronic Long-Term Services and Supports (eLTSS) Release 1 - US Realm
2.0.0 - STU2 United States of America flag

This page is part of the electronic Long-Term Services and Supports Implementation Guide (v2.0.0: STU2) based on FHIR (HL7® FHIR® Standard) R4. This is the current published version. For a full list of available versions, see the Directory of published versions

CapabilityStatement: eLTSS Client

Official URL: http://hl7.org/fhir/us/eltss/CapabilityStatement/eltss-client Version: 2.0.0
Standards status: Trial-use Maturity Level: 2 Computable Name: ELTSS_Client

This profile defines the expected capabilities of the eLTSS Client.

Raw OpenAPI-Swagger Definition file | Download

eLTSS Client

  • Implementation Guide Version: 2.0.0
  • FHIR Version: 4.0.0
  • Supported Formats: xml, json
  • Supported Patch Formats:
  • Published on: Thu Feb 07 22:00:00 MST 2019
  • Published by: HL7 International / Human and Social Services

Note to Implementers: FHIR Capabilities

Any FHIR capability may be 'allowed' by the system unless explicitly marked as "SHALL NOT". A few items are marked as MAY in the Implementation Guide to highlight their potential relevance to the use case.

FHIR RESTful Capabilities

Mode: client

This requirements capability statement imports the entirety of the US Core Client CapabilityStatement from US Core. Refer to the imported capability statement for full information on the capabilities defined by this capability statement.

The imports field in the JSON indicates from which capability statements an IG imports. As an implementer, you can think of this as similar to profiling. This means that the expectation of this Client Capability statement is that the entire US Core capability statement will be conformed too, in addition to specifications that follow. The JSON/XML version of the CapabilityStatement is the computable specification. This narrative is for convenience only.

Capabilities by Resource/Profile

Summary

The summary table lists the resources that are part of this configuration, and for each resource it lists:

  • The relevant profiles (if any)
  • The interactions supported by each resource (Read, Search, Update, and Create, are always shown, while VRead, Patch, Delete, History on Instance, or History on Type are only present if at least one of the resources has support for them.
  • The required, recommended, and some optional search parameters (if any).
  • The linked resources enabled for _include
  • The other resources enabled for _revinclude
  • The operations on the resource (if any)
Resource TypeProfileRV-RSUCH-ISearches_include_revincludeOperations
CarePlanSupported profiles:
  CarePlan_eltss		yyyy

Resource Conformance: supportedCarePlan

Core FHIR Resource
CarePlan
Reference Policy
Interaction summary
  • Supports search-type, read, history-instance, vread.

Supported Profiles

http://hl7.org/fhir/us/eltss/StructureDefinition/CarePlan-eltss