This is an old revision of the document!


Software Feature Wishlist

User Interface

  • Skinnable.
  • Uniform look-n-feel across products.
  • Uniform notation and terms across products.
  • Company colors and theme.

Technology

  • Platform: Win32 and .Net.
  • Database: Firebird (embedded for local database, server for network setup).
  • Server: PHP scripts.

Functionality

  • Select appropriate module to run (ezFIT 4 or 5) after detecting product, allowing new products to use version 5, and older products continue using version 4.
  • Based on audiogram, provide best suited products that provide that fitting range.
  • Link programming to both sides.
  • Undo button to undo changes from a history list.
  • Move equalizers in group (see Windows Media Player).
  • Create equalizer object, so all products have same look-n-feel.
  • Screen capture feature, for quick reporting or troubleshooting. This should perhaps include patient data and product fitting screen (each tab).
  • Authentication to access database (for security and auditing purposes, HIPAA compliance).
  • Logging of operations to create audit trail (for auditing purposes, HIPAA compliance).
  • Patient Appointment scheduling and details.
  • Order Tracking using secure Internet communications with Audina. Track new orders, manufacturing, and repairs.
  • Order Forms to be customized to each product (avoiding costly errors and confusing options) and generated to be printed and mailed.
  • Custom reports to include dispenser's logo.
  • RSS announcements fed to software, to inform users.

Audiograms

  • In Situ Audiograms
    • ezFIT 4.x: The issue is that once the in situ audiogram is selected and saved, that replaces the audiogram in the hearing aid and database. That was by design. We need to support both audiograms, but I think that will be left for the next platform…We only have space to save one audiogram in each hearing aid, and that is the main reason we replace the audiogram altogether.
    • ezFIT 5.x: Ensure that if a new audiogram is created that this is stored as a session. So that ezfit has record of each of the audiograms created. This is an important aspect of record keeping for the provider from a forensic perspective. If I have a patient that I test each year their hearing and then program their hearing aid, the audiogram function right now simply replaces the old one in our system. It is not set up to store the audio as a session. Additionally, if I use the in situ test to program the hearing aid, I would want to have a record of the audiogram from that session so that I can say that I used xyz audiogram which was performed via in situ testing on my patient to program the hearing aid. Without the information recorded anywhere, there is no leg for a provider to stand on for why the hearing aid is programmed a specific way and with the values being so different in some cases up to 15-20 dB, you would, as a provider, want documentation for that.