Notifications
Clear all
Topic starter
Has anyone found a way to pull the employer contacts into a VFE form. Any known data element name, symbol or OBS term. Our idea is to enter the employer into reg contacts for worker's comp and then pull that employer into the clinical documentation. I need to know the name of the field in reg to pull the info.
Thanks....
Posted : December 27, 2012 8:52 am
I recently tried to pull the employer to a form from the registration and had no luck at all. Even using the find() function didn't get me anywhere. It seems this isn't possible currently.
Posted : January 3, 2013 8:01 am
Try the object '_FaxEmployer' from mldefs8
Posted : January 4, 2013 2:11 am
I tried _FaxEmployer, but when I do getrowcount() on it, it's always 0. find("_FaxEmployer", "Name") returns nothing regardless of which employer I have in registration.
Have you used this before and got it to work?
Posted : January 4, 2013 2:15 am
I have never used it in production, after playing with it some more it looks like the object is only called (and updated) if you try to print to a fax first. It only worked for me by chance, so it is more trouble than its worth.
I guess you could always use PATIENT.CONTACTS and save employers as other contacts but that approach isnt the best solution either.
Posted : January 4, 2013 2:43 am
I have never used it in production, after playing with it some more it looks like the object is only called (and updated) if you try to print to a fax first. It only worked for me by chance, so it is more trouble than its worth.
Yeah, I was thinking that was the case.
I guess you could always use PATIENT.CONTACTS and save employers as other contacts but that approach isnt the best solution either.
I thought about that as well, but I didn't want our Front Desk employees having to enter this in two different places. We really need a PATIENT variable that has PATIENT.EMPLOYER...
Posted : January 4, 2013 2:51 am
I have created new PATIENT data symbols by joining additional data to the "vpatientprofile" sql view and then mapping the field(s) to a new PATIENT symbol in the mldef.txt file. This will expose the new symbol to Forms, Text Components, handouts, etc.
I caution that there are at least a couple very good reasons why GE doesn't exactly promote creating and maintaining your own symbols:
#1 stability: if it is not done correctly, it can lead to serious performance issues and crashing.
#2 change management: you might have to redo the custom view/mldef changes each time you upgrade Centricity. You will also have to deploy the update mldef file to all of your workstations using jobs.txt or via some other script.
That being said, if you have a test/demo database environment and you're interested in giving this a try, please give me your email and I can provide additional info.
Posted : January 6, 2013 2:02 pm
I would be interested in knowing how you do this.
Posted : January 6, 2013 11:32 pm
