This page is part of the Documentation Templates and Rules (v1.0.0: STU 1) based on FHIR R4. This is the current published version. For a full list of available versions, see the Directory of published versions
Note: The DTR IG base profiles are listed below Where appropriate, the HRex IG R4 base profiles may be utilized.
FHIR resources exchanged in the execution of a DTR process are subject to conformance requirements with the following HL7 Implementation Guides.
The Da Vinci DTR Implementation Guide (IG) will make use of US Core profiles that are based on the FHIR R4 specification wherever practical. The DTR IG uses the HL7 FHIR Release 4 specification as its base.
The DTR process accesses information about a patient to execute rules and gather documentation to satisfy payer needs. To do this, the DTR process will make requests to a FHIR server of the healthcare provider organization’s Electronic Health Record (EHR) system. The FHIR server SHALL conform to the US Core Implementation Guide R4 when providing access to a FHIR R4 server.
Payers have documentation requirements and rules that must be satisfied as part of their typical operations when reimbursing for care. In an ideal case, all of the information needed by a payer would be stored in a healthcare provider’s EHR system in a structured format for easy retrieval. Since relevant information is frequently unstructured, measures must be taken to allow users to input information that is not automatically discoverable. To facilitate this SDC and/or CQF Questionnaire is used as described below.
The Structured Data Capture Implementation Guide is used to allow payers to declare information needs and provide the DTR process with a means of obtaining this data from a user.
Payers will describe their information needs through the FHIR Questionnaire resource. These resources SHALL conform to the CQF Questionnaire Profile. This profile allows the Questionnaire to be associated with the Clinical Quality Language (CQL) used to find the desired information within a patient’s data. Further, it allows each individual item in the Questionnaire to be associated with an expression in the CQL.