Da Vinci - Documentation Templates and Rules (DTR) 0.1.0 - Ballot for Comment

This page is part of the Documentation Templates and Rules (v0.1.0: STU 1 Ballot 1) based on FHIR R3. The current version which supercedes this version is 1.0.0. For a full list of available versions, see the Directory of published versions

Underlying Technologies

FHIR

This implementation guide uses terminology, notations and design principles that are specific to FHIR. Before reading this implementation guide, it’s important to be familiar with some of the basic principles of FHIR as well as general guidance on how to read FHIR specifications. Readers who are unfamiliar with FHIR are encouraged to read the following prior to reading the rest of this implementation guide.

​This implementation guide also leverages the US Core set of profiles defined by HL7 for sharing human EHR data in the US. Additional information is located at: US-Core

This implementation guide supports the STU3 and R4 versions of the FHIR standard. FHIR services based on STU3 are being moved into production by EHR vendors. R4 is just recently published and the goal is to ensure the implementation guide is aligned with the current direction of the FHIR standard. Initial implementations will focus on STU3.

This implementation guide also builds on the US Core Implementation Guide and implementers need to familiarize themselves with the profiles in those Implementation Guides:

FHIR Version
​FHIR R4 US Core
FHIR STU3 US Core (1.0.1)

Implementers should also familiarize themselves with the FHIR resources used within the guide:

STU3 R4
Questionnaire ​Questionnaire
QuestionnaireResponse ​QuestionnaireResponse

US Core

Clinical systems will use the specification and workflows defined by US Core to initiate Document Template and Rule functionality with the payers. Implementers should be familiar with this specification.

CDS Hooks

Clinical systems will use the specification and workflows defined by CDS Hooks to initiate Document Template and Rule functionality with the payers. Implementers should be familiar with this specification.

CRD

Clinical systems will use the specification and workflows defined by CRD to initiate Document Template and Rule functionality with the payers. Implementers should be familiar with this specification.

SMART on FHIR

Client systems conformant to this implementation guide SHALL also serve as a SMART on FHIR client. This is to allow Document Template and Rule functionality to be invoked outside of regular clinical workflows using a SMART on FHIR application to provide a consistent way of evaluating “what if?” scenarios across EHR implementations. As such client implementers will also need to be familiar with the SMART on FHIR specification. Because the SMART on FHIR app will interact with payer systems through the CDS Hooks interface, payer implementers only need to be familiar with the SMART on FHIR specification if they plan to develop SMART apps for launch by CDS Hooks or for other purposes.

SDC

Clinical systems will use the specification and workflows defined by SDC to initiate Document Template and Rule functionality with the payers. Implementers should be familiar with this specification.

CQL

Clinical systems will use the specification and workflows defined by CQL to initiate Document Template and Rule functionality with the payers. Implementers should be familiar with this specification.