We have tested Openemr with NIST procedures and we found some inconsistencies in
problem list and medication allergies.
A. Problem list
1)According to NIST test data, While adding problem details, We have to enter the
“status” of the problem.(NIST’s recommended status - active,resolved and inactive).
As per the current logic, if the end date is blank,the status is considered as active.
For compliance with NIST test procedures, We can rename the existing field ‘outcome’
as ‘status’ & the other stasuses(inactive,resolved) can be added.
2)NIST rules also demands displaying the “status” along with the problem. So we can
add a column named ‘status’ in the display
list.
B. In Medication Allergy
1) As per NIST rules, there should be a field to denote the ‘Reaction to the allergy’.
For compliance with NIST, we can include a input field for ‘Reaction’ in the allergy
form .
and we can add a field named ‘reaction’ in ‘lists’ table. Do let us known if this
will affect the current setup.
2)The status and the reaction should be displayed in the medication allergy
list.
So we can add a column named ‘Reaction’ in the medication-allergy list.
hey,
Plan to look/test your patches soon. Something to think about is how to upgrade previous installations (i think your changes would break/wipe out previous smoking status entries).
-brady
Just tested it out. Agree with moving the tobacco field to the top. Rather than remove the current smoking status, can’t you just add this as a separate field. Then can join the two with javascript (ie. if select current smoker… then select active in the other and vice versa etc). Then you avoid any upgrade issues, fulfill NIST and give users more flexibility in reporting smoking status (for example, a quit date (clinically important) and a free text field). Very interested to see what others think; I put the code on github here: http://github.com/bradymiller/openemr/tree/visolve-smoking_1
We have started testing ‘Electronic syndromic surveillance’ feature in OpenEMR. In OpenEMR, HL7 2.5.1 version is used for generating the syndromic surveillance message. It is stated in NIST test procedures, if HL7 2.5.1 is used as version, the message should be tested against the ‘case notification message mapping guide’ to check whether the message is conformant or not.
Could you please specify which ‘case notification mapping guide’ OpenEMR is using to generate HL7 message?
Dr Brody team produced the code. If his teamd did not include that information on the wiki page for this item then he will need to answer the question you have.
I’m simply reviewing Visolve’s code and providing input. But I (and Visolve) definitely don’t want duplicate any efforts. Would it be best for Visolve(any myself) to wait on any more patches until EMRTech weighs in?
We found an inconsistency in demographics according to NIST procedures and CMS final rule.
Inconsistency: Race and Ethnicity should be entered in separate fields and to follow the standard specified by 'The Office of Management
and Budget Standards for Maintaining, Collecting, and Presenting Federal Data on Race and Ethnicity,Statistical Policy Directive No. 15, October 30, 1997.
At present, OpenEMR is getting either ‘Race’ or ‘Ethnicity’ and specified standards are not followed.
Proposed Solution: An additional field to enter ‘Ethnicity’ can be included keeping the present field to enter ‘Race’.
For the data entered previously, a migration script will be given which will compare the values in the old field with the standard codes of race and ethnicity. If any match found will move the data to corresponding field and will be displayed in patient demographics.