Hello, we upgraded our test environment to EMR 9.12 and Patient Portal 8.0.4. I have a Blood Pressure Readings eform in the patient portal go to the EMR desktop as an EMR document. I use the observation term BP SYS HOME and BP DIA HOME on the eform in the patient portal. When the form drops to the EMR desktop and the user sign the form and the systolic and diastolic BP display with a question mark following the reading on the flowsheet. I see an error message within the form in the EMR stating:
The following lab values were dispersed to the flowsheet
with no units conversion:
BP SYS HOME, 124, (F) expected units: mmHg
BP DIA HOME, 68, (F) expected units: mmHg
Prior to the upgrade this was not the case. The BP unit values came across and the BP displayed on the flowsheet without question marks. When I enter a home BP using an encounter form in the EMR, I do not get the error message. The EMR form and the patient portal eform share the same observation terms for home BP's. Therefore, I believe there is a disconnect between eforms in the patient portal sent as an EMR document and the EMR itself.
Is anyone else experiencing this same issue? If so, please contact me. I'd like to know if this is a bug with EMR 9.12 and PP 8.0.4. I called GE and they said they would have to escalate the case.
Kimberly West
708-229-5250
In your HL7 message, you should see an OBX segment for the systolic and diastolic. Here's an example from a different HL7 message, but the concept is the same.
OBX|2|NM|FVC-Pred||2.28|L
In this case, FVC-Pred is the result code from my source. It will most likely be matched to a CEMR code in the cross reference file for the lab interface.
The 2.28 is the measurement.
The "L" is for liters in this case. That's where the units are sent to CEMR. See if you are receiving units.
It sounds like perhaps GE made a change to not assume units under a certain condition.
-dp
You might want to compare the HL7 you were getting with the HL7 you are getting now. It may be that the portal for whatever reason dropped the units measure in what it is sending to Centricity. Or a recent Obs Term kit added units for those obs terms where it might not have existed before and now the same HL7 throws that error.
Thanks so much! I appreciate your responses. I will forward this to the support person assigned to the case at GE.
Kimberly