2.2.3.0 Windows Release Notes

When you print a patient care report (PCR), now all fields that are filled out in FH Medic appear in the PCR, whether or not they are required.

On the Patient tab, on the Meds sub-tab, when you click a medication button, the dosage dialog box that appears now contains the mEq unit of measure as an option.

The FH Medic Integration Suite can now process .cml files in addition to the other file types it already supports.

After updating to FH Medic 2.2.2.2, some departments experienced the following issues.

• Completed calls were uploaded as blank to the FH Medic administration web site.
• Incident number and quality assurance (QA) completion status in older calls were changed.
• Calls were slow in reaching the FH Medic administration web site, or did not reach it at all.
• Faxes were delayed or did not get sent.

On occasion, the Integration Suite for FH Medic stopped and had to be manually restarted for calls to be processed and sent to FH Medic. The necessary service is now automatically restarted periodically to avoid unexpected down time.

When trying to open or validate a PCR, a parsing error appeared.

FH Medic accepted dates of birth and incident dates in the future, and should not have.

The certification numbers for crew members were correct on the FH Medic administration web site, but were not correct when printed on the PCR.

When an incident was reviewed and sent back to the medic for changes, after the medic made the changes and resubmitted it, the incident did not move back to the FH Medic administration web site and become recorded as completed.

If you entered a social security number (SSN) on the Patient → Demographics tab, then went back to the field later and deleted the SSN number, when you validated the incident, the field was not highlighted with red text to indicate that it was required.

If you tried to view 4- or 12-lead data imported from a Zoll X-Series monitor, an error message stating that the Zoll case file could not be loaded appeared. If you tried to print the data, the expected prompts and printer selection options did not appear.

Some incidents from the CAD system were not completely processed before appearing in FH Medic.

Some incidents from the CAD system were processed, but not sent on to FH Medic as expected.

Files exported from FH Medic to the FH database did not always have values for unit times, aid given, incident type, action taken, or property use.

When an incoming CAD incident merged with an existing FH Medic incident, and you then filled in data for an incident and moved from tab to tab in FH Medic, if you went back to the Patient → Demographics tab, data for the patient's name, date of birth (DOB), race, and sex may have changed. After validation, the text in the narrative sometimes switched with another incident's narrative.

If you removed unused vitals items from the PCR, not enough space was left between the remaining vitals items, and they were run together.

On the PCR, the Treatments and Protocols headings appeared on the right side of their sections, and should have appeared on the left side.

If a patient's last name contained a single quote, when the incident was put into the QA review cycle, the incident did not appear on the mobile computer that created the PCR, or under the unit/crew that created the incident.

For Ohio departments, a number of items failed validation and cross-checking that should have passed, or which should have been required. The following items have been adjusted in FH Medic.

• Two crew members are now required before the crew dialog box can close.
• The patient's home zip code must be at least five characters long.
• For some customers, a cap value now exists for the diastolic blood pressure value.
• Incident numbers cannot contain letters.
• The incident address must be at least three characters long.
• Gender is required if patient contact is made.
• The number of procedure attempts is now required.
• Conditional required input now exists for MVC.
• FIPS codes must be unique to each customer.
• Destination codes for all hospitals must be set correctly for all customers.
• The incident zip code now validates during export.

FH Medic assigned the incorrect date for an incident if it was created on a date later than the date of service value entered for the incident.

Example: If you created an incident in FH Medic on 05/12/2016 for an event on 05/11/2016, the incident was time stamped as 05/12/2016, even though it printed 05/11/2016 correctly on the PCR. The incident also appeared on the FH Medic administration web site as 05/12/2016, but the PCR listed 05/11/2016.

The FH Medic Integration Suite did not remove alphabetic characters from incident numbers as expected.