Findings or other clinical data collected about a patient during care.
Data Element
|
Questionnaire
Description
A structured set of questions intended to guide the collection of answers from end-users. Questionnaires provide detailed control over order, presentation, phraseology and grouping to allow coherent, consistent data collection.
|
| Submitted By: Shelly Spiro
/ Pharmacy HIT Collaborative
|
| Data Element Information |
| Use Case Description(s) |
| Use Case Description |
With Pharmacist eCare Plan in the HL7 FHIR health concerns resource the questionnaire resource is used to capture standard assessments (e.g. PHQ2 and PHQ9). http://fhir.org/guides/argonaut/questionnaire/StructureDefinition-argo-questionnaire-definitions.html#Questionnaire. |
| Estimate the breadth of applicability of the use case(s) for this data element
|
19 System Vendor https://www.ecareplaninitiative.com/software-solutions; CPESN network (https://www.cpesn.com) which includes over 2600 pharmacies; and anyone that adopts the Pharmacist eCare Plan implementation guide. |
| Link to use case project page |
https://www.ecareplaninitiative.com |
| Healthcare Aims |
- Improving patient experience of care (quality and/or satisfaction)
- Improving the health of populations
- Reducing the cost of care
- Improving provider experience of care
|
| Maturity of Use and Technical Specifications for Data Element |
| Applicable Standard(s) |
Uses LOINC for questionnaire questions and responses.
http://fhir.org/guides/argonaut/questionnaire/StructureDefinition-argo-questionnaire-definitions.html#Questionnaire
|
| Additional Specifications |
http://fhir.org/guides/argonaut/questionnaire/StructureDefinition-argo-questionnaire-definitions.html#Questionnaire |
| Current Use |
In limited use in production environments |
| Supporting Artifacts |
AHRQ/NIDDK Multiple Chronic Condition project
https://confluence.hl7.org/display/PC/Multiple+Chronic+Conditions+%28MCC%29+eCare+Plan
|
| Extent of exchange
|
N/A |
| Potential Challenges |
| Restrictions on Standardization (e.g. proprietary code) |
None known |
| Restrictions on Use (e.g. licensing, user fees) |
Need a LOINC license. |
| Privacy and Security Concerns |
None known. |
| Estimate of Overall Burden |
Implementation of the FHIR standard |
|
Comment