PatientOS LinuxMedNews Update

up a level
post article
search
admin
Contact
main

PatientOS LinuxMedNews Update

Posted by Greg Caulton on Tuesday November 13, 2007 @ 07:54 AM
from the medical-open-source-development dept.
The next release of PatientOS is being refocused to focus on specific ambulatory clinic or Physician practice workflows that can be completed end-to-end. To that goal I have an initial use case to share: http://www.patientos.org/wikimedia/index.php/Nursing_documentation_and_progress_note Digg this article

If you are interested in adding your own use case that you believe would be beneficial for a first release of PatientOS you can do it on the wiki http://www.patientos.org/wikimedia

The development environment is underway to
a) Pre-configure an online developer environment using terminal services
b) Create instructions on how to replicate the development environment

The reason the development environment is non trivial is that I use a fair amount of code generation to

i) automate the creation of the java objects (com.patientis.model...)
ii) generate the Hibernate XML to map the objects to the database.
iii) generate the underlying code to bind objects to forms.
iv) generate the reference values in the source to ensure reference values are correct.

I wrote the code generation using Ruby Rails backed by a MySQL database though the data model is read from the local PostgreSQL database.

I can update the database and then it regenerates the

com.patientis.model.*DataModel.java and
com.patientis.model.common.ModelReference and
com.patientis.model.reference.*Reference.java. It only replaces the file if there are differences.

So the instructions have several technologies but the net effect is the ability to change the datamodel relatively quickly.

< | >

Related Links

Articles on Medical Open Source Development

Also by Greg Caulton

Contact author

The Fine Print: The following comments are owned by whoever posted them.
( Reply )

Re: PatientOS LinuxMedNews Update
by Tim Cook on Thursday November 15, 2007 @ 09:27 AM

>>So the instructions have several technologies but the net effect is the ability to change the datamodel relatively quickly.
<<

This sounds really cool from a technology perspective but what measures are in place to assure the future usability of data between instances or even between versions?

[ Reply to this ]

Re: PatientOS LinuxMedNews Update
by Greg Caulton on Thursday November 15, 2007 @ 09:58 AM

Good question, an upgrade process are essential to the system. PatientOS process consists of handling:
a) new PatientOS source code
b) new libraries
c) new database reference content
d) new schema

I developed (a while ago for different projects) a couple of different methodologies for upgrading the content and schema. As eluded above I have the schema captured, in a general form.

With each upgrade I generate the SQL to upgrade the schema, and the SQL to add or update the content by comparing either
a) The current and previous release
b) THe current and the target system release The former is easier but can create more issues if the schema has unexpectedly changed (perhaps for a patch). The latter is slower but can guarantee that the target system has the correct schema and correct content

One of the reasons I like PostgreSQL and Oracle is this can be automated fairly easily. In the past I have hit bumps in the road with other databases MySQL, SQLServer which may not have the breadth of commands to easily update the schema.

So the tools are there for an upgrade, I plan to add the overhead of distributing upgrade code/documentation once I roll out a system that is adopted for validation in preparation for real use

[ Reply to this ]

The Fine Print: The following comments are owned by whoever posted them.
( Reply )

This site is a member of WebRing.
To browse visit Here.

Advertisement: CCHIT certified EMR and Medical Practice Management Software from Medical Software Associates makes patient management easy. Free practice management and medical billing software demo available.