@Cédric: Yeah, that restriction on SQLite is annoying. If it were a static value to update, then I think a subquery could work. It's not a static update value though, so I don't actually know how to do it cleanly. However, from what I gather, every Health user should be running postgresql (!). So... maybe that's ok. =-) I updated it with your table suggestion. Thanks!

@Luis: Please do! I know I must've missed and/or broken something. Hehe.

> a = Table('gnuhealth.patient.ecg')

is not correct. You should write:

> ECG = pool.get('gnuhealth.patient.ecg')
> a = ECG.__table__()

SQLite doesn't support the UPDATE/FROM so your query will fail on it.

PS: it will be easier if we were using a codereview tool.

You should not write raw SQL queries in _register_
To add column, you shoud use the TableHandler.add_raw_column.
For update query, you should write a python-sql query.
To drop constraint, you should use Table.Handler.drop_constraint.

Otherwise the code will not work independently of the database backend.

The electrocardiogram class in currently on the ICU module.

Although is the right place to be, EKGs are also taken in an outpatient basis and for checkups.

We should include the EKG in the core.