This is an excellent post and an educational opportunity!
It is important to understand the following:
Form editors are standalone programs that make creating Encounter Forms exponentially easier than having to manually code content in a manner the EMR can understand and utilize. Since each editor has different capabilities, the form source code files are specific to the editor that creates them.
VFE:
- Creates and uses a single source code file for forms.
- Source code file is named with a .dlg file extension.
- Creates and uses a single source code file for user created function libraries that is named with a .lib file extension.
- Creates a form kit by interpreting the form source code and splitting it into the needed structure for each form kit file.
EFE:
- Creates and uses TWO source code files for forms.
- Source code files are named with .fd and .fs (both are required to edit).
- Does not create nor use user created function libraries.
- Creates a form kit by interpreting the form source code and splitting it into the needed structure for each form kit file.
CCC TFE files:
- Text files used by the CCC forms created by the CCC-TFE (text file editor).
- These files populate items on the forms, such as drop down lists, list boxes, labels, etc.
- They do not alter the physical layout of a form.
- Typically are located in the CCC folder of the EMR client installation and use a .txt file extension.
- Are NOT included in a form kit when exported from the EMR.
- TFE editor(s) are used to make changes or they can be manually applied.
- TFE editor(s) are not a form editor, rather a ‘list’ content editor specific to the CCC forms.
It is important to note that GE retains all source code for the CCC forms for the purpose of code control (important given how they are designed) and licensing. While most CCC forms proper technically *can* be manually edited by an experienced individual, it is a time consuming process with zero tolerance for errors. Edited forms will require ‘reapplication’ of the edits when new versions of the forms are released.
EMR and Form Kits:
- The EMR has no use for the source code files created by VFE and EFE. They are not imported into the EMR when a clinical kit is imported.
- The EMR cannot interpret the file structure of source code for forms.
- The form kit is produced by the form editor via source code translation into a format the EMR can import and use.
- A form kit is also produced by the EMR when exporting forms.
- Exporting a form does NOT export function libraries associated with the form, these must be exported manually.
- At this time, form kits are not able to be edited by an editor, but that *may* be changing soon. (Please don't ask just yet.)
More information about Form Kit Contents:
1) .efm or .efx where x is a number
- This file contains raw code that the EMR uses to draw the form on the screen
- .efm is always the first tab/page of a form, subsequent tabs adopt the tab number, i.e: .ef2, .ef3, etc.
- One file is generated per tab/page.
- Each file is limited 64Kb in size.
2) .xlt
- This file contains MEL code that the EMR uses to generate the chart note translation.
- It can also contain other MEL code depending on the form design.
- One file per form, irrespective of the number of pages/tabs.
- Limited to 64Kb in size.
3) .xlw
- This file contains MEL code that the EMR uses to execute instructions within the form.
- One file per form, irrespective of the number of pages/tabs.
- Limited to 64Kb in size.
4) .pef
- This file contains raw code that the EMR uses to generate a printed version of the form.
- One file per form, irrespective of the number of pages/tabs.
- Limited to 64Kb in size.
5) .lst
- This file contains raw code that the EMR uses to account for all forms in the clinical forms kit.
- One file per form, irrespective of the number of pages/tabs.
- Limited to 64Kb in size.
6) .ckt
- This file contains raw code that the EMR uses to ‘import and store’ the clinical kit in the EMR database.
- One file per form, irrespective of the number of pages/tabs.
- Limited to 64Kb in size.
7) .nts
- VFE generated forms only.
- This file is actually a text component file that VFE generates from an associated .lib file.
- Not part of the ‘basic’ form kit.
- Not exported when a form is exported, even if it is 'associated' with the form.
8) .txt (VFE created forms only – different from the CCC .txt files)
- VFE creates an information text file with each form kit it generates.
- This file is NOT imported into the EMR and will not appear in an exported version of the form.
- This file is for reference only.
All of the above files are first generated from ‘source code’ files using either VFE or EFE. Once created, they can be imported into the EMR for use. Exporting these files from the EMR is typically done for ‘back up’ purposes or to share the form with another site. Again, forms are typically not exported for editing purposes since the editors only translate one way (from source code to form kit).
The ADHD version:
Form Editors build/edit form kits for import into the EMR but cannot edit form kits exported from the EMR (at this time).
Posted : July 18, 2012 9:51 pm
