From: Gour <go...@go...> - 2010-07-11 07:15:27
|
On Sat, 10 Jul 2010 12:04:34 +1000 >>>>>> "Richard" == Richard Jones <ric...@op...> wrote: Richard> > However, I'm not sure if we create a separate class Richard> > where/when we would enter data for it? Richard> Richard> Here's an even easier idea: just have a single issue per Richard> patient. That way the entire patient history is in one place Richard> and the amount of customisation is really easy - you're just Richard> adding new fields to the issue class. Well, that owuld be too simplicistic in the sense that we *do* need to have separate issues per patient. In EMR parlance, there are different 'episodes' in patient's records which should be recorded separately. So, we'll continue exploring the idea of having special 'patient' class believing we need to create it, add it to the sidebar and then provide appropriate 'views' & templates. Otoh, it seems it is possible to explore the design in cli using ropundup's API even before we finish with all the customizations, right? Richard> You can lock down the interface to require a login for all Richard> accesses (turn off web access and registration for anonymous Richard> users). You can then probably (depending on your hosting) set Richard> it up so you work over HTTPS. Cool. That seems secure-enough. Sincerely, Gour -- Gour | Hlapicina, Croatia | GPG key: F96FF5F6 ---------------------------------------------------------------- |