DSM-Guest wrote:SWS,
Welcome to the discussion. Your input is without doubt a great boost to the usefulness of the topic.
On the issue of terminology in describing 'situations', I tried to address this with some suggestions in the Cpap Users Group thread.
Let me paint a hypothetical...
On the one hand we can have a user who purchases a machine and seeks to use it. The user has heard good comments about this machine from people here on cpaptalk.
However, the user finds that with their mixed brands of mask, humidifier & machine, they are not getting what they expect from the way the machine works, in fact they begin to think that the good reports on the machine just don't match their observations...
At this point we can deduce the following ...
- User appears to have a problem (user certainly thinks so)
- The machine could be faulty
- The user could be faulty
- The use could be faulty
- So the 'perceived problem' can be from a number of possibilities
--o User not using the machine as it was designed
--o User has a unique combination of mask, hose, h/h, machine & breathing
--o and the machine was never tested with this particular combination before
--o Manufacturer's algorithms may be incompatible with the combination
--o Machine may be a defective unit
Lets say that the user in this case decides the machine must be defective & it is just bad luck. The user then obtains another new one of these machines & finds the same pattern. If the user already knows that a couple of other brands of machines do work well allowing that all else remains equal, , then the user may well begin to look at the 1st brand of machine and say, it may be 'deficient' or have some 'limitations' compared to the other brands in the similar configuration.
The conclusions that the user can come to include
--o Brand x has a limitation when working with this combination
--o Brands y & z work as expected
--o People should be made aware of this
The user goes onto a discussion forum & states they think they have found a problem with brand x but rather than find an interactive discussion on what might be possible causes of the perceived 'issue', 'problem', 'defect', 'situation' (chose your own term), the user merely gets told by some other posters that they never experienced this machine problem, but more to the point, get asked to not be making apparently disparaging remarks about brand x.
The user still has a 'problem' but is being asked not to talk about it as being a problem. The user may then wonder just what is going on.
How does one broach the subject of possible problems without talking about them.
It is a given, and perfectly reasonable that the user be advised to engage in trials & tests to see if all parties can better understand if in fact it is a design issue or a usage issue.
So in this discussion I am now asking how does a user even get to talk about the possibilities if the topic is sidelined or squashed before it gets started ?
Saying there can never be a problem makes no sense at all.
Saying that manufacturers never make mistakes is not viable
Saying that the user must prove the problem before discussing it is a catch-22 (an in my opinion is what is being argued by some people in this thread).
However, I do agree that we could adopt a code of discussion that defines 'issues', 'problems', defects', etc: - it seems to me that a common language for talking about such issues may help.
DSM
DSM, I think it would suffice to document all problems. If your committee somehow managed to document which problems were most common to the rest of us, so much the better in my opinion. Just be aware that many of those problems truly are limitations of today's technology. I'll underscore the crux of today's technical limitations one more time for the non-technical readers who are following:
1) Patient airflow signals are
highly complex composite signals that
are comprised of many contributing factors
2) Those highly complex composite signals, unfortunately, manifest with great diversity across the human population
3) The SDB events themselves can never be directly measured via the patient airflow signal
4) Rather, each SDB event type must be indirectly derived on a probability basis from that airflow signal
5) Because airflow signals are so complex and diverse across the human population (even more so across the SDB patient population) there are no 100% probability airflow signals.
6) The lack of "100% probability" airflow signals across the SDB patient population is precisely why any given algorithm cannot achieve a 100% compatibility or efficacy rate across the patient population.
So simply being aware of the fact that many of the problems you document have to do with technical limitations versus "bugs" will probably go a long way toward interfacing with manufacturers. I think your point about finding some middle ground terminology is perfect, since your committee will not be able to discern the exact nature of each technical shortcoming you bring to the manufacturers. For better or worse, you will be at the mercy of the manufacturers regarding disclosure of each technical limitation. I think if you are to have any degree of success interfacing with the manufacturers, your approach will be key. This is an extremely delicate issue to them since their hands are tied regarding each technical shortcoming that has to do with the limitations of today's technology.
Tread lightly, my committee friends, and put your wonderful forte to work on behalf of all of us. Good luck and again, thanks!