-
Notifications
You must be signed in to change notification settings - Fork 2
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
8e8fcbc
commit 500e24d
Showing
17 changed files
with
128 additions
and
5 deletions.
There are no files selected for viewing
3 changes: 3 additions & 0 deletions
3
...unters/landingpages/chief-complaint.assets/00a01e6524b72cd71bd02e07838d24f7.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
3 changes: 3 additions & 0 deletions
3
...unters/landingpages/chief-complaint.assets/10602f15f1443fb544491827e9d729e5.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
3 changes: 3 additions & 0 deletions
3
...unters/landingpages/chief-complaint.assets/12999e46e366eea8cd89ee82d1d6c933.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
3 changes: 3 additions & 0 deletions
3
...unters/landingpages/chief-complaint.assets/144415de9354715778c39aec72af241f.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
3 changes: 3 additions & 0 deletions
3
...unters/landingpages/chief-complaint.assets/25f558e5b6cc6c2c144197e683c5719f.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
3 changes: 3 additions & 0 deletions
3
...unters/landingpages/chief-complaint.assets/35b8ce742c6c26c62b67a9d562958451.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
3 changes: 3 additions & 0 deletions
3
...unters/landingpages/chief-complaint.assets/55787f22ab9e062d6ae4b99679636e7a.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
3 changes: 3 additions & 0 deletions
3
...unters/landingpages/chief-complaint.assets/617e19dd7a31f28882c9cc0c543b6849.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
3 changes: 3 additions & 0 deletions
3
...unters/landingpages/chief-complaint.assets/684b99d74b755a1e5ed6cde1747d5416.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
3 changes: 3 additions & 0 deletions
3
...unters/landingpages/chief-complaint.assets/89327cd55fe6fe398986cdca266a0618.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
3 changes: 3 additions & 0 deletions
3
...unters/landingpages/chief-complaint.assets/ce10719ae037a4e3e4f11dc0a37d495d.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
3 changes: 3 additions & 0 deletions
3
...unters/landingpages/chief-complaint.assets/d53c753c77d7b071eb3025420869a7ec.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
3 changes: 3 additions & 0 deletions
3
...unters/landingpages/chief-complaint.assets/f1a8471feeb8221f293a1ca2d1806330.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
3 changes: 3 additions & 0 deletions
3
...unters/landingpages/chief-complaint.assets/f919793e0e2324ce30845c5aaf2f9869.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
3 changes: 3 additions & 0 deletions
3
...unters/landingpages/chief-complaint.assets/fcc3dc852921836222c87dc16939ab5b.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
3 changes: 3 additions & 0 deletions
3
...unters/landingpages/chief-complaint.assets/fd1e7655b4ff82f8df09b242c3025d2b.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
85 changes: 80 additions & 5 deletions
85
content/functions/encounters/landingpages/chief-complaint.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,12 +1,87 @@ | ||
--- | ||
id: '1_EFI6XA7aSkCqugmBfqh1FudkauR-2j6DWBM1nLAfVE' | ||
title: 'Chief Complaint' | ||
date: '2021-02-26T16:08:06.512Z' | ||
version: 17 | ||
lastAuthor: '' | ||
date: '2025-02-07T21:19:40.529Z' | ||
version: 59 | ||
lastAuthor: 'anichols' | ||
mimeType: 'text/x-markdown' | ||
links: [] | ||
links: | ||
- '../encounter-protocols.md' | ||
source: 'https://drive.google.com/open?id=1_EFI6XA7aSkCqugmBfqh1FudkauR-2j6DWBM1nLAfVE' | ||
wikigdrive: '0008bcbb1563384efe0a28ada6f97e9432e65f10' | ||
--- | ||
Chief Complaint | ||
A patient's Chief Complaint can be documented when scheduling an appointment and/or when working in an encounter. An appointment's chief complaint will populate the encounter chief complaint section, when the patient checks in for their appointment where an encounter is configured to automatically create upon checkin. Chief Complaints on appointments and/or encounters are reportable and visible throughout the system. | ||
|
||
## Appointment Chief Complaint | ||
|
||
When scheduling (adding) an appointment and/or editing an appointment, one can signify a Chief Complaint in the free text field. | ||
|
||
![](../chief-complaint.assets/12999e46e366eea8cd89ee82d1d6c933.png) | ||
|
||
## Visibility to Appointment Chief Complaint | ||
|
||
When the appointment is saved, the Chief Complaint will display on the various Scheduler views such as List View, Multi View and Week View. | ||
|
||
![](../chief-complaint.assets/35b8ce742c6c26c62b67a9d562958451.png) | ||
|
||
![](../chief-complaint.assets/89327cd55fe6fe398986cdca266a0618.png) | ||
|
||
The appointment chief complaint is visible from the Appointments chart tab listing of waitlist appointments, pending appointments, and past appointments. | ||
|
||
![](../chief-complaint.assets/10602f15f1443fb544491827e9d729e5.png) | ||
|
||
Another place where there is visibility to the appointment Chief Complaint is from the Appointments portlet found in the chart's Summary dashboard tab. | ||
|
||
![](../chief-complaint.assets/00a01e6524b72cd71bd02e07838d24f7.png) | ||
|
||
Lastly, an appointment's chief complaint is visible as the appointment reason when utilizing the Schedule portlet found within the Quick View sidemenu dashboard. | ||
|
||
![](../chief-complaint.assets/f919793e0e2324ce30845c5aaf2f9869.png) | ||
|
||
## Chief Complaint Encounter Section | ||
|
||
Within an encounter, there is a Chief Complaint section that can be utilized. The Chief Complaint contents will prepopulate with the linked appointment Chief Complaint details (if the encounter were generated automatically from the checked in appointment). | ||
|
||
The encounter Chief Complaint can be updated or edited. If an edit is made, it does not reflect back onto the linked appointment, it is simply reflective within the encounter and encounter document. | ||
|
||
![](../chief-complaint.assets/55787f22ab9e062d6ae4b99679636e7a.png) | ||
|
||
## Chief Complaint Protocol | ||
|
||
Protocols (primary and additional protocols) can be configured to be selected and utilized within the Chief Complaint encounter section. Please see separate guide [Encounter Protocols](../encounter-protocols.md) for detailed information. | ||
|
||
![](../chief-complaint.assets/ce10719ae037a4e3e4f11dc0a37d495d.png) | ||
|
||
## Visibility to Encounter Chief Complaint | ||
|
||
An encounter's chief complaint is visible as a column within the Encounters chart tab listing which is a datavis listing. | ||
|
||
![](../chief-complaint.assets/fd1e7655b4ff82f8df09b242c3025d2b.png) | ||
|
||
There is an optional system setting that can be disabled system wide to omit the Chief Complaint column from the Encounters chart tab listing. Otherwise, the Encounters listing is a datavis which users can make their own perspectives for as needed. | ||
|
||
![](../chief-complaint.assets/fcc3dc852921836222c87dc16939ab5b.png) | ||
|
||
An encounter's chief complaint is also visible within the Encounter's Properties as a column within the Encounter Revisions datavis listing. | ||
|
||
![](../chief-complaint.assets/25f558e5b6cc6c2c144197e683c5719f.png) | ||
|
||
![](../chief-complaint.assets/684b99d74b755a1e5ed6cde1747d5416.png) | ||
|
||
Once an encounter has been closed & archived, the encounter is made into a document that is stored and can be shared. The encounter's chief complaint (within a stored document) is also visible within the Documents listing as the *Subject* when looking at a list of stored documents. | ||
|
||
![](../chief-complaint.assets/617e19dd7a31f28882c9cc0c543b6849.png) | ||
|
||
There is a system setting for List View that sets the encounter's chief complaint as the stored document's subject. | ||
|
||
![](../chief-complaint.assets/144415de9354715778c39aec72af241f.png) | ||
|
||
## Reporting | ||
|
||
There are several standard reports and dashboards that may output the Chief Complaint from an encounter or appointment. | ||
|
||
![](../chief-complaint.assets/d53c753c77d7b071eb3025420869a7ec.png) | ||
|
||
Example of Encounters reporting dashboards output: | ||
|
||
![](../chief-complaint.assets/f1a8471feeb8221f293a1ca2d1806330.png) |