I have a form that I built in VFE. When I import in into GE. The user gets a pop-up stating that the Clinical function libraries are not installed. I have them on my computer, do I need to put them in the EMR?
The EMR should offer to import the library or libraries that are bound to the form when you load the clinical kit.
If you have the function libraries, and if your form uses functions from your function libraries, then the client needs to import those function libraries for the form to work.
.
Are these function libraries that you built ? Are they in your emr ?
You can export from the EMR the function libraries that your form is using,
the emr will export it as a group (*.ckt, *.lst, *.nts)
which you can zip and send to your client.
Then have the client import that kit of your forms function libraries.
~ Beverly
The function libraries are included in a form that was shared through the forums on here. When I import the form into GE it does not ask me about the libraries. I do not get the pop-up on my computer. I am on a thick client. It is only happening on thin clients. Any ideas?
Edit your import kit file (formname.ckt) for your form.
It will look something like this
.
[EFS][3][formname][Enterprise, YYY][formname Developed by xxx; Authored by xxx at . on 12/09/15 13:11:40][Page][formname.EFM][formname.XLT][formname.XLW][][][1][Arial][]
[NTS][0][FunctionLibName][Enterprise, Function Libraries][FunctionLibName.NTS]
.
The line that starts with [NTS] describes the function library that should be imported along with the form.
If you do not see a line starting with [NTS], then that means you are not including the function library in your import kit. You can add it by editing your *.ckt to include the [NTS] line.
.
You will need the *.nts file to be in the same folder as your *.ckt (import kit)
FunctionLibName.nts
.
NOTE - Especially important. When your client imports your form, and the function library
.
if they are prompted with a message asking if they should overwrite the function library - ANSWER NO. This means they already have a version of the function library and you do not want to overwrite it.
The "version" you have may not match the one that is in their system.
If you overwrite their function library, you may break other of their forms that depend on it.
Centricity Message
Text component [Enterprise\Function Libraries\FunctionLibName] already exists. OK to overwrite it?
[Yes] [Yes To All] [No]
ANSWER No
I do not have the NTS in my .ckt folder, but I am still getting the error every time the user opens the form in GE. I don't get it.
You said that you have this function library in your EMR ? You can export the function library as a clinical kit that your client can then import.
To do this (assuming you have access to the Administrative section of the EMR)...
. From the EMR menu, navigate to: Go / Setup Settings
Choose: Export Clinical Kits
Under "available Components"
choose Text Component
click [Add]
a popup "Find Text Components" appears
Choose "Function Libraries" in the left pane, and then select the function library your form uses from the list on the right.
Click OK
Screen returns the to Export Clinical Kits
Click [Export Clinical Kit...]
a popup "Export Clinical Kit" appears
Enter the Kit Name: (something like IMPORTLIB)
Enter Kit Location: (some filepath on your harddrive where the exported function library kit will be created) Example C:\TEMP
When you click [OK]
In the Export Results box, should see something like
Exporting clinical kit IMPORTLIB to C:\TEMP\IMPORTLIB\IMPORTLIB.ckt...
Exporting text component: Enterprise\Function Libraries\NameOfFunctionLibrary...
On your harddrive you should now see a folder
C:\TEMP\ IMPORTLIB
It will contain a kit that you can use to import this function library
Normally, when you create your own function library using VFE, it will be saved as part of your form clinical kit when you save your form. This is what the *.nts files are in your list of files that make up your clinical kit.
While your EMR may contain the function library, if you do not have this function library within your VFE, so the function library (*.nts file) is not being included when you save your form.
.
I think this is how it works...anyone want to add to how this works?
.
regards,
Beverly
I followed all of the steps that Beverly suggested. The file was saved on our hard drive. we are still getting the pop-up boxes on our thin client environment. I am not sure what I am doing wrong. Please help. Frustrated physicians.....
Katie, if you can run open the form successfully on your fat client but thin clients get an error, the function libraries must be in or be called from usrlib.txt. This file is in the program directory of Centricity. You need to compare the usrlib.txt file you have on your PC with the usrlib.txt file you have on one of the thin client servers. My guess is the file on the thin client server is missing an entry you have. If the function library was loaded as a text component, it would not matter if it was a thin or thick client.
I will try that out. Thank you for all of your help.