DTR (Documentation Template and Rules) FHIR API Specification
Service Overview
InterSystems DTR (Documentation Template and Rules) REST-based FHIR APIs are designed in compliance with the CMS-0057-F regulationsOpens in a new tab, which were written to improve the exchange of health care data with the aim of improving prior authorization processes while reducing burden on patients, providers, and payers. DTR supports payers in expressing their documentation requirements in a way that EHR users can quickly navigate and provide the information needed.
Refer to the Getting Started section for information on connectivity, authentication and how to get help.
To use the REST-based FHIR APIs, you will need to know the base URL of the FHIR server you will be connecting to. You can also use the Discovery APIs for the service.
DTR Discovery APIs
The following unauthenticated APIs are available for determining the capabilities and configuration of the DTR service:
-
.well-known/smart-configuration: retrieves the standard JSON discovery file used by SMART on FHIR Backend Services.
-
metadata: retrieves the FHIR CapabilityStatement for the service.
Your call should use the following base path, with the appropriate discovery endpoint appended:
<BaseURL>/csp/healthshare/<namespace-identifier>/dtr-v<IG version>
For example, append /metadata to access the FHIR capability statement.
In the above URL, <BaseURL> and <namespace-identifier> have been provided to you by the payer organization you are connecting with, and <IG version> is the version number of the DTR Implementation Guide you are working with. For example, this could be version 2.0.1 or version 2.1.0.
Available APIs
The APIs available with the DTR service are:
A visualization of the overall DTR processOpens in a new tab can be found in the DTR Implementation Guide. As part of the DTR APIs, a provider can use the $questionnaire-package API to obtain one or more questionnaires based on pre-defined payer requirements. The $next-question API is used as part of responding to an adaptive questionnaire to determine the next set of questions that should be displayed to a user based on their questionnaire responses so far.
A client application can use the $expand API to run an expansion to create a collection of codes in a value set returned in a questionnaire package. Note that when using the questionnaire-package API, value sets will be expanded automatically.
A client application can also use the $log-questionnaire-errors API to report issues or errors back to the originating payer that were encountered when working with their DTR artifacts, such as questionnaires or Clinical Quality Language (CQL) logic.
Implementation Guides
The DTR service conforms to the following implementation guide(s):
-
Da Vinci Documentation Templates and RulesOpens in a new tab implementation guide, version 2.0.1 and version 2.1.0.