Notes field: Difference between revisions
Ttenbergen (talk | contribs) |
Ttenbergen (talk | contribs) m discussion template fix |
||
Line 46: | Line 46: | ||
| always= We tried to standardize field into a kind of form, but collection practice is too non-standard to come up with a format that worked. | | always= We tried to standardize field into a kind of form, but collection practice is too non-standard to come up with a format that worked. | ||
| full= | | full= | ||
Just being curious if the notes field is a free space for '''optional''' additional info....what specific problems did this cause? | |||
*I actually prefer a blank notes field. The premise was good but turns out to not be all that helpful.--[[User:CMarks|CMarks]] 11:53, 2018 December 6 (CST) | *I actually prefer a blank notes field. The premise was good but turns out to not be all that helpful.--[[User:CMarks|CMarks]] 11:53, 2018 December 6 (CST) |
Revision as of 10:38, 2020 April 2
Data Element (edit) | |
Field Name: | Notes |
CCMDB Label: | Notes |
CCMDB tab: | Top Row |
Table: | L_Log table |
Data type: | memo |
Length: | not stated |
Program: | Med and CC |
Created/Raw: | Raw |
Start Date: | 1988-07-11 |
End Date: | 2300-01-01 |
Sort Index: | 9 |
Used by data collectors to keep notes during collection.
The notes field expands to a bigger form when you double-click on it.
Usage of the notes field
The notes field was set up to be a free-for-all where collectors can store any info they want. This resulted in non-standardized collection practices which result in problems during vacation coverage or on shared wards.
Guidelines
- Please do not write copious history notes from charts into this note section. This is only for reminders or points needed to do your work, dates where you left off at or any follow up of info, test etc., that need to be done by yourself or for others who help collect on your laptop. Notes have to be clear to others.
Patients being sent
- For patients you are ready to send, make sure you note explanations for data values that you think might cause call-backs from the Data Processor or Statistician. For example:
- Extreme data that was confirmed as correct:
- extreme physiological APACHE values, eg Sys BP of 50 valid , see APACHE_Scoring_table and APACHE_physiological_variable_collection#Exceptionally_high_or_low_values
- tasks for renal transplant patients that do not follow the norm
Up-to where/when collection is complete
- STB - where we have left off reading in the EPR notes by entering the date/time last read
Diagnoses or other data that needs to be reviewed or checked
Can be used to document suspected diagnoses (which would not be coded in ICD10 even for incomplete records, as per ICD10 collection#"Suspected" Diagnoses.
Supplemental data
- to clearly define some admit diagnoses-the ones that come up as other problems, other problems when you enter them.
- be aware that 99% diagnosis data analysis in the main office will not look at the notes field, as usually there are just filters or counts on the ICD10 dx entries.
- to enter info on base creatinine, bmi, or other tidbits of info that are useful to know.
- to define what exactly needs to be entered, when a profile is only partially completed.
Automatic population of notes field for newly entered patients
We tried to standardize field into a kind of form, but collection practice is too non-standard to come up with a format that worked. |
Just being curious if the notes field is a free space for optional additional info....what specific problems did this cause?
Recently a format was implemented and placed into the notes field. We would like to know if this format is helpful and if you use it. Please indicate here if you use it or not and any comments you would like to make regarding this:
|