3.0.1 Administration Site Release Notes
These Release Notes are for the FH Medic 3.0.1 administration web site, which supports NEMSIS 3.0, and provide a listing of the defects resolved and the enhancements implemented during this release.
The following enhancements were implemented this release.
A new page has been added to the FH Medic administration site to support NEMSIS 3.0. The Demographics page lets you specify information about your station, such as its units/vehicles, personnel, devices, destination facilities, agencies, and so forth.
-
In the top row of links across the page, click Demographics.
A new page appears, displaying icons for different demographic categories of information.
Information on using setting up demographic information for FH Medic is available in Specify department demographics.
On the Configurations > FH Medic page, the Signatures/Disclaimers icon now appears. When you click this icon, the Configurations > Signature/Disclaimers page appears, where you can enter disclaimer text associated with each signature type in FH Medic.
Information on using the Signature/Disclaimers page is available in Edit disclaimers for signatures.
On the Configurations > FH Medic page, the Quick Action Buttons icon now appears. When you click this icon, the Configurations > Quick Action Buttons page appears, where you can list action plan information such as treatment processes and medications that the medic may administer to the patient.
Information on using the Quick Action Buttons page is available in Set up quick button treatments for an impression.
On the Configurations > FH Medic page, when you click the Destination/Incident Facilities icon, that page that appears has been renamed from Configurations -> Locations to Configurations -> Destination/Facilities. The
On this page, references to Locations have been updated to Destination/Facilities, and Destination/Facilities has been added to all column titles.
The following issues were successfully resolved this release.
On the Configurations > Inputs page, for the Incident input group, for the City, State, Zip, or County inputs, you could not specify a default value.
On the Configurations > Inputs page, there was no District field on the FH Medic administration site supporting NEMSIS 3.0 as there had been on the administration site supporting NEMSIS 2.2.
On the Configurations > Inputs page, in the Input Group column, for the Call Times group, when you click Edit for the Unit Back at Home input, the Edit Input page appears in a separate tab or browser window.
For Require Always, if you selected Yes, then Save Changes, the requirement setting did not override other rules in FH Medic which present Unit Back at Home as not-mandatory, as expected.
On the Configurations > Inputs page, when you click Edit for one of the inputs in the list, the Edit Input page appears in a separate tab or browser window. If you then click Click Here To Sort Input Values, a new browser window opens, and the input values list appears in it.
If you then drag the button listing the input you want to move to the location you want the list renumbers as expected, but the position of the button does not change as expected.
On the Configurations > Field Users page, if you clicked Edit for a specific user, changed its password, and saved the change, left the configurations settings pages, then returned to the account with the changed password, the password was removed.
If you had attached an incident in FH Medic, you were not able to delete it on the administration site.
On the Configuration > Private Insurance page, under Private Insurance Companies, if you clicked Edit for any of the insurance companies listed, in the Edit Private Insurance dialog box that appeared, you could not add, edit, or enable/disable a private insurance code.
In FIREHOUSE Software, if you chose File > Station Management > Import Data From Station and tried to use the Import Data from Station dialog box to import NFIRS data from FH Medic the data did not populate into the database as expected. When the import log was inspected, the following error was found.
Error reading data element value for field ACT_CODE
When you click Incident in the top row of links across the page, the Tickets page appears. If you then select a date in the calendar, the incidents (tickets) for that date appear. In the Shift Date column, values did not populate with data as expected.
On the Configurations > Inputs page, when you click Edit for the Procedure input, the Edit Input page appears in a separate tab or browser window. If you then click Click Here To Sort Input Values, the following error appears.
Invalid column name 'ValueID'.