[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnumed-devel] re: constraints in gmClinicalRecord (FYI) and gmEMRBr
From: |
Karsten Hilbert |
Subject: |
Re: [Gnumed-devel] re: constraints in gmClinicalRecord (FYI) and gmEMRBrowser, gmPatientExporter |
Date: |
Fri, 22 Oct 2004 08:51:28 +0200 |
User-agent: |
Mutt/1.3.22.1i |
> Fixing at it now, what do you think about this approach?:
> ~ -According to cClinicalRecord:
> ~ def get_health_issues(self, id_list = None):
> ~ def get_episodes(self, id_list=None, issues = None):
> ~ get_encounters(self, since=None, until=None, id_list=None,
> episodes=None, issues=None)
>
> ~ -Filter hierarchically from top to botton, applying available
> criterias for each element:
> ~ healh_issue -> episodes -> encounters
> ~ ...and at the lowest level and last step, obtain items that
> belong to displayed encounter.
>
> ~ In the example above, only encounters in that date range would be
> shown. And, always, only items for resulting filtered encounters will
> be finally displayed.
That sounds OK to me.
Karsten
--
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346