Please turn yourself in to the nearest Terrorist Processing Center. You obviously have inappropriate knowledge of the FBI Internal Operations. It is innapropriate to inform the public that we 'might' be monitoring public computer systems.
While an investigation is being made into your means of obtaining this information, you will be our 'guest' at one of our fine Camps.
Thank you for your prompt cooperation in defending our country.
Call it the
Secure Linux Access Server Heisenberg Direct Operation Tester
It's designed to push a server to the utmost limits of it's capabilities!
(Forgive the obligatory technobabble)
Having worked in the Healthcare industry coding the applications to let Provider A talk to Insuror B and bill Patient C using credit card D, I can tell you the Health Care industry is about the poorest example to use when evaluating interoperability. Each segment of the industry has it's own rules and requirements, and not even in a face to face meeting can the data be communicated. It is, therefore, impossible to model the same data that requires literally hundreds of person hours to gather.
Add to that the fact that regulation, legislation, etc. complicate the matter, and what you have is 'One big medevial muddle' (Merlin).
If you want to examine interoperability, look to the logistics and transportation industry. In the T&L industry, there are standards, agreed to by all participants (ISO - International Standards Orginization). These standards mean that Customer A orders from Supplier B. Supplier B uses inventory to access Wharehouse C. Wharehouse C checks inventory, reorders as needed, and ships using Transportation company D. Transportation company D delivers the package to Customer A, collecting payment and signature as necessary. Transportation company D also notifies Wharehouse C (the shipper) who modifies inventory and notifies Supplier B.
This is all done using current technology. Combinations of standards, ODBC, XML, Common Data Modeling Language (CDML), etc. All this hype being given about interoperability is exactly that. It does not take a magic.NET or J2EE to accomplish it. It takes intelligent, creative programming and agreement on standards.
Just remember, the simplest form of interoperability is a pen and paper.
Freedom is irrelevant. Sigs are irrelevant. You must comply...
Slashdot Mirror
Please turn yourself in to the nearest Terrorist Processing Center. You obviously have inappropriate knowledge of the FBI Internal Operations. It is innapropriate to inform the public that we 'might' be monitoring public computer systems.
While an investigation is being made into your means of obtaining this information, you will be our 'guest' at one of our fine Camps.
Thank you for your prompt cooperation in defending our country.
Call it the Secure Linux Access Server Heisenberg Direct Operation Tester It's designed to push a server to the utmost limits of it's capabilities! (Forgive the obligatory technobabble)
Having worked in the Healthcare industry coding the applications to let Provider A talk to Insuror B and bill Patient C using credit card D, I can tell you the Health Care industry is about the poorest example to use when evaluating interoperability. Each segment of the industry has it's own rules and requirements, and not even in a face to face meeting can the data be communicated. It is, therefore, impossible to model the same data that requires literally hundreds of person hours to gather.
.NET or J2EE to accomplish it. It takes intelligent, creative programming and agreement on standards.
Add to that the fact that regulation, legislation, etc. complicate the matter, and what you have is 'One big medevial muddle' (Merlin).
If you want to examine interoperability, look to the logistics and transportation industry. In the T&L industry, there are standards, agreed to by all participants (ISO - International Standards Orginization). These standards mean that Customer A orders from Supplier B. Supplier B uses inventory to access Wharehouse C. Wharehouse C checks inventory, reorders as needed, and ships using Transportation company D. Transportation company D delivers the package to Customer A, collecting payment and signature as necessary. Transportation company D also notifies Wharehouse C (the shipper) who modifies inventory and notifies Supplier B.
This is all done using current technology. Combinations of standards, ODBC, XML, Common Data Modeling Language (CDML), etc. All this hype being given about interoperability is exactly that. It does not take a magic
Just remember, the simplest form of interoperability is a pen and paper.
Freedom is irrelevant. Sigs are irrelevant. You must comply...