Action Properties

The following is an alphabetical list of action properties available in the MedInformatix EHR, including the Decision Tree, The Document Repository, and PMS browser objects.

Action Properties
Action Property	Description
#ABSTRACT	Flow sheet used to track dates and/or notes (columns provided for both). Date field prompts an Enter Date Done screen where users supply a date to correspond to an item being tracked. The Note field prompts a keyboard where the insertion of a note (255 character limit) on the clinical item can be tracked. The dates are the result of queries from one or more SQL Tables. This is used primarily to track Health Maintenance History (HEDIS) in Primary Care.
#ACCOUNTNOTE	This action property will launch the Account Note window.
#ADDTOWORKLIST	Allows a patient to be automatically added to the Patient Working List using a tree click. Allows a '?' in the {Worklist Note} parameter to allow the user to type a worklist note instead of it being hard coded. Format: #ADDTOWORKLIST:{Worklist Name}\|{Worklist Note}\|{Display Confirmation value:Y/N} The Confirm Flag is optional and if set to ‘N’ will prevent a confirmation box from appearing.
#ALLERGY	Allergy Screen Window. Used to record all allergies and related reactions.
#ALERTSET	This allows one to set patient specific queries for alerts.
#ANTEPARTUM	Obstetrics/Gynecology Antepartum Flow Sheet
#ASSIGNEDPROVIDERS	This displays all the current providers associated with the patient (as determined by Billing Doctor and Rendering Doctor in any charge). In this window, one has the option to mark the role of the provider for the patient at the current time. Roles include Primary Care Provider, Encounter Physician, Attending Physician, Resident, and Consultant. In the standard Primary Care Decision Tree, this now appears at the bottom of the Triage Tree branch.
#AUTHORIZATIONS	Authorizations Window. This displays current authorizations for treatment and will allow the user to enter new authorizations.
#BILLDELAYED	Delayed Billing Window. This action property is utilized to record billing information without actually entering a charge. It is enabled in DIMPROF?.INI using the following setting. [DIM] Delayed Billing Mode=1 · Upon setting the above value, Billing from the tree using Billing Properties will not cause an immediate charge to be created but will instead put the charges in a temporary holding bucket which is visible only to this #BILLDELAYED action Process Delayed Billing window. A Bill button is provided that allows the charge to appear on the Bill screen and processed in claims processing. The purpose of this feature is to allow tree billing to occur while providing only the CPT code and any billing units specified with the CPT code. It will automatically read the entered ICD9 codes in #FINALIZE, which default from matching Authorization for current appointment number. This allows billing to be recorded even when the billing information is not complete. Rendering Doctor will default for billing if Provider Code is entered on the Security Setup screen. If not, last Doctor and Facility used in session will populate. The Delayed Billing screen allows the entry of up to 4 diagnosis codes and the editing of Units, Modifier and Remarks. · When using this action and “Use Appt No” setting is enabled, the delayed bill screen will always default to the day of the appointment. · It is possible to remove billing items that are linked to an appointment reason prior to processing a bill. This is not permanent however and the deletion is in effect only for the current bill processing step. Exiting from the window and reentering will restore the items again, as long as they have not yet been billed for the current Appt No. Billing items entered from the tree will be permanently deleted however (as before). · Delayed Billing will automatically execute an optional POSTBILL.SQL (in Tree folder) after processing charges. This can be used to perform SQL commands after processing such as marking certain Orders as done. · The Delayed Billing window includes a “View Document” checkbox, which when checked, automatically displays the document related to the current Appt. No. The system will remember the last checkbox status when moving to the next entry. The size of the Document View (on the right of the screen) will vary depending on the screen resolution. The width of the delayed billing may be 800, 1000, or 1200 in pixels. Thus at the widest resolution the document should be fully visible. For this reason, a high resolution monitor is optimal for the user performing this function. · An “Add” button opens a Confirm Charge screen where additional charges can be added directly (with a search function) without having to return to the tree. A line item remark is also available, which will be used during the actual billing. · In #BILLDELAYED, there are two queries that are used to populate the View Document window with a selected document. Both queries must be in OUTLINE folder. DELAYED2.SQL is a query that must return a chart section number (indexed starting from 1) for the document to be automatically displayed. An optional DELAYED.SQL query is provided to choose the correct page in that chart section. This is optional because in the absence of DELAYED.SQL, the page number is determined by a hard coded query that picks the highest page number for the selected chart section and appt no. within the above chart section determined in DELAYED2.SQL.
#BILLDELAYED2	N/A
#BROWSERPOPUP	Usage: #BROWSERPOPUP:Filename/URL\|CSS File\| szTitle\| Modal(Y/N Default=Y) a) Filename/URL Copies named HTML file from OUTLINE to HTML cache. Alternately opens URL. b) CSS File Copies named style sheet from OUTLINE to HTML cache for use with above HTML file. c) szTitle Window title. d) Modal Y/N. Default=Y. WIndow acts in modal mode unless explicitly set to not do so.
#CALLSTARTTIMER	Starts the “Call” timer, which is used to clock a collection call. The #CALLSTATUS property is used to end the collection call. The time recorded here will be tracked in the Collection Call Monitor in Workbench. This property causes no window to appear. However, any attempt to exit without closing the call will display an error message. This is used in the collection decision tree to track collector activity.
#CALLSTATUS	This property displays a window, which prompts the collector to enter the status of a collection call. The call will be ended (given an end-of-call time) when this function is used. This is used in the collection decision tree to track collector activity.
#CHGDIR	N/A
#CHIEF	Chief Complaint window. Used to enter Today’s chief complaints.
#CLOSE	Used to close the chart. Useful in scripts (SCRIPT.TBL). So if using #SCRIPT, #CLOSE can be the last action in the script in order to close the chart.
#CLOSECHART	Research
#COLLNOTES	Collection Notes Window. Enter collection notes here. The notes will be time stamped and the user entering the notes will be recorded.
#COLLTICKLER	Collection Tickler Entry Window. Use this to enter a followup for a collection process. You enter the followup (tickler) date and specify commitments made if any. This is used to create the Collection Tickler View in MD Workbench.
#CREATEVIRTUAL DOCWITHINTERPRET	This property has the ability to process Document Interpreter commands and can be used on DOC, DOCX, RTF, and TXT files.
#DEMOGRAPHICS	Patient Demographics Window (2 versions). A simplified version will be seen if DIMDB.EXE is removed from the current directory (\DIM). The more complete version with insurance information executes only if DIMDB.EXE is found. International clients should use only the simplified version.
#DESCSCORE	A new action property was added for use with the Indiana HAP Program (Psychiatry). To call the new windows, use the action property #DESCSCORE:filename Example: #DESCSCORE:LOF1.TBL In the TBL file, the following values are provided (values are examples): [General] Title=Level of Function – Adult [PROMPTS] 1=Factor 1A 2=Factor 1B 3=Factor 1C 4=Factor 2D 5=Factor 3E 6=Factor 3F 7=Factor 3G 8=Factor 3H 9=Factor 4I 10=Factor 4J 11=Factor 4K 12=Factor 4L 13=Factor 5M 14=Factor 5N [PROMPTS LONG] 1=Symptoms of Distress and Mood 2=Anxiety – Worrying 3=Depression – Sad, Blue, or Suicidal Thoughts/Actions 4=Health and Physical Status 5=Occupational Functioning 6=Daily Functioning and Independent Living Skills 7=Time and Task Orientation and Learning Ability 8=Thought Disorder 9=Social – Family Support and Interpersonal Relations 10=Consumer’s Satisfaction with Living Arrangement 11=Victimization 12=Disruptive – Inappropriate Behavior 13=Risk Behavior 14=Substance Abuse
#DICTATE:filename	Dictation using a Phillips microphone (USB version preferred) or just the use of the mouse is a standard feature. To use the dictation module, use the #DICTATE:filename action property. The filename is the name of the file as it will be saved in the \MEDINFO\RECORDS\C01\SOUND folder. An example format is #DICTATE:&MRNO.WAV which will create one sound file per medical record. #DICTATE:&MRNO-&DATESQL2K.WAV will create a unique sound file per day. #DICTATE:&MRNO-&USER.WAV will create a unique sound file per user, per patient. To use a microphone that is not Phillips Speech Mike, make the following entry in \MEDINFO.CLIENT\DIMDICTATE.INI: [Executable] default=1
#DISPENSE	This action property displays the Vaccine History Window for dispensing meds and has a single TYPE parameter (which is optional). It is intended to dispense non-drug items such as immunizations. #DISPENSE:TYPE
#DISPENSENEW	Allows parameters to be added to the action property which autopopulates the Immunization Entry Information fields and shows the result on the top of the Dispense window. #DISPENSENEW:DRUGNAME\|DRUGID(obsolete)\|DOSE\|MEASURE\|SITE\|ROUTE\| MANUFACTURER\|TYPE(obsolete) Note that all the parameters are optional.
#DISPENSEMODAL	Functions like #DISPENSE. Opens the Vaccine History screen but requires user interaction before returning to the parent application, such as clicking the Exit or Add button. #DISPENSEMODAL:TYPE
#DISPENSENEWMODAL	Functions like #DISPENSENEW. Opens the Vaccine History screen but requires user interaction before returning to the parent application, such as clicking the Exit or Add button.
#DOCCOLLECTION	Launches the Document collection from a Decision Tree node or HTML action. Syntax is as follows:: #DOCCOLLECTION:&XACID\|##\|{QUERY.SQL}\|DocumentType1\|DocumentType2\|DocumentType3\|... &XACID - sets the Appointment Number for which associated documents will be opened. [Optional] TOP N documents to open. Values: Integers from 1 to 99. Default = 1. [Optional] Link related appt numbers using a SQL statement in a defined SQL file. [Optional] Document Type(s) - defines which documents will be opened. [Required] Allow for more than one Document Type paramter. Allow for wildcards when many Document Types of a similar name must be included. Example: Diagnostic Report%.
#DX	Opens Add Diagnosis screen.
#DXMODAL	Functions like #DX but requires user interaction before returning to the parent application.
#DYNAMICXML	This allows one to print customized XML output which can be used to create CCD (Continuity of Care Document) or CCR (Continuity of Care Record) formatted Patient Care Records. To use, supply and action property in the following format: #DYNAMICXML:Sourcefile name\|Target Folder\|Output File name
#ECGVIEW	Calls the Questionnaire for ECG, which launches the Brentwood ECG Active-X Control.
#EDIT	Free Form Text Edit Window. It must be an ASCII file that is located on the OUTLINE directory. When you finish by pressing the SAVE button, a choice of Chart Sections will appear. After choosing a Chart Section, the Chart View Window will appear showing the new document. This option will not print the second page header by default. To activate second page heading, use the following dimprof setting: [DIM] Always Print Page 2 Heading In Tree=1 (See Creating Letters and Forms section.)
#EDIT:Textfilename	This action property functions exactly as #EDIT, however, if an optional TextfileName is supplied as an argument, the contents of the edit window will be initialized with the contents of TextFileName.
#EDIT?	This action property defaults the Service Date to the date of the appointment. To activate, use the following DIM setting: [DIM] Use Appt No=1
#EDITAPPTINFO	Opens the Edit Appointment Info screen, which allows the user to: - Change the appointment reason - Change the referring doctor - Change the STAT flag - Change the Priority - Change Appointment Notes Note: Requires the 'Use Appt No' is enabled.
#EDITB:Textfilename	This action property functions exactly like “#EDITC” (see below) except that the Print button launches a custom program for bar coding. This is not for general use.
#EDITC:Textfilename	This action property is the same #EDIT above except that it will store the document in the current chart section. A list of chart section choices will not be displayed. To make sure you place the document in the right place, you must use it with the [] markers. For example: [1]#EDITC This will save the document in chart section 1. After you use this property, the Chart View Window will appear to show the new document. An option to turn the header on/off when printing from #EDITC or a View Property window is available in DIMPROF?.INI: [DIM] Print Header in View Property=1 (1=On/0=Off) (See Creating Letters and Forms section.)
#EDITN:Textfilename	This action property is the same as #EDITC above except that the new document will not be displayed to the user after saving. Like #EDITC, you must specify the chart section using the [ ] markers when using this property. (See Creating Letters and Forms section.)
#EDITNT	This action property is the same as #EDITN above.
#EDITENHANCED	This action property is the same as #EDIT above except that it displays the document in an editor window where it can be enhanced and/or Word opened to enhance. (See Creating Letters and Forms section.)
#EDITENHANCED:filename	This action property will automatically take a boilerplate from the tree folder, pass it through the document interpreter, save it in the currently pointed chart section, and automatically display the Document Repository and the Enlarge button – Editor Window. Format for use is as follows in this example: [1]#EDITENHANCED:vwside.txt This feature is intended for Transcriptionists (Radiology) to have access to a WYSIWYG editor for final report alignment and then for immediate printing.
#EDITENHANCEDN	Similar to #EDITENHANCED. Opens the Enhanced Editor but does not display the document in the Document Repository after saving it
#ELIGIBILITY	This displays the same screen as the Eligibility View in the Master List.
#FAMILY	New Family History developed for Meaningful Use Stage 2 certification. Opens new Family History window from the Decision Tree. Note: Does not replace #FAMILYH, which is for legacy family history reference only.
#FAMILYH	READ ONLY as of v7.6. Family History, Selection lists come from FAMILYH.TBL and FAMILY.TBL in the OUTLINE directory. Use #FAMILY instead.
#FILEOUT:Filename	When using the new #FILEOUT action, the system will read the filename specified from the OUTLINE directory and pass it through the document interpreter. It will then save this processed file, and using the same name as the filename specified in FILEOUT, it puts the processed file into the TEMP directory. This feature can be used to use the decision tree to create data that will be exported to a file (using the Document Interpreter to process the data and SQL statements). The file can then be passed to an external program to be used to pass parameters. The &TEMPFILE global variable returns the complete path and file name of the temp file created by #FILEOUT. Here’s an example of how this can be used. Create a tree node and give it an action property of #SCRIPT:TEST. Then modify SCRIPT.TBL in the OUTLINE directory (or create it if it does not exist) with the following entries: [TEST] 1=#FILEOUT:VWSIDE.TXT 2=$NOTEPAD &TEMPFILE This will cause the program to search for VWSIDE.TXT in the outline directory, then it will pass it through the Document Interpreter and create the file VWSIDE.TXT in the TEMP directory. Next NOTEPAD will display the file automatically. You may substitute your own external program for NOTEPAD.EXE in the above example and this will allow you to pass a large block of data from MedInformatix to an external application
#FINALIZE	This action property is used to mark an appointment as completed. Once marked as completed, it triggers automatic billing of charges that are tied to an appointment reason code. (#BILLDELAYED) This feature is used to signal that billing can be done. The action property allows users to enter up to four (4) ICD9 codes. Diagnosis priority is assumed by order of diagnosis entry (i.e. first item is primary). However, a diagnosis entered on the Confirm Appointment window will appear as the first ICD9 in this action. When authorization is created, it will display diagnosis options based on the content of the matching authorization for current appointment number. It requires the DIMPROF setting: [DIM] Use Appt No=1 When marking an appointment as completed for the purpose of billing, one can also set the appointment as “Finished”. This will be done automatically but can be disabled using this DIMPROF?.INI setting: [DIM] Finalize will Finish=1 When using #FINALIZE to finalize an appointment, it is possible to prevent its reuse on the same appointment, as well as prevent the running of a script on Exit. To enable this special behavior, set the following in DIMPROF?.INI: [DIM] Finalize Once=1
#FINALIZE2	This is similar in appearance and functionality to #FINALIZE, however, it only allows one action, which is to update a DX. If diagnosis is pulled from authorization, updating the diagnosis here will update the authorization record’s diagnosis. A diagnosis entered on the Confirm Appointment window will appear as the first ICD9 in this action. Updating a diagnosis can be done at any time including before or after the appointment is finalized.
#FLOW:FlowsheetFileName	This launches a flowsheet format for viewing data which is basically made of up of a grid of columns and row. Each column is a date and each row displays unique data points. The data comes from SQL Queries, which can be customized for each row and column. Clicking on flowsheet rows may launch another function based on action properties. See chapter on Flowsheets.
#HPI	This provides a new way to enter History of Present Illness which is free form. It pulls up a new E&M Billing Window.
#HTMLDOSCRIPT	An action property #HTMLDOSCRIPT allows custom HTML scripts to be created that can communicate with a web server. The responses can be hidden from view from the user and the result of the interaction with the web server is then displayed in a modal child window for the user to acknowledge. This sophisticated feature can be used to (a) enable web based eligibility checking (which can occur in the background) and (b) drug interaction interfaces with any drug interaction vendor that provides a web server connection. This feature launches an actual Internet Explorer session and thus any feature available to that browser, including Active X controls are usable. For steps on using this feature, see Appendix A.
#ICD9	Displays the Problem List. Depending on the parameters passed when starting it, it can default to showing a common list of Diagnosis codes, a problem focused list from the ICD9-CM list, or the entire list of codes from ICD9-CM. It can search a particular range of ICD9 codes based on a section name in \DIM\OUTLINE\ICD9.TBL. For Example, the following action property will call up only the back pain related diagnosis in the ICD9 table. #ICD9:BACK PAIN Entry in ICD9.TBL: [Back Pain] Disc Related Disorders=722 Muscle, Ligament and Fascia=728 Spinal Stenosis=724 Spondylosis =720-721 Osteochondropathies=732 Deformities of Spine=737 You can also enter the problem focused ICD9 codes in ranges, as in: Symptoms - Abdominal=789.0-789.36,789.6-789.70
#ICD9OLD	This is a legacy function and should no longer be used. It will be removed in future versions. Use #ICD9 instead.
#IMPORTVIRTUALDOC	This action property can import a file from the inbox folder or some other specified folder into a virtual indexed folder on the server. The document may be any file format for which an Active-X viewer is available for Internet Explorer. The imported document will appear in the Document History window and will be given a name on the server of MRNO+Date+Time.Extension. The parameter DELETE allows the source file to be deleted after successful import. This will allow a new file to be written in its place without any conflict, to be import again (in general, into another chart). This request fulfills the need to be able to import a patient photo, taken with a static filename, into the Document Repository.The parameter OPENCHART to explicitly open the Document Repository after successful import. By default, Document Repository will not open. (Similar to #PDFFORM OPENCHART parameter. To use this feature, supply an action property in the following format: #IMPORTVIRTUALDOC:FolderTitle\|FileName\|AlternateSourceFolder\|DELETE\|OPENCHART FolderTitle must be a label in the Document Repository as entered in CHART.TBL (Chart Sections to Show Section) and must be an INDEXED folder. The Filename will be a fixed name and must include the extension to indicate the type of file being imported. Examples: #IMPORTVIRTUALDOC:Diagnostic Test PDF\|test.pdf The above example pulls from the inbox since the 3rd parameter was not supplied. #IMPORTVIRTUALDOC:Diagnostic Test PDF\| test.pdf \|\\SERVER\C$\SCANS\ The above example pulls from an alternate source folder.
#KEYVIEW:QuestName	This routine calls up a list of key fields, which will be used to access SQL Questionnaires that are designed for one to many data structures. The program will list up to four selected fields from the same table used by the SQL Questionnaire with the same name. When defining a Questionnaire, a place is given to supply the SQL Query which will populate a #KEYVIEW window. Also, different SQL statements must also be provided to delete from the list or to edit an existing entry from the list. This advanced feature allows creation of sophisticated one to many data entry windows with no programming. However, use of this feature still requires knowledge of a programmer because of its advanced capabilities. From a KEYVIEW window, when performing an ADD, clicking View Text will display the text but will also be the equivalent of DONE (save and exit). EDIT will function as described for Questionnaires.
#LABEDIT	Opens the Diagnostic Test Entry screen used to manually enter lab data, which will look like it was imported using the ASTM or HL7 interface. Configuration data is stored in LAB.TBL in the OUTLINE directory. (See Lab Data section of this manual.) This accepts up to 80 characters in the value area. Note however that such large values will appear right justified in the Lab View and may be confusing if you don’t expand the column. Long values should be indicated in comments. The LOINC code for each Observation can now be specified in LAB.TBL. LOINC codes are a national standard for coding Diagnostic tests. The last (5^th parameter) will be the LOINC code as shown below: [CBC W/Diff] 1=White Blood Cell Count\|thous/mcl\|3.8-10.8\|WBC\|MYLOINC 2=Red Blood Cell Count\|mill/mcl\|3.90-5.20\|RBC\|MYLOINC
#LABVIEW	View Lab Results. Lab results are imported either by the ASTM Lab Interface or the HL7 Interface modules. This window allows filtering on labs by LOINC Code (if used). LOINC Code is kept in CLLAB.OBSERVE_CODE and is imported from the Lab provider.
#LAUNCHTREEINSTANCE: actionproperty	This action property will launch a new instance of the application (assuming instance limits have not been exceeded) and the new instance will automatically go to the Decision Tree using the same patient, same company, and same user logged in. Exiting from the Decision tree will terminate this new instance of the app. The purpose of this new feature is to allow the medical record to remain open while returning to perform other administrative function like scheduling in the application, while allowing a visual reference to the patient’s record. This is useful when one needs to refer to a scanned document that is stored in the chart. The syntax of the command is: #LAUNCHTREEINSTANCE:actionproperty. Example: #LAUNCHTREEINSTANCE:[74]#VIEWCHART This example will automatically display the chart section 74 of the patient’s record in a separate instance. Note that this instance does not reduce the “Instance Limit” setting in CLIENT.INF. This property now allows launching of a different account number as well. Users will need to pass the name of a file containing a SQL statement (in OUTLINE folder) after the “~” delimiter which then needs to return an ACCOUNT. Example: #LAUNCHTREEINSTANCE:#VIEWCHART~ACCOUNT.SQL or #LAUNCHTREEINSTANCE:~ACCOUNT.SQL As before, if this SQL file is not provided as a parameter, the system will launch to the same patient as before. Note that the above feature assumes the patient is in the same company.
#LOADDLL	This action property was created to allow third parties to load external DLL modules in the Decision Tree without changing the main program. DLL’s can be loaded using the following command format: #LOADDLL:dllname=myowndll;param1=hello;param2=yes
#MEDINFORMATIX	For HTML clipboard users. #MEDINFORMATIX:ACTIONR is used to execute a cipbaord refresh upon return to the clipboard from the action property. This allows the clipboard to immediately display data entered or modified by an action property.
#MEDREPORT	Allows creation of reports related to a single patient. To use this feature, pass parameters to the action property as follows: #MEDREPORT:MEDINFORMATIX:{report filename in tables directory} – i{ini file in the tables directory} –s \|{Report Name Displayed on the Main Window}
#MEDS	Opens the Medications History Screen. Shows current Medications (From External Source) - Nurse.
#MESSAGE	Enter a New Message. Messages entered from here can be viewed in Workbench and using the #MSGVIEW property below.
#MSGVIEW	View Patient's message history.
#NEWEPI	This feature is used in billing. It increments the current episode number so that any charges which follow will belong to a new episode. You are able to provide different claim information for charges in the same batch as long as they have different episode numbers. Each episode number results in a separate claim.
#NOTIFY	The on-demand notification is a single SMS notification for a single patient account that allows the user to immediately contact a patient with a text message. Usage: #NOTIFY:{do not use}\|{do not use}\|Predefined text Use '?' in Predefined text parameter to allow user to free-text the message
#ORDERIMMUNIZATION	This checks the new Dispense table for previous dispensing of this immunization and if a reaction was recorded in the past, the reaction will be displayed with a warning. This allows one to stop the order if desired. It is formatted in the following: #ORDERIMMUNIZATION:INJ\|immunizationname
#ORDERS	Create New Orders. This is an alternate method of entering orders besides using the Orders Property on the tree.
#ORDERSBYDEPT [Deprecated]	[Deprecated] This action property displays a different method of entering orders. This window allows the department to be selected, and the list of orders and memos are also selectable, all from a combo box. The list of departments and orders are defined in PACSORDR.TBL and has the following format: Departments] CT=1 LAB=1 [Orders] This is an Order=1 This is another Order=1
#ORDERSET	This action will launch an Order Set Confirmation screen where multiple orders for order departments can be selected and an order created. Supporting order and billing information, such as diagnosis, facility, and rendering doctor are provided once, which eliminates individual confirmation of orders and speeds the order entry process. Rendering Doctor will default for billing if Provider Code is entered on the Security Setup screen. If not, last Doctor and Facility used in session will populate. This action can allow the inclusion of a claim remark for individual order items. Format of an Order in a *.SET file is: Department\|Order Description ^Order Code\|Units\|Measure\|Memo\|STAT Y or N\|Days Due\|CPT Code or Macro\|Claim Remark\|Modifier^Modifier Percent Example: [Laboratory] 1=LAB\|Panel-Arthritis\|\|\|\|N\|\|80072\|Line Item remark 2=LAB\|Bun & Creatinine\|\|\|\|N\|\|#BUNCR 3=LAB\|Panel-Arthritis(2)\|\|\|\|N\|\|80072\|Line Item remark\|55^80
#ORDERSET: OrderFileName.set	As in #ORDERSET, this action launches the Order Set Confirmation screen where multiple orders for the specified departments can be created in the file OrderFileName.set, stored in the OUTLINE directory. File Contents: [%DEPT%] Laboratory=1 Pathology=1 Radiology=1 The above example specifies the selection of departments. These do not have to match the actual department codes in DEPT.TBL since they just act as sections of order. The actual orders for each of the departments listed above must be defined, using the following format: Department\|Order Description ^Order Code\|Units\|Measure\|Memo\|STAT Y or N\|Days Due\|CPT Code or Macro All values other than Department and Order Description are optional. Billing is triggered by the [BILLING] Setting for the department as is used in other standard orders. Using ‘Laboratory’ as an example, the section in the file would appear as follows: [Laboratory] 1=LAB\|Panel-Arthritis\|\|\|\|N\|\|80072 2=LAB\|Bun & Creatinine\|\|\|\|N\|\|#BUNCR The format is almost exactly like the Order Property on the tree, except that a CPT code can be placed in the 8th position for billing. This CPT code may also be a billing Macro. Items must be listed in sequential order starting from ‘1=’. Each “.SET” file may have any number of departments but may not exceed 64K in size. A sample of this file is PLTEST.SET in M6DISK5.EXE (Primary Care Decision Tree).
#ORDERVIEW	View Patient's Order history.
#OVERRIDEDATE	This launches a date control and allows the user to select a date to override the &DATESQL2K global variable and is valid only for the current tree session. This has the effect of changing the date used in boilerplates and is useful for enabling the recreation of a document for saving to the repository such as when a doctor forgets to save the document for a prior date. It will also load unsaved boilerplates during the date specified and load it with the current date. It will then delete the old boilerplates from the records. Once the date has been overridden to go to a past date, the #QA’s will automatically backdate their entries to the prior date, including any new QA entries. The global variables &DATE, &DATESHORT will use the past date in addition to &DATESQL2K.
#PASTE:TXT	This action will cause text data currently in the Windows clipboard to be pasted to the Document Repository of the current chart section. This command should be used with the specification of a chart section as shown in this example: [1]#PASTE:TXT
#PASTE:BMP	This action will cause bitmap data currently in the Windows clipboard to be pasted to the Document Repository of the current chart section. This command should be used with the specification of a chart section as shown in this example: [1]#PASTE:BMP This command is used specifically to enable quick transfer of scanned documents from another software into MedInformatix.
#PASTH	Research
#PASTHIST	This option which allows entry of Past History as coded ICD9 items, and has the ability to assign a “History Group” to each added item. This is helpful for more precise sorting of the Past History in documents. The history groups are: Chronic Illnesses, Accidents, Surgeries, Infection History.
#PATAPPT	Opens the View Appointments (Appointments For…) window.
#PATARV	Opens the patient's Appointment Requests window. For use with the ARV.
#PATIDEDIT	Allows the user to define custom demographics values that are stored in a new CLPATIENTID table. This same window is shown in Demographics with the button title ‘Patient Identifiers.’
#PCPCOPY	Opens the Provider Copy List where providers who should receive a copy of a report can be selected from the Referral Source Database and added to the screen. Providers entered will be unique to an Appt No. This feature also includes a COPY LAST button which will copy the provider list of the highest previous Appointment Number. Used often in Radiology to send reports to additional providers. Providers entered in this list will override any providers listed in the Related Providers Information in Demographics (CLPCP Table) when printing copies in the Print Server Module. If the print server module is not installed, or if the Use Appt No setting is not used, this feature will have no effect.
#PDFFORM:Filename.xml	Opens up an interactive PDF as defined in the named XML file.
#PHARMACY	This brings up the Pharmacy Search screen. This allows users without access to the Medications History window to enter the Pharmacy preferences for the patient.
#POWERSCRIBE	This action property is used to activate MedInformatix Powerscribe Client Dialog.
#PROBLEM	This is a legacy function and should no longer be used. It will be removed in future versions. Use #ICD9 instead. Problem List/Diagnosis Entry. This is used both for billing and document to record the diagnosis for the patient.
#PROBLIMO	Launch the IMO Add Problem window directly, without having to navigate to the Problem List.
#PROGNOTENEW: SectionName	This action property is related to #PROGNOTES which is described below. It is a short cut feature because it allows a new note to be entered automatically without having to enter the Progress Notes View and click on the New button. In other words this is the “New Note” function of #PROGNOTES. This is useful if the user is expected to primarily enter a new note each time and thus cuts out the step of having the view existing notes first.
#PROGNOTES	This option opens the Progress Notes Window, where short notes for the medical record are entered. The entry date and user of the note will be automatically tracked and notes will be displayed from newest to oldest. Notes may be edited only by the original creator and only on the same day of creation. Notes can accept up to 4096 characters per note entry. An RX button is available for easy access and a Send as Message option allows a user to send a selected note to other users. (i.e. Used by nurse to alert doctor of important note(s)) A new, blank note may not be saved. However, an existing note can be made blank (based on rights) and saved.
#PROGNOTES: SectionName	This is a “database” version of the progress notes. You can pass the section name to this module, which will cause only the messages belonging to the same section to be displayed.
#PSTMT	Launches the new window from the Decision Tree.
#QA:FileName	QA Form displays a Question/Answer data entry window whose data is stored in the CLDICTIONARY table. The questionnaire format is defined in a *.QA file which is referenced by FileName. This data entry form is easily built by non-programmers and ensures that data is stored in a SQL database for historical analysis.
#QA2:FileName	Same as a QA form above, except that the Question area is much longer than the answer area. This is a good format when the answers are expected to always be brief (such as Y/N).
#QAHTML:Filename.HTM	The new format of a QA HTM file is much simplified and by default all the ‘Questions/Answers’ are organized into tables. It would be a simple matter for someone knowledgeable in the use of <Table> tags in HTML to rearrange this into any desired format (such as double columns). Both versions (old and new) can coexist). The new filename convention of the generated file will be the same as the QA file name but with an HTM extension (EXAM.QA will create EXAM.HTM). The new HTML files can be cut and paste to run irrespective of the host QA file. For example, you could cut and paste to combine EXAM.HTM and ROS.HTM into one. An HTML file of any name containing QA data can be launched alternatively using the action property: #QAHTML:SomeQA.HTM. Or you can also use the javascript command: <a href="_FR:QA\|LAUNCH\|SomeQA.HTM"> (Launch Some QA)</a> To keep the old and new separate, the new QA uses, QA.HTM (host), QA.JS and QA.CSS which are all in \MEDINFO\HTMLSTD.
#QAX2:FileName	Same as a QA form above, except that the Answer area is designed for Bilateral Ophthalmology QA's (OD and OS).
#QUESTIONNAIRE:Title	Execute an SQL Questionnaire. Runs a predefined SQL Data Entry Window, which accesses and modifies data in a predefined SQL Table. SQL Questionnaires are created using the SQL button in the Decision Tree.
#QUESTIONNAIRER:Title	Execute an SQL Questionnaire as described above. Also force a refresh of all global variables, Decision Tree Title, and the Decision Tree Side Text.
#RECALL	This action property displays the standard Recall screen when billing certain CPT’s.
#REFRACT	Ophthalmology Refraction and Visual Acuity Data Entry window. - The Refraction screen now has the Prism broken out as Horizontal vs. Vertical. Any previous values will show up in the Horizontal box. Use of this feature will require modification of Ophthal boilerplates to make use of the new columns in CLOPREFRACT. The old Prism items will still contain the horizontal values. Additional prism values in the table with a prefix of V (VPRISM, VBASE, VPRISM2, VBASE2) will store the vertical values. - The tables supplying the values from prism have been changed. Prism options were stored in VAPRISM.TBL and VABASE.TBL, which will now hold the horizontal values. Vertical values will be stored in VAPRISMV.TBL and VABASEV.TBL. - A Refraction Type “Prescribed2” is available in the Refraction window as a secondary prescription field for those requiring more than 1 optical prescription. - The Refraction window has a second set of Prism values and are labeled Distance and Near and the history window now has more data. - When the Add and Int fields are filled in OD, it will automatically default the values OS. - The field tabbing was changed to go from OD to OS for each set of related values rather than for the entire set of OD values and then OS values. - Note fields were added for each eye for retaining miscellaneous additional information.
#RELATEDPROV	Opens a dedicated Related Provider Record screen, allowing quick access to view Internal Care Teams and external specialists. The Related Provider Record also remains available towards the bottom of the Demographics screen.
#RETURN	Goes to decision tree defined in DIMPROF.INI under the entry “Flow Chart File”. This serves as a quick return to the topmost tree after you’ve used the #TREE property to move to different trees.
#RX	Prescription Writer. Opens the Medications History screen. Same as #MEDS except it assumes the Physician is entering the prescriptions and thus more rights are given (such as refills).
#RX:{MEDID}	Opens the Medications History screen and searches on the MEDID.
#SAVETREE:TreeFile Name	Save Desired Startup Tree. This function stores the name of the decision tree, which should be loaded first in DIM.INI. This takes effect only for the current user and the current computer.
#SCANIMAGE	Provides direct control of TWAIN driver equipped scanners. Certain parameters must be supplied – for detail, see Imaging: Scanning Documents. Opens scan option from selected branch and always attaches today’s date. (i.e. Reception Branch; Scanning; Insurance Card). It also specifies file format, color or b/w and the compression rate for ease of storage. To have the document scanned directly into a specific chart section, the following format is required: [{Document Type}]#SCANIMAGE:RESOLUTION\|FILE FORMAT\|IMAGE SHADING\|COMPRESS n where n is a number in the range of [1, 100]. For example, when a user clicks on a branch called Scan Insurance card, the property would be as follows: [Insurance Card]#SCANIMAGE:RESOLUTION150\|JPEG\|GRAY\|COMPRESS 100
#SCANIMAGE: PDF\|SETUP\|SHOWCAP	This allows scanning directly into a PDF file that will be stored directly into the Document Repository.
#SCANIMAGE: OPENCHART\|SETUP\| SHOWCAP	This forces the Document Repository to open after the scan.
#SCANIMAGE WITHCONFIRM	Provides ability listed for #SCANIMAGE with same setup requirements, however opens Confirm Scan screen with scan option that allows user to confirm or changed Date, Document Owner and Save of scanned document. (See Imaging: Scanning Documents.)
#SCANIMAGEWITHCONFIRM: PDF\|SETUP\|SHOWCAP	This allows scanning directly into a PDF file that will be stored directly into the virtual section. This also displays a confirmation window.
#SCANIMAGEWITHCONFIRM: OPENCHART\|SETUP\| SHOWCAP	This forces the Document Repository to open after the scan. This also displays a confirmation window.
#SCRIPT:ScriptName	Scripts are defined as sections in SCRIPT.TBL. Scripts can contain any action property and is defined in the SCRIPT.TBL file as [ScriptName] 1=Action Property Text 2=Action Property Text 3=Action Property Text … n=Action Property Text A. “Stop” button will appear in the lower right corner when a true script is launched from the Decision Tree It will stop the script and return to the tree after exiting the repository. However, when launching a document directly from Orders or Messages, a “Go to Tree” button will appear in the lower right corner. **See detailed explanation at the bottom of this section – Syntax of Action Property.
#SEARCHAPPT	Opens the standard Appointment Search screen.
#SEARCHAPPTF:Filename	Note that when using #SEARCHAPPTF:filename, although the content of filename will be processed by the Document Interpreter, the “\|” symbol must also be generated by the SQL statement as in this example below. This is because the “\|” symbol is recognized as a delimiter in the Docinterpreter &{SELECT 'DR'+'\|'+'TJ'+'\|'+'FUP'+'\|'+'WILSHIRE'+'\|'+''&DATESQL2K''+'\|'+'&DATESQL2K'+'\|'+'3'}
#SELAPPTALL	This action property brings up the Select Appointment screen for the desired patient. This allows users to select another appointment number to match the transaction and update the clipboard and decision tree. A checkbox will allow only tagged appointments to populate the field.
#SENDTOPORTALUSER	Creates a predefined message to the patient portal controlled by a boilerplate or a text file and contains links to patient education (e.g. website, video). #SENDTOPORTALUSER:[[BOILERPLATE]] Example: #SENDTOPORTALUSER:DIABETES.EDU, where #SENDTOPORTALUSER: is the action property and DIABETES.EDU is the boiler plate.
#SOCK:Command File	Sends a TCP Socket Message. Format of Command file is: IP address\|Port Number\|Text Message
#SQLQUERY:SQLFileName	Execute SQL Query. This function reads the contents of the specified file in the OUTLINE directory and executes It as a SQL statement. It must contain a valid SQL statement. This action property does not prompt for confirmation.
#SQLQUERYP:SQLFileName	Execute SQL Query as above but prompts user for confirmation. SQLFileName must be in the OUTLINE directory.
#STICKY	Sticky Note (Handwritten)
#STICKYT	Sticky Note (Text)
#TICKLER	Allows users to view and add Ticklers from the Decision Tree: #TICKLER:F/U Code (optional) - default [All]
#TICKLERNEW	Same as #TICKLER: #TICKLER:F/U Code (optional) - default blank so that the user must select the option.
#TRANSCRIBENOTES	Same as #PROGNOTES but does not default user ID to current user.
#TREEC:ConditionFile.CND	Jump to another tree if a condition is found to be true. Conditions are set up in Conditional Tree Setup Table.
#TREE:TreeFileName	Jump to another tree. Displays the top level of the specified decision tree file name, which must be in the OUTLINE directory.
#TREE:%PTYPE	This is an advanced variation of #TREE as described above. This command allows you to jump to a different tree for every different PATIENT TYPE code. The choices of different TREE.INI’s for each patient type code is defined in advance in a PTYPE.INI file. This is often used to present different “Billing Trees” to a user depending on the patient’s financial class. To use this feature, create a file PTYPE.INI with the entries as shown in the example below: [PTYPE] MEDICARE=MBILLING.INI GROUP=GBILLING.INI CASH=CBILLING.INI DEFAULT=BILLING.INI The above example shows patient types MEDICARE, GROUP, and CASH using their own billing INI files. All other patient type codes will use BILLING.INI, which is the value for the entry DEFAULT. To avoid a conflict with this feature, do not use a patient type code called DEFAULT. Reserve that name for this purpose. The %PTYPE value instead of the name of the Tree INI file can be accepted anywhere else in the system where a file name is expected. For example, you can specify %PTYPE as a startup tree in DIMPROF.INI under the entry “Flow Chart File”. You can also use %PTYPE in the #SAVETREE action property to make the %PTYPE option be used on the first tree displayed.
#UBHCFA	Claims Info Window
#URL:filename #URL:url	This property will launch the filename indicated and the corresponding program associated with the extension. This can be used specifically to launch HTML files by name and will display the default browser. (i.e. C:\WINDOWS\NOTEPAD.EXE.TEST.TXT”) In addition to filenames, one can also pass a URL and it will launch the website. Currently the parameter following #URL cannot be greater than 255 characters. When using global variables, the following syntax applies to form a proper URL: {&}variable (e.g., &{&}COMPANY &{&}ACCOUNT)
#URLFROMFILE:file name.url	This is the same as #URL except that in order to exceed the 255 character limit, the url data itself must be placed in a “yourname.URL” file. Then you can use this action property to call up that file. The contents of the file will be pre-processed in the document interpreter before sending. The file can be up to 64K large.
#VERNOTES	Verification Notes Window. Enter short notes for the medical record in this window. The entry date and user will be automatically tracked. Notes will be displayed from newest to oldest. This is a “database” version of the progress notes.
#VIEWCHART	Opens the Document Repository to the default, or last, Document Type. TREE.TBL determines default Document Type.
#VIEWCHARTAPPTNO	Automatically launches the Document Repository into the page and section of the latest document related to the Appt. No. This is used only when the DIM “Use Appt No” setting is enabled.
#VIEWER:SNDREC32\|.WAV	This will call up a voice (WAV) file, which belongs to the patient currently selected in the Decision Tree. The WAV file will be named MRNO.WAV where MRNO is the hexadecimal form of the Medical Record Number.
#VIEWER:exe_name\|file_ext	This routine will call up any EXE file specified by exe_name and which can be passed a file name parameter in the format of MRNO.file_ext, where MRNO is a hexadecimal Medical Record Number. This can be used to launch graphic viewers or AVI / MPEG viewers which can display patient specific multimedia data.
#VIEWERBOX:	Integrates external files containing medical records into the Decision Tree. There are often other sources of medical data, including transcription documents, JPG images from cameras, PDF files from Ophthalmology equipment, TIFF files from scanned or faxed documents, and even sound files. There is now a way provided to view or listen to these documents, while in the Decision Tree, without importing the data into the Document Repository. If you create the above-described documents, you need to store these in a fixed directory location on your server, to which all users have network access. You must also store the documents using a file naming convention that includes the medical record number and other document identifiers. For example, if you decide to keep your word transcription files, you can put these into a \DIM\RECORDS\WP folder. Then you could save the documents in a format such as MRNO-DATE.DOC. Here are some sample names kept in this format: 1-20010717.DOC, 1-20010718.DOC. In this example, the Medical record number is “1”. To call up the documents from the Decision Tree, one will use the new action property #VIEWERBOX and this will display a window that will list all files found in the specified directory and matching the file search criteria. When a specific file (document) is selected and the View button is pressed, the system will launch the document with it’s corresponding associated application. The procedure for making this work is: Make a tree item and use the action property #VIEWERBOX:WindowTitle\|FileDirectory\|FilenameWildcard\|DeleteEnabledFlag\|KeepWindowOpenFlag WindowTitle = Any Desired Text to describe the documents listed FileDirectory = Path to directory containing files to be displayed FilenameWildcard = Filename, presented in wildcard format to select for viewing. An example of this is “&MRNO-*.WAV” which will display all files starting the patient’s medical record number and ending with “.WAV”, with any characters in between. DeleteEnabledFlag = This value is “Y” if you wish the delete button to be enabled and “N” if the delete button is to be disabled. The default is “N”. KeepWindowOpenFlag = This value is “Y” by default which means that the Viewer List window will remain open until the exit button is clicked. The value “N” means that the window will be automatically closed after selection of an item.
#VIEWERDELETE:file_ext\| Message	This action property is used in conjunction with the #VIEWER action properties described above. It can be used to delete the file created by the above EXE’s. To use it, you must specify the file extension (such as “.WAV”) and the Message portion will specify the prompt to be presented to the user. Example: #VIEWERDELETE:.WAV\|Delete Voice File? This example will delete the files created by #VIEWER:SNDREC32\|.WAV
#VIEWCHART	View Documents in Current Chart Section. You must specify the current chart section number using the [Number] feature or unexpected results may occur. For example, this is the correct usage: [2]#VIEWCHART
#VIP	Allows a user with privileges to set VIP access for another user without privileges at the account level instead of replying on the global setting. This adds a greater degree of control to the "one-size-fits-all" global VIP access control.
#VITALS	Enter Vital Signs. Also displays a “More” button that activates #LABEDIT action property with the labs template VITALS. Allows users to expand amount of lab data captured during Vitals taking process.
#VITALSHIST	This shows a history of Vital Signs in a flow chart format. Buttons are available to add a new vital sign or delete an existing one. Entries can only be modified during the same day. Also displays a “More” button that activates #LABEDIT action property with the labs template VITALS.
#VITALSHISTPEDS	This is similar to the Vital Signs Flow chart above except that the content is geared towards the pediatric practitioner (because it displays Head Circumference and Height more prominently). Also displays a “More” button that activates #LABEDIT action property with the labs template VITALS.
#XACVIEW	This object displays the transaction history window, which displays all billing information and accepts payments. This window is an integral part of the billing system.
#ZEXEC\| &COMPANY\|ELGBTY\| <ELG.TXT>	This is used to perform the Zirmed Real-Time Eligibility Check.
TextFileName	Any TXT file can be specified as an action property. The document will immediately be inserted into the current chart section of the Document Repository. TheTextFileName should be in the FORMS directory. The TextFileName should be preceded by a chart section identifier [Number] as shown in the example below: [1]EXCUSE.TXT
GraphicFileName	Any DIB or BMP formatted graphic file can be specified as an action property. The image will immediately be inserted into the current chart section of the Document Repository. The GraphicFileName should be in the FORMS directory.. The GraphicFileName should be preceded by a chart section identifier [Number] as shown in the example below: [1]SOAP.DIB
[Chart Section Number]	This chart section identifier can precede any action property. It will cause the system to automatically change the current chart section to the specified Chart Section Number which can be from 1 - 255. This identifier can also be a property by itself.
[?]	This Change Chart Section option opens the Save Document-Select Chart Section screen where the user is able to select the chart section (from CHART.TBL – Chart sections To Save) in which to save the document.
[?I]	By adding the ‘I’ to the question mark, the option opens the same chart selection screen, but pulls from CHART.TBL {Chart Sections to Save Inbox], which adds Virtual Chart Sections.
$ExecutablePath	The executable path is the name and subdirectory of the executable file to be launched. For example: $C:\WINDOWS\NOTEPAD.EXE. This property is processed by the Document Interpreter which means that all global variables can be passed as parameters to an external program. For example: $NOTEPAD \DIM\RW\&MRNO.NOT In this example the variable “&MRNO” will be replaced with the Medical Record Number of the current patient. Be careful with the passed parameter since &MRNO may exceed 8 digits and may not be a valid file name for Windows 3.11 and DOS machines.