Main menu

Hummingbird PIM (Patient Information Management)

  • Chrome Browser and a high-speed internet connection
  • Screen Resolution of 1366 x 768

Chromebook:

  • Any Chromebook
  • Example – Asus 13-inch Chromebook

Windows Computers:

  • Windows 7 or greater
  • 1 GB RAM (4 GB or greater recommended)
  • 1 GHz processor or greater
  • Example – Dell Inspiron 14 3000

Apple Computers:

  • Mac OSX 10.6 or greater
  • 1 GB RAM (4 GB or greater recommended)
  • 1 GHz processor or greater
  • Example – Macbook Air

 

Hummingbird Clinical

  • Microsoft Windows XP/Vista/7/8/10 or Mac OS X 10.7 or higher
  • Intel x86 CPU/Processor (1.8ghz Core 2 Duo or anything ranking higher than 1200 on CPU Mark, Intel Core i5 is recommended)
  • 2 GB RAM (4 or more GB RAM is recommended)
  • 10 GB hard drive space (60 GB hard drive or larger is recommended)
  • 7200 RPM or faster hard drive (Solid State Drive is recommended)
  • Screen resolution of 1024 X 768 or higher
  • A high speed connection to the Internet
  • Windows - Hummingbird Clinical is installed in the user’s %ProgramFiles% directory - typically C:\Program Files(x86)\Mumms. The end user must have full permissions to this directory, recursively.
  • OS X - Hummingbird Clinical is installed as an application in /Applications/CPC.app. The end user must have read/write/execute permissions on the application and it’s subdirectories.
  • Although it is possible, mumms does not recommend (and will provide only minimal support for) the use of Citrix environments to serve up the HBC application.

 

Hummingbird Mobile on Phones & Tablets

  • Chrome Browser 58 or higher
  • iOS 10.0 or higher*
  • Android 5.0 or higher
  • We recommend Chrome 58+ on iOS devices, but in general Safari is acceptable on iOS 10.0+ devices

Encryption

At mumms, we take safety and security of PHI very seriously. Therefore, all data in the mumms’ ecosystem is encrypted at rest and in transient within our enterprise cloud platform. However, it is our recommendation to our customers to encrypt all devices accessing PHI. Although, not explicitly a HIPAA requirement, it is an unquestionable safeguard that will protect PHI stored locally, regardless of the source.