Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
ezfit:software_wish_list [2009/08/19 12:15]
smayr
ezfit:software_wish_list [2010/04/28 13:17] (current)
ajdavis added import request
Line 16: Line 16:
 * Based on audiogram, provide best suited products that provide that fitting range. * Based on audiogram, provide best suited products that provide that fitting range.
 * Link programming to both sides. * Link programming to both sides.
 +* Undo button to undo changes from a history list.
 * Move equalizers in group (see Windows Media Player).  * Move equalizers in group (see Windows Media Player). 
 * Create equalizer object, so all products have same look-n-feel. * Create equalizer object, so all products have same look-n-feel.
Line 26: Line 27:
 * Custom reports to include dispenser's logo. * Custom reports to include dispenser's logo.
 * RSS announcements fed to software, to inform users. * RSS announcements fed to software, to inform users.
- 
 ==== Audiograms ==== ==== Audiograms ====
- * 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. 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 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, would want to have a record of the audiogram from that session so that 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 providerwant documentation for that.+ 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 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 a patient is tested (hearing) each yearand then their hearing aid programmed, the audiogram function in 4.x simply replaces the old one in the database.  It is not set up to store the audiogram as a session.  Additionally, if the in situ verification is used to program the hearing aid, it would be wise to have a record of the audiogram from that session so that the provider can determine that xyz audiogram was used, which was performed via in situ verification on the 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
 +=== Audiology's Wish List === 
 +Easier to read font with a little more spacing between characters to make it a little easier on the eyes. 
 + 
 +==== Audiogram Tab ==== 
 +  # Ability for practitioner to indicate whether thresholds were measured in dB HL or SPL (it makes a difference) 
 +  # Ability for practitioner to record the following on the audiogram:  
 +    - Bone conduction thresholds 
 +    - Air conduction thresholds 
 +    - UCL thresholds (frequency specific) 
 +  # Speech Recognition Threshold (SRT)  for RELEBinaural 
 +  # Most Comfortable Loudness Measures (MCL)  for RE, LE, Binaural 
 +  # Uncomfortable Loudness Measures (UCL) for RE, LE, Binaural 
 +  # Speech Discrimination Scores for RE, LE, & Binaural (recorded as  % at XX dB) 
 +  # Automatic calculation of Pure tone Threshold Average (PTA) based on thresholds recorded  
 +    - 3 frequency average (5001000, 2000 Hz) 
 +    - Fletcher average (average of better two frequencies at 500, 1000, 2000 Hz) 
 +  # Automatic determination of agreement between SRT and PTA 
 +    - +-6 dB of each other = good agreement 
 +    - +-7  to +-12 dB of each other = fair agreement 
 +    - Difference of +-13 dB or greater = poor agreement 
 +    - References: 
 +       - Carhart R (1971) Observations on the relations between thresholds for puretones and for speech. J Speech Hearing Disorders; 36:476-483 
 +       - Fletcher H (1950) A method of calculating hearing loss for speech from an audiogram.  Acta Otolaryngol; 90 (Suppl):26-37 
 +       - Brady, W. T. (2002). Speech Audiometry. In J. Katz (Ed.), Handbook of Clinical Audiology (5th Edition ed., pp. 96-110). Philadelphia: Lippincott Williams & Wilkins. 
 +  # Additional testing note section  where the practitioner could write information that s/he felt was relevant to the testing session. 
 +  # Inability to change prior audiogram.  A prompt to say do you want to record a new audiogram based on the prior audiogram?  Then pull that information so the practitioner can make changes and it will be saved under the current/accessed date. 
 +  # Ability to customize the printout with the company name and information and possibly logo. 
 +   
 +==== Selection Tab ==== 
 +  # Ability to select product by using criteria to determine Audina products that will match with hovering providing extra information)  It’d be nice to be able to turn off the hover for long time users, under preferences/options. 
 +    - Technology (Digital, Analog) 
 +    - Styles (CIC, Mini canal, canal, half shell, full shell, mini BTE, BTE, Power BTE, Super 60, RIC, Open Fit, Arc) 
 +    - Directional Microphones (yes, no, show all) 
 +    - Volume Control (yes, no, show all) 
 +    - Telecoil (yes, no, show all) 
 +    - Multi-Memory (yes, no, show all) 
 +  # Once criteria is selected, a list of products with how well they match the criteria is shown (maybe using stars or some other icon to indicate how close a match it is) 
 +  # Fitting ranges overlaying the client’s entered audiogram for the various products  
 +  # Technical information (think spec sheet) for the products 
 +  # Pictures of the hearing device in and out of the ear 
 +  # A form field order form so the practitioner can then complete the form and print to mail with the order 
 +    - Autofill provider company information from data entered under preferences 
 +==== Personal Tab ==== 
 + 
 +  # Button to click to read instruments and go to the fitting screen. 
 +  # Button to take a previous session and load the parameters into an instrument of the same family. 
 + 
 +==== Fitting Tab ==== 
 + 
 +  # Mute Function during fitting:   R & L speaker click to mute (show speaker circled with line through it to show muted) 
 +  # Link and unlink RE and LE for making changes  
 + 
 +==== Solutions Tab ==== 
 +  # RE, LE, Both Ear option 
 + 
 +==== ezFIT Wizard ==== 
 + 
 +EZFit Wizard for first fit 
 +  - Select fitting strategy (prescription fitting strategy) 
 +  - For RIC and Open Fits select dome/tip size (just for practitioner records) 
 +  - Venting  
 +  - Earmold 
 +  - Earhook