Desde la web de Nathan Freeman, nos presentan una aplicación realizada para la gestión de pacientes en clínicas, consultas, hospitales. Así dicho no es muy impresionante, pero hay que comentar que es la aplicación realizada sobre Lotus Notes más asombrosa que he visto nunca. Os recomiendo que veáis el video, ya que no tiene desperdicio.



Es una aplicación realizada sobre Lotus Expeditor y  Lotus Notes. El interfaz está realizado con SWT sobre Eclipse y el cliente Lotus Notes, aunque está ahí, no se ve.

Lo interesante no es el desarrollo de una interfaz táctil, de cuidado diseño. No, lo interesante es la integración de la aplicación en una infraestrutura segura, con opciones para trabajo offline, con encriptación de la información y las comunicaciones, y  multisistemaoperativo entre otras características que proporciona Lotus Domino. Adicionalmente, se hace uso de Lotus Foundations como servidor.

Es quizá lo que hacía falta para mostrar de lo que es capaz una aplicación compuesta y un equipo técnico de altísimo nivel. Me consta que en España hay alguna que otra gran empresa "jugando" con este tipo de desarrollos, pero desconozco si han llegado a este nivel de aplicación.

Lo que queda claro es que las puertas que ha abierto Eclipse son enormes, pero hay que saber por cúal avanzar.

Para más detalles, podéis leer en la web del autor.

Adicionalmente os dejo unos comentarios del autor que tampoco tienen desperdicio.

...Domino Designer wasn't involved in this effort except in the most simplistic way (we do have forms & views, but for the sake of backend modeling, not UI.) 99% of the work was done in Eclipse 3.4.1 with the Expeditor 6.2 toolkit and Notes 8.5.0.

The prescription part of the system actually DOES use an RDBMS backend instead of Notes. We've designed it to consume JDBC sources just as readily as NSF sources (and local text and image file sources, for that matter.)

There is no question that the flexibility and breadth of OSGi bundles on the Eclipse platform helped enormously.

However, I wouldn't want to write our actual treatment information back to anything but NSF. We don't have to worry about identity management. We don't have to worry about federation. We don't have to worry about backup. We don't have to worry about scalability. We don't have to worry about reliability. We don't have to worry about distribution for maintenance cycles. We don't have to worry about encrypted storage. We don't have to worry about encrypted communications.

We can work with records that are as fine-grained as "blood pressure systolic in a supine position reading 130mmHg" or as cumbersome as a 300MB DICOMM file of a contrasted spinal MRI.

For all of that, NSF *just works.*

If that means we occasionally have to manually code a columnar JOIN by looping through some values in Java, I'll do it with a great big smile on my face.

Oh, and why is it not a web application? Do you think we could design that shuttle wheel list scroller (we call that control a "BigList" by the way) to work via JavaScript and AJAX? Ummmm... no thank you. It's hard enough to get it working when we're writing the RCP equivalent of Assembler by doing pixel-level transforms on graphics primitives to squeeze adequate performance out. We wouldn't even be able to do all those gradient buttons with rounded corners on the web, much less the anti-aliased centered text overlays. What would we do instead? Image slices?

I'd gouge out my eyes first.

HTML paradigms aren't ready for touch screens yet. Even sexy iPhone sites aren't ready for this yet. (Can you imagine searching through 40,000 ICD9 diagnoses, or 120,000 prescribable drugs on an iPhone? *page*... *page*... *page*...)