If your facility is using HEO Mapped Lab Concepts, I'm fairly certain that you've found that the McKesson built-in lab concepts are a good start, but are only a starting point. Most facilities have many more lab concepts that they would like to display and use for clinical decision support (not to mention other creative uses of the Lab Concepts to bring HED non-lab values to HEO). To accomplish these things, you need to create your own custom-built HEO Mapped Lab Concepts.
If you've gotten to this point, you may have found that, while the newly created lab concepts are available to the rules writer (and therefore available to Standard iForms), when you try to use @@patient.lab_result.myLab.value@@ or @@patient.lab_result.myLab.date@@ in the HTML of your VGR iForms, it doesn't work.
The HTML parser provided for VGR iForms, for whatever reason, can only "find" lab results for the HEO Lab Concepts that McKesson built into the system. So when you have custom lab concepts, the HTML parser for VGR iForms simply cannot see those particular lab results. However, the VGR engine can see them.
So, to access the information, you can create local variables in your VGR and map the information to the local variables.
INIT,MAP,LOCAL,myLabValue,TO,patient.lab_result.myLab.value INIT,MAP,LOCAL,myLabDate,TO,patient.lab_result.myLab.date
In this case, we have a custom lab named myLab. We create two VGR LOCAL variables named myLabValue and myLabDate and map them to the value and date of the myLab lab result. Once you declare these local variables, you can reference them at any point in your HTML by using @@myLabValue@@ and @@myLabDate@@.
Note: while you can retrieve the value and date of custom mapped lab results, the graph_url and some of the other data points not function, at least as far as I have seen. It is possible to create a graph, but it has to be done by hand by retrieving the values and dynamically creating the graph using some other method. These workarounds are possible, but not simple.
Scott Morris is available for training, mentoring, troubleshooting, and iForms consulting. Find out more at www.thinkiforms.com
0 comments: