In healthcare, there is a well defined interface called HL7 for messaging between systems. It is not without its problems, but can work. More recently, HIPAA has defined interfaces for talking to insurance systems.
I don't know about the relative complexity of billing with healthcare software, but don't completely despair.
It does however almost always require an integration engine (shameless plug for our Rhapsody Integration Engine) in order to translate between differences in interpretation and coding.
I was doing support for one of our applications, and the the customer was reporting that our app couldn't start up. The error was unable to resolve host, the name of the database server. Among other suggestions, I said
Your network is hosed causing name resolution to fail.
Normally, our support team reads these and rewrites if necessary. This time, they didn't, they cut & paste.
The reply was:
Our network admin says that our network is not hosed.
That's the same as in New Zealand. You even have the option to use either the retail place or the manufacturer's warranty, at your discretion. Either way, you get one year.
Actually, https is never cached. It's one of the reasons pages over https are so much slower, all those damned images and javascript have to be downloaded over and over again.
I installed this at work. I use Outlook with exchange. It only indexes files in outlook when I am logged it (so it doesn't need permissions as per windows explorer). Since then, it creates a cache of those emails and they can be searched. Great for me.
What if someone else can view that cache? Can they? I don't know. I certainly hope not. If they can, this is a serious flaw in the software, one that was certainly not made well known. FAQ my arse. What if Microsoft puts in an obscure webpage somewhere 'we don't guarantee this software is free of security holes'. Why aren't you rushing to their defense? Don't install it... they told you about it.
Quite honestly, if this makes it easier to view other people's documents, this is a flawed piece of software and you should be aware of this.
It can index Outlook emails. These are protected (especially if like me you use Exchange Server at work). They are only indexable when you are logged in to Outlook. Thus the index (and the cache) is built up while you have permissions, so anyone else can see your emails.
Unless it stores a different index per user, this is a definite issue.
However, you are quite correct. It can be quite difficult at times to ensure that all objects are correctly cleaned up after usage. As soon as you introduce items such as HashMaps, etc, you run into potential for these problems.
We once had this issue when we embedded the mozilla javascript interpreter in our app. The problem was that you have to create a scope object, with all sorts of predefined classes and functions and so forth. This was expensive, so we pooled them. Unfortunately this left a memory leak, as objects declared in scope by the javascript itself would not tidy up at the end of processing.
Indeed it turns out the library has parent scopes, so we could create a new child scope cheaply each time, but the point remains.
Real time has multiple uses. For example, my bank can display my bank account information 'real-time', which does not mean OS scheduling, it means if I use my debit card then go home and have a look, the update will be there.
Real time depends completely on context, even within the computers.
Not to mention that the safest place is directly under an antenna anyway. Radiation from an antenna radiates maximally perpendicualar to the antenna, falling off to absolutely nothing at the poles of the antenna. There should be next to no radiation underneath a transmitter tower.
I've just had to sink months of time in to a port from one database to another, because of the overuse of stored procedures. A good portion of them didn't do anything anyway, just some selects and so forth.
These days, so long as you are using a real language, you can find really good tools to perform persistence automatically, freeing you to have a wonderfully tidy place to put your business logic.
Having said that, it's not cut and dried. Stored procedures allow you to perform logic on your data. And if you use it for that, i.e., Data related logic, then you're fine. If you intrude into the world of business logic sitting in the database, you're going to run into problems very quickly... no extensibility, harder to test, etc.
So:
Make sure you're using a language that allows you to perform logic somewhere that is not a stored procedure and not a script inside an HTML page
Understand the difference between business logic and data related logic
Do your best to understand the potential for you to want to alter databases
The most likely next thing to occur is that the melting of the arctic ice (which is definitely happening) may cause the Atlantic gulf stream to stop. This is a huge current of warm water that warms up the east coast of the US and western Europe.
Of course people have heard of ice ages. That doesn't mean we should just bring one on. Can you imagine the devastation that will cause? Just consider the possibility, instead of dismissing it out of hand because you dont want to change your lifestyle.
Slashdot Mirror
I don't know about the relative complexity of billing with healthcare software, but don't completely despair.
It does however almost always require an integration engine (shameless plug for our Rhapsody Integration Engine) in order to translate between differences in interpretation and coding.
I'm lovin' it!
I was doing support for one of our applications, and the the customer was reporting that our app couldn't start up. The error was unable to resolve host, the name of the database server. Among other suggestions, I said
Normally, our support team reads these and rewrites if necessary. This time, they didn't, they cut & paste.The reply was:
Whoops.That's the same as in New Zealand. You even have the option to use either the retail place or the manufacturer's warranty, at your discretion. Either way, you get one year.
Even IE does this correctly.
Question and Answer folks?
Perhaps QA.
?
What if someone else can view that cache? Can they? I don't know. I certainly hope not. If they can, this is a serious flaw in the software, one that was certainly not made well known. FAQ my arse. What if Microsoft puts in an obscure webpage somewhere 'we don't guarantee this software is free of security holes'. Why aren't you rushing to their defense? Don't install it... they told you about it.
Quite honestly, if this makes it easier to view other people's documents, this is a flawed piece of software and you should be aware of this.
It can index Outlook emails. These are protected (especially if like me you use Exchange Server at work). They are only indexable when you are logged in to Outlook. Thus the index (and the cache) is built up while you have permissions, so anyone else can see your emails.
Unless it stores a different index per user, this is a definite issue.
Bush: 2.3
Kerry: 4.8
Draw your own conclusions...
However, you are quite correct. It can be quite difficult at times to ensure that all objects are correctly cleaned up after usage. As soon as you introduce items such as HashMaps, etc, you run into potential for these problems.
We once had this issue when we embedded the mozilla javascript interpreter in our app. The problem was that you have to create a scope object, with all sorts of predefined classes and functions and so forth. This was expensive, so we pooled them. Unfortunately this left a memory leak, as objects declared in scope by the javascript itself would not tidy up at the end of processing.
Indeed it turns out the library has parent scopes, so we could create a new child scope cheaply each time, but the point remains.
Real time depends completely on context, even within the computers.
Welcome to bogan country.
Not to mention that the safest place is directly under an antenna anyway. Radiation from an antenna radiates maximally perpendicualar to the antenna, falling off to absolutely nothing at the poles of the antenna. There should be next to no radiation underneath a transmitter tower.
These days, so long as you are using a real language, you can find really good tools to perform persistence automatically, freeing you to have a wonderfully tidy place to put your business logic.
Having said that, it's not cut and dried. Stored procedures allow you to perform logic on your data. And if you use it for that, i.e., Data related logic, then you're fine. If you intrude into the world of business logic sitting in the database, you're going to run into problems very quickly... no extensibility, harder to test, etc.
So:
- Make sure you're using a language that allows you to perform logic somewhere that is not a stored procedure and not a script inside an HTML page
- Understand the difference between business logic and data related logic
- Do your best to understand the potential for you to want to alter databases
Then find your happy medium!Don't feel embarrassed - we've all been in bed with your wife - in Japan
Not to nitpick, but alpha transparency is an optional part of the PNG specification. IE supports all of the required parts.
IE makes at most two concurrent connections to any given server.
Brilliant. Classic. And I live in NZ. And have money in the NZX (hmmm, I should just check....)
Hmm.
Don't forget the vaporware.
Feckin html. kelsey@.net.nz
Ben, It's Kelsey. If you want, send me an email at kelsey@.net.nz
Ben Goodger went to Auckland Grammar school, he was in my class :-)
Of course people have heard of ice ages. That doesn't mean we should just bring one on. Can you imagine the devastation that will cause? Just consider the possibility, instead of dismissing it out of hand because you dont want to change your lifestyle.
I tried to find it, but I kept getting a 'Not Found' error.