On Thu, 2005-07-21 at 16:25 -0500, [EMAIL PROTECTED] wrote:
> > 
> > On Thu, 2005-07-21 at 16:31 -0400, Joseph Dal Molin wrote:
> > > ...is it correct to infer from this and your earlier post that you have 
> > > rewritten CPRS?
> > > 
> > > J.
> > 
> > Yes, it would be correct to infer that we have a crossplatform client
> > that provides the same feature-set as CPRS.
> > 
> > --Todd
> 
> Todd,
> I certainly don't want to imply distrust for your statement,
> however, I'm sure most of the people in this mailing list
> will ask these questions themselves, so I would like to
> verbalize what many are thinking...
> 

Absolutely understandable.

I am an old-hat (well, kinda old ;)) to the opensource world, so I am
aware how cheap talk is. There is no offense taken here.

> Of course, the following questions can be answered by saying you
> actually read the CPRS code and re-implemented all of it, but in
> case you didn't actually do that, I'll bring out some of the capabilities
> of CPRS as line items.
> 
> Does that feature set include making orders for medication, lab, radiology,
> and generic free text orders ?
> 

Yes.

> Does that feature set include progress notes, templated as well as free text?
> 

Yes.

> Does that feature set include graphing vital signs as well as their data 
> entry?
> 

Yes.

> Does that feature set include reporting on lab results and demographic
> information about the patients?
> 

Yes, If I understand the question correctly. I assume you mean the
functionality in the Reports tab on CPRS.

> Does it include reporting on a coversheet the active problems, allergies,
> risks and other postings, clinical reminders, active medications, recent lab
> results, vital signs and appointments for the currently chosen patient?
> 

Yes.

> Does it include reminders for physicians about signing unsigned orders,
> periodic occurences such as vaccinations, diabetic foot exams, and other
> recurring care episodes?
> 

Yes.

> Does it include patient problems by name, with associated ICD-9 codes?

Yes.

> Does it record patient care encounters with date, time, location, provider
> and diagnoses?

Yes.

> Does it associate progress notes with those patient care encounters?
> 

Yes.

> Does it allow recording of vaccinations, and other recurring care episodes?
> 

Yes.

> Does it notify the doctor when drug interactions occur with allergies,
> foods, or other prescribed drugs?
> 

Yes.

> Does it do most or all of these through definitions on the server side
> of a VistA system?
> 

Yes. Exactly the same as CPRS.

> Well, I'm tired of typing and this should provide an initial checklist 
> that you can answer to tell us more about your system....
> 
> I would assume you are doing this with some kind of http connection which
> is impressive in and of itself. As Jim Self mentioned, the HTTP RPC Broker
> is something that has been on our "to be done" plate for a while.
> 
> David
> 


Now, to make sure there is no misunderstanding, we are in the final
stages of our initial implementation. The goal of our initial
implementation is an application that operates exactly as CPRS would
(well, excluding the minor bugs here and there ;)) before we start
implementing and integrating new functionality.

Some of these pieces are still undergoing finishing touches, but the
functionality is a) all planned to be completed and b) all very close to
completion. But everything listed above is either 100% functional or 99%
functional.

For example, we have finished reminder dialog support just recently.

The transition from VistA's binary RPC broker to the SOAP broker has not
been difficult, absolutely the difficulty faced so far is implementing
the rest of CPRS. As you most likely know, the communication layer in
CPRS is relatively simplistic.

--Todd



-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members

Reply via email to