Liberation (#33)

* Viva_la_revolucion

Here come the B-29's....

* file_rename

Case sensitivity does not seem to be an issue.

* Continue_rename

Some odd cases of renaming.

* conflict_resolution

Documentation/3rd_Party_Form_API.txt

@@ -1,5 +1,5 @@
 3rd Party Form API
-OpenEMR suite v2.0
+LibreEHR suite v2.0
 doc revision 2
 
 Pennington Firm
@@ -10,9 +10,9 @@ San Diego, California
 
  ******* Introduction *******
 
-OpenEMR is more than a simple EMR suite, it is a modular platform that allows for customized modifications to meet specific needs.
+LibreEHR is more than a simple EMR suite, it is a modular platform that allows for customized modifications to meet specific needs.
 
-To create a set of patient encounter forms for use with OpenEMR, at least a limited knowledge of the PHP scripting language and the MySQL syntax is needed. The script _must_ be stored in the interface/forms/your_script_name/ directory, with at least these four files:
+To create a set of patient encounter forms for use with LibreEHR, at least a limited knowledge of the PHP scripting language and the MySQL syntax is needed. The script _must_ be stored in the interface/forms/your_script_name/ directory, with at least these four files:
 	new.php		<-- will be acessed for new data entry
 	view.php	<-- will be used to view your form
 	print.php	<-- should be used to print your form
@@ -39,7 +39,7 @@ To initialize the 3rd party php library (from interface/forms/your_script_name/m
 
 		$myArray['column_name1']  = 'my column1 value';
 
-The third argument to formSubmit() is a url to redirect to after the data from a form has been saved.  If you set this to "0" (its default) then it will forward back to "openemr/interface/patient_file/encounter/patient_encounter.php". This is the preferred operation, since users expect to be taken back to the Patient Encounter screen after saving a new form.
+The third argument to formSubmit() is a url to redirect to after the data from a form has been saved.  If you set this to "0" (its default) then it will forward back to "libreehr/interface/patient_file/encounter/patient_encounter.php". This is the preferred operation, since users expect to be taken back to the Patient Encounter screen after saving a new form.
 
 
 --->>	formFetch("my_table", 'record id', 'columns wanted', 'activity state')
@@ -52,7 +52,7 @@ The third argument to formSubmit() is a url to redirect to after the data from a
 
 
 --->>	formDisappear("my_table", 'record id')
-	This effectively sets the activity state to 0, causing the records to be invisible during normal suite usage. This is equivalent to letting the user delete a record. However, for maximum legal compliance, all data entered into OpenEMR should be saved. Instead of deleting records then, we merely make them invisible to normal user interface operations.
+	This effectively sets the activity state to 0, causing the records to be invisible during normal suite usage. This is equivalent to letting the user delete a record. However, for maximum legal compliance, all data entered into LibreEHR should be saved. Instead of deleting records then, we merely make them invisible to normal user interface operations.
 
 
 --->>	formReappear("my_table", 'record id)

Documentation/Direct_Messaging_README.txt

@@ -1,23 +1,23 @@
-Direct Messaging with OpenEMR and EMR Direct phiMail(R)
+Direct Messaging with LibreEHR and EMR Direct phiMail(R)
 Version 1.3, 19 Jul 2014
 
-A. Purpose: To provide a secure method from within OpenEMR for sending/receiving 
+A. Purpose: To provide a secure method from within LibreEHR for sending/receiving 
 protected health information to/from another Direct address using the Direct Project 
 messaging standard, as a step toward the goal of satisfying the three MU2 criteria 
 requiring the use of Direct messaging.  (For general information about Direct messaging, 
 see http://www.emrdirect.com/about-directed-exchange-and-secure-direct-messaging.html)
 
-B. IMPORTANT:  Please be aware of the following limitations when using the OpenEMR 
+B. IMPORTANT:  Please be aware of the following limitations when using the LibreEHR 
 Direct Messaging features with PHI in a production environment:
 
-1. the current code only supports a single shared "group" Direct Address for each OpenEMR 
+1. the current code only supports a single shared "group" Direct Address for each LibreEHR 
 installation. Note that this model is fully compliant with the Direct Project 
 requirements for Direct messaging, but we may add additional models in the future 
 should we determine that doing so would provide a higher degree of interoperability for 
-OpenEMR users.
+LibreEHR users.
 
-2. the current code only sends the CCR or CCD XML data that is already available in OpenEMR; 
-these files as currently generated by existing OpenEMR code do not meet the requirements 
+2. the current code only sends the CCR or CCD XML data that is already available in LibreEHR; 
+these files as currently generated by existing LibreEHR code do not meet the requirements 
 of the MU2 criteria, and the current CCD files do not pass strict CDA validation tests.
 
 C. Problems Solved:
@@ -26,20 +26,20 @@ C. Problems Solved:
 Portal interface.
 
 2. Provider-initiated transmission of clinical data from the Report section of the Patient 
-pane in the main OpenEMR interface.
+pane in the main LibreEHR interface.
 
 3. Log all data transmissions including date/time, patient, and whether transmission 
-was initiated by the patient through the Patient Portal or by an OpenEMR user through the 
+was initiated by the patient through the Patient Portal or by an LibreEHR user through the 
 main interface.
 
 4. Receive Direct messages from other sources.
 
 D. How it Works:
-Once configured, OpenEMR will interface with a phiMail Direct messaging server to complete the
+Once configured, LibreEHR will interface with a phiMail Direct messaging server to complete the
 required message transactions. The phiMail platform is described on the EMR Direct website, 
 http://www.emrdirect.com and http://www.emrdirect.com/phimail-faq.html.
 
-E. What you need before enabling Direct Messaging in OpenEMR:
+E. What you need before enabling Direct Messaging in LibreEHR:
 
 1. Test Mode: Developers may request a complimentary test address at 
 https://www.emrdirect.com/subscribe-developer  
@@ -49,9 +49,9 @@ Access to a sandbox server is available for testing and development purposes.
 Direct messaging account with EMR Direct by registering at https://www.emrdirect.com/subscribe
 
 Subscribers will receive the username, password, and server address information with which to 
-configure OpenEMR.  
+configure LibreEHR.  
 
-F. How to enable the Direct Messaging Features in OpenEMR:
+F. How to enable the Direct Messaging Features in LibreEHR:
 Setup of phiMail Direct messaging Service is done in the Administration::Globals::Connectors 
 tab
 
@@ -62,18 +62,18 @@ will be of the form "ssl://servername.example.com:32541" - replace the hostname
 with the values provided to you by EMR Direct. The Username is your Direct Address. Do not 
 enter the server URL into your browser address bar, as this will not work.
 
-3. Specify the OpenEMR user who will receive notification of new incoming Direct messages. 
-Enter their OpenEMR username in the notification user field.
+3. Specify the LibreEHR user who will receive notification of new incoming Direct messages. 
+Enter their LibreEHR username in the notification user field.
 
 4. Specify the interval for automatic message checking; we suggest 5 or 10 minutes as a
 starting point, but installations processing a large number of Direct messages may want a 
-shorter interval. To disable automatic message checking through OpenEMR's background service
+shorter interval. To disable automatic message checking through LibreEHR's background service
 manager, set the interval to 0 (zero). Disabling automatic checking would be appropriate 
 if message checking is managed through another mechanism, such as a system cron job.
 
 5. Optionally check "phiMail Allow CCD Send" and/or "phiMail Allow CCR Send" to enable
 the Transmit feature for these data types. If you do not select at least one of these,
-OpenEMR will operate in a receive-only mode.
+LibreEHR will operate in a receive-only mode.
 
 6. Click the "Save" button.
 
@@ -84,20 +84,20 @@ Globals::Notifications tab to receive error notifications from the Direct Messag
 
 Note: This is *not* your Direct certificate; it is the trust anchor for the SSL 
 certificate issued to our servers, and is used only to validate the SSL certificate 
-presented by the phiMail server on the other side of OpenEMR's connection.  Your Direct private
-key and certificate are managed by the phiMail Server and are not installed in OpenEMR.
+presented by the phiMail server on the other side of LibreEHR's connection.  Your Direct private
+key and certificate are managed by the phiMail Server and are not installed in LibreEHR.
 Your Direct certificate is made availabe for your review by EMR Direct, but you will not
 need to install it anywhere.
 
-For added security, the trust anchor for the phiMail Server should be installed in the OpenEMR 
+For added security, the trust anchor for the phiMail Server should be installed in the LibreEHR 
 installation tree at:
 
 [installation_root]/sites/[site_id]/documents/phimail_server_pem/phimail_server.pem
 
 This phimail_server_pem directory and its contents should be readable by the the 
 webserver process, but only writable by trusted local users. The certificate file 
 itself must be PEM encoded. You can identify a PEM encoded certificate file because 
-it begins with the text "-----BEGIN CERTIFICATE-----". Although OpenEMR will connect 
+it begins with the text "-----BEGIN CERTIFICATE-----". Although LibreEHR will connect 
 to phiMail servers without installing this certificate, this is a required configuration 
 step for all production  accounts to ensure that you are connecting to the correct 
 server. You can obtain the correct certificate at the following URLs:
@@ -131,9 +131,9 @@ entries, each entry will also contain an error code:
   C4: failed to open connection. Fix: Confirm you Internet service and local DNS servers are
       online and your firewall is not blocking connections to the phiMail Server.
 
-H. Checking the status and history of the Direct Messaging Service in OpenEMR:
+H. Checking the status and history of the Direct Messaging Service in LibreEHR:
 Administrators may view the status of the service by Selecting Reports::Services::Background 
-Services from the main OpenEMR left navigation bar. The "View Log" link on this page or 
+Services from the main LibreEHR left navigation bar. The "View Log" link on this page or 
 Reports::Services::Direct Message Log will open the messaging history log showing each message 
 sent or received and the current status of that message (Received, Sent, Delivery Confirmed, 
 or Failed).
@@ -142,10 +142,10 @@ I. Note of message status messages: Receiving message status updates requires th
 checking be enabled. When receiving messages, the phiMail back-end is fully compliant with the 
 Direct messaging protocols to notify the sender and provide final delivery confirmation, but 
 please note that  many other Direct providers do not yet support these features. If a message 
-is sent to a recipient using one of these other systems, OpenEMR probably won't ever receive a 
+is sent to a recipient using one of these other systems, LibreEHR probably won't ever receive a 
 final delivery confirmation for that message.
 
-J. How to use the Direct Messaging Features in OpenEMR:
+J. How to use the Direct Messaging Features in LibreEHR:
 
 1. Sending:
 When the phiMail Direct Messaging service is enabled, an additional "Transmit" button will
@@ -160,14 +160,14 @@ Clicking "Transmit" again will hide the dialog.
 A Direct Address should have the same form as a regular email address, e.g. 
 [email protected]. Enter the address in the field and click the "Send" button 
 immediately to the right of the field. Only a single recipient may be specified in the field.
-The Send button will be temporarily disabled while OpenEMR is communicating with the phiMail 
+The Send button will be temporarily disabled while LibreEHR is communicating with the phiMail 
 server. This will only work for properly-configured Direct addresses. Attempts to send to a 
 regular email address or Direct address outside of our test mode "trust sandbox" will fail
 during testing. Production accounts have wide interoperability with other Direct service
-providers. Should you encounter a trust community with which OpenEMR does not interoperate,
+providers. Should you encounter a trust community with which LibreEHR does not interoperate,
 please let us know at [email protected].
 
-OpenEMR will then display a status message immediately below the Address field, the 
+LibreEHR will then display a status message immediately below the Address field, the 
 success or failure of the message transmission, or an error message. If the message is
 successfully submitted to the server, the Address field will be cleared to prevent accidental
 re-transmission. If multiple recipients are required, the next recipient can now be entered.
@@ -186,7 +186,7 @@ beginning with "EC" are listed here:
 
 2. Receiving:
 When the phiMail Direct Messaging service is enabled, and message checking is enabled either 
-through the background services manager of another mechanism, OpenEMR will automatically process 
+through the background services manager of another mechanism, LibreEHR will automatically process 
 message status updates and new messages. Status updates will be reflected immediately in the 
 Direct Messaging log. Additionally, if a "Failed" notification is received for a previously sent 
 message, a regular email message will be generated to the Notification Email Address specified 
@@ -197,7 +197,7 @@ New Direct messages will be processed as follows. A new "Patient Note" will be g
 sent to the phiMail notification user specified in the Connectors tab of the Global settings. 
 The patient note will contain information about the message, including any text at the beginning 
 of the message from the sender. Any attachments (and any non-text content) will be automatically 
-converted to separate OpenEMR Documents, which will be referenced in the new Patient Note.  
+converted to separate LibreEHR Documents, which will be referenced in the new Patient Note.  
 The Documents and the Patient Note are initially created without an assigned patient. 
 
 At this time, the envisioned workflow is that the notification user will review the message text

Documentation/Emergency_User_README.txt

@@ -7,7 +7,7 @@ Break glass refers to a quick means for a person who does not have access privil
 3. Auditing should be enabled to log details of the account usage and details.
 4. Disable or delete the emergency account(s) that were used to prevent re–use.
 
-Emergency Login In OpenEMR:
+Emergency Login In LibreEHR:
 ---------------------------
 
 Emergency Login acl can be assigned to the users in the following screens:-

Documentation/FAQ

@@ -4,19 +4,19 @@ version 1.1
 
 * After installation and setup, I get errors from login.php at lines 3 and 4 about failing to opening md5.js and sql.inc.
 
-Please check the openemr/interface/globals.php file and edit the line that sets $webserver_root.
-$webserver_root = "/var/www/html/openemr";
-It should be set to the absolute path of the openemr web directory, as shown above.
+Please check the libreehr/interface/globals.php file and edit the line that sets $webserver_root.
+$webserver_root = "/var/www/html/libreehr";
+It should be set to the absolute path of the libreehr web directory, as shown above.
 
 
 * During installation of setup.php, I see ';?> at the top of each step.
 
 PHP can be called from within Apache with either long tags: <?php or short tags: <?php 
-OpenEMR uses short tags throughout its program code, though some default installations have short tags disabled. If you see this error, short tags are not enabled. Please consult PHP's documentation at: http://www.zend.com/manual/language.basic-syntax.php. The solution is to enable the short_open_tag configuration flag in the PHP config file, or by compiling PHP with the --enable-short-tags option to configure. (Zend PHP Website)
+LibreEHR uses short tags throughout its program code, though some default installations have short tags disabled. If you see this error, short tags are not enabled. Please consult PHP's documentation at: http://www.zend.com/manual/language.basic-syntax.php. The solution is to enable the short_open_tag configuration flag in the PHP config file, or by compiling PHP with the --enable-short-tags option to configure. (Zend PHP Website)
 
 
-* How do I implement my own encounter forms into OpenEMR?
+* How do I implement my own encounter forms into LibreEHR?
 
-The encounter form system and API is intended to support a wide variety of diverse encounter forms. To create your own encounter forms, you have two options: you can implement them manually yourself, or you can contract PennFirm do generate them for you. If you would like PennFirm to generate forms for you, please email info@openemr.net, and you will be given a fax number to which all forms may be sent. PennFirm will create your forms, including layout, reporting, etc. and email them to you within 1 week.
+The encounter form system and API is intended to support a wide variety of diverse encounter forms. To create your own encounter forms, you have two options: you can implement them manually yourself, or you can contract PennFirm do generate them for you. If you would like PennFirm to generate forms for you, please email info@libreehr.net, and you will be given a fax number to which all forms may be sent. PennFirm will create your forms, including layout, reporting, etc. and email them to you within 1 week.
 
-If you would like to make forms yourself, please begin by taking a look at the existing forms that come with the default installation of OpenEMR. The Documentation/3rd Party Form API.txt document details the user-level functions available for form developers. While implementing your own forms, please remember that compatibility with the rest of the OpenEMR platform is crucial, for correct report generation and smooth functionality.
+If you would like to make forms yourself, please begin by taking a look at the existing forms that come with the default installation of LibreEHR. The Documentation/3rd Party Form API.txt document details the user-level functions available for form developers. While implementing your own forms, please remember that compatibility with the rest of the LibreEHR platform is crucial, for correct report generation and smooth functionality.