I was in the market for a stand-alone HL7 listener (incoming messages) and router (outgoing messages) for a patient check-in app we had been working on, my needs were simple, send an ADT message with some key patient identifiers collected at the kiosk and listen for the response with all of the demographic/insurance data I needed to present for verification. At the end of this transaction we needed to send a message with the appointment status change. There seems to be no shortage of available products in the market right now and one of them was recommended to me, HermeTech (http://www.hermetechnz.com/EasyHL7/) and their EasyHL7 product line.
The products are sold separately for $300 or bundled for $500 (if you can find the right page), there are other bundles available that look worth investigating. The highlights of this particular app include
- Ability to run as a system service
- Included service monitor (real-time stats)
- Simulator for testing
- Easy setup with intuitive graphical user interface
So if your in the market for a quick to deploy HL7 listener/router I would suggest looking at Hermetech, my conversation with their support line was great and informative while I was doing my preliminary research.
Another addition for AWS was recently released and adds a nice feature to the Route53/S3 combo, the ability to failover to an S3 bucket if your primary site goes down. This can be paired up with both weighted and latency based routing and can be configured whichever way is best for you.
What’s more intriguing about this is not the ability to failover to an S3 bucket but the ability to failover to another region, Say if us-east-1 goes down, redirect the traffic to us-west-1 or maybe a backup on a completely different provider…say Rackspace or even your own private cloud to save costs provided you can handle the traffic.
Then again, does AWS ever go down? Ha, that being said, this sure beats my website being load balanced over multiple Micro AWS instances…
Effective today root domains can now be hosted directly from an S3 bucket, previously you needed a sub domain like WWW or a web server to proxy request to an S3 bucket, this has finally been addressed by Amazon Web Services.
Full instructions can be found here:
Basically you just create a new bucket for your root domain (jeremyharlow.net) and they added a redirect option in the bucket configuration, just select redirect and point it to the bucket hosting the static site. The only catch? You need to let Route53 handle your DNS so you can add the alias and point the domain to an S3 bucket.
This is an awesome addition to S3.