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
When the DTR application has collected all of the necessary information, it must persist the results of the data collection. This implementation guide describes two methods for saving the collected information: a text block in the EHR System and a QuestionnaireResponse.
Many EHR Systems do not currently support writing a QuestionnaireResponse into a FHIR server. However, The US Core IG now includes a DocumentReference Profile, which allows clients, like the DTR application, to write notes into the EHR System’s FHIR server. The following section describes how the QuestionnaireResponse that is generated through the processes described in Section 4.4.3 and Section 4.4.4 can be transformed into text such that it may be persisted as a note in the EHR system.
The DTR application SHALL support transforming a DTR-QuestionnaireResponse resource into a Portable Document Format (PDF) representation. DTR applications SHALL ensure that the document indicates differences between user supplied information and data gathered from the EHR system.
The DTR application SHALL create a DocumentReference resource with this information that conforms to the US Core DocumentReference profile. The generated PDF SHALL be recorded in DocumentReference.content.attachment.data
. DocumentReference.content.attachment.contentType
SHALL be application/pdf
Note to ballot comments
This is an area the project is explicitly seeking comments on. Please provide any details on constraints that should be applied to the document generation process.
EHR systems that conform to US Core STU3 allow for the creation of DocumentationReference resources through a FHIR API. As such, the DTR application should use the typical FHIR create interaction to write the documentation into the EHR.
The DTR application creates a QuestionnaireResponse resource through the course of normal operation. This resource may be persisted in the EHR system of the healthcare provider if it is supported. It may also be transmitted to the Payer IT system.
The Payer IT system should support the FHIR create interaction to allow the DTR application to send the QuestionnaireResponse resource to the payer. The FHIR endpoint for the payer may require authentication. If it is required, it SHALL follow the procedures described in Section 4.4.1.1 - Authentication of SMART on FHIR application to payer API.