This page is part of the Documentation Templates and Rules (v2.1.0: STU 2.1) 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
Official URL: http://hl7.org/fhir/us/davinci-dtr/CapabilityStatement/light-dtr-ehr-700 | Version: 2.1.0 | |||
Standards status: Trial-use | Maturity Level: 2 | Computable Name: LightDTREHR |
This statement defines the expected capabilities of EHRs that rely on a SMART on FHIR application for USCDI 3 (US-Core 6.1) and USCDI 4 (US-Core 7.0) to handle the form filling function of DTR. This requires the server to provide access to the specified resources to allow such an app to retrieve and edit QuestionnaireResponses and related resources.
Raw OpenAPI-Swagger Definition file | Download
http://hl7.org/fhir/us/davinci-dtr/CapabilityStatement/light-dtr-ehr-700
This statement defines the expected capabilities of EHRs that rely on a SMART on FHIR application for USCDI 3 (US-Core 6.1) and USCDI 4 (US-Core 7.0) to handle the form filling function of DTR. This requires the server to provide access to the specified resources to allow such an app to retrieve and edit QuestionnaireResponses and related resources.
EHR systems which leverage a SMART app to manage data capture and rules execution, but which must be able to launch the SMART app.
Security:
Implementations SHALL meet the general security requirements documented in the HRex implementation guide.
Summary
♦ = SHALL expectation;⋄ = SHOULD expectation;▿ = MAY expectation;
Resource Type | Supported Interactions | Supported Profiles | Supported Searches | Supported _includes | Supported _revincludes | Supported Operations |
---|---|---|---|---|---|---|
QuestionnaireResponse | read♦, create♦, update♦, search-type♦ | DTR Questionnaire Response | context♦, patient♦ | |||
Encounter | read⋄ | CRD Encounter | ||||
DeviceRequest | read⋄ | CRD Device Request | ||||
MedicationRequest | read⋄ | CRD Medication Request | ||||
NutritionOrder | read⋄ | CRD Nutrition Order | ||||
CommunicationRequest | read⋄ | CRD Communication Request | ||||
ServiceRequest | read⋄ | CRD Service Request | ||||
VisionPrescription | read⋄ | CRD Vision Prescription | ||||
Task | read⋄, create⋄, update⋄ | PAS Task Profile |
Supported Profiles:
Profile Interaction Summary:
read
, create
, update
, search-type
.Modify Criteria:
POST [base]/QuestionnaireResponse/[id]{?_format=[mime-type]}
PUT [base]/QuestionnaireResponse/[id]{?_format=[mime-type]}
Fetch and Search Criteria:
GET [base]/QuestionnaireResponse/[id]
GET [base]/QuestionnaireResponse/[id]{?[parameters]{&_format=[mime-type]}}
Search Parameter Summary:
Conformance | Parameter | Type | Example |
---|---|---|---|
SHALL | context | reference | GET [base]/QuestionnaireResponse?context=[type]/[id] |
SHALL | patient | reference | GET [base]/QuestionnaireResponse?patient=[type]/[id] |
Search Parameter Requirements (When Used Alone or in Combination):
Supported Profiles:
Profile Interaction Summary:
read
.Fetch and Search Criteria:
GET [base]/Encounter/[id]
Supported Profiles:
Profile Interaction Summary:
read
.Fetch and Search Criteria:
GET [base]/DeviceRequest/[id]
Supported Profiles:
Profile Interaction Summary:
read
.Fetch and Search Criteria:
GET [base]/MedicationRequest/[id]
Supported Profiles:
Profile Interaction Summary:
read
.Fetch and Search Criteria:
GET [base]/NutritionOrder/[id]
Supported Profiles:
Profile Interaction Summary:
read
.Fetch and Search Criteria:
GET [base]/CommunicationRequest/[id]
Supported Profiles:
Profile Interaction Summary:
read
.Fetch and Search Criteria:
GET [base]/ServiceRequest/[id]
Supported Profiles:
Profile Interaction Summary:
read
.Fetch and Search Criteria:
GET [base]/VisionPrescription/[id]
Supported Profiles:
Profile Interaction Summary:
read
, create
, update
.Modify Criteria:
POST [base]/Task/[id]{?_format=[mime-type]}
PUT [base]/Task/[id]{?_format=[mime-type]}
Fetch and Search Criteria:
GET [base]/Task/[id]