Reformating FCS to meet specific clincal needs is a bit self centered
for
From: Robert C. Leif, Ph.D. (rl...@rleif.com)
Date: Tue Jul 29 1997 - 20:25:22 EST
* Next message: Vincent Falco: "Salary Survey Responses"
* Previous message: Maryalice Stetler-Stevenson: "Re: CD20
Gating"
* Maybe in reply to: Jim Houston: "Re: Re[2]: Leave FCS3.0
alone."
* Next in thread: Dave Coder: "Re: Re[2]: Is FCS3.0 obsolete?"
* Messages sorted by: [ date ] [ thread ] [ subject ]
[ author ]
[ attachment ]
________________________________________
To: cyto-inbox
From: Bob Leif
Please see Suzanne Leif's and my posting on the ISAC web site and
R. C. Leif and S. B. Leif, "Evolution of Flow Cytometry Standard,
FCS3.0,
into a DICOM-Compatible Format". Optical Diagnostics of Biological
Fluids
and Advanced Techniques in Analytical Cytology, Ed. A. V. Priezzhev ,
T.
Asakura, and R. C. Leif. A. Katzir Series Editor, Progress Biomedical
Optics Series , SPIE Proceedings Series,Vol. 2982, pp 354-366 (1997).
Many of your very good suggestions were separately arrived at by us.
However, there are two separate subjects: 1) What should be included
in a
Flow Cytometry File for Data Transfer and 2) The actual format for
the
Flow
Cytometry File for Data Transfer. We suggested switching to the
Digital
Imaging and Communications in Medicine, DICOM, format after the year
2000.
My client Phoenix Flow has a product, QC-Tracker, which can be
transformed
into a generic FCS reader, data storage system, and user programmable
data
analysis system. Would you or others be interested in this type of
product?
---------------------------------------------------------------------------*-
---------------------------------
At 03:35 PM 7/28/97 +0100, you wrote:
Let
Date: Tue Jul 29 1997 - 20:25:22 EST
* Next message: Vincent Falco: "Salary Survey Responses"
* Previous message: Maryalice Stetler-Stevenson: "Re: CD20
Gating"
* Maybe in reply to: Jim Houston: "Re: Re[2]: Leave FCS3.0
alone."
* Next in thread: Dave Coder: "Re: Re[2]: Is FCS3.0 obsolete?"
* Messages sorted by: [ date ] [ thread ] [ subject ]
[ author ]
[ attachment ]
________________________________________
To: cyto-inbox
From: Bob Leif
Please see Suzanne Leif's and my posting on the ISAC web site and
R. C. Leif and S. B. Leif, "Evolution of Flow Cytometry Standard,
FCS3.0,
into a DICOM-Compatible Format". Optical Diagnostics of Biological
Fluids
and Advanced Techniques in Analytical Cytology, Ed. A. V. Priezzhev ,
T.
Asakura, and R. C. Leif. A. Katzir Series Editor, Progress Biomedical
Optics Series , SPIE Proceedings Series,Vol. 2982, pp 354-366 (1997).
Many of your very good suggestions were separately arrived at by us.
However, there are two separate subjects: 1) What should be included
in a
Flow Cytometry File for Data Transfer and 2) The actual format for
the
Flow
Cytometry File for Data Transfer. We suggested switching to the
Digital
Imaging and Communications in Medicine, DICOM, format after the year
2000.
My client Phoenix Flow has a product, QC-Tracker, which can be
transformed
into a generic FCS reader, data storage system, and user programmable
data
analysis system. Would you or others be interested in this type of
product?
---------------------------------------------------------------------------*-
---------------------------------
At 03:35 PM 7/28/97 +0100, you wrote:
________________________________________
* Next message: Vincent Falco: "Salary Survey Responses"
________________________________________
* Next message: Vincent Falco: "Salary Survey Responses"
Purdue Cytometry Mail List Plans to have Isac Congress Persuade the
FDA to FORCE their FCS STANDARDS!
From: Randy T. Fischer (fisch...@vax.grc.nia.nih.gov) Date: Thu Jul 17
1997 - 03:25:15 EST * Next message: kc...@samsung.co.kr: "LDL Receptor
Assay for FH" * Previous message: Bob Ashcroft: "RE: Cell Culture
after DNA Ploidy Staining" * Messages sorted by: [ date ] [ thread ]
[ subject ] [ author ] [ attachment ]
________________________________________ I agree with both Marty and
Gunter in the very important issue of standardizing data formatting. I
would point out that lobbying ISAC is only, however, part of the
answer. Regardless of what ISAC may choose to recommend, it is still
up to the manufacturers to implement what they want to do, and if they
do not agree with ISAC, then too bad for ISAC and the flow community.
A potentially more powerful force for change might be the FDA, which
regulates machines used in CLINICAL settings.
If the FDA could be persuaded to require all CLINICAL data be
universally both accessible and readable, then the manufacurers would
be forced to upgrade machines and software
or
lose theLUCRATIVE CLINICAL market.
This would make anlyzing data from different sources easier, and could
facilitate the exchange of crucial clinical results from various
trials where multiple sites and machines are in use.
So how does this get done?
Gunter (and Paul's agreeing response) are correct this needs to be
revisited at Asilomar, with perhaps an additional idea.
Any concrete standardization protocol, FCS3.0 or whatever it ends up
being designated, should be then presented to any and all regulatory
agencies by ISAC to ensure no individual manufacturer decides FCS3.0
in their format is acceptable, even if it is not universally
readable.
Randy T. Fischer NIA/NIH GRC Baltimore, MD 21224
fisch...@vax.grc.nia.nih.gov
Is this Collusion on the Purdue Cytometry Mail List Would the Purdue
Cytoemtry Mail List Software Vendors and the President of ISAC J Paul
Robinson Fall into a the definition of COLLUSION? KEEPING OTHER
VENDORS FROM ENTERING THE MARKET SINCE THE PURDUE CYTOMETRY MAIL LIST
IS THE ONLY OUTLET WITH ISAC AND EVERY UNIVERSITY..ECT
Collusion is an agreement, usually secretive, which occurs between two
or more persons to deceive, mislead, or defraud others of legal
rights, or to obtain an objective forbidden by law typically involving
fraud or gaining an unfair advantage and can involve "wage fixing,
kickbacks, or misrepresenting the independence of the relationship
between the colluding parties."[1] All acts affected by collusion are
considered void.[2]
http://en.wikipedia.org/wiki/Collusion
http://yedda.com/questions/Collusion...2730616624105/
