Showing posts with label hit. Show all posts
Showing posts with label hit. Show all posts

Tuesday, 31 May 2011

Cloud storage for the exchange of health information

ZH_dossier_voorbeeld.pdf Download this file

For several years I'm complaining that paper health records are getting lost when one of the elderly residents of our carehome is hospitalised.

We did all kinds of efforts to prevent loss of the papers, but no success till now.
In case of loss we had to fax (alas, no email) the papers to the central reception of the hospital (alas, no fax at the specific department).
I was approached by a hospital and a software vendor to find a solution.
A logical suggestion was to use cloud storage (like Amazon, Dropbox, Nomadesk, ...) and to use encrypted folders (per user or per organisation) for such papers. Such cloud solutions are easy to use, very flexible, easy to implement and safe enough for this purpose. When hospital staff reacts outraged 'how unsafe this is', I point them to the current 'solution' where we fax the papers to the central reception.
I'm very curious which cloud solution they are going to produce, how cheap it will be and how user friendly it will be.

Monday, 29 June 2009

Ten Principles for an “iPhone­-like” Platform for HIT

Ten Principles for Fostering Development of an “iPhone­-like” Platform for Healthcare Information Technology

http://www.chip.org/platform

  1. Technology platforms that support substitutable applications should be promoted.

  2. Messages and protocols for data exchange should be allowed to emerge on demand in a market-driven approach, and specified transparently at every level.

  3. Protocols and application programming interfaces should allow the possibility of multiple platforms co-existing.

  4. Application programming interfaces should be open.

  5. Substitutable application or platform vendors should not have control over what is installed on the platform.

  6. Application installation should be turnkey.

  7. The intellectual property of platforms and applications should be kept separate.

  8. All applications should be removable and none should be required to run a platform.

  9. The platform should have a highly efficient delivery mechanism for applications.

  10. Certification requirements for platforms and applications should be kept minimal to maximize substitutability.

Posted via email from bartcollet's posterous