I actually work (both then and now) with the guy that wrote the first iteration of VA's BCMA system in Topeka back in the mid-'90s. The original was a VA class 3 product that used handheld laser scanners with built-in VT220 LCD screens.
Second System Effect took over, and we ended out going from a handheld laser to a pushcart with a permanently mounted laptop with a laser scanner (as the next version was a Win 3.1/Delphi client that used the Broker). At that point, Central Office got a whiff of it and the rest, as they say, is history.
VA's stuff has always been public domain (since taxpayers pay for the development), and anyone can file a FOIA request for the software. It will be interesting to see how well the current push to truly Open-Source VistA actually works, though.
I typically don't respond to AC's, but someone may read this and actually decide you know what you're talking about. Apache pilots do NOT use image intensifier night vision devices. They use the TADS (Target Acquisition and Designation System) and PNVS (Pilot's Night Vision System), which are both mounted in turrets in the front of the aircraft. These turrets contain true IR sensors, which display the image in a mini-Heads Up Display known as the monocle, which clips to the right side of the pilot's/CPG's helmet.
Other helicopters in the army's inventory use image intensification, but the Apache doesn't (NB: I'm not sure about the Super Cobras, but IIRC, those are all used by the USMC at this point).
Actually, if you look at a tank in thermals, the hottest thing you're gonna see is the roadwheels. The engine isn't nearly as hot. Those roadwheels get a metric buttload of friction from the tracks (which is the main reason that tank tracks have such a limited life expectancy: you'll get something like 5-10 TIMES the wear out of your car tires than an M1 does with its tracks).
However, tankers prefer to operate head-on with their enemy. All of the armor on a tank is thickest/most protective on the head-on aspect. And, with that aspect, cloaking the heat wouldn't be that bad a problem (and yes, I know the TFA showed it on a Challenger's skirts).
FYI: there ain't no such animal. The searchlight that you were seeing on the M60 was IR based, and was used by the light-amplification night vision sight used then. As an aside, the M60A3 was far enough behind the times that it had to use "frog eyes" to get the range to an enemy tank before shooting: the "frog eyes" were visible immediately above the smoke grenade launchers on the turret of the second picture on the first page of the link you sent. They actually had to use trig and parallax to determine the range before the M1 brought out the laser range finder (the M60A5 incorporated the laser range finder as well as a few of the other goodies that came out on the M1).
The first flight M1 included a true thermal night vision system for the gunner, which allowed them to shoot at night without lighting off a big "Shoot Me, Please" sign on top of the tank. The driver and loader both had light amplification viewers that could be swapped into one of the periscope mounts at night. These LA viewers worked on ambient light only (they came with IR filters for the tanks' headlights, but I think we only used 'em once or twice).
I changed my MOS from 19K to 67R before we got M1A1's (much less M1A2's, if that tells you how old I am), but IIRC, the M1A2 has a second thermal viewer that allows the TC (tank/track commander) to operate independently of the GPS, allowing hunter/killer ops between the TC and gunner. There were rumors that they were going to include true thermal systems for the driver and loader, too, but I don't personally know if that came to pass.
Sorry: forgot to log in and posted this anonymously a few minutes ago.
And I've been reasonably happy with it. As you can probably guess, all of these bags are compromises. You can carry your laptop, and your DSLR, but you aren't going to carry much more. I've got my Canon 350D (with my "go-to" lens, the standard Canon 27-135 IS lens) mounted on it in the top spot in the camera area, then another 5 lenses (ranging from a Sigma 75-300 to a Canon 50 mm prime), along with a Sigma shoe flash stashed in camera area. I still have enough room for my 17" MacBook Pro and power adapter (the laptop has a dedicated, zippered pouch that fits like it was made for it). That's ALL you have room for, though.
You won't have room for much more than a thin paperback (I had JUST enough room to stick my Nook in the front pocket where the wall wart/mouse/extra stuff goes).
So the verdict: it does what you need it to do, and does it well (it even has a pretty nice system for carrying a tripod along). Just don't expect to carry much more than the camera and laptop.
I can tell you that, until 1993 (at least), TADS video was not encrypted.
I got out in 1993 as a 67R, and cannot speak for what they did to the video recorders in the Apache after that (particularly in the Longbow upgrade, which was just a wet dream in Boeing's eye when I left).
He just has to ask himself whether or not he feels lucky. I work with ePHI every day, and would NOT want to be the first person targeted with prosecution over that. Remember, HIPAA is a criminal statue, not just civil. Lawsuits would be the least of your worries if you ended out disclosing patient information.
Which is why a lot of pros (and even this amateur) turn as much of that off as they can stand. Particularly when doing portraiture or landscape work (where you have a mostly stationary subject and camera). Which is also why I prefer the Canon DSLR habit of NOT putting Image Stabilization in the body itself.
For me, when I can take a picture at ISO 6400 equivalent with no noise, I'll be a happy guy. I'll no longer have to worry about saving up another $500-$600 for an f2 75 mm prime just to have something I can use in a museum.
Well, it doesn't have to be accessible from the absolute latest and greatest system. However, we're talking about a DBMS old enough that it is still hierarchal instead of relational. None of the common commercial tools available for other relational systems really work with the VA's system. Then, it makes it very difficult to get qualified people to work on (and audit) your systems when they're so old that all the experts are pretty much homegrown.
Please someone mod this insightful, intelligent or otherwise freakin' brilliant! There have been discussions of the VA's medical database in the not-too-distant past on Slashdot (too lazy to try to track the links down right now), and they've (rightly) concentrated on the antiquity of the current database management system.
And, in my opinion, oversight is the problem. If you have enough oversight to keep a$$hats from taking advantage of the system, it becomes virtually impossible to get anything done. Then, you have the inertia of having 20 years worth of medical data that has to at least be accessible from the new system (even if it isn't migrated). If you decrease oversight enough that the system can be responsive, the next thing you know is that everyone starts bring in their brothers/sisters/parents and making them contractors.
Although, to be fair, system stability is another big problem. When my health is riding on the health of the medical records system in a particular hospital, I want the system to be more stable than I am.
Well, all of our systems are set up to store patient info only in the remote database: none of the systems store patient info locally. However, we distinctly do NOT use Google. I'm firmly in favor of Google as a search engine, but the concept of storing medical info and data in something like Google Docs just leaves me cold and clammy.
No worries! I'm a government employee involved with electronic medical records, and I tend to get a bit thin-skinned about such things. Sorry if I sounded grouchy! (Off in search of coffee.)
Neither the story nor the summary mentioned anything about government employees. The private sector is just as capable of screwing up as the government is.
You do raise some good points about VistA. There are some folks in the old guard that cling to M, but I think the vast majority of the the VA's OI&T group have realized that M needs to go away at some point.
The problem is that the "D" in DHCP really became a joke. Due to some of the quirks of the M language, and the way they were abused back in the late '80s to early '90s, the whole system is really a big hairball at this point. So, the first thing that the VA has to do is to tease all of the separate subsystems out from each other. These can then be modernized onto new systems (the strategic direction going forward is Java on the middle-tier and client, and either M or Oracle on the backend, the last I heard). And, since the VA these days uses Cache almost exclusively, those old M globals can be mapped to SQL tables when the time comes to grab the data and move it.
So, the Feds can't just help by throwing resources at PatientOS (or anything else, for that matter). Without those slow backend upgrades, you'd be left with a whole load of data in a legacy system that would be virtually impossible to migrate. If the migration is going to succeed, we have to get the data onto something like a standard system first, and THEN we can start looking at options to go into the future.
While it is written in M, there is most certainly an integrated billing package (frighteningly enough, in the IB namespace). The VHA most certainly DOES bill 3rd party insurance for recoverable claims.
Even more unfortunately, that name was picked in about 1997 or 1998 or so. The prior name of the VHA's electronic medical record system was DHCP (the Decentralized Hospital Computer Program), which was confusing for obvious reasons.
So, they switched to VistA about 10 years or so ago, and look what Microsoft did.
iTunes missing one feature compared to other players does not mean it has less features overall.
True, but the one thing I do miss about WinXP was the combination of my Cowon X5 and MediaMonkey. Want your main music library to be in a free codec? MediaMonkey will do it. Want your music player to keep your library in a different codec set? MediaMonkey will do it (My main library was in FLAC for archival purposes, but when I synced my X5, it transcoded everything to -q6 OGG on the fly). For quite a while, MediaMonkey was the only reason I kept a Parallels copy of XP around.
Compare that to iTunes: Oh, I'm sorry - did you want to use a non-Apple media player? Gee - it sucks to be you. Don't like MP3, AAC, or Apple Lossless? Too bad so sad. I actually ended out buying a new 80gb iPod just to have something that I could plug in and sync.
Then, you get into the UI of iTunes. Frankly, from a usability perspective, it sucks. The fact that everyone in the world OTHER than Apple uses a TreeView and a series of TreeNodes to do a sort by Artist, Album, Album Artist, Label, Amount of Fibre the Artist Had For Breakfast While Recording The Album, etc. just means that everyone ELSE is wrong. You get two choices: you can either make a playlist, or you have to use that goshawful grid control to try to sort it? Want to do a multilevel sort? Tough. You'll do a single level sort using that grid, and YOU'LL LIKE IT!!! Or, you make playlists. Sagans and Sagans of freakin' playlists so that you can halfway keep track of things.
If it weren't for the fact that MediaMonkey was written in Delphi (and thus is not particularly source-portable to any compiler available on an Apple platform), I'd have paid for the port of the darned app myself. (You! In the back!! Put DOWN that copy of Apple Pascal!) That's how good a media player MediaMonkey is.
By and large, Apple does pretty good with their home-grown software, but they missed the mark HORRIBLY with iTunes, and I, for one, can't wait until Songbird matures a bit more.
Sorry to get up on the soapbox, but iTunes is pretty much the one app since I've switched to Mac OS that has been like a slice of bamboo under the fingernails every time I've had to use it.
I'm a little late to the party here, but all of my stuff goes through 01.com. They host all the e-mail for my domain with Zimbra. If you pay 44.95 for a year, you get free smartphone calendar/contacts/email push.
Far, FAR more reliable than hosting my own (which I've done).
So, what YOU'RE telling us is that, deep in the bowels of MI5 somewhere, a man was given a Blackberry and a mission to go to China to "take one for the team". And if he was caught or captured, the PM would disavow all knowledge, etc.
Now THAT sounds like a job for Mr. Bond.
Or me (back before I got married and took the sedate path through life).
Unless he decides that he'd rather not go to jail for 25 years for armed robbery when you identify him, and he decides to shoot you anyway.
Personally, I'd rather take my chances with a firearm.
Re:Assholes calling cops
on
The DIY Tank
·
· Score: 1
Former M-1 Abrams driver here. I can tell you that at least the M-1 and M-1A1 have rubberized tracks by default. As in, I never saw a purely metal track for either of them (not to say they don't exist).
And for us, our tanks were very rarely ever driven on the road. We were usually out in the back 40 taking the most direct route between 2 points.
Slashdot Mirror
I actually work (both then and now) with the guy that wrote the first iteration of VA's BCMA system in Topeka back in the mid-'90s. The original was a VA class 3 product that used handheld laser scanners with built-in VT220 LCD screens.
Second System Effect took over, and we ended out going from a handheld laser to a pushcart with a permanently mounted laptop with a laser scanner (as the next version was a Win 3.1/Delphi client that used the Broker). At that point, Central Office got a whiff of it and the rest, as they say, is history.
VA's stuff has always been public domain (since taxpayers pay for the development), and anyone can file a FOIA request for the software. It will be interesting to see how well the current push to truly Open-Source VistA actually works, though.
Um...
I typically don't respond to AC's, but someone may read this and actually decide you know what you're talking about. Apache pilots do NOT use image intensifier night vision devices. They use the TADS (Target Acquisition and Designation System) and PNVS (Pilot's Night Vision System), which are both mounted in turrets in the front of the aircraft. These turrets contain true IR sensors, which display the image in a mini-Heads Up Display known as the monocle, which clips to the right side of the pilot's/CPG's helmet.
Other helicopters in the army's inventory use image intensification, but the Apache doesn't (NB: I'm not sure about the Super Cobras, but IIRC, those are all used by the USMC at this point).
Actually, if you look at a tank in thermals, the hottest thing you're gonna see is the roadwheels. The engine isn't nearly as hot. Those roadwheels get a metric buttload of friction from the tracks (which is the main reason that tank tracks have such a limited life expectancy: you'll get something like 5-10 TIMES the wear out of your car tires than an M1 does with its tracks).
However, tankers prefer to operate head-on with their enemy. All of the armor on a tank is thickest/most protective on the head-on aspect. And, with that aspect, cloaking the heat wouldn't be that bad a problem (and yes, I know the TFA showed it on a Challenger's skirts).
FYI: there ain't no such animal. The searchlight that you were seeing on the M60 was IR based, and was used by the light-amplification night vision sight used then. As an aside, the M60A3 was far enough behind the times that it had to use "frog eyes" to get the range to an enemy tank before shooting: the "frog eyes" were visible immediately above the smoke grenade launchers on the turret of the second picture on the first page of the link you sent. They actually had to use trig and parallax to determine the range before the M1 brought out the laser range finder (the M60A5 incorporated the laser range finder as well as a few of the other goodies that came out on the M1).
The first flight M1 included a true thermal night vision system for the gunner, which allowed them to shoot at night without lighting off a big "Shoot Me, Please" sign on top of the tank. The driver and loader both had light amplification viewers that could be swapped into one of the periscope mounts at night. These LA viewers worked on ambient light only (they came with IR filters for the tanks' headlights, but I think we only used 'em once or twice).
I changed my MOS from 19K to 67R before we got M1A1's (much less M1A2's, if that tells you how old I am), but IIRC, the M1A2 has a second thermal viewer that allows the TC (tank/track commander) to operate independently of the GPS, allowing hunter/killer ops between the TC and gunner. There were rumors that they were going to include true thermal systems for the driver and loader, too, but I don't personally know if that came to pass.
Sorry: forgot to log in and posted this anonymously a few minutes ago.
And I've been reasonably happy with it. As you can probably guess, all of these bags are compromises. You can carry your laptop, and your DSLR, but you aren't going to carry much more. I've got my Canon 350D (with my "go-to" lens, the standard Canon 27-135 IS lens) mounted on it in the top spot in the camera area, then another 5 lenses (ranging from a Sigma 75-300 to a Canon 50 mm prime), along with a Sigma shoe flash stashed in camera area. I still have enough room for my 17" MacBook Pro and power adapter (the laptop has a dedicated, zippered pouch that fits like it was made for it). That's ALL you have room for, though.
You won't have room for much more than a thin paperback (I had JUST enough room to stick my Nook in the front pocket where the wall wart/mouse/extra stuff goes).
So the verdict: it does what you need it to do, and does it well (it even has a pretty nice system for carrying a tripod along). Just don't expect to carry much more than the camera and laptop.
I can tell you that, until 1993 (at least), TADS video was not encrypted.
I got out in 1993 as a 67R, and cannot speak for what they did to the video recorders in the Apache after that (particularly in the Longbow upgrade, which was just a wet dream in Boeing's eye when I left).
are true. We'll leave it as an exercise for the reader to decide which.
He just has to ask himself whether or not he feels lucky. I work with ePHI every day, and would NOT want to be the first person targeted with prosecution over that. Remember, HIPAA is a criminal statue, not just civil. Lawsuits would be the least of your worries if you ended out disclosing patient information.
Which is why a lot of pros (and even this amateur) turn as much of that off as they can stand. Particularly when doing portraiture or landscape work (where you have a mostly stationary subject and camera). Which is also why I prefer the Canon DSLR habit of NOT putting Image Stabilization in the body itself.
For me, when I can take a picture at ISO 6400 equivalent with no noise, I'll be a happy guy. I'll no longer have to worry about saving up another $500-$600 for an f2 75 mm prime just to have something I can use in a museum.
Well, it doesn't have to be accessible from the absolute latest and greatest system. However, we're talking about a DBMS old enough that it is still hierarchal instead of relational. None of the common commercial tools available for other relational systems really work with the VA's system. Then, it makes it very difficult to get qualified people to work on (and audit) your systems when they're so old that all the experts are pretty much homegrown.
That assumption isn't made. They keep a pretty close eye on outbound traffic as well. But your point is well made. :)
Please someone mod this insightful, intelligent or otherwise freakin' brilliant! There have been discussions of the VA's medical database in the not-too-distant past on Slashdot (too lazy to try to track the links down right now), and they've (rightly) concentrated on the antiquity of the current database management system.
And, in my opinion, oversight is the problem. If you have enough oversight to keep a$$hats from taking advantage of the system, it becomes virtually impossible to get anything done. Then, you have the inertia of having 20 years worth of medical data that has to at least be accessible from the new system (even if it isn't migrated). If you decrease oversight enough that the system can be responsive, the next thing you know is that everyone starts bring in their brothers/sisters/parents and making them contractors.
Although, to be fair, system stability is another big problem. When my health is riding on the health of the medical records system in a particular hospital, I want the system to be more stable than I am.
Well, all of our systems are set up to store patient info only in the remote database: none of the systems store patient info locally. However, we distinctly do NOT use Google. I'm firmly in favor of Google as a search engine, but the concept of storing medical info and data in something like Google Docs just leaves me cold and clammy.
No worries! I'm a government employee involved with electronic medical records, and I tend to get a bit thin-skinned about such things. Sorry if I sounded grouchy! (Off in search of coffee.)
Neither the story nor the summary mentioned anything about government employees. The private sector is just as capable of screwing up as the government is.
You do raise some good points about VistA. There are some folks in the old guard that cling to M, but I think the vast majority of the the VA's OI&T group have realized that M needs to go away at some point.
The problem is that the "D" in DHCP really became a joke. Due to some of the quirks of the M language, and the way they were abused back in the late '80s to early '90s, the whole system is really a big hairball at this point. So, the first thing that the VA has to do is to tease all of the separate subsystems out from each other. These can then be modernized onto new systems (the strategic direction going forward is Java on the middle-tier and client, and either M or Oracle on the backend, the last I heard). And, since the VA these days uses Cache almost exclusively, those old M globals can be mapped to SQL tables when the time comes to grab the data and move it.
So, the Feds can't just help by throwing resources at PatientOS (or anything else, for that matter). Without those slow backend upgrades, you'd be left with a whole load of data in a legacy system that would be virtually impossible to migrate. If the migration is going to succeed, we have to get the data onto something like a standard system first, and THEN we can start looking at options to go into the future.
While it is written in M, there is most certainly an integrated billing package (frighteningly enough, in the IB namespace). The VHA most certainly DOES bill 3rd party insurance for recoverable claims.
So, they switched to VistA about 10 years or so ago, and look what Microsoft did.
iTunes missing one feature compared to other players does not mean it has less features overall.
True, but the one thing I do miss about WinXP was the combination of my Cowon X5 and MediaMonkey. Want your main music library to be in a free codec? MediaMonkey will do it. Want your music player to keep your library in a different codec set? MediaMonkey will do it (My main library was in FLAC for archival purposes, but when I synced my X5, it transcoded everything to -q6 OGG on the fly). For quite a while, MediaMonkey was the only reason I kept a Parallels copy of XP around.
Compare that to iTunes: Oh, I'm sorry - did you want to use a non-Apple media player? Gee - it sucks to be you. Don't like MP3, AAC, or Apple Lossless? Too bad so sad. I actually ended out buying a new 80gb iPod just to have something that I could plug in and sync.
Then, you get into the UI of iTunes. Frankly, from a usability perspective, it sucks. The fact that everyone in the world OTHER than Apple uses a TreeView and a series of TreeNodes to do a sort by Artist, Album, Album Artist, Label, Amount of Fibre the Artist Had For Breakfast While Recording The Album, etc. just means that everyone ELSE is wrong. You get two choices: you can either make a playlist, or you have to use that goshawful grid control to try to sort it? Want to do a multilevel sort? Tough. You'll do a single level sort using that grid, and YOU'LL LIKE IT!!! Or, you make playlists. Sagans and Sagans of freakin' playlists so that you can halfway keep track of things.
If it weren't for the fact that MediaMonkey was written in Delphi (and thus is not particularly source-portable to any compiler available on an Apple platform), I'd have paid for the port of the darned app myself. (You! In the back!! Put DOWN that copy of Apple Pascal!) That's how good a media player MediaMonkey is.
By and large, Apple does pretty good with their home-grown software, but they missed the mark HORRIBLY with iTunes, and I, for one, can't wait until Songbird matures a bit more.
Sorry to get up on the soapbox, but iTunes is pretty much the one app since I've switched to Mac OS that has been like a slice of bamboo under the fingernails every time I've had to use it.
She's discovering the joys of shoelaces now, and you want to talk about knots.. Boy, oh boy. She's gonna be a mathematician for sure!
I'm a little late to the party here, but all of my stuff goes through 01.com. They host all the e-mail for my domain with Zimbra. If you pay 44.95 for a year, you get free smartphone calendar/contacts/email push. Far, FAR more reliable than hosting my own (which I've done).
So, what YOU'RE telling us is that, deep in the bowels of MI5 somewhere, a man was given a Blackberry and a mission to go to China to "take one for the team". And if he was caught or captured, the PM would disavow all knowledge, etc.
Now THAT sounds like a job for Mr. Bond.
Or me (back before I got married and took the sedate path through life).
Personally, I'd rather take my chances with a firearm.
And for us, our tanks were very rarely ever driven on the road. We were usually out in the back 40 taking the most direct route between 2 points.
Which means, at my level, they're completely disallowed. But then, I don't have any access to sensitive information anyway.