2.0 on the iPad Release Notes
These Release Notes are for FH Medic 2.0 on the iPad (using NEMSIS 2.2), and provide a listing of the defects resolved and enhancements implemented during this release. This release covers changes made between FH Medic 1.7 and 2.0.
The following issues were successfully resolved this release.
On the Response > Incident Information screen, the Street Type and Street Prefix fields did not appear with the other street identification fields.
If you used an external keyboard with your iPad to enter data into a field inFH Medic, then swiped the screen with your finger to scroll up or down in FH Medic, the screen scrolled halfway and then froze.
In the Update Crew dialog box, under Non System User, the Type field was not a drop-down menu of options, and should have been.
If you made fields required on the FH Medic administration site, the required fields did not always highlight in red as expected in FH Medic on the iPad.
If you changed the ownership of an incident, the incident appeared on the FH Medic administration site with a status of review, but did not appear on the iPad in the review status.
The color menu options were not correction, and have been renamed. Red now indicates mandatory fields, and purple indicates required fields.
On the Patient > Assessment screen and the Summary > Narrative screen, the assessments and narrative created by a user did not always appear in FH Medic when the user logged in on different iPads.
Not all protocol groups defined on the FH Medic appeared in FH Medic on the mobile computer. In some cases, a protocol appeared on the iPad, but could not be opened for viewing.
If you created an incident, accessed the Treatments screen, added medication records, deleted one of the medication records, edited a different medication record, and then touched Save Treatment, FH Medic stopped functioning.
the Treatments screen, if you added a new medication record, then edited an existing medication record, the name of the newly added medication is duplicated for the edited record.
Example: If you added a new medication named Advair Diskus
, then edited an existing medication record named Aciphex
, the existing medication name changed to Advair Diskus
.
FH Medic accepted dates of birth and incident dates in the future, and should not have.
Even when a medic supplies the required signature for the patient care report (PCR), the signature still appears as a requirement when the incident validates.
All units were displayed in FH Medic as active, even if their status was set to inactive.
When entering information on the Vitals screen, FH Medic closed unexpectedly.
On the Patient screen, if you touched Scan DL and used the iPad to read the bar code on the back of the driver's license, information from the license populated the Demographic section of the screen as expected. However, you were not always able to then open the Phone Number field for editing.
When scanning an Illinois driver's license, the following error appeared.
Unable to parse input string
FH Medic closed unexpectedly if you accessed the Narrative screen and then touched the Auto Narrative tab, or if you touched the printer icon in the upper right corner of the screen, selected PCR Report from the menu that appeared, and then touched Preview Report.
Incidents were not automatically removed from FH Medic on the iPad after a specific number of days, as expected.
When multiple CAD files are imported from the FH Medic Integration Suite, not all of them appeared in FH Medic on the iPad.
When two separate doses of a narcotic drug were administered from the same vial and recorded by the medic as two separate narcotic treatments, FH Medic assumed that two vials had been opened and incorrectly calculated the amount of wasted medication.
If you specified a default values on the FH Medic administration site, the value did not propagate to FH Medic on the iPad.
On the Patient → Demographics tab, for Race, not all the expected selections appeared.
If a completed ticket contained narrative information on both the Response > Narrative and Summary > Narrative > Medic Narrative tab, on the administration site, the incident narrative text replaced the medic's narrative.
If the incident status was set to Review
, when the incident was opened again on the iPad, the incident narrative appeared in both the Response > Narrative and Summary > Narrative > Medic Narrative tabs.
On the Situation → Injury tab, if you clicked Cause of injury, the list that appeared on the right was not sorted alphabetically.