|
description
Adds a new problem and/or assessment comment to the patient’s problem list.
Note. Do not use this function outside of a chart update; otherwise, the note will not be signed.
type
Data symbol function
syntax
MEL_ADD_PROBLEM(type, description, code, onset_date, end_date, annotate, assessment, comment)
arguments
| type |
The problem prefix. Use one of the following:
DX OF = Diagnosis of
H/F = Hospitalized for
HX OF = History of
S/P = Status Post
R/O = Rule out
? OF = Question of
SX OF = Symptom of
RS OF = Risk of
NOTE: = Take Note of
FH OF = Family History of
|
| description |
The description of the problem.
|
| code |
Optional. ICD-9 code for the problem. If no ICD-9 code is present, the problem is added as uncoded. See the Comment below for more details.
|
| onset_date |
Optional. The date when the problem started. Must be in the MM/DD/YYYY format. If ._TODAYSDATE is used, it must be used with the str function (see example below). Approximate dates are not accepted. |
| end_date |
Optional. The date the problem stopped. Must be in the MM/DD/YYYY format. This will only be used if the TYPE is MDX_OF.
|
| annotate |
Optional. A comment about the problem.
|
| assessment |
Optional.
New or N
Improved or I
Unchanged or U
Deteriorated or D
Comment only or C
Note. Codes that were supported in previous releases may also appear as Better (B), Same (S), or Worse (W).
|
| comment |
Optional. A text value for the problem assessment comment (up to 2,000 characters in size)
|
when to evaluate
This function does not support the ability to evaluate continuously.
returns
Add the specified problem to the patient’s problem list, with an optional problem comment, assessment, and assessment comment.
comment
Uncoded problems may be added to the problem list using MEL_ADD_PROBLEM, even if the application is set up not to allow uncoded problems.
error handling
If you’ve used this function in an encounter form, the error code is not returned to the text translation. It is captured in MEL and can be used in conjunction with USEROK or USERYESNO to pop up an alert to the user, indicating that there is a problem with their data entry. To determine what type of error occurred, use the following error codes:
0 success
-1 Type is not provided or is invalid
-2 Description is blank, the wrong type, or too long
-3 Code is the wrong type or too long
-4 Onset is the wrong type or format
-5 End is the wrong type or format
-6 Problem comment is the wrong type or too long
-7 Assessment is the wrong type or too long
-8 Assessment comment is the wrong type or too long
-9 Can't get the clinical list lock
-10 Can't add problem for some other reason
example
{MEL_ADD_PROBLEM(‘DX OF’,’Cholera’,’ICD-001.9’,str(._todaysdate),’’,’Pt. traveled in Africa’,’N’,’monitor for improvement’)}
Add as diagnosis of Cholera to the patient’s problem list with a start date of today’s date, no end date, a comment, an assessment of New, and an assessment comment.
|
