2.1.3 Windows Release Notes

Several new signature types have been added to FH Medic, including those of a nurse, doctor, coroner, police department representative,spouse, other relative, someone with power of attorney, and more. A new signature button has also been added for parent or guardian who wishes to refuse treatment for a minor.

To find this new feature, do the following.

1. Click the Summary tab, and then click the Signatures sub-tab.

   The Receiving RN / Doctor button has been renamed Person/Entity Receiving Patient. The new Other and Parent/Guardian Refusal for Minor buttons appear on the right side of the interface.

   

2. Do any of the following.

   • View new signature choices for a person or entity type that might receive the patient.

     1. Click Person/Entity Receiving Patient.

        The Person/Entity Receiving Patient Signature dialog box appears, and the new Signature Type field appears near the top of the dialog box.

        

     2. Click the Signature Type field.

        The Person/Entity dialog box appears.

        

   • View other types of signature choices that are now available.

     1. Click Other.

        The Other Signature dialog box appears, and the new Signature Type field appears near the top of the dialog box.

        

     2. Click the Signature Type field.

        The Other Signature Type dialog box appears, and buttons for the other signature types appear.

        

   • View the new signature type options for a parent or guardian who wishes to refuse treatment for a minor.

     • Click Parent/Guardian Refusal for Minor.

       The new Parent/Guardian Refusal for Minor Signature dialog box appears.

       

   Information on using these new signature types and dialog boxes is available in the FH Medic online Help, in Acquire, edit, and delete signatures.

You can now have the streets of your EMS service area or municipality imported into FH Medic, so that personnel in the field can simply select a street name instead of manually typing it in when responding to an incident.

If you do not have an FH database, download the template provided at https://firehousesoftware.box.com/FHMedicStQuery, and populate it with the streets in your EMS service area or municipality.

If you do have an existing FH database, download and run the FH query available at https://firehousesoftware.box.com/FHMedicStQuery to capture a list of streets in the FH database, and to export the information to a spreadsheet.

Once you have completed the spreadsheet of streets, the FH Medic support staff can then import the spreadsheet into FH Medic and enable the streets feature in FH Medic.

Information on creating and sending the spreadsheet to the FH Medic support staff, displaying the street buttons in FH Medic, and then using the new buttons, is available in the FH Medic online Help, in Import streets into FH Medic.

If you are sending FH Medic data to an FH database through the FH Medic Integration Suite, you can now request to have that data filtered to only the information you want to keep in FH.

If you request to use one of the data filter options listed above, if the data exported from FH Medic contains all the information FH requires for completing the record, and if you disable the batch update option on your automated FH import task for the FH Medic data, then the unit and patient records are now automatically marked as complete. In the past, unit and patient records created in FH from data exported from FH Medic were marked as incomplete in FH, and you had to manually open the records and save them to complete them.

The data filter options you can request are:

• NFIRS incidents only
• EMS incidents only
• NFIRS and EMS incidents
• NFIRS and EMS incidents with patient data
• EMS incidents with patient data
• NFIRS incidents with no units and personnel data
• EMS incidents with no units and personnel data

To use this new feature, email support@firehousesoftware.com with your request to have the data being exported to FH filtered, and which data filter option you would like to use.

Below are steps for disabling the batch update option on the automated FH import task for FH Medic data.

1. Log into FH as an administrator.

2. Choose Administration → Automated Tasks.

   The Automated Task Setup dialog box appears.

3. From the list in the dialog box, select the automated task you created for importing FH Medic data into the FH database.

4. Click Properties.

   The Automated Task Properties dialog box appears.

5. Click Setup Task Parameters.

   The Import Data from Station dialog box appears.

6. At the bottom of the dialog box, under Incident Reports, clear Batch update completion status of imported incident reports.
7. Click OK.
8. In the The Automated Task Properties dialog box, click Save, and then click Close.
9. In the Automated Task Setup dialog box, click Close.

If you entered a decimal value for a narcotic medications dosage ( for example, such as 7.5) with the steps below, the value was rounded up to the nearest integer value (7.5 was rounded up to 8).

1. Click the Events tab, and then click the Treatments sub-tab.

   A list of possible treatments for the patient appears.

2. Click Medication Administration.

   The Medication Administration screen appears.

3. Fill out the field of the screen as normal, selecting a narcotic drug (such as morphine supfate) or Drug Name, and specifying a decimal value for Dose (such as 7.5).

4. In the lower right corner of the interface, click Submit.

   The Treatments sub-tab reappers.

5. In the upper right corner of the interface, click Validate.

   The Incident Validate form appears, displaying any errors or missing information in the data currently entered.

6. Click Fill out Narcotic Form.

   The Controlled Substance Usage / Waste Form appears, and in the Amount Used column, the decimal dosage value was rounded up to the nearest integer value (7.5 was rounded up to 8).

If you changed the outcome of an existing patient record to a multiple-patient refusal record, you were prompted to clear the patient information. When you validated the record with the steps below, you were prompted again to clear out patient data.

1. Open a single patient record as normal.
2. Click the Summary tab, and then click the Disposition sub-tab.

3. Under Details, click Outcome.

   Buttons appear on the right side of the interface.

4. Click Multi-Patient Refusal.

   A dialog box appears, informing you that the ticket has personal information filled out and instructing you to either clear the personal information or copy the incident to a new ticket.

5. Click OK.
6. Click the Patient tab, and clear the personal information from the fields.

7. In the upper right corner of the interface, click Validate.

   The same dialog box appears, informing you that the ticket has personal information, even though you have cleared the data from the record.

If you use the FH Medic Integration Suite, incidents imported from a CAD file with a time stamp before midnight, and the duration of which extended into the next day, caused time validation errors when you later tried to create a patient care report (PCR).

FH Medic Integration Suite now bases the date and time for the incident on the alarm date, instead of the date the CAD file was processed.

If you use the FH Medic Integration Suite to export FH Medic data to an FH database, the identification of the OC (Officer in Charge) was not being sent to the FH database.

If you created a patient care report (PCR) as normal, the Treatments and Protocols headings in the PCR were right-justified, and should have been left-justified.

If you use the FH Medic Integration Suite to import data from a CAD system into FH Medic, the prefix (N, S, E, W, and so forth) on the street name was not importing into FH Medic.

If you do not have Internet access, and if your mobile computer suffers an unexpected shut down with data that has not yet been updated to the FH Medic Cloud, parts of the FH Medic database on the mobile computer could become corrupted. When the automatic recovery process runs on the database, it could inadvertently assign some of the unsent data to the wrong incident.