Is there an API to save non-VA/Home Meds to Vista?

[Sam Habiel]

I am working on an e-prescription application, and I need to be able
to import meds not originating in my system to Vista. Hope there is
one, but I know too well that the answer is probably no.

Sam

[kdt...@gmail.com]

I'm not aware of one.

Sam, do you know if the "home meds" are just names, or are they linked
to real drugs with real drug numbers and entries in the VA Product
file?

I don't have a newer CPRS, but can't the newer ones input non-va
drugs? If so, then can you look at what RPC is being called? And
then you could call that same code on the server side.


Kevin

[Sam Habiel]

Kevin,

Home meds are real drugs linked to a drug and a pharmacy orderable
item. I have just completed the mapping process between a first
databank number (which we get back from the service we use) to RxNorm
to VUID to local drug, so I can match incoming drugs against vista
drugs. I looked at the CPRS RPC calls (I was doing that for the last
hour or so); unfortunately, the code to save a Home med is buried so
so so deep inside OR that I gave up looking for now.

I tried directly adding home meds to the non-VA med multiple in the
pharmacy patient file (where it actually lives); but CPRS also expects
an entry in file 100 for it to behave properly.

Sam

> --
> http://groups.google.com/group/Hardhats
> To unsubscribe, send email to Hardhats-u...@googlegroups.com

[kdt...@gmail.com]

I wish I could help you better. The only thing that I could offer
would be TMG-CPRS that allows you to track back more than just the
past 10 RPC calls. I don't know if that would help or not.

Kevin

[Rich Vertigan, CPRS Developer (retired)]

Actually, it uses all of the same ordering functionality as all other
ordering, by way of a new order dialog in 101.41, [PSH OERR]. This
was added in CPRS v27, and wasn't there in v26.

> > > To unsubscribe, send email to Hardhats-u...@googlegroups.com- Hide quoted text -
>
> - Show quoted text -

[Sam Habiel]

Rich,

How/where does the order information get translated into the non-VA
multiple in the Pharmacy Patient file? That's the piece that's eluding
me.

Sam

[Rich Vertigan, CPRS Developer (retired)]

Sam, I'll be in over my head here shortly, having done very little
with any meds stuff in CPRS. But I would guess that the usual HL7-
like messaging that passes between OE/RR and the other packages would
be the mechanism. Take a look at NVA1^ORMBLDPS. This routine builds
the messages that pass all med orders to Pharmacy, and that tag does
some special stuff for non-VA meds, like create a "ZRN" segment.

Also, if you haven't already, take a look at page 206 of the CPRS GUI
User Guide, that gives an overview of the non-VA stuff. Not sure
that's deep enough, but there may be something there that rings a
bell.

> >> > > To unsubscribe, send email to Hardhats-unsubscr...@googlegroups.com- Hide quoted text -

[Sam Habiel]

HL7! You know, I grepped the code over and over and said to myself...
no this couldn't be it. I never knew that Vista used HL7 to
communicate within itself.

My next question: how is HL7 created by CPRS processed by the
ancillary packages? It is stuffed into a global that's monitored for
new entries; or is it sent over the wire and there is a listener
somewhere?

Sam

> To unsubscribe, send email to Hardhats-u...@googlegroups.com

[Sam Habiel]

Never mind. I found it. Both my initial guesses were wrong because
both require taskman to run; but ordering never needed taskman in my
experience. So it's called directly from the code.

ORMBLD calls ORMBLDPS for pharmacy. Then it calls the unwinder to run
the protocols. In file 101, the entry responsible for sending to the
pharmacy package is OR EVSEND PS, which calls PS RECEIVE OR, which
calls D EN^PSJHL4(.XQORMSG) then PSOHLNEW then PSONVNEW.

Pharmacy code gets the prize for being completely unreadable.

Sam

[Rich Vertigan, CPRS Developer (retired)]

I just posted a document to the Files area that contains the message
specifications and entry points for all of this internal messaging
that CPRS does. This document is kept up to date as needed by mutual
agreement between CPRS and the ancillary package developers, and this
is the version that was current as of Dec 2007 when I retired - it may
have changed since then. I'm a little surprised that this isn't more
publicly available somewhere, but it doesn't appear to be.

http://groups.google.com/group/hardhats/web/Oe3specv3.doc

[George Timson]

Yeeeow! What a gold mine! Thank you, thank you!!

--George Timson

On Nov 30, 6:28 am, "Rich Vertigan, CPRS Developer (retired)"

<vertiga...@gmail.com> wrote:
> I just posted a document to the Files area that contains the message
> specifications and entry points for all of this internal messaging
> that CPRS does.  This document is kept up to date as needed by mutual
> agreement between CPRS and the ancillary package developers, and this
> is the version that was current as of Dec 2007 when I retired - it may
> have changed since then.  I'm a little surprised that this isn't more
> publicly available somewhere, but it doesn't appear to be.

> .......

[Rich Vertigan, CPRS Developer (retired)]

I had a feeling *somebody* might like this..... :)

I've always wondered what it would take to substitute "real" HL7
messaging for the protocol file approach, and really make this thing
talk to the world.

> > .......- Hide quoted text -

[Sam Habiel]

I am just so amazed by the million answers the document provides. Thank you!!!!

Sam

> --
> http://groups.google.com/group/Hardhats
> To unsubscribe, send email to Hardhats-u...@googlegroups.com

[glilly]

This document is truly amazing....

Thank you Rich!

...(so much to learn...)

gpl

On Nov 30, 8:28 am, "Rich Vertigan, CPRS Developer (retired)"

[bayan....@ehs.com.jo]

Dears,

May I get the following document, is it publicly available any more ?

http://groups.google.com/group/hardhats/web/Oe3specv3.doc

Thanks, much appreciated

[Nancy Anthracite]

I uploaded what I think is a copy and maybe even an updated copy that I got by
a FOIA request. It should be here:
http://opensourcevista.net:8888/NancysVistAServer/CPRS_Windows_Messaging_Standards.doc


I will later upload one to here for those who are on corporate networks.

http://download.opensourcevista.net/downloads/CPRS_Windows_Messaging_Standards.doc
--
Nancy Anthracite

[bayan....@ehs.com.jo]

Many Thanks Nancy :)