SpringCharts is initially activated at ‘Low Security’ level which enables each User to determine when or if the password is changed and how long the program would remain inactive before it shuts down.
SpringCharts has a 'High Security' feature also which, when enabled, enforces the following rigorous password rules.
· All passwords are encrypted and obfuscated from user view.
· Users must reset passwords every 60 days and are prohibited from logging on after this time until the password is changed.
· Passwords must be 8 to 16 characters.
· Passwords are case sensitive.
· Passwords must contain at least one number, one character and one special character (!@#$%&*). The '^' character is prohibited.
· Users must request a new Password from the Administrator if the password is forgotten.
· Users may change passwords at any time.
· Users have three attempts at logging into SpringCharts, after which the program closes.
Once selecting either Low or High Security the administrator will need to restart SpringCharts Server.
20. SpringCharts Exchange
This feature on SpringCharts Server needs only be activated if the clinic has purchased a database link to a Medisoft program prior to version 9.
21. SpringLabs
SpringLabs is the interface between SpringCharts and lab testing facilities to enable lab results to be automatically entered into the patient’s pending labs. The activation code must be entered and the appropriate interface checked. Often this interface module is paid by the lab facility for the clinic depending on the number of labs ordered from that facility.
22. SpringReports
SpringReports works similar to SpringLabs except the interface is between SpringCharts and other testing facility, e.g. x-ray, MRI, and other medical tests. This interface enables the test results to automatically be entered into the patient’s pending tests.
23. Superbill Form
Modify the Superbill Form so that it is customized for the practice. This form only needs to contain codes that are billable and not normally documented by the provider within the Office Visit note, e.g. the administration of injections and immunizations, supplies and consumable items and non-office evaluation & management codes. The Superbill Form is available to the Provider when finalizing the Routing Slip to add any of these billing codes by clicking on them.

24. Time Clock Setup
If the clinic is opting to utilize the Time Clock feature, the setup window will need to be enabled and the administrator selected from the drop-down list of Users. Once activated, the Time Clock feature can be used under the Productivity Center menu on each Client or the icon on the toolbar.
25. Twain Setup
Twain setup enables a direct connection between SpringCharts and to selected TWAIN-compatible devices such as scanners, cameras and web-cams. The TWAIN device interface enables direct connection. For example, a picture of a patient could be taken from within the patient’s chart and immediately store within the patient’s chart. It also enables the ability to do one-touch scanning from within SpringCharts to scan documents directly into a patient’s charts. Extracting images directly from digital cameras and web-cams directly into SpringCharts is possible as well. If the clinic has purchased this feature, enter the TWAIN interface key.
26. Tracker Setup
a) Set Tracker Locations. These are short phrases used by the tracking system to display where patients are located in the clinic. Enter any location where patients might be seen as part of the normal office encounter such as: Waiting Room, Exam Room 1, Exam Room 2, Exam Room 3, Exam Room 4, Nurse Desk, Lab, etc. Place the location items in logical order from where the patient would be first seen to where they would be last seen.
b) Set Tracker Status. These are short phrases used to indicate the status for the patient in each of the locations that have been setup. Examples include: Vitals, Needs Shot, Ready for Dr., Needs Lab, Lab Done, Needs X-ray, BP Check, Nebulizer, Lab Only, Nurse Check, Doctor Check, etc. This will help to identify what is or needs to happen to the patient located in a specific room.
c) Set Tracker Groups. Tracker Groups need only be setup if the clinic has multiple locations and is using the same database to run SpringCharts for each location. SpringCharts provides the User with the option to view the Patient Tracker at each location and see the locality and status of each patient at the other facilities. If using Tracker groups, each patient add to the tracker should be assigned a specific Tracker Group. Under the User Preferences on the Client version each User will select which Tracker Group he/she wants to view as the default window.

27. Vitals
SpringCharts provides the clinic with the option of adding additional vital items to the nine set vitals that are in the program. Based on the clinic’s specialty, vitals, such as oxygen saturation, blood sugar or another blood pressure reading, may be added to the vitals section on SpringCharts server.
To create additional vitals, add:
1) The abbreviated label for the vital (five character or less.)
2) Indicate whether the vital reading will be a number or a text.
3) Select the maximum number of characters for the length of the vital taken.
4) Enter the minimum and maximum ranges for the possible vital reading (optional).
5) Click on the Enable radio button and press the [Done] button.
Note: SpringCharts Clients will need to be restarted to see any additional vitals.

28. XML Export
The XML Export feature will export ALL patient charts in the database in industry standard .xml files. Once selected the administrator will be presented with an Export Charts to Folder window into which all patient chart information will be sent. There is no ability to select specific charts in the XML Export function. Individual charts can be exported form SpringCharts Client by using the CCR (Continuity of Care Record) feature located in the Client version within each patient chart under the File menu.
29. SpringScripts
This interface enables the electronic prescribing of prescriptions. Enter the activation key and then check Enable SpringScripts. Enter the information in the next 3 fields and check Use certification server.
Note: SpringMedical Support can assist with the set up SpringScripts.

To use SpringScripts, you must obtain an activation code from Spring Medical Systems. The activation code is placed in the text box next to Enable SpringScripts. Practice UserName, Vendor UserName and Vendor Password are provided by Spring Medical Systems.
Save to Tab: Whenever a prescription is created in SpringScripts, a prescription notification is sent to SpringCharts. Like Rx Refills, these are stored in the encounter tree under Encounters. This option forces the SpringScripts ePrescribing encounter to be stored in any Chart Tab as created in Category Preferences.
Bulk Upload: The bulk uploader performs a synchronization of patients between SpringCharts and SpringScripts. This process needs to be done only once, and transfers all patient demographics, medication history, allergies and problem lists to SpringScripts. Note: This process can take some time; please do no t execute this command during normal business hours.
SpringScripts Advanced Configuration Options:
Send on Save: This section governs how SpringCharts processes current medications in an OV or Rx Refill with respect to SpringScripts.
ý Send on any save: Sends medications to the SpringScripts current medication list every time a save is performed, either through clicking on Done, or by the auto save feature.
ý Send on updates to eRx’s only: This will only send medication updates to the SpringScripts current medications for medications that already have a SpringScripts ID (ie: have been previously sent to SpringScripts, or were created in SpringScripts and sent to SpringCharts as an ePrescription).
ý Don’t send (Recommended): Do not send any medications to SpringScripts.

Other Options:
ý Use Certification Server: This is for development purposes and should remain unchecked.
ý Send meds on eRx (Recommended = off). This controls the button on the SpringCharts Prescription Pad. If set, the medications in the pad will be sent to SpringCharts by pressing the eRx button. If you don’t want to send the medication, but want the medication documented in the OV, then click use the ePrescribe button on the bottom of the OV screen.
ý Show Rx print button: This will enable/disable the prescription printing button in SpringCharts.
Sample Configurations:
For a doctor that wants all medications from SpringCharts sent to SpringScripts, set Send on Save to "Send on any save", and select "Send meds on eRx".
For a doctor that doesn't want medications from SpringCharts sent to SpringScripts but wants to be able to stop a medication in SpringCharts that was created in SpringScripts , set Send on Save to "Send on updates to eRx's only". Select "Send meds on eRx" only if the doctor wants the ability to send the prescription from SpringCharts to SpringScripts by pressing the eRx button in the prescription pad.
For a doctor that does not want medications to be send to SpringScripts at all, thus ensuring that all medications are entered and prescribed in SpringScripts, then set Send on Save to “Don’t Send” and deselect “Send meds on eRx.”
30. Patient Categories. This allows a clinic to add to the Category drop down menu located in the Edit Patient and New Patient windows. To add a new category click on the [Add] button, then type in the category and select an identifying color. Select the [Done] button to save the new category. An existing category may be modified by selecting the [Edit] button.


31. Dictionary Tools. This enables the clinic to make some changes to the SpringCharts drug database.
1. Load Drug Dictionary: Activates the most recent complete drug dictionary.
2. Sync Drug Database with Dictionary: Syncs the active drug database with the most recent complete drug dictionary.
3. Replace Drug Database with Dictionary: Replaces the active drug database with the most recent complete drug dictionary.
4. Update Drug Interaction Data: Updates the drug interaction data with the most recent drug interaction data.

32. Scheduler. This feature enables a clinic to regularly schedule .XML file exports of patient charts.
33. Login Setting. This enables a clinic to unlock a user after they have attempted to login more than the allotted attempts. This also enables the clinic to define the maximum number of times a user may attempt to login incorrectly before locking the user out of the application.

Related Topics