I just had a contractor tell me that the problem with my Diabetic
detection and
Listing 'feature' in their product (Integrated Clinical Database, ICDB)
is because the
'view' crafted for that detection is going 'stale'.

I admit that most my SQL design experience is in MSSQL's T-SQL although
I'm starting to come up to speed on SQL*Plus, anyway, the above
explanation provided to be from the TriCare guy seems bogus.

Simply put there are four or five good Lab Chemistry parameters one
could use in a SQL select statement to determine if a patient is
diabetic or a diabetic candidate without having specific ICD9 diagnosis
coding that declares the patient diabetic.

A select statement returns a cursor of data that meets the selection
criteria and on MSSQL is a static snapshot of what is in the database at
the time the query was executed.  Thus, if a patient had parameters that
met diabetic conditions stored in the database over the past year, how
can a view go 'stale'?  Is this just a Oracle peculiarity or am I
getting a smoke screen as I suspect?

v/r

Stephen S. Wolfe, GS-11, DAFC
Data Services Manager
[EMAIL PROTECTED]
(813) 827-9974  DSN 651-9974
-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.net
-- 
Author: Wolfe Stephen S GS-11 6 MDSS/SGSI
  INET: [EMAIL PROTECTED]

Fat City Network Services    -- 858-538-5051 http://www.fatcity.com
San Diego, California        -- Mailing list and web hosting services
---------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).

Reply via email to