You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The non-visit note is a special kind of note that, as the name suggests, is not associated with a visit. These notes, in their simplest form, provide a chronological account of information about the patient. While they can be plain text, they can also contain vitals and links to other documents.
The use case for Non-Visit Notes
Patient books appointment (or patient is created)
Triggers a webhook (coming soon...)
we start a flow
We send text message with hosted pages link
Patient fills in some form in hosted pages
Data is piped back to Elation as a note
My understanding is that non-visit notes are the most appropriate format for this sort of information.
Tasks
Create a non-visit note
Update a non-visit note
Get a non-visit note
Delete a non-visit note (to complete CRUD functionality)
Details
In terms of how we want to handle, the goal here will be to not mutate the required object, but instead omit items we can't support. So, we'll support tags as an array of ints. we won't support note_documents or note_items yet.
The one exception is going to be bullets. We're going to have to support that, because that's where the note is. Here, we'll just support a single note:
Normally, the note is used for historical documents from other doctors. "Hey, you've got your old charts? we'll log them as non-visit notes, add them as documents, and include bullets to summarize the documents."-
That's the normal use case ☝️ ... but, we're going to be using these as a way to log inputs from forms.
If we get feedback from customers that the non-visit note is not the best way to use these notes, we'll make adjustments and perhaps add some other way to perform this use case... but that's where we're starting for now.
The text was updated successfully, but these errors were encountered:
Quick note: i put #107 ahead of this one because we will use the physicianUserId from the Find Physician action in order to populate the author field of the chart note. these should correspond in field/datapoint type
Chart Notes
The non-visit note is a special kind of note that, as the name suggests, is not associated with a visit. These notes, in their simplest form, provide a chronological account of information about the patient. While they can be plain text, they can also contain vitals and links to other documents.
The use case for Non-Visit Notes
My understanding is that non-visit notes are the most appropriate format for this sort of information.
Tasks
Details
In terms of how we want to handle, the goal here will be to not mutate the required object, but instead omit items we can't support. So, we'll support
tags
as an array of ints. we won't supportnote_documents
ornote_items
yet.The one exception is going to be
![image](https://user-images.githubusercontent.com/19916684/233533757-d362deab-3cc1-4451-87e6-34f56d9f210e.png)
bullets
. We're going to have to support that, because that's where the note is. Here, we'll just support a single note:physicianUserId
(see Elation: Find Physician #107 )What's missing?
Normally, the note is used for historical documents from other doctors. "Hey, you've got your old charts? we'll log them as non-visit notes, add them as documents, and include bullets to summarize the documents."-
That's the normal use case ☝️ ... but, we're going to be using these as a way to log inputs from forms.
If we get feedback from customers that the non-visit note is not the best way to use these notes, we'll make adjustments and perhaps add some other way to perform this use case... but that's where we're starting for now.
The text was updated successfully, but these errors were encountered: