How do I get this query to work?

[--CELKO--]

Re: How do I get this query to work?

>> IOW, within your own domain, BE CONSISTENT. <<

... because it makes global correction changes easier. Seriously.

The bad news is when the correction has to be done one unit at a time.
I had a situation where "Misc" was a bit toooooo broad and needed to be
defined better. Then we found out that there was a code used by the US
Army for classifying medical exam results we should have used.

[Ed Prochak]

Re: How do I get this query to work?

It's agreed that using SSNs inapproprtiatel y is wrong. That not what
Joe said. His point is:
If you need SSNs (note his reference to federal programs)
AND you also need to deal with folks that don't have SSN's,
Then there exists a set of SSN numbers that can be used.

HTH
ed

[David W. Fenton]

Re: How do I get this query to work?

"Ed Prochak" <ed.prochak@mag icinterface.com > wrote in
news:1121962928 .759994.256390@ f14g2000cwb.goo glegroups.com:
[color=blue]
> It's agreed that using SSNs inapproprtiatel y is wrong. That not
> what Joe said. His point is:
> If you need SSNs (note his reference to federal programs)
> AND you also need to deal with folks that don't have SSN's,
> Then there exists a set of SSN numbers that can be used.[/color]

The context of the discussion was the identification of universally
application candidate primary keys, like VIN and UPC. SSN is simply
not at all in the same class -- not even close.

There are two reasons for that:

1. it's not international.

2. there are major privacy considerations that make its storage
problematic even in medical applications (I went through this a few
years back when HIPPA went into effect).

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc

[Ed Prochak]

Re: How do I get this query to work?

David W. Fenton wrote:[color=blue]
> "Ed Prochak" <ed.prochak@mag icinterface.com > wrote in
> news:1121962928 .759994.256390@ f14g2000cwb.goo glegroups.com:
>[color=green]
> > It's agreed that using SSNs inapproprtiatel y is wrong. That not
> > what Joe said. His point is:
> > If you need SSNs (note his reference to federal programs)
> > AND you also need to deal with folks that don't have SSN's,
> > Then there exists a set of SSN numbers that can be used.[/color]
>
> The context of the discussion was the identification of universally
> application candidate primary keys, like VIN and UPC. SSN is simply
> not at all in the same class -- not even close.[/color]

Actually the context was a subthread of that, Specifically whether
standards were "complete". Look back at the remark Joe made:

--CELKO-- wrote:
replying to someone's comment[color=blue][color=green][color=darkred]
> >> Sometimes the rules are very much deficient and this is when the rule-makers are at their most silent. <<[/color][/color]
>
> I disagree completely.
>
> Most standardized codes are seldom "very much deficient"; home-made
> schemes are. Standardized codes tend to cover more of the problem
> space than exists at the time of their creation and have an ordrely
> pattern for growth. .
>
> And the "rule makers" are far, far from silent. They hold meetings,
> issue White Papers and publish changes at a trusted source.
>
> Examples: The current changes in UPC and VIN. ICD-8 to ICD-9 changes,
> etc.
>
> I don't if you are aware of it, but can extend UPC codes to cover items
> you make at your own grocery store. No need to throw out the whole
> thing because you bake bread on site. Likewise, the unused SSN ranges
> that can cover non-SSN people in several federal programs. Etc.[/color]
--end of CHELKO quote--

[color=blue]
>
> There are two reasons for that:
>
> 1. it's not international.[/color]

You don't need to use SSN for international applications. That's
obviously an inappropriate use. We agree, it's not an international
standard and doesn't need to be such.
[color=blue]
>
> 2. there are major privacy considerations that make its storage
> problematic even in medical applications (I went through this a few
> years back when HIPPA went into effect).[/color]

Again, in HIPPA applications SSN may be inappropriate data to collect.
But Privacy concerns were not part of the thread. That's a different
issue than whether standards are always complete.
[color=blue]
>
> --
> David W. Fenton http://www.bway.net/~dfenton
> dfenton at bway dot net http://www.bway.net/~dfassoc[/color]

HTH explain the context of my comments. Hopefully we are all on the
same thread again.

Ed Prochak

[AK]

Re: How do I get this query to work?

>> Likewise, the unused SSN ranges
that can cover non-SSN people in several federal programs. <<

well, my employer demanded that my health and dental insurers do not
use my SS# as a primary key.
Apparently the insurers seem to have complied, and I don't see my SS#
on insurance cards any more, and I was not asked to verify it the last
time I needed to call them. Looks like the whole SS# thing is being
thrown out, and for a good reason

[--CELKO--]

Re: How do I get this query to work?

SSN used to be School ids (I just ordered a college transcript),
driver's license numbers, insurance policy ids, etc. It is dying, but
it is dying very slowly. My guess is that within 5 -10 years a smart
card/ RFID/biometric system will become the standard beause of Homeland
Security, ID Theft and cheaper hardware.

[Lemming]

Re: How do I get this query to work?

On 2 Aug 2005 21:01:07 -0700, "--CELKO--" <jcelko212@eart hlink.net>
wrote:
[color=blue]
>My guess is that within 5 -10 years a smart
>card/ RFID/biometric system will become the standard beause of Homeland
>Security, ID Theft and cheaper hardware.[/color]

I believe you are right.

Be afraid. Be very afraid.

Lemming
--
Curiosity *may* have killed Schrodinger's cat.