Re: [Op-torch-devel] Thoughts on TORCH and RHIO integration

[Michael A R. M. <mro...@we...>]

On Jan 16, 2007, at 11:40 PM, David Willis wrote:

> Michael:
>
> I was thinking...as I always tend to be about the synergy between  
> our projects. One of the features that i want the RHIO to provide  
> is clinical dashboards--preventive health, diabetes, cardiovascular  
> disease, asthma, depression, etc. These with be patient and disease- 
> specific summaries of patient care--very useful. Since much of that  
> information is sources in the RHIO, would it be possible to develop  
> these clinical dashboards once and utilize the programming in both  
> systems. In other words, when you go to click on a dashboard in  
> TORCH you pull up a RHIO-based programming feature. Save time and  
> work, and create a marketing tool for the client who uses the RHIO- 
> based dashboard but wants more, i.e TORCH-which is an office-base  
> solution that simply extends the physicians capabilities.
>
>  I realize that there are separate databases, but the RHIO is still  
> in flux and the basis of the programming languages are compatible.  
> I realize you probably cannot answer the question without the  
> details, but consider the possibility for the future.
>
> David
>

Hey David,

this is an interesting Idea, I think that this fits most closely into  
the idea of the Problem List.  We have talked before how the Problem  
lists aren't usually done correctly, so here is what I have been  
thinking of.

	The Problem List needs to be DX based: this only makes sense
	Should give you a much better view of the problem, and show you  
associated thinks
		For example: when DM is the problem:
			this should show you their last visit for this problem
			List of Encounters that list this encounter as a diagnosis.
			The medications that are currently linked to this problem
			And the last labs that are linked to this problem (could also  
throw in Radiology)

	These are things that we can create a base list of things included  
with _every_ problem, which means that it is generalizable, and if we  
access the RHIO for this information, we get it from all providers  
who input to the RHIO.

I know exactly how I would program this through Zope and the ZODB,  
how the layout of your DB is done is of course going to be different,  
but still easily doable.

Thoughts?

Michael