Template for Refunds

Can someone tell me what the name for the Refund template is? I can't find it and if staff try to print one I get a collection error.

Cheers,
Matt C

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Re: Template for Refunds

Hi Matt,

No standard template in openvpms distribution for refunds. Hence collection error which is shorthand for " I don't have a template for this archetype". Easily created though using payment templates as a .. "template" .. :-)

Cheers Tony

On 8/09/09 6:12 PM, "Mpcosta@Boroniavet. Au" :

> Can someone tell me what the name for the Refund template is? I can't find it > and if staff try to print one I get a collection error. > > Cheers, > Matt C > _______________________________________________ > OpenVPMS User Mailing List > users@lists.openvpms.org > To unsubscribe or change your subscription visit: > http://lists.openvpms.org/listinfo/users > Posts from this mailing list can be viewed online and replied to in the > OpenVPMS User's forum- http://tinyurl.com/openvfu

_______________________________________________ OpenVPMS User Mailing List users@lists.openvpms.org To unsubscribe or change your subscription visit: http://lists.openvpms.org/listinfo/users Posts from this mailing list can be viewed online and replied to in the OpenVPMS User's forum- http://tinyurl.com/openvfu

Refund template

Hey everyone,

Thanks Tony,

I did the following:

1. Copied my Payment or Receipt document (jrxml) and changed "Receipt" in docuemnt to say "Refund".

2. Created a new template in OpenVPMS of Type = "Customer Refund"

3. Now it works

Cheers,

Matt C

Pathology systems

Hi was wondering if the proposed imaging integration using HL7 or similar could also be used to pull in reports from Pathology machines or outside laboratories.

I know that, for instance, Gribbles use a HL7 based internet reporting system and presume the other Labs are capable of the same. In house lab equipment pushes out ASCII reports which I imagine can be mined for data fields, though that is more laborious.

What are thoughts on this?

Steve

_______________________________________________ OpenVPMS User Mailing List users@lists.openvpms.org To unsubscribe or change your subscription visit: http://lists.openvpms.org/listinfo/users Posts from this mailing list can be viewed online and replied to in the OpenVPMS User's forum- http://tinyurl.com/openvfu

Re: Pathology systems

Hi Steve,

Definitely looking into this approach for the next phase of the investigations management system. I am all for using proven standards rather then constantly reinventing the wheel.

Some of the things we will need to do to achieve this is develop a tool to render the hl7 content into a better format so easier to read as a whole report. I.e. Store as raw HL7 so we can get access to the atomic data but allow users to display the hl7 in a format suitable for clinicians to read. As most practices are used to reading a nicely formatted (red out of ranges, graphs, scatter plots etc) view of the results I think this is important.

Although most Pathology companies send both the atomic results and a text representation of the report in the HL7 the text representation has little or no formatting. From reading the HL7 2.3 standard this doesn't have to be the case as HL7 2.3 supports EC (Encapsulated Data) so html, pdf , even image data can be sent in a hl7 message. Unfortunately not many labs actually utilise this feature.

The other pity is many companies have already developed the parser to do this but they are all proprietary or imbedded in download applications or the like. This means each software provider has to develop this hl7 parser which is non trivial. Its' a pity one of the companies doesn't put this out into the public space to promote hl7 use in our industry ... we can only hope :-)

While we are at it I should have a gripe about the internal lab Equipment manufacturers as well. It would seem they have a similar approach as they make every software supplier build and maintain sometimes complex interface applications in order to get the results from their equipment into a form suitable for upload into the Practice Management System. I have had the displeasure of looking at the interface specifications of these units and trying to decipher how to get even the most simple of data consistently and reliably. The interfaces are often poorly designed and implemented. Some of these purposely make it difficult so to limit interfacing to a fixed set of software systems. Even newer models with networkable PC's still limit or make it difficult to get access to the raw as well as formatted data.

If Lab equipment suppliers where forced to provide HL7 interfaces like X-ray providers are becoming forced to provide DICOM interfaces we would be a lot better off.

Anyway look for HL7 support in many parts of OpenVPMS in the near future.

Cheers Tony

_______________________________________________ OpenVPMS User Mailing List users@lists.openvpms.org To unsubscribe or change your subscription visit: http://lists.openvpms.org/listinfo/users Posts from this mailing list can be viewed online and replied to in the OpenVPMS User's forum- http://tinyurl.com/openvfu

Re: Pathology systems

Hi Tony, I have been rattling on at a few of the bigger vendors of vet path gear. Had a pretty quick response from Abaxis and they have no HL7 now or any plan to do so. They export exclusively as ASCII. Though they have a plan to modify one of their suite (the Biochem machine) to export xml. To date IDDEX have yet to reply.

I am at melb Uni ICU and getting pretty keen to move us away from endlessly writing results on charts. Our radiometer blood gas supports HL7 2.5. We also deploy abaxis biochem and Haematology and an IDDEX vetscan for some limited tests..

Abaxis have offered to supply details of how to access their interface, if you are interested I will forward on the contact details.

all the best steve

On Sep 10, 2009, at 5:27 PM, Tony De Keizer wrote:

> Hi Steve, > > Definitely looking into this approach for the next phase of the > investigations management system. I am all for using proven standards > rather then constantly reinventing the wheel. > > Some of the things we will need to do to achieve this is develop a > tool to > render the hl7 content into a better format so easier to read as a > whole > report. I.e. Store as raw HL7 so we can get access to the atomic > data but > allow users to display the hl7 in a format suitable for clinicians > to read. > As most practices are used to reading a nicely formatted (red out of > ranges, > graphs, scatter plots etc) view of the results I think this is > important. > > Although most Pathology companies send both the atomic results and a > text > representation of the report in the HL7 the text representation has > little > or no formatting. From reading the HL7 2.3 standard this doesn't > have to be > the case as HL7 2.3 supports EC (Encapsulated Data) so html, pdf , > even > image data can be sent in a hl7 message. Unfortunately not many labs > actually utilise this feature. > > The other pity is many companies have already developed the parser > to do > this but they are all proprietary or imbedded in download > applications or > the like. This means each software provider has to develop this hl7 > parser > which is non trivial. Its' a pity one of the companies doesn't put > this out > into the public space to promote hl7 use in our industry ... we can > only > hope :-) > > While we are at it I should have a gripe about the internal lab > Equipment > manufacturers as well. It would seem they have a similar approach > as they > make every software supplier build and maintain sometimes complex > interface > applications in order to get the results from their equipment into a > form > suitable for upload into the Practice Management System. I have had > the > displeasure of looking at the interface specifications of these > units and > trying to decipher how to get even the most simple of data > consistently and > reliably. The interfaces are often poorly designed and > implemented. Some > of these purposely make it difficult so to limit interfacing to a > fixed set > of software systems. Even newer models with networkable PC's still > limit or > make it difficult to get access to the raw as well as formatted data. > > If Lab equipment suppliers where forced to provide HL7 interfaces > like X-ray > providers are becoming forced to provide DICOM interfaces we would > be a lot > better off. > > Anyway look for HL7 support in many parts of OpenVPMS in the near > future. > > Cheers > Tony > > > _______________________________________________ > OpenVPMS User Mailing List > users@lists.openvpms.org > To unsubscribe or change your subscription visit: > http://lists.openvpms.org/listinfo/users > Posts from this mailing list can be viewed online and replied to in > the OpenVPMS User's forum- http://tinyurl.com/openvfu

_______________________________________________ OpenVPMS User Mailing List users@lists.openvpms.org To unsubscribe or change your subscription visit: http://lists.openvpms.org/listinfo/users Posts from this mailing list can be viewed online and replied to in the OpenVPMS User's forum- http://tinyurl.com/openvfu

Re: Pathology systems

Hey Guys, We have written parsing for ascii type data (inhouse and external labs)and I do some atomic manipulations (or for non techno types break the results into their parts) on in house labs. This mechanism is external to OpenVPMS but cos OpenVPMS is such a joy to work with, once the parsing is done, adding it into histories as pretty attachments is pretty easy.

However this is exactly what Tony describes as constantly reinventing the wheel. My solution is completely at the mercy of providers changing their formats, reporting styles etc etc etc.

It would be bloody great to come up with a industry standard HL7 parser utility that sits between the provider and consumer. It would serve EVERYONE! Lab providers, software vendors, oh, I almost forgot, and us the end consumer... It may fall to the OpenVPMS community to be the leaders in this regard and if we can find the resources, hope our industry follows us.

Matt Costa

On Thu, 10 Sep 2009 18:28:31 +1000, steve isaacs

wrote:

> Hi Tony, I have been rattling on at a few of the bigger vendors of vet > path gear. > Had a pretty quick response from Abaxis and they have no HL7 now or > any plan to do so. They export exclusively as ASCII. Though they have > a plan to modify one of their suite (the Biochem machine) to export xml. > To date IDDEX have yet to reply. > > I am at melb Uni ICU and getting pretty keen to move us away from > endlessly writing results on charts. Our radiometer blood gas supports > HL7 2.5. We also deploy abaxis biochem and Haematology and an IDDEX > vetscan for some limited tests.. > > Abaxis have offered to supply details of how to access their > interface, if you are interested I will forward on the contact details. > > all the best > steve > > On Sep 10, 2009, at 5:27 PM, Tony De Keizer wrote: > >> Hi Steve, >> >> Definitely looking into this approach for the next phase of the >> investigations management system. I am all for using proven standards >> rather then constantly reinventing the wheel. >> >> Some of the things we will need to do to achieve this is develop a >> tool to >> render the hl7 content into a better format so easier to read as a >> whole >> report. I.e. Store as raw HL7 so we can get access to the atomic >> data but >> allow users to display the hl7 in a format suitable for clinicians >> to read. >> As most practices are used to reading a nicely formatted (red out of >> ranges, >> graphs, scatter plots etc) view of the results I think this is >> important. >> >> Although most Pathology companies send both the atomic results and a >> text >> representation of the report in the HL7 the text representation has >> little >> or no formatting. From reading the HL7 2.3 standard this doesn't >> have to be >> the case as HL7 2.3 supports EC (Encapsulated Data) so html, pdf , >> even >> image data can be sent in a hl7 message. Unfortunately not many labs >> actually utilise this feature. >> >> The other pity is many companies have already developed the parser >> to do >> this but they are all proprietary or imbedded in download >> applications or >> the like. This means each software provider has to develop this hl7 >> parser >> which is non trivial. Its' a pity one of the companies doesn't put >> this out >> into the public space to promote hl7 use in our industry ... we can >> only >> hope :-) >> >> While we are at it I should have a gripe about the internal lab >> Equipment >> manufacturers as well. It would seem they have a similar approach >> as they >> make every software supplier build and maintain sometimes complex >> interface >> applications in order to get the results from their equipment into a >> form >> suitable for upload into the Practice Management System. I have had >> the >> displeasure of looking at the interface specifications of these >> units and >> trying to decipher how to get even the most simple of data >> consistently and >> reliably. The interfaces are often poorly designed and >> implemented. Some >> of these purposely make it difficult so to limit interfacing to a >> fixed set >> of software systems. Even newer models with networkable PC's still >> limit or >> make it difficult to get access to the raw as well as formatted data. >> >> If Lab equipment suppliers where forced to provide HL7 interfaces >> like X-ray >> providers are becoming forced to provide DICOM interfaces we would >> be a lot >> better off. >> >> Anyway look for HL7 support in many parts of OpenVPMS in the near >> future. >> >> Cheers >> Tony >> >> >> _______________________________________________ >> OpenVPMS User Mailing List >> users@lists.openvpms.org >> To unsubscribe or change your subscription visit: >> http://lists.openvpms.org/listinfo/users >> Posts from this mailing list can be viewed online and replied to in >> the OpenVPMS User's forum- http://tinyurl.com/openvfu > > _______________________________________________ > OpenVPMS User Mailing List > users@lists.openvpms.org > To unsubscribe or change your subscription visit: > http://lists.openvpms.org/listinfo/users > Posts from this mailing list can be viewed online and replied to in the > OpenVPMS User's forum- http://tinyurl.com/openvfu >

_______________________________________________ OpenVPMS User Mailing List users@lists.openvpms.org To unsubscribe or change your subscription visit: http://lists.openvpms.org/listinfo/users Posts from this mailing list can be viewed online and replied to in the OpenVPMS User's forum- http://tinyurl.com/openvfu

Lobbying the companies

Hi all,

 

I think that the time has come for us to start heavying the companies of the internal pathology machines to provide an interface so that we can easily transmit test results. We have all invested massive amounts of money into these machines over the years (we have 2 idexx machines and one vetscan) and we really need to have an easy way of getting this info off them and into our patient records.

Now I think that someone should draft a technical type email (as I don't have the lingo to be able to do it) and then we send a copy from everybody's email addresses to the companies and use weight of numbers.

 

For Idexx  the contact is Carl Eden carl-eden[at]idexx[dot]com

For Vetscan the contact is Frank Elwin felwin[at]remsystems.com[dot]au

 

Are there any other machines we whould do this for as well? There is power in numbers and persistence.

 

What does everyone think?

Amanda

 

 

Amanda Hulands-Nave Bellarine Veterinary Practice

Re: Lobbying the companies

ASASP machines interface with Open VPMS so is worth having a look at their solution. They are also a lot cheaper to buy and run (about 1/2 the idexx). A PAP is about $19 in consumables and the full profile about $28. The machines cost about $10/day if you spend around $1500/month with them. Chris On Wed, Apr 7, 2010 at 2:41 PM, <mnave@bigpond.net.au> wrote:
Hi all,   I think that the time has come for us to start heavying the companies of the internal pathology machines to provide an interface so that we can easily transmit test results. We have all invested massive amounts of money into these machines over the years (we have 2 idexx machines and one vetscan) and we really need to have an easy way of getting this info off them and into our patient records. Now I think that someone should draft a technical type email (as I don't have the lingo to be able to do it) and then we send a copy from everybody's email addresses to the companies and use weight of numbers.

  For Idexx  the contact is Carl Eden carl-eden@idexx.com For Vetscan the contact is Frank Elwin felwin@remsystems.com.au   Are there any other machines we whould do this for as well? There is power in numbers and persistence.   What does everyone think? Amanda     Amanda Hulands-Nave Bellarine Veterinary Practice _______________________________________________ OpenVPMS User Mailing List users@lists.openvpms.org To unsubscribe or change your subscription visit: //lists.openvpms.org/listinfo/users" target="_blank">http://lists.openvpms.org/listinfo/users Posts from this mailing list can be viewed online and replied to in the OpenVPMS User's forum- //tinyurl.com/openvfu" target="_blank">http://tinyurl.com/openvfu

Re: Lobbying the companies

Hi, I believe this is a project that has had some work done. All the vet machines are non standards compliant and frankly very old technology. That said they can export files in formats that Open VPMS can interpret and import. More modern machines support standards that allow the machines to pull data from the patient record into the analyser and then link the results back. Its cool and saves a lot of double entry, but its a dream for us at the present time. The ASAP machine looks pretty good. The operating costs are certainly very attractive. That needs to be weighed up against some other operating "features" that may prove annoying or even costly. Look closely at parameter ranges, smart card limiting technologies and sample requirements. Its not a bad machine by a long shot and its good competition. ( and isn't that what Open VPMS is about?) On 07/04/2010, at 3:12 PM, Chris Barton wrote:

ASASP machines interface with Open VPMS so is worth having a look at their solution. They are also a lot cheaper to buy and run (about 1/2 the idexx). A PAP is about $19 in consumables and the full profile about $28. The machines cost about $10/day if you spend around $1500/month with them. Chris On Wed, Apr 7, 2010 at 2:41 PM, <mnave@bigpond.net.au> wrote:
Hi all,   I think that the time has come for us to start heavying the companies of the internal pathology machines to provide an interface so that we can easily transmit test results. We have all invested massive amounts of money into these machines over the years (we have 2 idexx machines and one vetscan) and we really need to have an easy way of getting this info off them and into our patient records. Now I think that someone should draft a technical type email (as I don't have the lingo to be able to do it) and then we send a copy from everybody's email addresses to the companies and use weight of numbers.

  For Idexx  the contact is Carl Eden carl-eden@idexx.com For Vetscan the contact is Frank Elwin felwin@remsystems.com.au   Are there any other machines we whould do this for as well? There is power in numbers and persistence.   What does everyone think? Amanda     Amanda Hulands-Nave Bellarine Veterinary Practice _______________________________________________ OpenVPMS User Mailing List users@lists.openvpms.org To unsubscribe or change your subscription visit: //lists.openvpms.org/listinfo/users" target="_blank">http://lists.openvpms.org/listinfo/users Posts from this mailing list can be viewed online and replied to in the OpenVPMS User's forum- //tinyurl.com/openvfu" target="_blank">http://tinyurl.com/openvfu

_______________________________________________OpenVPMS User Mailing Listusers@lists.openvpms.orgTo unsubscribe or change your subscription visit:http://lists.openvpms.org/listinfo/usersPosts from this mailing list can be viewed online and replied to in the OpenVPMS User's forum- http://tinyurl.com/openvfu

Syndicate content